Website Migration SEO Checklist: Redesign or Relaunch Without Losing Rankings
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