Can you actually merge two sites using the Change of Address feature in Search Console?

What is the difference between migration and site merging?

Google makes a clear technical distinction: the Change of Address is designed for a unique scenario where site-a.com becomes site-b.com, with a direct mapping. This is a pure migration, not a consolidation.

Merging involves a different target architecture. You're integrating multiple domains into one, which necessarily creates multiple redirects to common destination pages. The Change of Address cannot handle this complex topology, it expects a strict 1:1 mapping.

Why does Google impose this limitation?

The Change of Address system treats the source domain as obsolete and transfers trust signals in bulk to the new domain. It's a fast-tracked process that partially bypasses the usual delay in evaluating redirects.

In a merge, multiple source domains coexist temporarily, with heterogeneous redirect patterns. The engine cannot apply the same trust transfer logic: each 301 redirect must be evaluated individually, based on its thematic relevance and structural consistency.

How does Google actually evaluate these redirects?

The recommendation to identify and contact the source sites of the most powerful backlinks reveals something: Google knows that directly updated links transfer their authority better than redirects. A backlink to the final page is worth more than a backlink to a redirected page.

301 redirects retain some PageRank, but introduce a marginal loss and a consolidation delay. The more complex the redirect network (chains, cross redirects), the more this friction increases. That’s why Google advises strict page-to-page mapping.

• Change of Address = single domain migration, accelerated transfer of signals
• Multi-domain merger = classic 301 redirects, individual page evaluation
• Direct backlinks to final URLs > backlinks via redirects in terms of authority transmission
• Precise page-to-page mapping is mandatory: avoid generic redirects to homepage
• Backlink prioritization: contact high Domain Authority referring sites for manual updates

Is this manual approach really scalable?

Let's be honest: manually contacting referring sites only works for high-value backlinks. On a medium-sized site, you potentially have thousands of referring domains. Prioritizing the 20-30 most powerful links makes sense, but beyond that it's impractical.

Google's approach implies that 301 redirects will do the work for the rest. Correct, but you need to anticipate a consolidation delay of several months before all signals are fully transferred. Clients often expect stabilization within 4-6 weeks, but the reality could be more like 3-6 months depending on the size of the site.

What about complex mergers with thematic cannibalization?

Google remains vague on a common scenario: merging two sites that cover partially the same topics. You have site-a.com/seo-guide and site-b.com/seo-tutorial, and you want to consolidate everything onto site-c.com. Which page do you keep? [To be verified] but experience shows that Google rarely penalizes a smart consolidation if the final page provides more depth.

The issue arises when you redirect 5 average pages to 1 consolidated page: Google might interpret this as a manipulation attempt if the final content doesn’t actually add more value. The official recommendation does not cover this scenario, so caution and gradual testing are essential.

Is Google's method complete or minimalist?

This statement describes the strict technical minimum, not an optimal strategy. There is no mention of managing sitemaps during the transition, the pacing of redirects to avoid crawl spikes, or communication with users.

On the ground, successful mergers often include a phase of temporary coexistence (2-4 weeks) where both sites remain active with cross-canonicals before switching to redirects. Google neither validates nor invalidates this approach, leaving a gray area. If you strictly follow the official method (backlink audit + 301 redirect), you are compliant but not necessarily optimal.

What should you do before launching a domain merger?

First critical step: a complete audit of all backlinks from the source sites using a tool like Ahrefs, Majestic, or Semrush. Export the full list, then filter by Domain Rating or Citation Flow to identify the 50 most powerful links.

At the same time, document the URL structure of each source site and define the precise mapping to the target site. A spreadsheet with columns [Source URL | Target URL | Content Type | Traffic Volume] is essential. Each source URL should have a logical destination, never mass redirects to the homepage.

How to technically manage redirects without breaking the site?

Implement 301 redirects at the server level (htaccess, nginx.conf, or through a CDN like Cloudflare). JavaScript or meta-refresh redirects do not properly transmit PageRank according to official guidelines.

Test the redirect file on a staging environment before going live. Ensure there are no redirect chains (A→B→C): each source URL should point directly to its final destination. Chains dilute authority and slow down crawling.

What critical mistakes should be avoided after the switch?

Never remove 301 redirects prematurely. Google recommends maintaining them for at least 1 year, ideally indefinitely. Some backlinks take months to be recrawled, and users may have bookmarks to the old URLs.

Monitor Search Console for 404 or soft 404 errors in the weeks following the merger. A 404 error on a page that received organic traffic signals a failed mapping. Correct it immediately to avoid permanent position loss.

• Export the comprehensive list of backlinks for each source domain
• Contact the 20-50 most authoritative referring sites for manual link updates
• Create a rigorous URL-by-URL mapping (no generic redirects to homepage)
• Implement 301 redirects server-side, test in staging
• Check for the absence of redirect chains (A→B→C)
• Monitor Search Console for at least 3 months after the switch