The Website Migration SEO Checklist: How to Move Without Losing Everything

The Most Dangerous Day in Your Website’s Life

There’s a moment in every website’s history that determines whether years of SEO work survive or vanish. It’s not a Google core update. It’s not a competitor stealing your keywords. It’s the day you migrate your website.

A CMS switch. A domain change. A redesign. A protocol upgrade. Whatever the reason — this is the single highest-risk event in organic search. We’ve watched companies lose 40–70% of their organic traffic in a week because someone forgot to map redirects, left noindex tags from staging, or assumed the new platform would “handle it.”

The good news? Migrations aren’t mysterious. They’re mostly about discipline. Document what exists, decide what changes, redirect old URLs properly, and watch the launch like a hawk. This checklist is built from real migrations we’ve managed — not theory, not tool vendor advice, but the actual sequence of decisions that separates a smooth transition from an SEO disaster.

What Is a Website Migration?

A website migration is any major structural change that affects how search engines crawl, index, and understand your site. The term covers a wide range of scenarios, each with different risk levels:

The common thread: something a search engine relies on to understand your site is about to change. The scale of the risk tracks the scale of the change. And here’s the uncomfortable truth — you can stack these changes. A rebrand that includes a domain change, a new CMS, and a redesign all at once? That’s three high-risk migrations wrapped in one project, and each one multiplies the risk of the others.

Phase 1: Pre-Migration (4–6 Weeks Before Launch)

This is where migrations are won or lost. Skip this phase, and no amount of post-launch monitoring will save you.

1. Build Your Baseline

Before touching anything, you need a complete picture of your current SEO performance. Without this baseline, you have no way to measure whether the migration helped, hurt, or changed nothing.

Export at least 12 months of data from Google Search Console: top pages by clicks and impressions, top queries, average positions, and click-through rates. Do the same from Google Analytics for organic sessions, bounce rates, and conversions. Export your backlink profile from Ahrefs or Serpstat. Record your Core Web Vitals scores.

This data is your bible for the next three months. Every anomaly after launch gets measured against it.

2. Crawl and Inventory Every URL

Run a complete crawl of your current site with Screaming Frog or Sitebulb. Every URL gets catalogued — pages, images, PDFs, everything. This inventory becomes the foundation of your redirect map.

For each URL, record: HTTP status code, title tag, meta description, H1 heading, canonical tag, internal links pointing to it, external backlinks pointing to it, and monthly organic traffic.

Flag your priority pages — the ones that drive 80% of your organic traffic. These get the most attention during the entire migration process.

3. Build the Redirect Map

This is the single most important document in the entire migration. Every old URL gets mapped to its new equivalent. One-to-one. Server-side 301 redirects only.

Avoid redirect chains (A → B → C). Link A directly to C. Avoid 302 temporary redirects — they don’t pass link equity reliably. And absolutely no JavaScript redirects — Googlebot may not execute them.

4. Audit the Staging Site

Your staging environment should be a near-perfect replica of the production site, but completely invisible to search engines. Password-protect it or block crawlers with robots.txt. If Google indexes your staging site, you’ll face duplicate content problems before you even launch.

Run a full technical SEO audit on the staging site:

Check every redirect. Does each old URL land on the correct new URL? Are there chains? Are any returning 302 instead of 301?

Validate metadata. Title tags, meta descriptions, and canonical tags don’t transfer automatically between platforms. Check every priority page manually. A platform switch that replaces your carefully crafted title tags with auto-generated defaults will cost you click-through rates immediately.

Test structured data. Use Google’s Rich Results Test on staging URLs. Schema markup often breaks during CMS changes — especially Product, FAQ, and Organization schemas.

Verify internal links. Update internal links at the database level to point to new URLs directly, not through redirects. Every internal link that goes through a redirect wastes crawl budget and dilutes link equity.

Confirm mobile experience. Google uses mobile-first indexing — your mobile version is your SEO experience. Test on actual devices, not just Chrome DevTools.

5. Prepare Your SEO Infrastructure

Before launch day, have these ready and tested on staging:

Phase 2: Launch Day

Launch during low-traffic hours. Saturday or Sunday night is ideal for most B2B websites. This minimizes user impact if something goes wrong and gives you time to fix issues before Monday morning.

6. Execute the Launch Sequence

Here’s the exact sequence — order matters:

Step 1: Deploy the new site to production.

Step 2: Activate all 301 redirects simultaneously. Not in batches — all at once.

Step 3: Verify robots.txt is the production version (not staging). This is the single most common catastrophic error. One leftover Disallow: / from staging, and Google stops indexing your entire site.

Step 4: Remove any noindex meta tags carried over from the staging environment.

Step 5: Submit the new XML sitemap in Google Search Console.

Step 6: If this is a domain migration, use Google’s Change of Address tool in Search Console. This tells Google directly about the move and accelerates recrawling.

Step 7: Verify GA4 and GTM are firing correctly on all pages. Check conversions, events, phone clicks — everything you track monthly.

Step 8: Spot-check your top 20 priority pages manually. Load them on desktop and mobile. Verify titles, content, redirects, and structured data are all correct.

Phase 3: Post-Migration Monitoring (Days 1–90)

The migration isn’t over when the site goes live. It’s over when your organic traffic stabilizes — which takes anywhere from 4 to 12 weeks depending on site size and complexity.

7. Daily Monitoring: Days 1–14

Check these every single day for the first two weeks:

Google Search Console: Index coverage report (new errors?), crawl stats (is Googlebot finding and crawling the new URLs?), and any manual actions or security issues.

Crawl errors: Run a crawl of your live site on Day 1, Day 3, and Day 7. Compare against your pre-migration inventory. Every new 404 is a missed redirect — fix it within 24 hours.

Rankings: Track your priority keywords daily. A 10–15% temporary dip is completely normal. A sustained drop beyond 30% signals a real technical problem.

Traffic: Compare organic sessions against the same period last year (not last week — seasonal patterns matter). Annotate the migration date in GA4 so stakeholders can separate migration effects from normal fluctuations.

8. Weekly Monitoring: Weeks 2–8

Index coverage trends. Are the new URLs being indexed at the expected rate? Are old URLs being dropped from the index? Both should be happening simultaneously.

Core Web Vitals. New templates often have different performance characteristics. Monitor field data (not just lab data) for LCP, CLS, and INP regressions.

Backlink integrity. Check that your most valuable backlinks are resolving correctly through the redirect chain to the new URLs. If a referring site links to an old URL that 404s instead of redirecting, that link equity is lost.

Internal link health. A fresh crawl at week 4 should show zero internal links pointing to redirected or 404 URLs. Any remaining ones need manual cleanup.

9. Monthly Review: Months 2–3

By month two, traffic should be stabilizing. Compare against your baseline: organic traffic, keyword rankings, impressions, click-through rates, and conversions.

If everything is within 10–15% of pre-migration levels, you’re on track. If specific pages or sections are underperforming, investigate individually — it’s usually a redirect, canonical, or content issue specific to that section, not a sitewide problem.

The 10 Most Common Migration Mistakes (And How to Avoid Them)

Migration Timeline: What to Expect After Launch

Set expectations with stakeholders before launch day. Here’s the realistic timeline based on our experience with migrations of different scales:

Migration and AI Search: The 2026 Factor

Website migrations in 2026 carry an additional dimension that didn’t exist before. AI systems — Google’s AI Overviews, ChatGPT, Perplexity — are indexing and citing web content independently. During a migration, you risk losing not just traditional search rankings but also AI citations and referrals.

Make sure your robots.txt allows AI crawlers (GPTBot, ClaudeBot, PerplexityBot) on the new site. Verify that structured data — especially Organization, Author, and Article schema — survives the migration intact. AI systems rely heavily on entity markup to determine source credibility. A migration that breaks your schema effectively resets your AI visibility.

If you maintain an llms.txt file, update it with your new URL structure. And test your content extractability: can AI crawlers access your content without JavaScript rendering? If your new CMS delivers content via client-side JavaScript, AI crawlers may not see it at all.

How Much Does a Site Migration Cost?

The migration itself has a cost. But the bigger cost is getting it wrong.

According to Fortune Business Insights, the global SEO services market is growing fast — a clear sign that businesses increasingly understand the cost of poor technical execution. A professional SEO partner during migration isn’t an expense. It’s insurance.

Frequently Asked Questions About Website Migration SEO