Reading time: 4 min
Key takeaways
- All variants matter: For any domain migration, you must submit a Change of Address request for every subdomain, www, and non-www version of the old domain—even if you don’t actively use them.
- Verification required first: Each variant must be verified in Google Search Console before you can submit its Change of Address request.
- Signals are stranded otherwise: Unmigrated variants can retain independent ranking signals in Google’s index, leaving SEO equity behind and weakening your new domain’s performance.
Google made a quiet documentation update. It changes everything for site moves.
Let me show you the data. I’ve seen site migrations go sideways more times than I can count. Usually it’s the same story: a team migrates from old-domain.com to new-domain.com, submits a single Change of Address request for the primary version, and wonders why rankings tank on the other side. Here’s what actually happened.
Google revised its site migration documentation in June 2026. The update is small—a single paragraph in a support article—but the implication is massive. The company now explicitly states that when moving from one domain to another, you must submit Change of Address requests for all subdomains and both www and non-www variants of the old domain name.
Not just the one you think is canonical. All of them.
The example that hits hardest: en.example.com, www.example.com, example.com
Google’s documentation gives this specific case: if you’re migrating to new-example.net, you need to submit Change of Address requests from en.example.com, www.example.com, and example.com. All three. Not just the one that redirects to your canonical. Not just the version with the most traffic. Every property that has ever been indexed under that domain.
This isn’t a take—it’s a pattern. I’ve walked through audits where a client migrated their main domain but forgot a subdomain used for a blog or a regional site. The result? That subdomain’s traffic vaporized, and Google never transferred the link authority to the new site. The playbook changed. Again.
Why unused variants still carry SEO weight
Nobody talks about this part. Many site owners assume that if www.example.com redirects to example.com, the www variant is irrelevant. It’s not. Google’s index can retain independent records for both. Over years, each variant may have built its own set of backlinks, crawled signals, and even content snapshots—especially if different servers responded differently to Googlebot at any point.
When you migrate only the primary URL, those secondary records remain in the index, orphaned from the new domain. Your site migration isn’t complete until every variant is formally told where to go.
Slow down. Think. How many subdomains does your old domain have? Test each one in Google Search Console. If you see data for en., es., or blog., they need their own Change of Address requests. Every single one.
Verification is the gating step—don’t skip it
Before you can submit a Change of Address request for any variant, you must verify that variant in Google Search Console. This means adding a TXT record or DNS entry for www.your-old-domain.com, for the non-www version, and for every subdomain. If you haven’t verified these properties—even the ones you consider secondary—Google won’t accept your requests.
I’ve seen teams spend days debugging a stalled migration only to find that the www variant was never verified. That one step can delay your entire move by a week or more. Do it upfront.
This is a clarification, not a new technical feature
As Barry Schwartz noted on Search Engine Roundtable back in June 2026, this documentation update doesn’t change how the Change of Address tool actually works under the hood. Google hasn’t launched a new feature. What changed is the explicitness of the guidance. The tool always accepted multiple requests, but the documentation never told you that you needed to submit them for every variant.
Here’s why that matters: if you’re planning a migration right now, the old way of thinking—one request, done—is no longer defensible. Every SEO audit for a domain move should now include a checklist item that reads: “Verify all domain variants and submit Change of Address for each.” If you’re not doing that, you’re leaving signal on the table.
How to act on this today
Let me give you the practical steps. Before your next domain migration:
- Audit all variants: List every subdomain and URL prefix that ever served content under your old domain. Use a crawl tool or check your DNS records for subdomain.
- Verify each in Search Console: Add each property as a separate site in Google Search Console and complete verification via DNS or HTML file.
- Submit Change of Address requests: For each verified variant, use the Settings > Change of Address tool to point it to the corresponding URL on the new domain.
- Monitor after migration: Check the new domain’s performance in Search Console for at least 30 days. If traffic doesn’t recover, verify that all old variants were migrated and that redirections are still in place.
This isn’t optional anymore. Google made the rule explicit. I’ve seen migrations fail because teams skipped this step. Don’t be that team.
Building websites since before Google existed. I’ve run SEO, growth, and content for startups across California — and I’ve watched every ‘revolutionary’ tactic eventually expire. What doesn’t expire: understanding systems, compounding effort, and thinking slower than everyone else.