# Website migration redirect checklist

Canonical: https://beyondphp.com/insights/website-migration-redirect-checklist/

Language: English

Reviewed: 2026-10-22

Insights / BeyondPHP

Every changed address needs a decision a visitor can understand.

The short answer

A redirect plan connects an old URL to an appropriate new destination when a page moves. It should distinguish a real replacement from a page deliberately retired without an equivalent, and it must be checked against actual responses after release.

Published 22 October 2026 · Reviewed 22 October 2026 · [BeyondPHP editorial review](https://beyondphp.com/editorial/)

## Create the map before the old site disappears

Start from an inventory of current URLs, including pages that do not appear in the main navigation. Record the planned destination and the reason for each change. Preserve query-dependent or document URLs where they matter to the business. Keep a copy of the old inventory so omissions can be investigated after launch.

## Choose destinations by meaning

A changed service page should lead to its relevant successor, rather than an unrelated homepage. Consolidated articles need an explanation of which useful material survives. Where no replacement exists, decide the retirement treatment explicitly. Avoid chains that pass through several intermediate destinations, and update internal navigation to point directly to the intended final page.

## Verify behaviour instead of just configuration

A saved redirect rule is not proof that visitors receive it. Check the public response, final URL and destination content for representative and high-priority paths. Review case, trailing-slash and media variations that exist in the source inventory. Revisit the map when monitoring identifies missing URLs, and preserve a record of corrections.

A practical next step

## What to prepare.

- **Source list** Store old URLs and their priority using available evidence.

- **Mapping decision** Assign a relevant destination or deliberate retirement status to each changed URL.

- **Response evidence** Check status, hop sequence and final content on the actual released host.

## Questions worth asking.

Can every missing URL go to one page?

That usually obscures intent. A relevant replacement is preferable where one exists.

Do redirects guarantee rankings?

No. They help communicate URL changes, while search engines decide how to process the resulting pages.

Are preview tests sufficient?

They can verify planned rules locally, but the final host and release behaviour still need authorised public checks.

## Sources & further reading.

Primary documentation for the factual background. Our project recommendations depend on your requirements.

[**Google Search: site moves with URL changes** Primary documentation for preparing redirects and monitoring a URL move.](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes)

Continue with the right context

## Useful next reads.

[Migration Website migration with SEO continuity planning Plan URL mapping, redirects, internal links and post-launch checks to reduce avoidable search disruption during a website migration.](https://beyondphp.com/migration/seo-preserving-migration/)

[Services Technical SEO Build a clearer technical foundation for search: crawlable content, deliberate canonicals, useful internal links and carefully planned website changes.](https://beyondphp.com/services/technical-seo/)

[Insights Business website launch checklist Review content, contact journeys, indexing settings, release recovery and post-launch checks before publishing a website.](https://beyondphp.com/insights/website-launch-checklist/)