A website migration is one of the highest-risk projects in SEO. Get site migration SEO right and you carry your rankings, traffic, and revenue over to the new setup untouched. Get it wrong and you can lose months of organic visibility overnight. Whether you're redesigning, moving to a new CMS, changing domains, or finally shifting from HTTP to HTTPS, the difference between a smooth move and a disaster comes down to planning and disciplined execution.
This is a complete SEO migration checklist built for US marketing managers, business owners, and dev leads who can't afford to gamble with search traffic. You'll learn how to benchmark before you move, map 301 redirects correctly, avoid the mistakes that tank rankings, understand the normal SEO dip, and monitor recovery for 60–90 days after launch plus how to keep showing up in AI Overviews once you're live. If you'd rather hand the whole project to specialists, Centric's US SEO services team runs migrations end to end.
What Counts as a Site Migration (and Why SEO Risk Varies)
A site migration is any significant change to your website's location, structure, platform, or technology that search engines must re-crawl and re-evaluate. Not every migration carries the same risk and grouping them all under one generic checklist is exactly how sites lose traffic. Here are the main types and what each one threatens.
Website redesign (same domain, new templates)
A visual and structural refresh where URLs may or may not change. The hidden risk is template-level change: navigation, internal linking, heading structure, and on-page content getting silently altered. Even without URL changes, a redesign can shift how Google understands each page. Read our guide to protecting rankings during a website redesign, and involve SEO before the new templates are built not after. If you're rebuilding the front end, loop in your web and mobile design and development partner early.
Replatforming / CMS change
Moving from one system to another WordPress to a headless build, or onto Shopify, for example. URL patterns, rendering method, and technical defaults almost always change. Ecommerce replatforms are especially fragile because faceted navigation, product URLs, and canonical logic differ per platform, so get specialist ecommerce SEO eyes on it before launch.
Domain change (rebrand)
Moving from olddomain.com to newdomain.com. This is high risk because you're asking Google to transfer all authority signals to a brand-new host. Complete redirects and a Search Console Change of Address are non-negotiable here.
HTTP → HTTPS
Migrating to a secure protocol. Lower risk when done cleanly, but every http:// URL becomes a new https:// URL that must redirect, and mixed-content issues can break pages or trigger browser warnings.
URL structure change
Reorganizing folders or slug patterns (e.g., /blog/post → /insights/post). Even on the same domain, every changed URL needs a redirect and every internal link must be updated to the new path.
Domain consolidation / merge
Combining multiple sites or subdomains into one. The most complex scenario: you're merging authority, resolving duplicate content, and redirecting at scale. Most real-world projects combine two or three types at once redesign plus replatform plus URL changes is common which multiplies the risk and the number of things to check.
Pre-Migration Benchmarking: Capture Everything First
You cannot measure loss you never recorded. Before anything moves, benchmark current performance so you have a baseline to compare against and a complete inventory to migrate.
Crawl and inventory the current site. Run a full crawl with Screaming Frog to export every indexable URL, status code, title, meta description, canonical, and word count. This becomes the source of truth for your redirect map. For a structured approach, follow our process for how to audit a website for SEO and the full SEO audit checklist.
Record rankings and traffic:
-
Google Search Console: Export 16 months of Performance data (queries, pages, clicks, impressions, average position). Your top pages by clicks are the URLs you protect first.
-
GA4: Export organic sessions, conversions, and landing-page performance. Universal Analytics is fully retired, so confirm GA4 is your baseline and tracking correctly before launch.
-
Ahrefs or Semrush: Snapshot organic keywords, positions, top pages, and the backlink profile, and save the export with a date.
Map your backlinks. Identify which URLs earn the most referring domains those pages must redirect to a strong, relevant equivalent so link equity survives. A link audit before migration flags the pages you can't afford to break. Store every export in one dated folder; when you're staring at a traffic chart 30 days post-launch, this baseline tells you whether a dip is normal noise or a real problem.
The 301 Redirect Map: The Single Most Important Step
If your URLs change, redirects are what carry rankings from old to new. A broken or incomplete redirect map is the number-one cause of migration traffic loss. Treat this as the core of your SEO migration plan.
Build a 1:1 redirect map
Create a spreadsheet with two primary columns Old URL and New URL. Every indexable old URL should point to the most relevant new URL, ideally a true 1:1 equivalent. Mass-redirecting everything to the homepage is treated by Google as a soft 404 and passes almost no value.
Use 301s, not 302s (usually)
-
301 (permanent): Use this for migrations. It signals a permanent move and passes ranking signals.
-
302 (temporary): Reserve for genuinely temporary situations. Using 302s for a permanent migration slows consolidation and can hold back recovery.
Avoid redirect chains and loops
A redirect chain (A → B → C) wastes crawl budget and dilutes signals point every old URL directly to its final destination (A → C). A redirect loop (A → B → A) breaks the page entirely. After launch, re-crawl to confirm every redirect resolves in a single hop to a 200 status.
Fix canonicals and internal links
Update internal links to point at the new URLs directly don't rely on redirects to do it. Set self-referencing canonical tags on new URLs, and watch for canonical mistakes that can quietly de-index pages, covered in our guide to the canonical error. For large or complex sites, structured technical and enterprise SEO governance keeps thousands of redirects consistent.
Why Traffic Drops After Migration (the SEO Dip)
Some ranking fluctuation after a migration is normal even when you do everything right. Google has to re-crawl, re-render, and re-evaluate your site. Knowing what's normal versus what's a red flag stops you from panicking, or from ignoring a real fire.
What's normal: A temporary dip in rankings and traffic in the first 2–4 weeks as Google re-indexes. Positions bounce around before settling. For most well-executed migrations, traffic stabilizes and recovers within 4–8 weeks, with full recovery typically inside 60–90 days.
What's a red flag:
-
Traffic drops sharply and keeps falling past week four with no sign of recovery.
-
Large numbers of pages showing as “Crawled – currently not indexed” or dropping out of the index.
-
Redirect errors, 404 spikes, or server errors appearing in Search Console.
-
Rankings vanish for your money terms specifically, not just minor shuffling.
If you see red flags, don't wait out the “normal dip” window audit immediately. Most catastrophic drops trace back to redirect gaps, blocked crawling (a stray robots.txt disallow or a noindex left over from staging), or lost content.
Launch Day: The Go-Live SEO Checklist
The moment you flip the switch is when preventable disasters happen. Work through these before and immediately after go-live.
-
Remove staging blocks. Confirm the noindex tag and robots.txt disallow from your staging environment are gone. This single oversight has killed more migrations than anything else.
-
Verify robots.txt allows crawling of important sections and points to the correct sitemap.
-
Submit new XML sitemaps in Google Search Console clean sitemaps containing only final, 200-status URLs.
-
Keep old sitemaps temporarily (for domain/URL changes) so Google discovers and processes redirects faster.
-
File a Change of Address in Search Console for domain migrations.
-
Spot-check redirects across templates: homepage, top money pages, top blog posts, paginated pages, and edge cases.
-
Confirm analytics fire GA4 and tag manager events working on the new site.
-
Check Core Web Vitals on the new build; a redesign can quietly wreck performance see our Core Web Vitals SEO guide.
Post-Launch Monitoring: The First 60–90 Days
Migration doesn't end at launch. The following weeks decide whether you recover fully.
Watch indexation. In Search Console's Pages (Index Coverage) report, monitor indexed versus not-indexed counts. Rising “not indexed” numbers signal redirect or crawl problems worth a technical SEO audit.
Track redirects and errors. Re-crawl weekly with Screaming Frog to catch new 404s, broken redirects, and chains. Fix 404s on high-value or heavily linked pages first.
Analyze log files. Server logs show how Googlebot is actually crawling the new site which URLs it hits, how often, and where it wastes budget on redirects or dead ends. This is the ground truth that tools only estimate.
Monitor rankings and traffic for 60–90 days. Track priority keywords in Ahrefs or Semrush against your pre-migration baseline weekly. Expect movement; watch the trend line, not daily noise. Our guide on how to improve SEO rankings covers the recovery levers if progress stalls.
Run a full technical audit at ~30 days. Once things settle, a complete technical SEO site audit catches anything the migration introduced orphaned pages, thin content, and internal link gaps.
Common Site Migration Mistakes That Kill SEO
A “bad” migration is rarely one big error it's a stack of avoidable ones. The most damaging:
-
No redirect map, or redirecting everything to the homepage. The fastest way to lose rankings.
-
Leaving the staging noindex or robots block live. Instant de-indexing.
-
Redirect chains and loops that bleed crawl budget and link equity.
-
Changing URLs, content, and design all at once with no way to isolate what caused a drop. Sequence changes when you can.
-
Losing content. Trimming pages that ranked and earned links removes the very signals you're trying to keep.
-
Forgetting internal links, canonicals, hreflang, and structured data. These get overlooked and quietly damage crawlability the fundamentals covered in what technical SEO is.
-
Not benchmarking first, so you can't diagnose what actually changed.
-
Treating launch as the finish line instead of the start of monitoring and ongoing website maintenance.
Don't Forget AI Search: Protecting AEO & AI Overviews
Migrations now carry a newer risk: losing visibility in AI-powered search. Google's AI Overviews and assistants like ChatGPT and Perplexity pull from your content and structured data. If a migration strips your schema or restructures content, you can vanish from AI answers even while classic rankings hold steady.
Protect your answer-engine presence by carrying over all structured data (Organization, Product, FAQ, Article, Breadcrumb) to the new URLs, keeping the clear, answer-first content blocks that get cited, and re-validating schema after launch. Our answer engine optimization work and this guide on how to show up in AI Overviews walk through preserving and growing that visibility through a move.
The Complete Site Migration SEO Checklist
Use this scannable recap as your working checklist. Copy it into your project tracker and tick each item as you go.
Pre-Migration
☐ Identify migration type(s) and map the risk for each
☐ Full Screaming Frog crawl of the current site
☐ Export 16 months of Google Search Console performance data
☐ Export GA4 organic traffic and conversions
☐ Snapshot keywords, rankings, and backlinks in Ahrefs/Semrush
☐ Identify top pages by traffic and by backlinks
☐ Build a 1:1 old-to-new redirect map in a spreadsheet
During / Launch
☐ Implement 301 redirects no chains, no loops
☐ Remove staging noindex tag and robots.txt disallow
☐ Update internal links to point to new URLs
☐ Set self-referencing canonical tags
☐ Migrate all structured data / schema to new URLs
☐ Submit new XML sitemap in Google Search Console
☐ File Change of Address for domain moves
☐ Confirm GA4 and tag manager events fire correctly
☐ Check Core Web Vitals on the new build
Post-Launch (60–90 days)
☐ Monitor the Pages / Index Coverage report
☐ Re-crawl weekly for new 404s and broken redirects
☐ Review server log files for Googlebot behavior
☐ Track priority keyword rankings against baseline
☐ Fix high-value 404s and redirect errors quickly
☐ Run a full technical audit at ~30 days
☐ Re-validate schema for AI/AEO visibility
Frequently Asked Questions
What is a website migration SEO checklist?
A website migration SEO checklist is a structured list of tasks that protects organic rankings and traffic when you change your site's domain, platform, design, or URL structure. It spans three phases: pre-migration benchmarking (crawling and exporting current data), launch execution (301 redirects, sitemaps, and removing staging blocks), and 60–90 days of post-launch monitoring to confirm recovery.
How long does the SEO dip last after a site migration?
For a well-executed migration, expect a temporary dip in the first 2–4 weeks while Google re-crawls and re-indexes the site. Traffic usually stabilizes within 4–8 weeks and fully recovers inside 60–90 days. If traffic keeps falling past week four with no recovery, that's a red flag pointing to redirect, indexing, or content problems that need an immediate audit.
Do I need 301 redirects for every page?
You need a 301 redirect for every indexable URL that is changing, pointing to its closest 1:1 equivalent on the new site. Pages that aren't changing URLs don't need redirects. Avoid mass-redirecting everything to the homepage — Google treats that as a soft 404 and passes almost no ranking value.
When should I use a 302 instead of a 301 in a migration?
Almost never during a migration. Use a 301 (permanent) redirect so Google consolidates ranking signals to the new URL. Reserve 302 (temporary) redirects for genuinely short-term situations, such as a page temporarily offline for maintenance. Using 302s for a permanent move slows recovery.
Why did my traffic drop after a site migration?
The most common causes are a leftover staging noindex or robots.txt block, missing or broken 301 redirects, redirect chains and loops, lost or trimmed content, and forgotten canonicals or structured data. Benchmarking before you migrate makes it far easier to pinpoint which of these caused the drop.
What tools do I need for an SEO site migration?
The core toolkit is Google Search Console (performance data, index coverage, Change of Address), GA4 (traffic and conversions), Screaming Frog (crawling and redirect verification), and Ahrefs or Semrush (rankings and backlinks). Server log files add ground-truth insight into how Googlebot crawls the new site.
Does moving from HTTP to HTTPS affect SEO?
Done correctly, an HTTP-to-HTTPS migration is low risk and HTTPS is a lightweight ranking signal. But every http:// URL becomes a new https:// URL that must 301-redirect, and unresolved mixed-content issues can break pages. Update internal links, canonicals, and your sitemap to the HTTPS versions.
How do I keep appearing in Google AI Overviews after a migration?
Carry all structured data (Organization, Product, FAQ, Article, Breadcrumb) over to the new URLs, preserve the clear, answer-first content blocks that AI engines cite, and re-validate your schema after launch. AI Overviews and assistants rely on crawlable content and intact markup, so the same redirect and indexation discipline that protects rankings also protects AI visibility.
Conclusion: Migrate Once, Migrate Right
A site migration is only risky when it's unplanned. Benchmark everything first, build a clean 1:1 redirect map, remove staging blocks on launch, and monitor closely for 60–90 days and you can move your site without surrendering the rankings you worked to earn. The teams that lose traffic are almost always the ones that skipped the checklist.
Planning a redesign, replatform, or domain move and want to protect every ranking? Centric's US SEO team plans and executes migrations that hold rankings and recover fast. Talk to us before you build the new site that's when SEO input is worth the most.
