Website migration SEO checklist: protect rankings, leads, and analytics
A practical pre-launch and post-launch checklist for changing domains, platforms, or URL structures without losing search visibility.
What makes a website migration risky?
A migration can change the URLs, templates, content, internal links, hosting, or tracking that search engines and customers rely on. The main risk is not the redesign itself. It is breaking the relationship between an established URL and the relevant page that replaces it.
Build the URL map before launch
Export the URLs that currently receive organic traffic, links, leads, and revenue. Assign each one a specific destination on the new site. Use a server-side permanent redirect when a genuine replacement exists, and return a real 404 or 410 when content has been removed without an equivalent.
- Include URLs from the current sitemap, analytics, Search Console, crawl data, and backlink records.
- Map each old URL directly to the closest relevant new URL.
- Avoid redirecting unrelated pages to the homepage.
- Remove redirect chains by pointing old URLs to the final destination.
- Keep the mapping as a testable launch artifact, not an informal spreadsheet that disappears.
Verify the new site as a search system
Before launch, crawl the staging build and confirm that intended public pages return 200, use self-referencing canonical URLs, contain crawlable internal links, and are included in the new XML sitemap. Remove temporary noindex rules from public pages, while keeping private dashboards, authentication, APIs, and duplicate filters out of search.
Protect measurement and conversion paths
Test analytics and conversion events before switching traffic. Forms, checkout, booking, consent controls, campaign parameters, and thank-you states should work on the new domain or platform. A migration that preserves rankings but loses attribution or enquiries is still a failed release.
Launch with evidence and a rollback threshold
Activate redirects, publish the new sitemap, and test representative old and new URLs immediately. Monitor Search Console, analytics, server errors, conversions, and important queries. Some search fluctuation is normal while systems recrawl changed URLs, but unexpected 404 growth, redirect loops, lost canonicals, or broken conversion events need prompt investigation.
What should the handover include?
The final migration record should include the URL map, redirect rules, crawl results, sitemap location, analytics verification, known exceptions, monitoring owner, and rollback criteria. This makes the move auditable and gives the team a clear response when an issue appears after launch.