Website migration

Build the Redirect Map Before You Move the Website

Plan a website migration with one-to-one redirects, preserved internal links, canonical checks, and post-launch monitoring.

SEO6 min readPublished Jul 11, 2026

Export the old URLs while the old site still works

A redirect map is much easier to build before launch. Export URLs from the current Sitemap, crawl data, analytics landing pages, Search Console, and any important campaign lists. No single source contains everything.

Add the planned destination beside each old URL. The best destination serves the same intent; sending every removed page to the homepage is convenient for the migration team but rarely helpful to the visitor.

Prefer one permanent hop

Old URL to new URL is the clean pattern. Chains such as old to temporary to new add latency and make future maintenance harder. Update internal links so visitors and crawlers go directly to the final address.

Test query strings, uppercase variants, trailing slashes, and the HTTP-to-HTTPS or host change. Migrations often fail at the edges rather than on the handful of URLs everyone checks manually.

Launch is the start of monitoring

After launch, crawl the old URL list and verify final status, destination, canonical, and indexability. Submit the new Sitemap and inspect high-value URLs in Search Console.

Keep the redirects long enough for old links and bookmarks to remain useful. Watch 404 logs and search performance, but avoid changing the map every time daily traffic moves; migrations need a stable period for recrawling.

Practical checklist

  • Combine old URLs from Sitemaps, analytics, links, and crawls.
  • Map each valuable old page to the closest relevant destination.
  • Avoid redirect chains and homepage catch-alls.
  • Update internal links, canonicals, and hreflang references.
  • Crawl the old URL list again after launch.

FAQ

Common questions

Should every old URL redirect to the homepage?

No. Redirect to the closest relevant replacement. If no meaningful replacement exists, a clear 404 or 410 can be more honest than an unrelated homepage redirect.

How long should migration redirects remain?

Keep them for at least as long as users, external links, and search engines may rely on the old URLs. For valuable URLs, maintaining them indefinitely is often sensible.

Should the old URLs remain in the Sitemap?

No. The new Sitemap should list final canonical URLs. Keep the old list separately for redirect testing.

Do I need a paid SEO platform to follow this process?

No. You can complete the checks with the page itself, browser tools, Google Search Console, and focused validators. Paid platforms can save time on larger sites, but they do not replace clear decisions.

Should I test the live URL as well as the source code?

Yes. Redirects, response headers, JavaScript rendering, and deployment settings can make the live response different from a local template or editor preview.

How soon should I check the result after making an SEO change?

Verify the implementation immediately, then allow time for crawling and indexing before judging search performance. The delay varies by site and URL.

Can Google choose a different result from the signal I provide?

Yes. Canonicals, titles, and other SEO annotations are interpreted alongside page content, redirects, internal links, and external signals.

Where should I record technical SEO changes?

Keep a dated change log with the affected URLs, old and new values, reason for the edit, and the checks performed after release.

Keep reading

More SEO articles