Consultancy

SEO Migration: migrate without avoidable ranking loss

By Miguel Maio ·

A migration is the moment when a site can lose years of traffic in an afternoon. Changing platform, domain or URL structure, or moving to HTTPS, looks technical and harmless - and it's where I see the most damage. The good news: almost every loss is avoidable, with method.

A site's highest-risk moment

The numbers are harsh and worth facing head-on: 60-80% of migrations lose significant traffic and only around 1 in 10 improves rankings (agency studies). 50% losses are common and, in severe cases, reach 80-90%. WooCommerce lost over 90% of organic visibility moving to the Woo.com domain; one retailer lost roughly £3.8 million in the first month by ignoring redirect recommendations. Recovery, when it happens, takes 6 to 12 months.

Be honest with yourself: even a well-executed migration usually sees 5-15% volatility in the first 2-4 weeks - that's normal and it recovers. What isn't acceptable is the structural loss that stays. That's the goal of my work: zero structural loss at 90 days.

The errors that cause the losses

They're almost always avoidable, and almost always the same: an incomplete or missing redirect map, 302 (temporary) instead of 301 (permanent), redirect chains and loops, URLs changed without 301s, important content removed in the process, broken hreflang, mispointed canonicals, outdated sitemaps and - the classic - redirecting everything to the homepage "to keep it simple".

The migrations I handle

Platform or CMS changes (WordPress, Shopify, Webflow, Magento, headless, custom), domain or brand changes, HTTP to HTTPS, URL or information-architecture restructures, consolidating several sites into one, and redesigns that change URLs. In all of them the risk is the same - and so is the method.

The method to reduce avoidable losses

Step by step, with validation at each phase:

  1. Baseline before touching anything: a full inventory of URLs, traffic, rankings, highest-value pages and best backlinks
  2. A prioritized 1:1 redirect map (old URL → closest equivalent), no chains and not pointing everything at the home
  3. Staging validation: full crawl, headers, status codes, canonicals, hreflang and structured data
  4. A controlled launch: correct 301s, new sitemaps submitted and, if the domain changes, Change of Address in Search Console
  5. Daily post-launch monitoring (indexing, errors, logs, rankings) to catch problems in hours, not weeks

Tools I use

Screaming Frog for the before/after crawl and URL comparison (what existed vs. what exists), Google Search Console (Coverage, URL Inspection and Change of Address), redirect testers to catch chains and improper 302s, log analysis to see what bots do post-launch, and backlink data to prioritize the pages that can't lose authority.

What's included

  • Pre-migration baseline (URLs, traffic, rankings, backlinks)
  • A prioritized, chain-free 1:1 redirect map
  • Technical requirements for the development team
  • Full staging validation before launch
  • Launch plan and go-live checklist
  • Post-launch monitoring and fixes

How I work

  1. Diagnosis and baseline of the current site
  2. Redirect map and requirements, reviewed with the team
  3. Staging validation - nothing goes live without passing
  4. Support during launch
  5. Daily monitoring in the first weeks, and adjustments

Who it's for

For anyone changing platform, domain or URL structure who can't afford to lose the traffic they've built - e-commerce, publishers, brands with organic history. It's also for anyone who has already migrated, lost traffic and needs to recover. It isn't for trivial migrations of a handful of pages, where a good redirect map is enough.

Proof

I've run and overseen platform and domain migrations for clients, in consulting and agency settings - the kind of project where a botched redirect costs months of traffic and where preparation is everything. I take a very limited number of clients at a time, because a migration demands focus and presence at launch.

Sources

See also Technical SEO and GEO.

FAQ

Frequently asked questions

I'm changing platforms. Will I lose traffic?

You don't have to. Most losses come from avoidable errors - missing redirects, 302 instead of 301, URLs changed with no plan. With a baseline, a 1:1 map, staging validation and monitoring, the goal is zero structural loss. Expect 5-15% volatility in the first weeks, which recovers. Get in touch →

Can I just redirect everything to the homepage?

No. Mass-redirecting to the home is one of the errors that destroys the most traffic - Google treats it almost like a 404. Each old URL should point to its closest equivalent (a 1:1 redirect). See Technical SEO →

When does traffic recover?

If the migration is done well, the first 2-4 weeks of volatility recover within 1-3 months. If errors are left unresolved, recovery can take 6-12 months - which is why the preparation and post-launch monitoring are everything. Get in touch →

Do you work with the development team on the migration?

Yes. I hand over the redirect map and technical requirements in an executable, testable format, and validate in staging before launch. A migration is teamwork, not a document handed over and forgotten. Get in touch →

Migrating? Talk to me before, not after.

The work that prevents losses happens before launch. Tell me what you're migrating and I'll propose the safe path.

Let's talk