Is it really necessary to use the address change tool for migrating subdomains?

Is the address change tool mandatory for a migration?

No. Google has always treated site migrations by autonomously detecting 301 redirects, without the Search Console tool being essential. This tool is merely an additional signal sent to Google to explicitly indicate your intention to move a site.

The nuance — and it's a significant one — is that the address change tool is only available for complete domain migrations, not for subdomains. If you migrate from blog.example.com to www.example.com/blog, the tool is simply not accessible. Mueller thus confirms what practitioners have observed for years: 301 redirects are technically sufficient.

Why is Google communicating about this point now?

Because many SEOs panic when they realize that the address change tool is not available for their subdomain migration. This statement aims to reassure practitioners: Google does not need an explicit signal to understand that a migration has taken place.

The engine detects 301 redirects, progressively transfers ranking signals (backlinks, authority, content history) to the new URLs, and updates its index. The process is automatic, even if it may be slower than with the address change tool for a complete domain.

What are the risks if we only use 301 redirects?

The main risk is the processing delay. Without an explicit signal, Google has to discover the redirects through crawling, which can take several days to weeks depending on your site's crawl frequency. During this period, you may observe fluctuations in traffic and indexing.

The other risk involves configuration errors. If your 301 redirects are poorly implemented (redirect chains, temporary 302 redirects, 404 URLs), Google may misinterpret your intention and treat it as content removal rather than a migration. This is where the absence of the address change tool becomes a hindrance: you don't have a safety net to correct misinterpretations by Google.

• 301 redirects are the primary technical signal for any site or subdomain migration
• The address change tool is not available for subdomains, only for complete domains
• Google automatically detects and processes migrations through crawling, with no manual intervention needed
• The transfer of ranking signals can take several weeks depending on the size of the site and its crawl frequency
• Incorrect configuration of redirects can lead to sustained traffic loss if Google misinterprets the intention

Is this statement consistent with field observations?

Yes, absolutely. Subdomain migrations without the address change tool are common and generally go well if the redirects are clean. I have assisted numerous migrations from blog.example.com to www.example.com/blog/ without ever using the tool, achieving a complete transfer of signals in 3 to 6 weeks.

Where Mueller is vague is on timelines and guarantees. He doesn't say “it will take X days” or “you'll regain 100% of the traffic.” This vagueness is typical of Google: technically possible, but in reality, there are variables they don't control — and they don't want to formalize publicly. [To be verified]: Does the absence of the tool systematically lengthen the transfer timeline of signals compared to a domain migration with the tool? Public data is lacking on this point.

What nuances should be added to this claim?

The first nuance: Mueller says “correctly” to qualify 301 redirects, but he does not detail what “correctly” means. What does it exactly include? 1-to-1 redirects without chains? An updated XML sitemap on the new domain? Canonical backlinks pointing to the new URLs? The lack of precision creates a dangerous gray area for less experienced practitioners.

The second nuance: the address change tool, when available, does not just “signal” a migration. It also allows you to validate the ownership of both sites in Search Console, which gives Google additional confidence that you are indeed the legitimate owner of both versions. Without this tool, if you migrate a subdomain to a domain you do not fully control (for example, an acquisition by another company), Google may be more cautious in transferring signals.

In what cases does this rule not apply?

If you are migrating a complete domain (not a subdomain), always use the address change tool in addition to the 301 redirects. It’s free, takes 2 minutes, and significantly speeds up the signal transfer process — I’ve observed complete migrations in 10-15 days instead of 4-6 weeks.

Another case: if you are migrating a very large site (tens of thousands of pages) or a site with a low crawl frequency, relying solely on 301 redirects may expose you to several months of delays. In this scenario, proactive actions should be taken to compensate for the absence of the tool: submit the XML sitemap of the new site, request accelerated indexing via the Indexing API (if eligible), and monitor coverage reports daily in Search Console.

What should you do concretely for a subdomain migration?

Implement permanent 301 redirects for each URL from the old subdomain to its exact equivalent on the new domain or subdirectory. No redirect chains, no temporary 302 redirects, and especially no redirects to the homepage if the target URL no longer exists — rather create a semantic equivalent or use a 410 Gone code if the content is permanently removed.

Ensure that both properties (old subdomain and new domain) are verified in Search Console. Submit the XML sitemap of the new structure as soon as the redirects are in place. Monitor the coverage report and 4xx/5xx errors in the following days: any anomalies must be corrected immediately to avoid a misinterpretation by Google.

What mistakes should you absolutely avoid?

Do not leave old URLs in 404 thinking that Google will “understand” on its own. Without 301 redirects, Google interprets this as content removal, not as a migration. You will lose your ranking signals and your organic traffic will collapse.

Avoid removing the old subdomain too quickly. Keep the 301 redirects active for at least 12 months — Google can take several months to transfer all signals, and some external backlinks may take time to be re-crawled. If you cut the redirects after 3 weeks because “it looks fine,” you risk losing late signals.

How to check that the migration is proceeding correctly?

Daily monitor the number of indexed pages on the old and new site via Search Console (site: request in Google or coverage report). You should observe a gradual decline of the old subdomain and a symmetrical growth of the new domain. If the old remains stable or the new does not rise, that's a warning signal.

Also, keep an eye on your positions and organic traffic via Google Analytics 4 and Search Console. A temporary drop of 10-20% over 2-3 weeks is normal during a migration — but if it exceeds 30% or lasts more than a month, there's a technical issue (broken redirects, duplicate content, poorly configured canonicals). Use a position monitoring tool (Semrush, Ahrefs, SE Ranking) to quickly detect URLs losing rankings.

• Implement permanent 301 redirects for each URL, without chains or 302
• Verify both properties in Search Console and submit the XML sitemap of the new site
• Keep the redirects active for at least 12 months after migration
• Daily monitor indexing and 4xx/5xx errors in Search Console
• Monitor positions and organic traffic to detect any lasting anomalies
• Create semantic equivalents for content that cannot be redirected 1-to-1