A website migration SEO checklist is the difference between a smooth relaunch and a months-long traffic collapse. Whether you are redesigning, replatforming, or moving to a new domain, every URL change tells Google your website is a different entity than the one it trusted yesterday. Get it right and rankings dip only briefly before recovering; miss the fundamentals and you can lose years of SEO equity.
This website migration SEO checklist covers five phases: pre-migration audit, redirect mapping, staging hygiene, launch-day protocol, and post-launch monitoring. It includes everything the top-ranking guides cover, plus the gaps they miss — JavaScript rendering pitfalls, AI-search citation continuity when URLs change, the exact Change of Address workflow, and a traffic-loss triage decision tree.
Why Websites Lose Rankings During a Migration
Most migration disasters trace back to three ordinary failures. First, URL inventory is incomplete — the redirect map covers the homepage but misses orphaned pages that still earn traffic and backlinks. Second, staging leftovers go live — a noindex tag or blocked robots.txt rule gets deployed to production. Third, signals get scrambled — canonicals point at old URLs, internal links point at 404s, or structured data breaks in the new templates. A good website migration SEO checklist exists to catch all three before they cost you.
Phase 1 — Pre-Migration Audit: Crawl, Inventory, and Benchmarks
Preparation decides the outcome: before any code changes, build a complete picture of what you are protecting. This groundwork is the foundation of any website migration SEO checklist.
Build a master URL inventory from multiple sources
Never rely on a single crawl. This website migration SEO checklist requires at least four sources — pull your full URL list from all of them and merge the results:
- Your own crawl (Screaming Frog, Sitebulb) of the live site — captures every page your navigation reaches.
- Google Search Console’s Pages report — surfaces indexed URLs your crawler cannot see, including orphaned pages.
- Analytics landing-page data for the last 12 months — catches URLs that still receive organic traffic.
- Backlink reports (Ahrefs, Majestic, or GSC’s Links report) — identifies pages with external link equity that must be preserved.
Tag every URL by business value
For each URL in the inventory, record traffic value (12 months of organic sessions), ranking value (page-one positions for commercial terms), backlink value (referring domains), and conversion value (leads, sales, sign-ups). A blog post with modest traffic but twenty quality backlinks deserves the same protection as your top landing page. This value map is the first item on any serious website migration SEO checklist.
Snapshot your baselines
Record a “before” picture: export priority keyword rankings, screenshot Search Console coverage data, record Core Web Vitals scores, and document every canonical tag, schema type, and hreflang rule currently live. Agree on a rollback plan now — who can pause the launch, how DNS reverts, and who notifies stakeholders. A website migration SEO checklist without baselines cannot prove recovery later.
Phase 2 — Redirect Mapping: The Heart of This Website Migration SEO Checklist
Redirects are infrastructure, not decoration. Every valuable legacy URL needs a destination on the new site, mapped to the closest content match — never blanketed to the homepage. In this website migration SEO checklist, redirect mapping gets its own detailed phase because it carries the most ranking risk.
The 1:1 redirect mapping protocol
Build your redirect map in a spreadsheet: old URL, new URL, match type, traffic, backlinks, status. Handle three scenarios explicitly:
- Direct match: the old page has an equivalent new page — redirect one-to-one, no exceptions.
- Consolidation: several thin legacy pages merge into one hub — redirect all contributors there, and preserve the exact internal anchor text that pointed at them, because that anchor text carried relevance signals.
- Genuine removal: pages with no modern equivalent get a proper 410 Gone status, not a forced redirect to somewhere irrelevant. A 410 tells Google plainly the page is gone, which processes faster than a confusing 404 or an unrelated redirect.
301 vs 302 vs 308: get the status code right
Use 301 (Moved Permanently) for every permanent URL change — it passes ranking signals to the new URL. Use 302 (Found) only for genuinely temporary moves; misused 302s are a classic cause of slow recovery. Use 308 when you need permanent semantics with the request method preserved. Serve all redirects from the server config, test them in bulk, and keep them live for at least 12 months — removing them early silently kills the equity they carried. No website migration SEO checklist is complete without a commitment to keep redirects live long term.
Flatten chains and avoid homepage blankets
Audit every redirect for chain length and flatten each one to a single direct hop — chains dilute authority and slow crawlers. Routing dozens of old URLs to one generic destination is treated by Google as a soft 404, meaning the page gets dropped from the index anyway. Auditing redirect hops is a website migration SEO checklist task that pays for itself many times over.
Phase 3 — Staging Hygiene: Lock It Down, Then Test It
Staging is where mistakes are cheap — but only if search engines cannot index it and you test it properly. This phase of the website migration SEO checklist has five non-negotiables:
- Lock staging down with HTTP authentication or a site-wide noindex so search engines cannot crawl your unfinished site.
- Crawl staging twice: once early in development and once 48 hours before launch. Developers make last-minute template changes, and a second crawl catches the noindex tag someone forgot to remove after the “final” review.
- Compare staging against the legacy crawl page by page: missing pages, internal links still pointing to old URLs, duplicate title tags, and meta descriptions lost in the rebuild — automate this website migration SEO checklist comparison so developers can re-run it after every deployment.
- Check mobile rendering specifically — Google evaluates your site through its mobile user agent, so render staging with Google’s mobile crawler and compare the output HTML (including schema markup) against the legacy site’s mobile output.
- Validate every JSON-LD block through the Rich Results Test. If your legacy site used Organization, Article, Product, or FAQ schema, confirm each type migrated intact and correctly nested.
JavaScript Rendering Pitfalls During Redesigns (What Most Checklists Miss)
This is where redesign migrations quietly die. When you rebuild on a JavaScript framework, Google must render your pages in a second wave after the initial HTML crawl. If your staging site carried a noindex directive, Google may never bother rendering those pages at all — meaning launch-day problems in your rendered content go completely undetected until real rankings drop. A complete website migration SEO checklist must address this failure mode.
Three rules for JS-heavy redesigns that this website migration SEO checklist recommends:
- Serve critical content as real HTML. Use server-side rendering (SSR) or static site generation (SSG) so Googlebot sees content on first crawl, not after JavaScript executes. Google’s JavaScript SEO documentation confirms that relying on client-side rendering alone delays indexing and can leave Googlebot staring at a blank shell.
- Compare rendered DOM, not just source code. Your CMS preview can look perfect while the rendered DOM Google actually evaluates is missing headings, canonicals, or schema. Run DOM parity checks between legacy production templates and staging.
- Test rendering with Google’s mobile user agent before launch. A new hydration routine or lazy-loading pattern can push key content out of the initial render — catch it on staging, not in your rankings.
Phase 4 — Launch-Day Protocol
Launch day rewards preparation and punishes improvisation. Work this ordered website migration SEO checklist sequence:
- Schedule DNS changes for a low-traffic window and lower your TTL 24–48 hours beforehand so propagation completes quickly.
- Verify redirects are live — hand-test your 20 highest-value URLs, then run a bulk check across the entire redirect map.
- Confirm noindex is removed and the live robots.txt permits crawling of every page you want indexed.
- Submit your XML sitemaps in Search Console and confirm property verification carried over.
- Run Google’s Change of Address tool (for domain changes): verify both old and new properties in Search Console, confirm the site-wide 301 redirect from the old domain is live first — the tool refuses to proceed without it — then submit the change request from the old property, exactly as Google’s site move documentation describes. Follow up with URL Inspection on priority pages to verify Google sees the new versions and request indexing. This exact sequence is another item most website migration SEO checklists gloss over.
- Check canonicals, hreflang, and status codes across a representative sample — a canonical pointing back at a staging URL silently cannibalizes your new page.
- Run a live crawl immediately and inspect top landing pages for title tags, schema output, and internal linking.
- Confirm analytics, conversion tracking, and forms fire correctly before calling the launch complete — a broken form never appears in an SEO crawl but shows up in conversions within hours.
- Keep your rollback owner on standby for the first few hours, with a clear trigger for pulling it.
AI-Search Citation Continuity: Protecting Your Visibility When URLs Change
Here is the gap almost no migration guide covers. In 2026, visibility is not just Google rankings — it is citations in AI Overviews, ChatGPT, Perplexity, and Gemini. When your URLs change, AI systems that learned your content at the old addresses can lose the thread. Your llms.txt file and entity consistency are migration-critical assets. Protecting AI visibility is the newest entry in a modern website migration SEO checklist.
- Migrate your llms.txt to the new domain and update every URL it references. If AI crawlers hit 404s on the paths your llms.txt advertises, your llms.txt visibility degrades exactly when you need it most.
- Keep entity signals consistent — organization name, addresses, and brand identifiers in schema must match exactly between old and new templates, or AI systems may split your entity into two weaker profiles.
- Monitor AI Overview citations for your money keywords before and after launch. A page surviving classic rankings can still vanish from AI-generated answers if its content structure changed.
- Preserve content structure on high-performing pages — the headings and FAQ blocks that earned AI citations should survive the redesign.
Phase 5 — Post-Launch Monitoring and the Traffic-Loss Triage Decision Tree
The last phase of this website migration SEO checklist is post-launch monitoring: track Search Console clicks and impressions, index coverage, crawl error rates, and server logs showing what Googlebot actually requests — for at least 60 days. Prioritize your value-tagged pages from Phase 1: if your ten highest-traffic pages hold steady, smaller pages wobbling is normal churn. Rankings typically shuffle for one to two weeks, then stabilize within four to eight weeks.
When a drop looks real, use this website migration SEO checklist decision tree instead of panicking:
| Symptom | Likely Cause | First Action |
|---|---|---|
| Sudden drop across ALL pages, Day 0–2 | Leftover noindex or blocked robots.txt | Inspect live robots.txt and meta robots; remove; request indexing |
| Steady decline on many pages, Week 2–4 | Redirect chains, homepage blankets, or canonical mismatches | Bulk-test redirect map; flatten chains; fix canonicals |
| Drop concentrated on specific high-value pages | Broken 1:1 redirects, lost backlinks, or rewritten content killing relevance | Check each URL’s redirect target, inbound links, and content intent match |
| Pages stuck in “Discovered, not indexed” | JS rendering failure or weak crawl budget signals | Test rendering with Google’s mobile user agent; improve SSR; request indexing |
| Classic rankings fine, AI citations vanished | Broken llms.txt paths or changed content structure | Validate llms.txt URLs; restore FAQ/schema structure on key pages |
Backlinks need separate attention: ask your highest-value linking sites to update links pointing to old URLs directly, instead of relying on redirects to carry that equity forever. It is a step this website migration SEO checklist insists on, because external links outlive any redirect map.
Common Migration Mistakes (and Fast Fixes)
Even teams working from a solid website migration SEO checklist stumble on these five recurring mistakes:
- Staging leakage: noindex left on production. Fix: remove, verify in URL Inspection, request re-indexing.
- Homepage blanket redirects: dozens of URLs pointed at one generic page. Fix: rebuild as true 1:1 redirects to relevant pages.
- Redirect chains: two or three hops before landing. Fix: audit and flatten to single hops.
- Metadata loss: title tags and meta descriptions reset by the new CMS. Fix: re-import from your pre-migration snapshot.
- Analytics gaps: tracking IDs not transferred. Fix: verify GA4/GTM firing on the new domain before launch day ends.
FAQs
The questions our website migration SEO checklist answers most often:
How long does it take to recover traffic after a website migration?
Expect one to two weeks of ranking volatility as Google recrawls your site. Well-executed migrations typically stabilize within four to eight weeks, while complex domain changes or large replatforms can take up to 90 days to fully settle. A sharp decline lasting beyond four weeks usually signals a technical fault — run the triage decision tree above rather than waiting.
How long should I keep 301 redirects live after a migration?
Keep every redirect live for at least 12 months, and ideally permanently for your highest-value URLs. Google needs repeated crawls over months to transfer signals, and external sites will link to old URLs for years. Removing redirects early destroys the equity they carried.
Should I launch my migrated site at night or on a weekend?
Yes — schedule the DNS cutover during your lowest-traffic window, typically a weekend evening. Lower your DNS TTL 24 to 48 hours beforehand so changes propagate quickly. Keep your rollback owner and monitoring dashboard staffed for the first few hours after launch.
Should I use 301 or 302 redirects during a website migration?
Use 301 (Moved Permanently) for every permanent URL change — it passes ranking signals to the new URL. Reserve 302 for genuinely temporary moves only. Using 302s as placeholders during a permanent migration is a classic mistake that delays recovery because Google treats the move as reversible.
How do I use Google’s Change of Address tool correctly?
Verify both the old and new domains as properties in Search Console, ensure a site-wide 301 redirect from the old domain to the new one is live, then submit the Change of Address request from the old property. The tool rejects the request if redirects are missing. Follow up with URL Inspection and indexing requests on your priority pages.
How can I tell if a traffic drop was caused by the migration?
Compare Search Console performance for the four weeks before and after launch on identical page groups. If the decline aligns with launch day and concentrates on migrated pages while non-migrated sections hold steady, the migration caused it. Use the triage decision tree above to isolate noindex issues, redirect failures, or rendering problems.
Conclusion: Migrate With a Checklist, Not With Hope
A successful website migration SEO checklist comes down to preparation plus discipline. Crawl and inventory everything before you touch code, map every redirect one-to-one, lock down and test staging, follow an ordered launch-day protocol, protect your AI-search visibility alongside your classic rankings, and monitor with a triage plan instead of guesswork. Follow this website migration SEO checklist and your redesign or relaunch will strengthen your SEO instead of resetting it.
Planning a redesign or domain move and want an expert website migration SEO checklist review before launch day? Get a free site audit from our team — we will crawl your current site, flag migration risks, and map a safe path to your new launch.