# Removed Pages During Website Migration: What to Do

> Review removed pages during website migration. Decide what to preserve, combine, rebuild, or retire when no matching replacement exists on the new site.

Canonical: https://www.getdexseo.com/blog/website-migration-seo/removed-pages-website-migration/
Author: Dex SEO, Editorial team
Published: Oct 20, 2026 · Updated: Oct 20, 2026

## Key takeaways

- Do not remove a page based only on recent traffic.
- Check its reader task, useful content, links, and owner.
- Use a relevant replacement only when it meets the need.
- Record and test an approved removal rather than hiding it.

For removed pages during website migration, decide whether the useful answer should be kept, combined, rebuilt, or retired. Do not turn “no matching page yet” into a default redirect to the home page. Give each case an owner, a reason, and an expected public result.

This guide covers pages that lack a matching target on the new site. It does not rebuild the full URL inventory or teach server rules. Its job is to resolve the content choice before the technical team applies and tests it. Keep the [overall migration plan](https://www.getdexseo.com/blog/website-migration-seo/) as the project reference.

## Review removed pages during website migration before approving loss

Keep each old address in the [URL inventory](https://www.getdexseo.com/blog/website-migration-seo/website-migration-url-inventory/) until its owner has made and recorded the choice.

Ask whether the page was meant to disappear. A planned retirement and a failed import can look the same to a reader. Check the release notes, the old content, and the page owner’s intent before choosing a fix.

If the answer is unclear, mark the case pending. Do not treat the absence of a new page as approval to delete the old one. The team needs to know which cases were agreed and which were simply missed.

Keep the old URL and a trusted copy of the useful material. Note when it was saved and any limits. An archive can help recover context, but old claims, offers, and permissions still need a current review before reuse.

## Look beyond recent visits and direct sales

Review the page’s task and who uses it. A guide may support a service choice without taking an order on that same page. A warranty page may matter to existing customers even if it attracts few new visits.

Check known search, link, and business notes with its dates and filters. Ask support and sales whether they still send people to that address. Low recent traffic can be a clue; it is not a complete case for removal.

Also inspect the answer itself. Is it still useful, accurate, and relevant to what the business provides? Keeping outdated advice solely because the page once had visits is not a sound choice either.

## Choose among keeping, combining, rebuilding, and retiring

Once a relevant new page is agreed, update the [migration URL map](https://www.getdexseo.com/blog/website-migration-seo/url-mapping-for-website-migration/) with its exact target and reason.

Keep the page when its task still matters and the content can serve it well. A new design does not require a new URL for every useful answer. The technical team should confirm how the agreed public route will work.

Combine material when another page can genuinely meet the old need. Read the planned target and list what it must preserve. A broad mention of the topic is not the same as an answer to the old question.

Rebuild when the task remains useful but no current page serves it. Assign an editor, scope, and review date. Keep the gap visible until there is a real page to approve, rather than mapping it to a future URL that does not exist.

Retire when the owner confirms that keeping or replacing the answer is no longer useful. Record the reason. The choice should account for reader use and business context, not just a wish to make the new site smaller.

## Do not invent a match to avoid an error response

A page that opens successfully can still be the wrong answer. Sending a detailed guide to a generic service offer may leave the reader without the promised steps. Judge relevance before choosing a redirect.

Google advises against sending many old URLs to an unrelated target. It also describes using a 404 or 410 response when removed content has no matching page. Have the technical owner apply the agreed behavior and verify it.

A useful not-found page can help a reader continue through the site. Its appearance does not settle the response status or the choice to remove content. Keep the editorial choice and the technical result as separate checks.

## Record enough detail for a reviewable choice

Keep these page-level choices separate from the [site rollback choice](https://www.getdexseo.com/blog/website-migration-seo/website-migration-rollback-plan/). A missing article does not by itself settle whether the whole release should be reversed.

Use one row for each unresolved page. Include its old address, task, useful content, notes, planned action, reason, owner, and sign-off state. If a matching page is chosen, record the exact public target.

For a combined page, name the sections or files that must survive. For a retired page, record any places that still link to it and who will review those references. Avoid an approval that says only “SEO handled it.”

Set a review point for open cases. A pending page should not remain hidden in a spreadsheet while the rest of the site is marked complete. The release owner needs to know what remains uncertain.

## Example: a retired event package has no new page

Imagine a fictional catering business that no longer sells an old event package. Its page contains both outdated prices and a useful equipment checklist. The new service page does not include that checklist. No ranking outcome is assumed in this example.

The business owner confirms the old package should not be offered. The editor checks whether the checklist still helps current customers. They may move the useful checklist into a relevant guide while removing the outdated offer.

The old route still needs an explicit choice. The owner should not assume that saving one paragraph makes the new service page equivalent to the old package page. They review what a visitor following that old link would reasonably expect.

The team records the chosen action and its reason, then asks the developer to test the public result. This example shows a choice method, not a rule that every retired page should be merged or deleted.

## Handle accidental removals as a separate issue

Use the [CMS content comparison](https://www.getdexseo.com/blog/website-migration-seo/cms-migration-content-checklist/) to check a restored answer, assets, and useful actions against the trusted source.

If a useful page vanished by mistake, find the last trusted version and compare it with current needs. Confirm ownership of text and assets and review dated facts before republishing. Do not restore a stale copy without reading it.

Ask whether the existing address can be restored or whether an agreed new route is required. Keep that choice with the URL map. Then test the page, its useful files, and links that readers still use to reach it.

A drop in visits after the move does not prove removal was the only cause. Keep the access fault separate from later search analysis. Fix a confirmed missing answer without promising a deadline for traffic recovery.

## Verify the chosen outcome after release

Use the [route-testing method](https://www.getdexseo.com/blog/website-migration-seo/test-redirects-after-website-migration/) when a redirect is part of the agreed outcome. Check the result, not just a browser success message.

Open the old address and inspect the intended result. If content was preserved or combined, read it and check the promised files and next action. If the page was retired, confirm the approved response and review internal links that should change.

DEX Health can review the SEO quality of public matching page pages, including on the free plan. It supports that page review; it does not choose which business content to remove or guarantee how search traffic will respond.

Close the row when the owner-approved choice is applied and checked. Keep the reason known so a later editor does not mistake a planned removal for a transfer fault and reverse it without context.

## FAQ

### Should every removed page redirect to the home page?

No. Check for a relevant replacement. An unrelated destination can leave readers without the answer they expected.

### Does no recent traffic prove a page has no value?

No. Review business use, links, seasonality, and the limits of the data before deciding.

### Can we restore an accidentally removed page?

Review a trusted old copy and its current accuracy, rights, and purpose. Have the owner approve restoration and the public route.

## Sources

- [How to move a site](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) — Google Search Central