Why does merging two websites lead to traffic loss even with perfect redirects?

How does a merger actually differ from a standard migration?

A standard migration moves a site from domain A to domain B with a one-to-one URL match. Google follows the 301 redirects, gradually transferring signals, and typically retains 85-95% of the traffic after stabilization.

A merger operates under a different mechanism. You have two sites with two distinct histories, two backlink profiles, two internal linking structures. Google needs to determine which pages from site A correspond (or do not correspond) to pages on site B, how they complement each other, and which ones should be removed.

The engine recalculates the internal PageRank from scratch. What was a strong page on site A could become a weak page on the merged site if the new linking structure does not value it properly. External links still point to the old URLs — through redirects — but their weight dilutes differently.

Why is the combined traffic never the sum of both sites?

Because Google does not perform arithmetic addition. It reevaluates the overall relevance of the new domain for each query. If two pages on the two old sites ranked for the same query, you will not have two positions after the merger — you will have one, possibly ranked lower.

Trust signals (backlinks, age, thematic authority) do not cumulate linearly. A site A with DA 45 and a site B with DA 38 do not yield a merged site with DA 83. Google recalculates the authority of the new domain considering thematic consistency, quality of the linking structure, and potential cannibalization.

Adding to this is the recalculation time: while Google digests the new structure, some pages temporarily lose visibility. This is not a bug — it's the normal functioning of an engine that needs to reevaluate everything.

What specific factors does Google recalculate?

The internal linking structure is the first task. Google tracks every link to understand the hierarchy of the new site. A page that received 50 internal links on site A may only get 10 on the merged site if the architecture changes.

The thematic relevance signals are also reevaluated. If site A was about B2B marketing and site B was about e-commerce, Google must determine if the merged site is generalist or maintains a clear specialization. Thematic dilution causes rankings to drop.

• Recalculation of internal PageRank: every page starts with a score based on the new linking structure, not the old one.
• Reevaluation of search intents: Google determines which page of the merged site should rank for which query — often removing duplicates.
• Consolidation of backlinks: external links go through redirects, which slightly dilutes their weight (approximately 10-15% estimated loss per redirect).
• Crawl and indexing time: Google needs to recrawl the entire new site to understand its final structure, which takes months.
• User signals: CTR metrics, time spent, and bounce rates start over on the new domain.

Is this statement consistent with real-world observations?

Absolutely. I have assisted with about ten mergers over the past few years — none have ever retained 100% of the combined traffic. The best performance observed: 78% of initial traffic after 9 months of stabilization, with a tightly controlled redirect and linking strategy.

The problem is that many clients arrive with the idea that a merger = migration × 2. They expect to add the Analytics curves together. When they lose 30-40% of traffic in the first three months, they panic — when it’s perfectly normal.

Google is not lying here. It describes exactly what is happening on the algorithm side: complete recalculation, reevaluation of relevances, temporary dilution of signals. This is not a penalty — it’s the time needed for the engine to understand the new graph.

What nuances should be added to this claim?

Mueller does not provide any figures. How long does this recalculation take? What traffic loss is “acceptable”? Do certain architectures mitigate damage better than others? [To be verified] — Google remains vague about timelines and concrete metrics.

A rarely discussed point: the merger can also create opportunities. If both sites had complementary backlinks, the merged site can rank on queries that neither dominated alone. But it requires a clear editorial strategy to avoid cannibalization.

Another nuance: the size of the sites matters. Merging two sites of 50 pages each is manageable. Merging two sites of 10,000 pages each is a project of at least 12-18 months with a risk of structural loss if the internal linking is not rebuilt intelligently.

In what cases does this rule not apply — or apply less?

If one of the two sites is nearly dead (negligible traffic, few backlinks, partial indexing), the merger resembles a standard migration. Google doesn’t have much to recalculate — you’re just injecting some pages into an existing site.

Another exception: merging subdomains into the main domain. Technically, this is not really a merger — Google already considers subdomains as linked to the root domain. The recalculation is faster and less violent.

What should you do before launching a merger?

Start with a cross-audit of both sites. Identify the pages that overlap in search intent, those that are unique, those that generate traffic versus those that are dead. A URL mapping table is essential — no merger without this foundation.

Next, reconstruct the target architecture of the merged site. Define the thematic silos, click depth, and pillar pages. If you keep two nearly identical pages, Google will deindex one — it’s better to decide yourself which one to consolidate.

Test the new internal linking before the launch. Use a tool like Screaming Frog or OnCrawl to simulate the linking graph. Ensure that strategic pages receive enough internal juice — otherwise, they will drop even with perfect redirects.

What mistakes should you absolutely avoid during a merger?

Never redirect two distinct pages to a single generic page (like a homepage or overly broad category). Google detects that the match is vague and transfers fewer signals. Worse: it might consider that you are removing relevant content.

Avoid also merging without notifying Google. Submit the sitemaps of both sites with active redirects, use the Search Console to signal the address change if you’re also migrating domains. The more information Google has, the quicker it recalculates.

Another classic mistake: underestimating the time required. A merger takes 6 to 12 months of intensive follow-up. If you stop optimizing after 2 months because "it seems stable", you miss out on critical adjustments that mitigate losses.

How do you measure that the merger is progressing correctly?

Monitor the crawl rate in the Search Console. If Google drastically slows down after the merger, it’s a bad sign — it doesn’t understand the new structure. Increase the publishing frequency, add fresh content to restart the crawl.

Analyze positions by intent cluster, not just overall traffic. A successful merger maintains positions on strategic queries even if long-tail traffic temporarily drops. If your top keywords plummet, there’s an issue with relevance or linking structure.

• Map every URL from both sites with a 1:1 match or a justified consolidation
• Rebuild the internal linking around strategic pages before launch
• Submit sitemaps with active redirects in both Search Consoles
• Audit duplicate content and decide which to merge or remove
• Monitor crawl rates and indexing for a minimum of 6 months
• Track positions by search intent, not just aggregated traffic