Why website migrations crater SEO so often
When a business migrates its website — a redesign, a CMS switch, a URL restructure, a domain change — rankings almost always dip in the first 30-60 days. The question is how big the dip is and how fast rankings recover. In our experience, 70 percent of migrations we audit were done without the SEO work the migration required, and the result is a 40-80 percent ranking loss that takes 4-9 months to recover. The other 30 percent were done with proper SEO work and either held rankings or lost less than 10 percent that recovered within 60 days.
The failure modes are repetitive. Redirects were missed or wrong. Internal links were not updated. The sitemap still points to old URLs. The new URLs lack the schema the old URLs had. The crawl budget got burned on 404s. Each failure is boring and fixable; together they wreck the launch.
The three migration types that need different treatment
All migrations are not equal. Each type carries different risk and different checklist items.
- Redesign migration — same URLs, new design, same CMS. Lowest risk. Main concerns: Core Web Vitals changes, schema preservation, internal link updates.
- CMS migration — same URLs, new CMS (WordPress to Webflow, Wix to Shopify, custom to Next.js). Medium risk. Main concerns: URL preservation, schema reimplementation, redirect handling for parameters.
- URL migration — new URL structure or new domain. Highest risk. Main concerns: complete 301 redirect map, internal link rewrite, sitemap updates, Search Console reverification, backlink update outreach.
The pre-launch checklist (do this 2-4 weeks before launch)
The migration is won or lost before launch day. The following items should be complete and verified in staging before the DNS switch.
- Full crawl of the existing live site — complete URL inventory with status codes, canonical tags, title tags, meta descriptions, H1s, internal links, outbound links, schema types, and current organic traffic per URL
- Mapping document — every live URL mapped to its new destination (same URL, new URL, or 410 Gone). Zero URLs should fall into "not sure yet"
- Redirect rules written and tested in staging — 301s only (never 302 or JavaScript redirects), one hop maximum (A → B, never A → B → C)
- Schema migration planned — every LocalBusiness, Service, FAQPage, Review schema from the old site re-implemented on the new site
- Core Web Vitals verified in staging — the new site should pass LCP, INP and CLS before launch, not after
- Analytics and Search Console tags verified — Google Tag Manager, GA4, Meta Pixel, Microsoft Clarity, Search Console verification file. Easy to lose during a CMS migration.
- Robots.txt and XML sitemap verified — robots.txt should not block the new site; sitemap should list only new URLs
- Internal links audited — every link in body content pointing to the old URL should be updated to the new URL
The launch-day sequence
Launch day is a sequence, not a flip of a switch. The order matters.
- 00:00 — Final staging verification. One more crawl of staging to confirm all URLs 200, canonicals correct, schema valid
- 00:30 — DNS switch to the new site. Clear CDN caches. Verify the live site is serving the new codebase
- 00:45 — Verify redirects are serving 301 responses on 20-30 representative old URLs. Any 404 or 302 here is an emergency.
- 01:00 — Submit new sitemap to Google Search Console and Bing Webmaster Tools. Use URL Inspection on 5-10 top pages to request indexing
- 01:30 — Test analytics are firing on the live site. Confirm tag firing in Google Tag Assistant, Meta Pixel Helper and GA4 real-time
- 02:00 — Monitor Search Console Coverage report for the next 24 hours for any immediate warnings
- Within 24 hours — Submit to IndexNow (notifies Bing, Yandex, Seznam instantly)
The post-launch 90-day monitoring plan
The migration is not done at launch. It is done at day 90 when rankings have fully resettled. The post-launch monitoring plan.
- Day 1-7 — Daily Search Console Coverage check. Any sudden spike in "404 Not Found" means a redirect gap. Fix immediately.
- Day 7-30 — Daily organic traffic monitoring in GA4. Expect a 15-30 percent dip in the first 2 weeks (normal), recovering by week 4-6.
- Day 30-60 — Weekly rank tracking on top 50 keywords. Compare to pre-launch baseline. Investigate any keyword that lost 10+ positions.
- Day 60-90 — Full crawl comparison vs. pre-launch. Verify every important URL still exists, every important schema still fires, every important internal link still works.
- Day 90 — Post-mortem. Compare pre-launch and post-launch metrics. Document what worked, what did not, and what to do differently next migration.
The specific mistakes we see most often
From dozens of migration audits, the five recurring mistakes.
- Trailing slash inconsistency — old URLs ended in / and new URLs do not (or vice versa). Both versions resolve, Google treats them as duplicates. Pick one and 301 the other sitewide.
- JavaScript redirects instead of 301s — JS redirects pass partial link equity at best and often zero. Server-level 301s only.
- Blog post slug changes with no redirect map — a client CMS migration often renumbers posts (/blog/123 becomes /blog/post-title). Without a redirect map, every link ever earned to the old URL dies.
- Lost schema — old site had rich FAQPage schema, new site is a React SPA without SSR and the schema never renders. Google loses the enhanced listings.
- Analytics tag drop — GA4 property reconfigured but not reverified. Months of data gaps nobody notices until a quarterly report.
When to call for help
Migrations are the engagement where in-house teams most commonly lose their rankings. If any of the following apply, hiring a specialist is almost always cheaper than fixing the aftermath: your site has 500+ URLs, your site has significant organic traffic (>5,000 sessions/month), you are changing both CMS and URL structure, you are consolidating multiple domains, or you depend on local SEO signals that would be hard to recreate.
Frequently asked questions
How long does a website migration take?
The migration project (planning, redesign, development) typically takes 60-120 days. The SEO migration work (crawl, mapping, redirects, verification) should run in parallel starting 30+ days before launch. The post-launch recovery window to stable rankings is typically 60-90 days.
Can I migrate without losing any rankings?
In practice, a well-executed migration loses less than 10 percent of rankings in the first 30 days and recovers to or above baseline by day 60-90. Zero loss is the target but not the realistic expectation; the realistic expectation is a short dip followed by full recovery.
Should I do SEO work before or after a redesign?
Both, with the heavy work before. The pre-launch SEO work (crawl, mapping, redirects, schema planning) prevents disaster. Post-launch SEO work (monitoring, catching gaps, resubmitting) fine-tunes recovery. Skipping either half is where migrations go wrong.
What is the biggest migration risk I should worry about?
Missing redirects. If your old URL does not 301 to the equivalent new URL on launch day, every backlink pointing to that old URL dies, every indexed URL becomes a 404, and your rankings crater within 48 hours. Verify redirects immediately after launch.
Do I need to re-verify Google Search Console after a migration?
Only if the domain changes. For same-domain migrations (CMS or URL structure change), Search Console continues to work. For domain changes, add the new domain in Search Console, verify, and use the Change of Address tool to transfer signal history.
Does Local Visibility AI handle migration SEO?
Yes — migration SEO is one of our one-time project services. Scope depends on site size and complexity; typical engagements run $3,000-$12,000 and include pre-launch audit, mapping, redirect rules, launch-day verification and 90-day post-launch monitoring.
Planning a migration? Let us pressure-test the plan
Free 30-second check to see where your current site stands before you ship the new one.
Keep exploring
Related services, industries, cities and resources from Local Visibility AI.