Can you really migrate multiple sites to a single domain using Google's Change of Address tool?

What is the Change of Address tool and why does this limitation exist?

The Change of Address tool in Search Console allows you to notify Google that a site has migrated from one domain to another. Specifically, it informs the algorithm that old-domain.com has become new-domain.com, which speeds up the transfer of ranking signals, link equity, and indexing history.

This feature was designed exclusively for a 1:1 scenario. Google has never extended this logic to cases of multi-source mergers (3 or 4 sites to one), likely because these migrations are more complex to validate automatically. Hence, the structure of the tool imposes a strict architectural constraint.

Does this mean that multi-domain migrations are impossible?

No. 301 redirects remain the go-to technical mechanism for any migration, whether 1:1 or N:1. Google crawls the redirects, follows the chains, and progressively transfers the signals. The Change of Address tool is merely a declarative accelerator, not a mandatory technical condition.

The issue is that without a declaration via the tool, tracking the migration becomes opaque. It is impossible to know if Google has properly acknowledged the transfer, how much time it has left, or if errors are blocking the process. You are flying blind, only monitoring traffic trends and server logs.

What are the practical consequences of this limitation?

For a standard migration (rebranding, TLD change), the tool is a valuable ally. It reduces the floating period between the old and new version of the site, limits position fluctuations, and provides a clear signal to the algorithm.

For a merger of multiple sites into a single platform, you must accept that Google will provide no assistance through the interface. No validation, no real-time tracking, no end-of-migration notifications. You will have to rely on indirect metrics: changes in crawl budget, click trends in Search Console, tracked redirects in the logs.

• The Change of Address tool only works to migrate a single source domain to a single target domain.
• 301 redirects remain valid and recommended for any migration, regardless of its configuration.
• Google offers no official tool to track a multi-source migration to a single domain.
• Signal transfer still occurs, but without visibility or declarative acceleration.
• Therefore, you must monitor the migration through server logs, Search Console, and Analytics, without expecting automated feedback from Google.

Is this statement consistent with field observations?

Yes, and it's even a welcome confirmation. Many practitioners believed they could stack multiple Change of Address declarations in series or create a kind of multi-source mapping in the interface. It doesn't work, and Mueller makes that clear.

In practice, we observe that multi-domain migrations take significantly longer to stabilize than 1:1 migrations. Signals do not transfer at the same speed, some source domains retain their residual indexing for weeks, and Google seems to apply a cautionary logic before consolidating equities.

Should this limitation be considered a technical barrier?

Not really. The Change of Address tool is merely a declarative accelerator, not a technical prerequisite. 301 redirects are sufficient; Google crawls them, follows them, and transfers signals. The difference lies in the delay and visibility.

What is missing is a dedicated monitoring tool for complex migrations. Currently, we cobble together Analytics segments, Search Console filters, and server logs exports. [To verify]: Google has never communicated about a project to evolve the tool to handle multi-source mergers, and nothing indicates that it's on the roadmap.

What mistakes should be avoided in this context?

The most common mistake: believing that the absence of a declaration via the tool means that Google will not understand the migration. False. 301 redirects are a sufficient technical signal. Google crawls, follows the chains, and gradually transfers. It's slower, but it works.

Another pitfall: neglecting manual tracking while thinking that an automated tool will do the job. During a multi-source migration, each source domain must be tracked individually, monitor the logs to ensure Googlebot is following the redirects, and compare traffic trends before/after. Without this diligence, it is impossible to diagnose a loss of traffic or a technical blockage.

How to technically manage a multi-source migration to a single domain?

First, map each source URL to its final destination on the target domain. No chain redirects, no generic redirects to the homepage. Each old URL must point to the closest semantic equivalent on the new site. This is time-consuming but essential to preserve link equity.

Next, implement 301 redirects at the server level, not via meta refresh or JavaScript. Nginx, Apache, Cloudflare Workers — regardless of the stack, the important thing is that Googlebot can follow the redirect during the initial crawl. Check the configuration with a crawler (Screaming Frog, OnCrawl) before switching the DNS.

What metrics should be monitored during and after the migration?

First metric: the percentage of redirects followed by Googlebot. Analyze server logs to verify that Google is indeed crawling the old domains, following the 301s, and indexing the new URLs. If the old domains are no longer being crawled after 2-3 weeks, that’s a good sign. If they remain intensively crawled, there’s a problem (undetected redirects, conflicting canonical tags, or outdated sitemaps).

Second metric: the evolution of impressions and clicks in Search Console, compared domain by domain. Filter data by property to isolate each source and compare with trends of the target domain. A sharp drop on an old domain without an equivalent rise on the new indicates a loss of visibility, often linked to a faulty URL mapping.

Should old domains be maintained indefinitely?

No, but redirects should be kept for at least 12 months, ideally 18-24 months for sites with a strong history. Google continues to crawl old URLs for several months after migration, and some backlinks take time to be recrawled. Cutting the redirects too soon means losing some of the accumulated equity.

After this period, you can let the source domains expire — unless you're concerned that a competitor or a squatter may buy them to redirect to spam, which could pollute your backlink profile. In that case, keeping the domains parked with redirects remains a defensive option.

• Map each source URL to a semantically equivalent destination on the target domain, without generic redirects to the homepage.
• Implement 301 redirects at the server level (Nginx, Apache, Cloudflare), and check their proper functioning with a crawler before migration.
• Monitor server logs to confirm that Googlebot is crawling the old domains and following the redirects to the new site.
• Compare trends of impressions/clicks in Search Console between source domains and target domain to detect losses in visibility.
• Keep redirects active for a minimum of 12 months, ideally 18-24 months for sites with a strong history.
• Analyze incoming backlinks to the old domains and, if necessary, contact referring sites to update links to the new domain.