How can you merge two domains without losing your SEO rankings?

Why does Google recommend a complete migration?

The reasoning is straightforward: when you merge two domains into a third (or into one of the two existing ones), Google must recalculate all signals such as backlinks, thematic authority, crawl history, and behavioral patterns. If you migrate in stages, the engine ends up with three active entities at the same time, each with a portion of the signals.

The issue? Google's algorithms operate through signal consolidation. A domain that gradually receives content does not immediately benefit from the full authority of both sources. Worse, if 301 redirects are incomplete or misconfigured, you create PageRank leaks between the old and new structures.

What do these ranking fluctuations actually mean?

Let's be honest: Google does not specify the magnitude or duration. On-the-ground observations show traffic variations of 20 to 60% for 4 to 12 weeks post-migration. These fluctuations are due to the recalculation of indexes, the reevaluation of temporarily duplicated content, and the redistribution of crawl budget.

The engine also tests consolidated relevance: does the new domain fulfill search intents better than before? If you merge a technical blog with an e-commerce site, Google needs to determine what thematic authority to assign to the result.

What is the concrete risk of a phased migration?

Some SEOs defend the gradual approach to limit risks. The problem: you artificially maintain multiple active domains, which dilutes consolidation signals. Google sees three sites in transition, not a reinforced site.

Technically, partial redirects create redirect chains if you need to make adjustments along the way. And if an old domain remains indexed with active content, you generate duplicate content between the old and new, blurring canonicalization signals.

• Migrate all content in a single operation to expedite the transfer of SEO signals
• Accept temporary fluctuations — this is the normal price of a domain merge, impossible to avoid
• Prepare exhaustive 301 redirects before the switch, mapping each source URL to its final destination
• Monitor crawl budget post-migration: Google will intensify exploration of the new domain for several weeks
• Avoid phased migrations that keep multiple active domains simultaneously and dilute consolidated authority

Is this recommendation consistent with observed practices?

Yes and no. For migrations of small sites (fewer than 5,000 URLs), total migration generally works well. Traffic drops by 20 to 40% for 3 to 6 weeks, then gradually rises. Signals consolidate relatively quickly.

But for sites with 50,000+ URLs or domains with very different backlink profiles, observations are more nuanced. Some total migrations have caused drops of 60%+ for several months, especially when the themes of the two domains were not perfectly aligned. [To be verified]: Google provides no data on the average recovery time based on site size.

What nuances should we introduce to this rule?

Google intentionally oversimplifies. In reality, the migration strategy depends on several variables: site size, thematic consistency, backlink quality, technical architecture. A phased migration may make sense if you need to revamp the architecture profoundly or if the two domains operate in distinct markets.

The real issue with phased migrations is not the progression itself, but chaotic management of redirects and temporarily duplicated content. If you master canonicals, redirects, and controlled de-indexing of the old domain as you go, a phased migration can mitigate business risks while preserving some SEO.

In what cases does this rule not apply?

When merging a testing or staging domain into production: here, a gradual migration makes no sense since the source domain never had organic traffic. Another exception is international migrations where multiple ccTLDs are consolidated into a gTLD with hreflang — a simultaneous total switch across 10 countries can create unmanageable technical chaos.

Finally, if you merge two domains with unresolved manual or algorithmic penalties, total migration will transfer negative signals along with the positive ones. In this case, it is better to clean up before consolidating. [To be verified]: Google remains vague on the transfer of penalties during migrations.

What should you do concretely before the migration?

Before making any changes, thoroughly map both domains: complete crawl, inventory of indexed URLs, analysis of priority backlinks, identification of traffic-generating pages. Then, create a 1:1 redirect matrix — each source URL must point to a specific destination, not defaulting to the homepage.

On the technical side, prepare the server redirect files (nginx, Apache, or CDN rules) and test them in pre-production. Configure canonical tags on the new domain to avoid any ambiguity. Export your GA4 and Search Console data from the last 12 months: you will need precise benchmarks to measure impact.

What critical errors should be avoided?

The classic mistake: redirecting en masse to the homepage or a few generic categories. Google detects this pattern and may ignore some redirects, considering them disguised soft-404s. Result: loss of PageRank and rankings on long-tail terms.

Another pitfall: not actively de-indexing old domains after migration. If you leave source content accessible for weeks, Google continues to crawl both versions, diluting signals and slowing consolidation. Use noindex tags + robots.txt to progressively shut down the old domain once the redirects are active.

How can you verify that the migration is going smoothly?

Monitor three critical metrics in Search Console: crawl rate of the new domain (it should increase significantly), 404 errors (any spike reveals missing redirects), and the evolution of impressions per query. If key URLs lose 80%+ of their impressions after two weeks, check the redirects and canonicals.

Also, use server logs to trace Googlebot's activity: the engine should intensify exploration of the new domain within 48-72 hours post-switch. If this is not the case, it means consolidation signals are not detected (probably a redirect or sitemap issue).

• Thoroughly map both domains: complete crawl, backlinks, high-traffic pages
• Create a 1:1 redirect matrix — no URL should redirect to the homepage by default
• Test redirects in pre-production before the actual switch
• Configure canonicals on the new domain to avoid any indexing ambiguity
• Actively de-index the old domain post-migration (noindex + robots.txt) to speed up consolidation
• Monitor Search Console and server logs for at least 8 weeks after migration