Website Migration Guide: Move Without Losing Rankings

Whether you're switching platforms, redesigning your site, changing domains, or moving to HTTPS, a website migration requires careful planning. The stakes are real: businesses have lost 30-60% of their organic traffic from botched migrations that could have been avoided with proper preparation.

Types of Website Migrations

Not all migrations are equal. The complexity and risk depend on what's changing:

• Platform migration — moving from WordPress to a custom build, or Shopify to WooCommerce. URL structures often change.
• Domain migration — changing from olddomain.com to newdomain.com. The highest-risk migration type.
• Protocol migration — HTTP to HTTPS. Low risk if handled correctly, but still requires redirects.
• Redesign migration — same platform, new design. Risk depends on whether URLs and content structure change.
• Hosting migration — moving to a new server or hosting provider. Lowest risk if DNS is handled properly.

For context on choosing the right platform before migrating, see our guide on Choosing the Right Tech Stack.

Pre-Migration Planning

The work before the migration matters more than the migration itself. Spend 80% of your effort here.

1. Crawl and Audit Your Current Site

Before changing anything, document what you have. Use a crawler (Screaming Frog, Sitebulb, or similar) to capture:

• Every URL on your current site
• Page titles and meta descriptions
• Internal link structure
• Current rankings for key terms
• Pages with the most organic traffic (Google Analytics or Search Console)
• Inbound links from external sites (Ahrefs, Moz, or Search Console)

This becomes your baseline. You'll compare post-migration data against it to identify problems.

2. Map Old URLs to New URLs

This is the most critical step. Every URL on your old site needs a destination on your new site. Create a spreadsheet:

• Column A: Old URL
• Column B: New URL
• Column C: Redirect type (301 permanent)
• Column D: Monthly traffic (prioritize high-traffic pages)

If a page is being removed entirely, redirect it to the most relevant existing page — not the homepage. Homepage redirects for everything signal to Google that you didn't plan properly.

3. Preserve Your Content

Content is what Google ranks. If your migration changes content significantly, expect ranking fluctuations. Keep:

• Page titles and H1 tags as close to original as possible
• Meta descriptions intact or improved
• Body content preserved — don't "clean up" high-ranking pages
• Image file names and alt text consistent

4. Set Up a Staging Environment

Build the new site on a staging server. Test everything before going live:

• All redirects work correctly
• No broken internal links
• Forms, checkout flows, and interactive elements function
• Mobile responsiveness is intact
• Page load speed meets targets

Redirect Strategy

Redirects are the bridge between your old site and your new site. Get them wrong, and Google loses the connection between your established rankings and your new pages.

301 Redirects: The Standard

Use 301 (permanent) redirects for all URL changes. A 301 tells search engines: "This page has permanently moved to a new location. Transfer the ranking signals."

Common Redirect Mistakes

• Using 302 instead of 301 — 302 is temporary. It tells Google the old URL might come back, so ranking signals aren't fully transferred.
• Redirect chains — Page A redirects to Page B, which redirects to Page C. Each hop loses some SEO value. Go directly from A to C.
• Missing redirects — Every old URL must redirect somewhere. Crawl your old site thoroughly to catch them all.
• Blanket redirects to homepage — Lazy and harmful. Redirect each page to its most relevant counterpart.

Migration Day Execution

When it's time to flip the switch:

1. Choose low-traffic timing — Saturday morning or late evening. Not Monday at 9 AM.
2. Implement redirects first — before DNS changes propagate
3. Update DNS records — if changing hosts or domains
4. Verify redirects — spot-check your top 50 URLs manually
5. Submit new sitemap — in Google Search Console immediately
6. Request indexing — for your most important pages
7. Monitor crawl errors — watch Search Console for 404s and redirect issues

Post-Migration Monitoring

The migration isn't done when the new site goes live. The next 90 days are critical.

Week 1: Damage Control

• Check Google Search Console daily for crawl errors
• Monitor organic traffic in Google Analytics
• Fix any 404 errors immediately
• Verify all redirects are functioning

Weeks 2-4: Stabilization

• Track ranking changes for target keywords
• Monitor indexed page count in Search Console
• Check for duplicate content issues (old and new URLs both indexed)
• Update external links where possible (social profiles, directories, partners)

Months 2-3: Recovery Assessment

• Compare organic traffic to pre-migration baseline
• Identify pages that haven't recovered and investigate
• Monitor Core Web Vitals for performance regressions
• Continue fixing redirect issues as they surface

A well-executed migration typically sees a 10-20% traffic dip in the first few weeks, followed by full recovery within 2-3 months. If you're still down after 3 months, something went wrong.

When to Hire Help

Small sites with 50 pages? You can probably handle the migration yourself. But if your site has:

• 500+ pages
• Significant organic traffic (10,000+ monthly sessions)
• Complex URL structures with parameters
• E-commerce with product pages, categories, and filters
• Multiple subdomains or international versions

Invest in professional help. The cost of a botched migration far exceeds the cost of doing it right the first time.

Related Reading

• Choosing the Right Tech Stack
• Technical SEO Checklist
• Website Launch Checklist