A site migration — moving to a new domain, new platform, or new URL structure — is one of the highest-risk events in SEO. Done correctly, migrations cause minimal disruption and rankings recover within weeks. Done poorly, they can cause traffic drops that last months or permanently destroy rankings that took years to build. The difference is preparation.
Quick Answer: A site migration changes your domain name, CMS platform, URL structure, or protocol. To do it without losing rankings: create a complete redirect map before moving, implement 301 redirects from every old URL to its equivalent new URL, update Search Console and sitemaps immediately, monitor Search Console daily for the first month, and fix any missed redirects within days. A 10–20% temporary ranking dip is normal; a 50%+ dip signals a problem requiring immediate investigation.
What types of changes count as site migrations?
- Domain migration — moving from oldsite.com to newsite.com
- HTTP to HTTPS migration — the most common type, usually low-risk when done correctly
- URL structure change — changing /blog/post-name to /articles/post-name across your whole site
- Platform migration — moving from one CMS to another (WordPress to Shopify, for example)
- Subdomain to subdirectory — moving blog.yoursite.com to yoursite.com/blog
- Site consolidation or split — merging two domains into one, or splitting one into two
| Historical Audit Area | Healthy Domain Baseline | Toxic Warning Flag | Remediation Action |
|---|---|---|---|
| Content Niche Continuity | Consistent industry focus over time | Sudden shift to casino, pharma, or crypto | Disavow or purge toxic URL structures |
| Historical HTTP 301 Chains | Clean 1-to-1 page migrations | Mass redirection chains from PBNs | Break loop and route straight to final canonical |
| Historical Anchor Profile | Organic brand citations & editorial mentions | Foreign anchor text spam bursts | Submit disavow file in Search Console |
| Archive DNS History | Stable hosting and nameservers | Parked domain / repeated dropped auctions | Conduct fresh crawl and re-index audit |
What should you do before migrating?
Pre-migration preparation prevents most post-migration ranking problems:
- Crawl your current site — use the free SEOLinkScan Broken Link Checker to generate a complete URL list of your current site. This is your redirect source list.
- Export your Search Console data — download your current ranking positions, impressions, and top queries as a pre-migration benchmark
- Create a redirect map — for every current URL, identify the equivalent URL on the new site. This is the most time-consuming step but the most critical.
- Verify the new site crawl — ensure the new site works correctly before going live, has no noindex tags on important pages, and loads quickly
- Test on staging first — if possible, test the redirect map on a staging environment before pointing live traffic to the new site
What must you do immediately after migrating?
- Verify all 301 redirects are live — spot-check 20–30 URLs from your most important pages using your browser's developer tools network tab
- Update Search Console — add the new domain as a property and submit an updated sitemap. If it is a domain change, use Search Console's Change of Address tool.
- Update all internal links — links still pointing to old URLs create unnecessary redirect chains. Update them to point directly to new URLs.
- Verify HTTPS configuration — check with the free SEOLinkScan SSL Checker that HTTPS is working correctly on the new domain
- Test page speed on new platform — platform migrations often affect performance. Check with our speed tool.
How long does it take to recover rankings after a migration?
With correct redirects in place, most rankings begin recovering within 2–6 weeks as Google re-crawls and re-indexes your new URLs. A complete return to pre-migration levels typically takes 2–4 months for domain migrations. HTTP to HTTPS migrations with correct redirects typically see minimal disruption — often less than two weeks of minor fluctuation.
What causes post-migration ranking drops?
- Missing redirects — old URLs returning 404s instead of redirecting
- Redirect chains — old URL → intermediate URL → new URL loses equity at each hop
- Noindex tags on new URLs — accidentally blocking the new site from being indexed
- Canonical tags pointing to old domain — telling Google the old site is still the preferred version
- Missing or incorrect sitemap — Google is not being told which new URLs to prioritise crawling
Technical Diagnostic Checklist: Historical Domain Due Diligence
- Audit Wayback Archive Snapshots: Inspect historical captures on Wayback Extractor to verify clean continuous content ownership.
- Check Historical Redirects: Verify whether previous domain owners forwarded expired domains or spammed link equity through deceptive 301 redirects.
- Examine Historical Anchor Velocity: Look for sudden unnatural spikes in referring domains that may have triggered historical manual penalties.
- Verify DNS & Clean Indexation: Confirm that no leftover spam subdomains or staging environments remain cached in Google's index.
Strategic Action Plan: Mastering Historical Domain Due Diligence
- Site migrations are high-risk SEO events — preparation is the entire difference between smooth and catastrophic
- Create a complete URL-to-URL redirect map before migrating
- Implement 301 redirects for every old URL, update Search Console, fix internal links immediately
- Monitor Search Console daily for the first month — fix any missed redirects within 48 hours of discovering them
- A 10–20% temporary dip is normal; 50%+ drops require immediate investigation of redirect and indexing issues
Continue reading: How do you optimise for AI Overviews in Google Search?