Site Migration Checklist SEO: The Complete Run-Sheet

Most migration advice tells you why migrations are risky. This one tells you exactly what to do, in what order, and why — backed by real traffic-loss and recovery-time data rather than generic best practices. Treat it as a literal run-sheet: three timed phases, checkable tasks, no fluff.

What's Actually at Stake in a Migration

Site migration traffic loss isn't a sign of failure — it's the norm. A poll covered by Search Engine Roundtable found 78.3% of SEOs expect at least some traffic loss after a migration, even when the work is done well. Google's own guidance on site moves with URL changes warns that rankings can fluctuate while new URLs get re-crawled, re-indexed, and re-evaluated — and that this takes time, not hours.

Bring that number into any stakeholder meeting where someone expects traffic to "stay flat." What separates a normal dip from a collapse is how fast it recovers and whether it stays contained instead of compounding. A seo migration checklist exists to keep the dip small, temporary, and explainable — not to prevent it entirely. For the strategic framework behind this tactical piece, see the companion SEO site migration checklist that protects your rankings.

Phase 1: Pre-Migration Checklist (Before You Build Anything)

Everything here happens before a single line of code moves to production. Skipping this phase is the single biggest predictor of a bad outcome, because you can't build an accurate redirect map if you never established what exists on the old site.

• Full crawl baseline of the old site. Capture status codes, titles, meta descriptions, canonical tags, and internal link counts. This becomes your source of truth for confirming nothing got lost.
• Prioritized page list by traffic and links. Pull top pages by organic sessions (analytics) and referring domains (backlink tool). These are launch-blocking pages; a redirect mistake on a zero-traffic page is a shrug, on your top 50 it's a crisis.
• Full 1:1 URL redirect map. Every old URL maps to exactly one new URL, ideally the closest topical match. Avoid mapping everything to the homepage — search engines and users both notice.
• Backlink export. Document which external domains link to which URLs so you can confirm link equity flows to the right destinations, and start a domain authority transfer conversation with anyone who'll update a link manually.
• Staging environment rules. Confirm staging is noindexed today, and write down exactly who removes that noindex tag and when. Forgetting this has taken entire new sites out of Google's index on launch day.

This is also the moment to run a pre-migration seo audit for existing technical debt — broken canonicals, orphaned pages, thin content — since a migration is the worst time to discover unrelated problems.

Phase 2: Cutover Day Checklist

Cutover day is unforgiving: most of these tasks are launch-blocking, meaning the site shouldn't go fully live until they're verified, not just "done."

• Implement 301 redirects for every URL on your map. Temporary (302) redirects don't pass signals the same way and have no place in a permanent migration.
• Verify no redirect chains or loops. Old URL → new URL should be one hop. An intermediate hop wastes crawl budget and dilutes signal strength; Googlebot follows chains reluctantly and abandons long ones.
• Update and submit the XML sitemap containing only new, live, canonical URLs — never old or redirected ones. If sitemap issues show up post-launch, this sitemap troubleshooting guide covers every error type.
• Update internal links site-wide so navigation, footers, and in-content links point to new URLs directly, not through a redirect.
• Confirm robots.txt isn't blocking Googlebot from the new site — a shockingly common staging-to-production carryover mistake.
• Re-verify Google Search Console properties for the new domain or subdomain immediately, since historical data doesn't transfer.
• Submit the Change of Address tool — only if the domain itself changed (not for a subdomain, subfolder restructure, or protocol change like HTTP to HTTPS on the same domain). Google's Change of Address documentation is explicit this tool is for full domain moves; 301 redirects do the heavy lifting either way.

Phase 3: Post-Migration Monitoring (First 30-90 Days)

Post migration seo monitoring is where most teams lose discipline, checking sporadically instead of on a set cadence — exactly when a fixable problem turns into a permanent loss.

• Daily crawl-error checks in week 1. Run a fresh crawl of the new site every day, watching for spiking 404s, redirect errors, or unexpected noindex tags.
• GSC coverage report checks, at minimum every 2-3 days for the first month. Watch "Not found (404)" and "Page with redirect" counts — both should trend toward zero as Google finishes re-crawling.
• Rank tracking against your pre-migration baseline, not last week. Track your priority page list from Phase 1 daily for two weeks, then weekly. This rank tracker comparison breaks down what matters for migration monitoring specifically.
• Log file review to confirm Googlebot is hitting new URLs and not repeatedly requesting old ones — a strong early signal of redirect map gaps. Log file analysis is the most reliable way to see this directly rather than inferring it from rankings alone.

On the recovery timeline: expect initial fluctuation for 1-4 weeks as re-crawling happens, with most well-executed migrations substantially recovering within 8-12 weeks. If key pages are still down more than 20-30% at the 90-day mark with no upward trend, that's a real problem requiring investigation, not more patience.

5 Mistakes That Turn a Migration Into a Traffic Collapse

These mistakes account for the overwhelming majority of severe, slow-to-recover traffic losses.

1. Redirect chains left unresolved. Each extra hop increases the chance Googlebot gives up before reaching the final destination, and signal strength degrades with every link in the chain.
2. Missing canonical tag updates. If canonical tags still point to old URLs (or staging), you're telling Google the new pages aren't authoritative. Canonical tag troubleshooting covers failure patterns basic audits routinely miss.
3. Orphaned high-traffic pages. A page can redirect correctly and still lose value if nothing on the new site links to it internally, starving it of crawl priority and authority flow.
4. Forgetting GSC re-verification. Waiting weeks to reconnect Search Console means the most useful diagnostic tool during the highest-risk window isn't collecting data.
5. Moving to a domain with toxic backlink history. A domain authority transfer only helps if the history is clean; migrating onto a previously penalized or spam-linked domain can suppress rankings independent of anything you did right.

If any of these show up in your post-launch audit, this technical SEO priority framework helps you triage what to fix first based on traffic impact.

Running This Checklist Without Losing Track

The checklist above is manageable in theory and hard in practice, because it requires running Screaming Frog for crawls, GSC for coverage and re-verification, a separate rank tracker for baseline comparisons, and a spreadsheet stitching it all together — with no single view telling you what's been checked versus what's still open.

That's the gap Rankevra closes. It runs the pre-migration crawl baseline automatically, builds and validates your redirect map so chains and loops get flagged before launch instead of after, and tracks rankings against your pre-migration baseline through the entire 30-90 day recovery window — all in one dashboard instead of five disconnected tools and a spreadsheet nobody trusts. Try Rankevra before your next migration and run this checklist as one automated workflow instead of a manual scramble.

Frequently Asked Questions

How much traffic should I expect to lose during a site migration?

Some loss is normal and expected — 78.3% of SEOs report anticipating traffic loss after a migration, according to a widely cited industry poll. The size of the dip matters less than its duration; a well-executed migration typically sees a temporary dip that begins recovering within a few weeks rather than compounding.

How long does it take for SEO rankings to recover after a migration?

Most well-executed migrations show meaningful recovery within 8-12 weeks, with initial fluctuation common in the first 1-4 weeks as Google re-crawls and re-indexes new URLs. If key pages remain down 20-30% or more with no upward trend by the 90-day mark, that indicates an unresolved technical issue rather than normal fluctuation.

Do I need to use Google's Change of Address tool for every migration?

No — the Change of Address tool is only for full domain changes, not for subfolder restructures, subdomain moves, or HTTP-to-HTTPS switches on the same domain. For those other migration types, properly implemented 301 redirects handle the signal transfer on their own.

What's the single most common cause of ranking loss after a migration?

Broken or chained 301 redirects are the most frequent cause, followed closely by canonical tags still pointing to old or staging URLs. Both errors tell search engines conflicting information about which URL is authoritative, delaying or preventing signal transfer to the new pages.

How long should I keep old-URL redirects live after a migration?

Keep 301 redirects live indefinitely, or at minimum for 12 months, since external links and bookmarks pointing to old URLs can persist for years. Removing redirects too early breaks any link equity and referral traffic still flowing through those old paths.

Can I migrate a site without any SEO traffic loss at all?

Realistically, no — even technically flawless migrations typically see some short-term fluctuation as search engines re-crawl and re-evaluate new URLs. The achievable goal isn't zero loss; it's a small, temporary dip followed by full recovery within roughly 8-12 weeks.