Website Migration Without the SEO Disaster: A Step-by-Step Survival Guide

Migrations Go Wrong More Often Than Right

A website migration should be a step forward — better design, faster platform, cleaner URLs. But without careful SEO planning, it becomes a step off a cliff.

The pattern is painfully common: a business launches their shiny new website and watches organic traffic drop 30-50% over the following weeks. Rankings disappear. Leads dry up. The phone stops ringing. And everyone wonders what went wrong.

What went wrong is usually one (or more) of these:

Old URLs returning 404 errors instead of redirecting
Content restructured without mapping old pages to new ones
Internal links pointing to dead pages
Metadata wiped during the migration
Google losing trust in the domain during the transition

All of these are preventable. A migration done right might see a temporary 10-15% traffic dip that recovers within weeks. A migration done wrong can take 6-12 months to recover — if it recovers at all.

Types of Migrations

Different migrations carry different risk levels.

Low Risk

HTTP to HTTPS — standard security upgrade. Minimal impact if redirects are correct.
Minor URL changes — cleaning up URL structure without changing content.

Medium Risk

CMS change (WordPress to Webflow, Shopify migration, etc.) — URLs almost always change, templates shift.
Redesign on same domain — new layout, potentially restructured content.
Subdomain moves (blog.site.com to site.com/blog) — URL structure changes.

High Risk

Domain change — moving from olddomain.com to newdomain.com. Google has to transfer all trust signals.
Major content restructuring — merging, splitting, or reorganising content significantly.
International expansion — adding subdomains or subdirectories for different markets.
Multiple changes at once — redesign + CMS change + domain move = maximum risk.

Golden rule: Change as few things as possible simultaneously. If you're changing your CMS, don't also change your URL structure, domain, and content all at once.

Pre-Migration: The Work That Saves You

1. Crawl and Document Everything

Before you touch anything, create a complete record of your current site.

Crawl your site using:

Screaming Frog (free up to 500 URLs)
Sitebulb
Ahrefs Site Audit

Export and save:

Every URL on the site
Page titles and meta descriptions
H1 tags
Canonical tags
Internal link structure
Status codes
Hreflang tags (if multilingual)

This is your baseline. You'll compare everything against it after migration.

2. Identify Your Most Valuable Pages

Not all pages are equal. Focus your redirect efforts on the pages that actually drive traffic and links.

In Google Analytics 4:

Pages with the most organic traffic (Landing page report)
Pages with the highest conversion rates
Pages that drive the most revenue

In Google Search Console:

Pages with the most impressions and clicks
Pages ranking for your target keywords

In Ahrefs/SEMrush:

Pages with the most backlinks
Pages with the highest referring domains

These pages are non-negotiable — they must redirect correctly, and ideally, their content should survive intact on the new site.

3. Build the Redirect Map

This is the single most important document in the entire migration.

Create a spreadsheet:

| Old URL | New URL | Status Code | Notes | |---------|---------|-------------|-------| | /services/seo | /services/search-engine-optimization | 301 | URL changed | | /blog/old-post | /blog/old-post | 200 | Same URL kept | | /about-us | /about | 301 | Shortened | | /services/removed-service | /services | 301 | Service discontinued, redirect to parent | | /old-landing-page | — | 410 | Intentionally removed |

Rules:

Every old URL that has traffic, rankings, or backlinks gets a 301 redirect to the most relevant new URL
Redirect to equivalent content, not just the homepage (homepage redirects waste link equity)
Use 301 (permanent) redirects, not 302 (temporary)
If a page is genuinely gone with no equivalent, use 410 (gone) rather than letting it 404

4. Preserve On-Page SEO

For every page migrating to the new site, verify:

Title tags — same or improved (don't let your CMS template overwrite custom titles)
Meta descriptions — carried over
H1 tags — present and relevant
Header structure — H2s, H3s maintained
Image alt text — preserved
Schema markup — recreated on the new platform
Canonical tags — pointing to the correct new URLs

5. Check Internal Links

Your new site should have clean internal links pointing to new URLs — not old URLs that rely on redirects.

Redirect chains (old URL → redirect → another redirect → final page) slow down crawling and leak link equity.

6. Audit the New Site on Staging

Before launch, crawl the staging version of the new site:

All pages returning 200 status codes?
Title tags and meta descriptions present?
No broken internal links?
Images loading correctly?
Schema markup working?
XML sitemap generated and correct?
Robots.txt not blocking important pages?
Page speed acceptable?
Mobile experience working?

Migration Day

Timing

Don't migrate on a Friday (you want weekdays to monitor and fix issues)
Avoid peak traffic periods (no migrations during your busy season)
Morning is better than evening (more time to catch problems)

Launch Checklist

Implement all 301 redirects — every single one from your redirect map
Submit new XML sitemap to Google Search Console
Update robots.txt — ensure nothing important is blocked
Update Google Search Console — add new property if domain changed, verify ownership
Update Google Analytics — ensure tracking code is on all pages, data streams are correct
Test critical pages — homepage, service pages, top blog posts, contact page
Test forms — every form on the site should work
Spot-check redirects — manually test 20-30 redirects from your map
Check mobile — load the site on an actual phone
Monitor server logs — watch for spikes in 404 errors

If You Changed Domains

Additional steps:

Set up a Google Search Console property for the old domain
Use the Change of Address tool in Search Console
Keep the old domain active with redirects for at least 12 months (longer is better)
Update backlinks where possible (reach out to top referring sites)

Post-Migration Monitoring

Week 1: Watch Everything

Daily checks:

Google Search Console for crawl errors
Server logs for 404 errors
Organic traffic in GA4 (compare to previous period)
Key page rankings (use a rank tracker)

Fix immediately:

Any 404 errors on pages that should be redirecting
Broken forms or CTAs
Missing tracking codes
Slow-loading pages

Week 2-4: Track Recovery

Monitor:

Organic traffic trends (day by day, compare to pre-migration)
Ranking changes for your target keywords
Crawl stats in Search Console (is Google crawling the new site properly?)
Index coverage (are new pages being indexed?)
Core Web Vitals (has performance changed?)

Normal expectations:

10-15% traffic dip in the first 1-2 weeks
Rankings may fluctuate as Google reprocesses
Recovery to pre-migration levels within 4-8 weeks

Red flags:

30%+ traffic drop persisting after 2 weeks
Key pages not appearing in search at all
Crawl errors increasing instead of decreasing
New pages not being indexed

Month 2-3: Validate and Clean Up

Confirm all old URLs are redirecting properly
Remove any remaining 404 errors
Check that backlinks are pointing to live pages (or redirecting correctly)
Verify all schema markup is working
Run a full site audit
Compare current organic traffic to pre-migration baseline

Recovery: When Things Go Wrong

If traffic has dropped significantly and isn't recovering:

Step 1: Audit redirects

Crawl old URLs — are they all redirecting to the right places?
Check for redirect chains (more than one hop)
Verify no redirects point to 404 pages

Step 2: Check indexing

In Search Console, check Index Coverage
Are new pages being indexed?
Are old pages being dropped?
Is anything accidentally noindexed?

Step 3: Compare content

Did important content get lost in the migration?
Are title tags and headers different?
Has the page structure changed significantly?

Step 4: Check technical health

Page speed (did it get slower?)
Mobile usability issues
JavaScript rendering problems
Crawl budget issues (if large site)

Step 5: Request re-crawling

Submit updated sitemap in Search Console
Use URL Inspection tool to request indexing of key pages
Be patient — Google needs time to reprocess

The Migration Checklist (Summary)

Pre-migration:

[ ] Full site crawl and documentation
[ ] Identify top-value pages (traffic, backlinks, conversions)
[ ] Build complete redirect map
[ ] Preserve all on-page SEO elements
[ ] Audit staging site thoroughly
[ ] Set up monitoring (rank tracker, analytics alerts)

Migration day:

[ ] Implement all redirects
[ ] Submit new sitemap to Search Console
[ ] Update robots.txt
[ ] Verify tracking codes
[ ] Test critical pages and forms
[ ] Spot-check redirects

Post-migration:

[ ] Monitor daily for first 2 weeks
[ ] Fix 404 errors immediately
[ ] Track ranking and traffic recovery
[ ] Full audit at 30 days
[ ] Confirm full recovery by 60-90 days

One Last Thing

Every migration is stressful. Traffic will dip. Rankings will wobble. You'll find issues you didn't anticipate.

The difference between a successful migration and a disastrous one isn't zero problems — it's catching and fixing problems fast. If you've done the prep work, built a solid redirect map, and have monitoring in place, you'll recover. The businesses that don't recover are the ones that skipped the prep and only noticed the damage months later.