Migrating Sites Without Losing Rankings: A Step-by-Step Guide

Site migrations are the scariest thing in SEO. I've seen companies lose 50% of their organic traffic overnight from botched migrations. Rankings they spent years building, gone in a day.

But I've also run migrations that went smoothly. Traffic dipped for a week, then recovered and grew. The difference isn't luck. It's preparation.

What Counts as a Site Migration

Migration isn't just moving hosts. Any of these is a migration:

• Changing domain names
• Switching from HTTP to HTTPS
• Moving to a new CMS or platform
• Major URL structure changes
• Redesigning with significant content changes
• Merging multiple sites into one
• Splitting one site into multiple

Each carries SEO risk. The more things change at once, the higher the risk.

Pre-Migration: The Critical Phase

Most migration problems happen because of poor preparation. Spend more time here than you think you need.

1. Crawl and Document Everything

Before touching anything, crawl your entire site with Screaming Frog or similar. Export:

• All URLs
• Page titles and meta descriptions
• H1s and H2s
• Internal links
• Canonical tags
• Response codes
• Word counts

This is your baseline. You'll compare the new site against this.

2. Identify Your Most Important Pages

Pull from Google Analytics and Search Console:

• Top pages by organic traffic
• Top pages by conversions
• Pages ranking for valuable keywords
• Pages with the most backlinks (check Ahrefs or similar)

These pages get extra attention. If something goes wrong with your top 50 pages, you feel it immediately.

3. Build Your Redirect Map

This is the most important deliverable. A spreadsheet mapping every old URL to its new URL.

Format:
Old URL | New URL | Status Code | Notes

Every single indexed page needs a destination. No exceptions. If a page is being removed, decide: redirect to most relevant alternative, or let it 404 (only for truly worthless pages).

Common patterns:

• 1:1 redirects (old page → new equivalent)
• Many:1 redirects (consolidating similar pages)
• Category changes (/blog/post → /articles/post)

4. Check for Redirect Chains

If your current site already has redirects, don't create chains. A → B → C → D loses link equity at each hop and slows crawling.

Update old redirects to point directly to the final destination.

5. Set Up Monitoring Before Migration

You need to know immediately if something breaks:

• Rank tracking for top keywords (daily during migration)
• Google Search Console access for both old and new properties
• Uptime monitoring
• Log file analysis setup

Migration Day: Execute Carefully

Implement All Redirects

Use 301 redirects for permanent moves. 302s don't pass link equity the same way and signal temporary changes.

Test every redirect before going live. Automated tools can help but spot-check important pages manually.

Update Internal Links

Don't rely solely on redirects for internal links. Update them to point directly to new URLs. This:

• Reduces server load
• Improves page speed
• Signals to Google these are permanent changes

Submit New Sitemap

Update your XML sitemap with new URLs. Submit to Search Console. If you're changing domains, submit to both old and new properties.

Update Google Search Console

If changing domains, use the Change of Address tool in Search Console. This tells Google explicitly about the move.

Update Canonical Tags

All canonical tags should point to new URLs. A common mistake: redirecting pages but leaving canonicals pointing to old URLs.

Check Robots.txt

Make sure robots.txt on the new site allows crawling. Many staging sites block crawlers and that config accidentally goes live.

Post-Migration: Monitor Aggressively

Week 1: Daily Checks

• Crawl errors in Search Console (check every day)
• Index coverage (are new pages getting indexed?)
• Ranking changes for top keywords
• 404s from redirect misses
• Server logs for crawl activity

First Month

• Compare traffic week-over-week
• Monitor impressions and clicks in Search Console
• Check crawl stats (is Googlebot crawling at expected rate?)
• Look for soft 404s (pages returning 200 but with error content)

Common Post-Migration Problems

Traffic drops: Some drop is normal. Google needs time to process changes. Panic threshold is 30%+ sustained drop after 2 weeks.

Pages not indexing: Check if they're blocked by robots.txt or noindex. Check canonical tags. Check if redirects are working.

Redirect loops: A redirects to B, B redirects to A. Nothing loads. Test redirects thoroughly.

Mixed content: After HTTPS migration, HTTP resources cause security warnings. Scan for mixed content and fix.

Domain Change Specific Considerations

Changing domains is the highest risk migration. Additional steps:

• Keep old domain active with redirects for at least 1 year
• Use Search Console's Change of Address feature
• Update backlinks where possible (reach out to top linking sites)
• Update all brand mentions and citations
• Expect 6-12 months for full recovery

Don't change domains unless you have a compelling reason. The SEO cost is real.

What Success Looks Like

Realistic expectations:

• Week 1-2: 10-30% traffic drop (normal)
• Week 3-4: Recovery begins
• Month 2-3: Back to pre-migration levels
• Month 4+: Traffic should match or exceed previous performance

If you're not recovering by week 4, something is wrong. Audit redirects, check for technical issues, and review Search Console errors.

Migrations don't have to be disasters. Plan meticulously, execute carefully, monitor obsessively. The sites that fail are the ones where someone said "we'll figure out redirects later." There is no later. Do it right from the start.