Do you really need the address change tool to migrate between subdomains?

Why does Google make this distinction between domains and subdomains?

The address change tool was designed to manage signals at the root domain level. When you switch from old-site.com to new-site.com, you completely change your identity in Google’s eyes.

Historical signals — authority, backlinks, trust — need to be explicitly transferred. This is where the tool comes into play: it speeds up the process by signaling to Google that the two domains are related and that the old one should be replaced by the new one in the index.

In contrast, subdomains already share the same root domain. Google treats them as distinct entities for crawling and indexing, but they benefit from common recognition at the main domain level. A migration between m.domain.com and www.domain.com remains within the same

Is this statement consistent with field observations?

Yes, and it’s even reassuring. Hundreds of migrations between subdomains have been conducted without using the address change tool, with perfectly normal results. No abnormal ranking loss, no extra delay in the consolidation of signals.

On the other hand, some SEOs attempted to use the tool “out of caution” during m. → www. migrations and found… absolutely no difference. The tool does not actually return any specific errors or confirmations in this context — it seems simply ignored by Google.

What really matters is the quality of the redirects, updating the sitemaps, and ensuring that all old URLs return a clean 301 code. The rest is cosmetic.

In what cases could this rule cause problems?

Let’s be honest: this statement remains quite general. It does not explicitly cover certain edge cases. For example, what happens if you migrate simultaneously from m.old-domain.com to www.new-domain.com? Changing both the subdomain AND the root domain.

In this hybrid scenario, [To be verified] if the address change tool should point the old root domain to the new one, or if the 301 redirects are still sufficient. Google does not specify this particular case, and feedback from the field is rare.

Another gray area: completely independent subdomains (blog.domain.com, shop.domain.com) merging into www.domain.com/blog and www.domain.com/shop. Technically, it’s still a migration between subdomains, but the structure of information changes radically. The redirects must be ultra-precise, and careful monitoring in Search Console becomes essential.

What nuances should be added to this statement?

Mueller talks about “signals at the domain level,” but does not detail which ones exactly. We know that trust, overall authority, and some historical signals are attached to the root domain. But what about manual penalties? Anti-spam actions?

If a subdomain has been penalized, that penalty does not automatically transfer via the address change tool anyway — it’s attached to the URL, not the root domain. But Google never clarifies this point in this context.

Another missing element: the consolidation timeframe. Mueller does not say if using the tool accelerates or not the transfer during a real domain change. Tests show that the impact is marginal, but Google does not publish any numerical data on this.

What should you actually do when migrating between subdomains?

First step: set up permanent 301 redirects for each URL from the old subdomain to its equivalent on the new one. No temporary redirects (302), no chain redirects (m. → temp. → www.), and most importantly, no orphan pages returning 404.

Next, submit a new XML sitemap in Search Console for the new subdomain. Remove or disallow the old sitemap of the source subdomain. Google needs to understand that the content is now elsewhere.

Check that the old URLs do not generate any crawl errors in Search Console. The redirects must be immediate, return a HTTP 301 code, and point to the correct final URL — not to a generic page or a homepage.

What mistakes should you absolutely avoid?

Never leave the old URLs accessible alongside the new ones. This is guaranteed content duplication. If m.domain.com/page and www.domain.com/page both respond with 200, Google has to choose which one to index — and that choice will not always be the one you want.

Avoid also abruptly deleting the old subdomain before Google has had time to recrawl all the redirects. Keep the redirects in place for at least 6 months, ideally 12 months, so that external backlinks are well consolidated.

Another common mistake: not updating the internal links that still point to the old subdomain. Even with redirects in place, it wastes crawl budget and degrades quality signals.

How can you verify that the migration went well?

Monitor the coverage report in Search Console. The old URLs should slowly change to “Redirected” and disappear from the index. The new URLs should be indexed without error.

Compare average positions and organic traffic before/after migration. A temporary drop of 10-15% is normal while Google consolidates signals. If the drop exceeds 30% or persists for more than 4-6 weeks, there is a structural problem to identify.

Finally, check the server logs to confirm that Googlebot is crawling the new URLs correctly and following the redirects. An initial crawl spike on the old subdomain followed by a gradual transfer to the new one is the expected behavior.

• Set up permanent 301 redirects for each URL from the old subdomain
• Submit a new XML sitemap for the new subdomain in Search Console
• Check that all old URLs return a proper 301 code and no 404 errors
• Update all internal links to point directly to the new URLs
• Monitor the coverage report in Search Console for at least 3 months
• Compare organic traffic and positions before/after migration to spot any anomalies