An SEO site migration checklist is the single most reliable way to move a website — to a new domain, platform, or design — without losing the rankings and traffic you spent years building. In most failed migrations, the damage does not come from one big mistake but from a dozen small, skippable checks. This guide walks you through all 21 steps we use at Amezing Tech for client migrations, split into before, during, and after launch.

What Is an SEO Site Migration?

A site migration is any significant change to a website that can affect how search engines crawl, index, and rank it. That includes domain changes (oldbrand.com to newbrand.com), platform moves (WordPress to Shopify), HTTPS upgrades, URL structure changes, major redesigns, and consolidating several sites into one. Google treats each of these differently, but they all share one risk: if signals from old URLs are not transferred correctly, rankings drop — sometimes by 30–60% for months. Famous example: when TransferWise rebranded to wise.com, monthly organic visits reportedly fell from around 32 million to 13 million before recovering. A migration is not an SEO project bolted onto a dev project; it must be planned as one combined project from day one.

Pre-Migration: Steps 1–9 (Planning and Benchmarking)

1. Crawl your entire current site with Screaming Frog or Sitebulb and export every URL, title, meta description, canonical, and status code. This is your inventory.
2. Benchmark rankings and traffic. Export Search Console queries, top pages, and impressions, plus analytics data for at least 12 months. You cannot prove recovery without a baseline.
3. Identify your high-value URLs — pages that drive traffic, earn backlinks, or generate revenue. These get priority treatment and manual redirect checks.
4. Pull your backlink profile from Search Console, Ahrefs, or Semrush so every linked URL gets a redirect.
5. Build the URL mapping spreadsheet. One row per old URL, one column for its exact new destination. Never map everything to the homepage — Google treats mass homepage redirects as soft 404s.
6. Decide what to prune. Migrations are the best time to drop thin or duplicate pages, but record every deliberate removal.
7. Stage the new site behind noindex and password protection, and crawl the staging site to compare against your inventory.
8. Prepare 301 redirect rules — server-level (htaccess or nginx) where possible, not plugin-level chains.
9. Freeze content changes. Do not rewrite titles and content during the migration itself; change one variable at a time so you can diagnose issues later.

Launch Day: Steps 10–15

10. Launch Monday to Thursday, never on a Friday or before a sales peak, so your team is available if something breaks.
11. Remove noindex and staging blocks — the most common catastrophic mistake is shipping the staging robots.txt to production.
12. Deploy 301 redirects and immediately test your top 100 URLs by hand plus a full list crawl.
13. Update internal links to point directly at new URLs instead of bouncing through redirects.
14. Submit the new XML sitemap in Search Console — and keep the old sitemap live temporarily so Google recrawls old URLs and discovers the redirects faster.
15. Use the Change of Address tool in Search Console if the domain itself changed.

Post-Launch: Steps 16–21 (Monitoring and Recovery)

16. Crawl the live site the same day and fix 404s, redirect chains, and canonical errors.
17. Watch Search Console daily for two weeks: Coverage report, Crawl Stats, and the “Discovered – currently not indexed” bucket. We cover that report in detail in our guide to fixing Discovered – currently not indexed.
18. Check server logs to confirm Googlebot is reaching new URLs and getting 200s.
19. Compare rankings weekly against your benchmark for your high-value keyword set.
20. Reclaim top backlinks by asking key referring sites to update their links.
21. Keep old-domain redirects live for at least 12 months — ideally permanently. Do not delete the old site or let the old domain expire.

How Long Does Migration Recovery Take?

For a clean, same-domain migration with correct redirects, expect ranking turbulence for 2–6 weeks. Domain changes typically take 3–6 months to fully stabilize because Google must re-evaluate sitewide signals. If traffic is still down more than 20% after eight weeks, something is wrong — usually redirect gaps, lost internal links, or removed content that used to earn long-tail traffic. Timelines follow the same logic we explain in how long SEO takes to work.

The 5 Most Common Migration Mistakes We See

After auditing dozens of failed migrations, the same five mistakes appear again and again. First, the staging robots.txt goes live. The disallow-all file that protected staging ships to production, and the entire site silently drops out of the index over the following days. Add a launch-minute check for this, and a second check the next morning. Second, redirects map everything to the homepage. Google treats mass homepage redirects as soft 404s, which means every backlink pointing at old deep pages passes nothing. One-to-one mapping is non-negotiable for any URL with links, traffic, or revenue. Third, internal links keep pointing at old URLs. The site works because redirects catch the clicks, but every internal click now bounces through a redirect hop, wasting crawl budget and diluting signals — update the links themselves. Fourth, analytics and Search Console get forgotten. Teams launch, then realize a week later that the new domain was never verified and tracking codes never migrated, leaving a permanent hole in the data exactly when monitoring mattered most. Fifth, the migration and a content rewrite happen simultaneously. When rankings then drop, nobody can tell whether redirects, design, or new copy caused it. Change one variable at a time: migrate first, stabilize, then optimize. Every one of these mistakes is cheap to prevent and expensive to repair — which is exactly why the checklist above exists, and why the pre-launch crawl comparison in step 7 is the item we never allow clients to skip.

Key Takeaways

• Benchmark everything before you touch anything — recovery cannot be measured without a baseline.
• The URL mapping spreadsheet is the heart of the migration; one-to-one 301 redirects, never mass homepage redirects.
• Launch Monday–Thursday, verify robots.txt and noindex removal within minutes of going live.
• Monitor Search Console and server logs daily for two weeks; keep redirects live for 12+ months.
• Change one variable at a time — do not redesign, rewrite, and re-platform simultaneously.

FAQs

Do 301 redirects lose PageRank?

Google has confirmed that 301 redirects pass full PageRank. Ranking drops after migration are almost always caused by redirect gaps, changed content, or lost internal links — not the redirects themselves.

When can I delete the old website?

Keep the old domain and its redirects live for at least 12 months, and ideally forever. Backlinks pointing at old URLs keep passing value only while redirects exist.

Should I migrate everything at once or in phases?

Large sites (100k+ URLs) often migrate section by section, which limits risk and makes issues easier to isolate. Small and mid-size sites are usually better served by a single, well-rehearsed cutover.

Will traffic drop even if I do everything right?

A temporary dip of 5–15% for a few weeks is normal while Google recrawls and reprocesses signals. A correct migration recovers; a sloppy one plateaus at a permanent loss.

Planning a migration? Amezing Tech is a Semrush Agency Partner and has handled domain, platform, and redesign migrations without traffic loss. Call +91-7709645632 for a free migration risk review.