A site migration — a domain change, a full replatform, or even just a URL structure change — is one of the few moments where you can lose years of accumulated rankings in a matter of days, purely from sequencing mistakes. The technical work itself usually isn't hard; missing a step in the wrong order is what causes the damage. Here's the checklist I run for any migration, regardless of what platform it's moving to or from.
Before migration checklist
- A full crawl and URL inventory of the current site is exported (every indexed URL, not just the ones in the main nav).
- Current rankings, organic traffic, and backlink profile are benchmarked before anything changes, so post-migration comparisons have a real baseline.
- A 1:1 redirect map is built — old URL to new URL — for every single indexed page, not just the top 20.
- The new site is built and tested on a staging environment with a noindex tag or password protection, so it can't get partially indexed before launch.
During migration checklist
- Redirects are implemented as 301 (permanent), not 302 (temporary) — 302s tell search engines the move might not be permanent and can delay rankings transfer.
- URL structure is preserved wherever realistically possible — every unnecessary structure change is one more redirect that has to work perfectly.
- Canonical tags are updated to point to the new URLs, not left pointing at the old domain or old paths.
- Internal links across the site are updated to point directly to new URLs — links that route through a redirect chain still work, but they dilute link equity and slow crawling.
- A new XML sitemap is generated reflecting only the new URL structure, with no old or redirected URLs included.
- Robots.txt is reviewed on the new site to confirm it isn't accidentally blocking crawlers (a common default-staging-config mistake that ships to production).
Launch day checklist
- The new sitemap is submitted in Google Search Console immediately at launch, not days later.
- Indexing is requested manually for the top 10-20 highest-traffic pages rather than waiting for organic recrawl.
- Crawl Stats and the Coverage/Indexing report in GSC are checked daily for the first week, watching specifically for a spike in 404s or "discovered, not indexed."
- The old domain or hosting stays live with redirects intact — never let the old domain expire or the old server get decommissioned immediately after launch.
Post-migration checklist (first 30-90 days)
- Rankings are reviewed weekly, not daily — some fluctuation in the first 1-2 weeks is normal as search engines recrawl and reprocess the new URLs.
- Redirect chains and loops are checked for and flattened (A redirecting to B redirecting to C should become A redirecting directly to C).
- Core Web Vitals and mobile usability are re-verified on the new platform, since a replatform can quietly regress page speed even when the visual design looks identical.
- Orphaned pages — pages that exist but aren't linked from anywhere on the new site — are identified and either linked in or deliberately retired with a redirect.
| Common Mistake | Ranking Impact | Fix |
|---|---|---|
| Using 302 instead of 301 redirects | Link equity transfer delayed or incomplete | Convert all migration redirects to 301 |
| Incomplete redirect map (only top pages covered) | Long-tail pages 404, losing accumulated rankings and links | Redirect every indexed URL, verified against the pre-migration crawl |
| New sitemap not submitted at launch | Slower re-crawling and re-indexing of new URLs | Submit sitemap and request indexing on launch day, not after |
| Old domain taken down immediately | Redirect chain breaks, all authority lost at once | Keep the old domain/hosting live with redirects for at least 6-12 months |
Migrations are also when a full architecture change — like moving from a static site to a CMS — tends to surface, and that's a different scope of work than a simple redirect map: it usually means rebuilding IT infrastructure around the new platform, not just pointing old URLs at new ones. Either way, the sequencing above is what determines whether a migration is invisible to rankings or a multi-month recovery project.
FAQ
How do you migrate a website without losing SEO rankings?
Preserve rankings through a migration by building a complete 1:1 redirect map covering every indexed URL, using 301 (not 302) redirects, updating internal links and canonical tags to the new URLs, submitting a new sitemap on launch day, and keeping the old domain live with redirects for at least 6-12 months after launch.
- The redirect map needs to cover every indexed URL, not just top-traffic pages — missed long-tail pages lose their accumulated rankings.
- 301 redirects (permanent) transfer ranking signals correctly; 302 redirects (temporary) can delay or limit that transfer.
How long does it take for rankings to recover after a site migration?
A well-executed migration with complete 301 redirects typically shows rankings stabilize within 2-4 weeks as search engines recrawl and reprocess the new URLs, while a poorly sequenced migration — missing redirects, changed URL structures, or a sitemap submitted late — can take several months to recover, if it fully recovers at all.
- Some short-term ranking fluctuation in the first 1-2 weeks is normal even in a well-executed migration.
- The biggest single factor in recovery time is redirect map completeness, not the platform being migrated to.