Should you really use the address change tool when migrating between subdomains?

What is the true purpose of the address change tool?

The address change tool in Search Console is used to inform Google about a complete domain name change — for example, from old-site.com to new-site.com. Its role: to speed up the transfer of signals at the root domain level (authority, history, reputation).

What matters here: the tool operates at the main domain level, not at the subdomain level. Google treats subdomains as distinct entities in terms of crawling and indexing, but they share the reputation of the root domain. Therefore, the tool does not manage these internal nuances.

Why doesn’t moving between subdomains require this tool?

When migrating from m.example.com to www.example.com, you remain on the same root domain (example.com). Google does not need a specific signal to understand that it is an internal reorganization.

Permanent 301 redirects are more than sufficient. Crawling will follow the redirects, transferring PageRank URL by URL, and consolidating the signals. The address change tool would add no value — it is designed for cases where the root domain changes entirely.

In what cases should the address change tool really be used?

The tool is relevant only for a complete domain change: old-domain.com to new-domain.fr, or example.net to example.com. In these scenarios, you ask Google to transfer all authority and history from the source domain to the target domain.

Even then, the tool is not magic. It accelerates the process, but correct 301 redirects remain the essential technical foundation. Without proper redirects, the tool won’t compensate for anything — it simply confirms your intention to Google.

• The address change tool only transfers signals at the main domain level, not subdomains
• A migration between subdomains (m.example.com → www.example.com) only requires well-configured 301 redirects
• The tool applies to complete domain changes (old-site.com → new-site.com), not internal reorganizations
• Even with the tool, 301 redirects remain the essential technical foundation — the tool does not replace anything

Is this statement consistent with field observations?

Yes, and it is confirmed by hundreds of observed migrations. 301 redirects between subdomains work exactly like classic internal redirects. The transfer of PageRank and signals happens URL by URL, with no significant loss if the structure is clean.

What still surprises some practitioners: Google treats subdomains with a certain autonomy in crawling and indexing, but not in authority. The root domain acts as a safety net — a subdomain benefits from its reputation but does not need a specific tool to transfer its URLs to another subdomain of the same parent.

What nuances should be considered based on context?

If your migration involves a massive historical subdomain (for example, 500,000 URLs from blog.example.com to www.example.com/blog/), the absence of the tool changes nothing — but your redirect plan becomes critical. A mapping error can cost a lot in traffic.

Another point: some practitioners use the tool "just in case" during subdomain migrations. [To be verified] Google claims it is unnecessary, but no public data shows a negative impact from using it incorrectly. In doubt, focus on redirects — that's where everything happens.

In what cases might this rule not apply?

If you are migrating a subdomain that was set up as a separate Search Console property with a distinct history (link disavowals, manual penalties, specific settings), ensure that these configurations do not get lost. The address change tool does not transfer them — you will need to reconfigure them manually.

Edge case: migrating a subdomain to a totally different domain (blog.example.com → new-blog.fr). Here, you step outside of Mueller's statement — it's a real domain change, and the tool becomes relevant.

What should you concretely do during a migration between subdomains?

Absolute priority: a comprehensive and tested 301 redirect plan. Each URL from the old subdomain must redirect to its semantic equivalent on the new one. Avoid cascading redirects (A → B → C) — they dilute PageRank and slow down crawling.

Set up both subdomains (old and new) as distinct properties in Search Console. This allows you to monitor crawling, 404 errors, and the indexing transition. Google recommends keeping redirects active for at least 6 months — some practitioners maintain them indefinitely to avoid losing dormant backlinks.

What mistakes should you absolutely avoid?

Classic mistake: redirecting all URLs from the old subdomain to the homepage of the new one. You immediately lose the granularity of PageRank, and the user experience is catastrophic. Google may even interpret this as soft 404s.

Another trap: forgetting to update internal links that pointed to the old subdomain. Redirects work, but they create unnecessary latency and dilute internal juice. An internal crawl post-migration must validate that all links point to the new URLs.

How can you check that the migration is proceeding correctly?

Closely monitor the Search Console metrics: indexed pages, impressions, clicks. A temporary drop (10-15 days) is normal — the time it takes for Google to recrawl and consolidate. If the drop exceeds 20% after 3 weeks, dig deeper: redirect errors, poorly configured canonical tags, or crawl budget issues.

Also, keep an eye on your positions on strategic queries. A well-executed migration should not impact ranking beyond a normal fluctuation. If key URLs lose their positions abruptly, check that the redirects point to the correct target pages and that the content has not changed.

• Map each URL from the old subdomain to its exact equivalent on the new one (1:1 mapping required)
• Implement permanent 301 redirects, never 302 or meta refresh
• Add both subdomains as separate Search Console properties to monitor the transition
• Update all internal links to point directly to the new URLs
• Check the XML sitemaps: remove old URLs, add new ones
• Keep redirects active for at least 6 months, ideally longer