Does the Search Console address change tool really work for all migrations?

Why does Google limit this tool to complete domains?

The address change tool in Search Console was designed with a binary logic: an entire site shifts from domain A to domain B. This approach simplifies processing on Google's end, allowing them to propagate the redirect signal throughout their index for that domain.

When you are migrating only a part of a site — for example /blog/ or /shop/ — the situation becomes more complex. Google then has to manage two entities simultaneously: the old domain, which remains partially active, and the new one which picks up a fraction of the content. The algorithm cannot apply a blanket transfer rule.

What exactly constitutes a complete domain move?

A complete move means that all content from example.com switches to newdomain.com. Each URL from the old domain finds its counterpart in the new one through a structured 301 redirect. No page remains active on the old domain after migration.

This definition excludes hybrid migrations where you keep part of the content on the old domain. It also excludes the consolidation of multiple subdomains into a main domain, or vice versa. If your final architecture retains active URLs on the old domain, you fall outside the scope of this tool.

Are subdirectories completely ignored by the tool?

Yes, and this is a point that many practitioners discover too late. If you redirect example.com/section/ to newsite.com, the address change tool will not track that transition. Google will treat these redirects like any other 301s, without any special priority in crawling.

You will need to monitor migration by other means: tracking impressions and clicks in Search Console for both properties, analyzing server logs to check crawl frequency, and monitoring positions on your key queries. The process becomes manual and requires heightened vigilance for several weeks.

• The address change tool only works for complete domain migrations
• Redirects of subdirectories do not receive any priority processing through this tool
• A partial migration requires manual monitoring via Search Console, logs, and analytics
• Google considers "significant movement" solely the complete switch of one domain to another
• Hybrid migrations or complex consolidations are beyond the scope of this tool

Does this limitation align with real-world observations?

Absolutely. I have assisted in migrations where teams attempted to use the tool for partial migrations, hoping for a ranking transfer boost. The result: no visible effect and sometimes confusion in tracking metrics. The tool simply does not send a signal when the structure does not match its binary model.

What is even more surprising is that Google does not technically block the use of the tool in these cases. You can attempt to activate it for a partial migration, but it will remain ineffective. There is no clear error message, just a lack of results. [To be verified]: Google could improve UX by detecting and reporting incompatible configurations.

Should you always use this tool for every domain migration?

Yes, but with an important nuance. The tool speeds up the propagation of the signal of change in the index, which may reduce the period of fluctuation where your positions vary. However, it does not replace a proper implementation of 301 redirects and does not guarantee automatic maintenance of positions.

In my practice, I have observed technically well-executed migrations that still suffered temporary traffic losses despite using the tool. The quality of URL redirects, the preservation of internal structure, and the crawl speed of the new domain often matter more than activating this feature in Search Console.

What pitfalls should you watch for during a complete domain migration?

The first pitfall: believing that the address change tool does the work for you. It does not replace a rigorous, URL-by-URL redirect plan. I have seen sites lose 40% of their traffic because 15% of URLs pointed to undetected 404s before launch.

The second common mistake: activating the tool before redirects are stable. If Google crawls the new domain and finds errors or inconsistencies, the signal sent will be noisy. Wait until you have at least 48 hours of clean redirects and check logs to confirm that Googlebot is correctly following your 301s.

How do you manage a complete domain migration with this tool?

Before activating the address change tool, ensure that your new domain is already verified in Search Console. Google requires that you have owner rights on both domains. Next, implement your 301 redirects and test them on a representative sample of URLs.

Activate the tool only when you see in your server logs that Googlebot has correctly followed the redirects for at least 24 to 48 hours. This caution prevents sending a premature signal that may create confusion in the index. Daily monitor impressions on both properties for the first three weeks.

What should you do if your migration involves only a subdirectory?

Forget the address change tool, it will not be useful. Focus on a perfect implementation of 301 redirects and manual monitoring. Create segments in Google Analytics to isolate traffic from the migrated section and compare before/after.

In Search Console, use page filters to track specifically the URLs of the old subdirectory and their equivalents on the new domain. Export impression and click data weekly to quickly detect any anomalies. This artisanal approach requires more rigor, but it is the only viable option.

What mistakes should you absolutely avoid during a migration?

Never leave the old domain in double indexing with the new one. If Google continues to crawl and index the old URLs without redirection, you create a canonicalization conflict that dilutes your ranking signals. Check the index via site searches to ensure that the old URLs gradually disappear.

Avoid also changing the URL structure simultaneously along with the domain. An ideal migration should maintain the relative path of URLs: example.com/category/page becomes newdomain.com/category/page. If you simultaneously alter the structure, you increase the risk of error and complicate diagnosis in case of problems.

• Validate both domains (old and new) in Search Console before any actions
• Implement and test all 301 redirects before activating the address change tool
• Wait 48 hours for stable redirects and check server logs to confirm Googlebot's monitoring
• Daily monitor impressions and clicks on both properties for at least 3 weeks
• For partial migrations, abandon the tool and build a manual monitoring dashboard
• Avoid any simultaneous modification of URL structure when changing domains