Google today updated its site move documentation to require the use of the Change of Address tool for all subdomain variants when migrating a domain - a quiet but meaningful fix for a gap that has long caught webmasters off guard during domain transitions.

What changed on June 17

On June 17, 2026, Google published a revision to its site move guide on Google Search Central, adding explicit instructions on handling subdomain variants during domain migrations. According to Google's documentation update log, the site move guide now includes information on using the Change of Address tool for all subdomain variants - including www and non-www versions of a domain - when executing domain-level moves. The stated reason is direct: domain migrations work best when all variants of a site are migrated properly.

This is a targeted, narrowly scoped documentation change. It does not alter how Google processes crawl signals or how PageRank flows during a site move. What it does is close a blind spot in the written guidance that site owners and technical SEO professionals have relied on when planning migrations. Previously, the site move documentation did not spell out the requirement to submit Change of Address requests for every subdomain variant of the origin domain. That absence left room for migrations that partially executed the process - completing the main-domain submission while leaving www or non-www variants unaddressed.

The Change of Address tool itself sits inside Google Search Console. It signals to Google that a site has moved permanently from one domain to another, helping the indexing system transfer ranking signals from old URLs to new ones. According to Google's site move documentation, the tool should be used for domain migrations specifically - not for HTTP-to-HTTPS migrations, which follow a different process and do not require the Change of Address step.

The technical scope of the update

The new guidance affects how operators should verify and submit properties inside Search Console before, during, and after a domain move. According to the documentation, the process now requires that all variants of the old domain be verified in Search Console. That means a migration from example.com to example.net must account for four distinct properties at minimum: example.com, www.example.com, example.net, and www.example.net. Operators moving from a domain with active subdomains beyond the www variant - such as en.example.com or blog.example.com - would need to cover those as well.

According to the site move guide, Change of Address requests should be submitted for all subdomains and both the www and non-www variants of the old domain name, "even if you're not actively using these variants." That parenthetical matters. A domain that resolves only through its www version may still have a bare-domain property indexed by Google. Leaving the non-www variant without a Change of Address submission creates an incomplete migration signal, which can slow the transfer of ranking authority to the destination domain.

The guide specifies that all of these variants must be verified in Search Console before submitting Change of Address. Verification methods in Search Console include HTML file upload, HTML meta tag insertion, DNS record modification, Google Analytics association, and Google Tag Manager container verification. Each method has its own considerations when a CMS migration is running in parallel - a point the documentation raises elsewhere but does not specifically address in the new domain-variants section.

Why this matters for domain migrations

Domain migrations are among the highest-risk operations in technical SEO. The consequences of a poorly executed move - lost indexing, ranking drops, broken internal links, and disrupted crawl signals - can persist for months. Google's site move documentation acknowledges this. According to the guide, "a medium-sized website can take a few weeks for most pages to move in our index; larger sites can take longer." Speed depends on server capacity and the number of URLs involved.

The specific risk that this documentation update addresses is one that tends to surface after the move has already begun. A webmaster submits a Change of Address for the primary www domain, implements server-side 301 redirects, submits a new sitemap, and monitors the Index Coverage report. If the non-www variant was not submitted for Change of Address, Google may continue crawling and indexing the old non-www URLs alongside the new destination. The result is a split migration signal - part of the domain appears to have moved, while another part has not formally communicated the change.

This matters more than it might appear. According to the site move documentation, the Change of Address tool submission is separate from and complementary to the redirect configuration. Redirects handle individual URL-level traffic. The Change of Address tool operates at the domain level, providing an explicit signal to Google's indexing infrastructure about the nature and direction of the move. Without that tool-level signal for every verified variant, the system relies more heavily on crawl-based inference, which is slower and less reliable.

PPC Land has tracked the relationship between subdomain architecture and search performance in prior coverage, noting that Google has historically treated subdomains as distinct entities for ranking purposes, even when those subdomains are closely related to the main domain. That distinctness makes the variant-by-variant Change of Address requirement logical: Google's systems do not automatically infer that a www redirect implies a completed non-www migration at the domain-level signal layer.

The broader context of the June 2026 documentation cycle

This update is part of a broader wave of Google Search Central documentation changes published in June 2026. The same changelog entry for June 15 notes that Google added a clarifying note about llms.txt files to its AI optimization guide, stating that these files are not needed for Google Search and "won't negatively or positively impact your visibility or rankings." That same date also saw Google remove documentation for the FAQ rich result feature, which stopped appearing in Google Search results following an announcement in May 2026.

Earlier in the month, on June 12, Google created a new article specifically for small business owners in Tennessee, explaining how they can receive notifications from Google Search when their web content is removed or restricted. And on June 5, Google published guidance on evaluating third-party SEO tools, services, and advice, a documentation update PPC Land covered in detail, noting that it formalized positions Google's search advocates had previously communicated through informal channels.

The June 17 site move update is the most recent item in that changelog at the time of writing.

Redirect strategy and the role of 301s

The site move documentation provides a clear hierarchy for redirect types during a domain migration. Server-side permanent redirects - HTTP 301 and 308 status codes - are the recommended mechanism. According to the documentation, "301 and other permanent redirects don't cause a loss in PageRank," a clarification that addresses one of the more persistent anxieties in the SEO community about redirect chains diluting ranking signals.

The guide places specific constraints on redirect chain length. Googlebot can follow up to 10 hops in a redirect chain - for example, page 1 redirecting to page 2, which redirects to page 3, and so on. But the documentation advises against relying on this ceiling. The recommendation is to redirect directly to the final destination. Where chaining is unavoidable, the guide suggests keeping the chain to no more than 3 redirects and under 5 where possible. Chaining adds latency for users, and some user agents do not support long chains reliably.

Client-side redirects are described as a last resort - usable when no server-side option is technically available, but not a preferred path. The documentation does not assign a PageRank penalty to client-side redirects explicitly, but the framing makes clear they are a fallback, not an equivalent alternative.

Redirects should also be maintained for a minimum of one year after the move is complete. The rationale is signal transfer: Google needs time to recrawl both the old and new URLs, discover the redirects, and reassign inbound link signals from the old domain to the new one. The documentation notes that from a user-experience standpoint, keeping redirects in place indefinitely is reasonable - even after Google has completed its signal transfer, some users and external sites will continue to reference old URLs for years.

Preparing Search Console before the move

The documentation lays out a preparation sequence that applies to all site moves, not just domain migrations. Several steps are directly relevant to the new subdomain-variants guidance.

The first is property verification. Both the old and new sites must be verified in Search Console before the move begins. The guide explicitly says to verify "all variants of both the old and new sites." This is the step where the new June 17 guidance has the most direct operational impact: operators now have explicit written confirmation that the www and non-www versions of the old domain need separate verification entries in Search Console, not just one.

The second is reviewing configured settings on the old site. Crawl rate preferences, disavowed backlinks, and any manual actions applied to the old site need to be carried over to the new Search Console property. If a disavow file was uploaded for the old site, Google recommends reuploading it under the new site's account. Any outstanding URL removals left over from a previous domain owner should be cleared before the move begins.

The third is addressing manual actions. If the new domain has any pre-existing manual actions - from a previous owner who may have engaged in spam practices - those need to be remediated and a reconsideration request filed before the move. The documentation includes this point in the "clean up your recently purchased domain" section, which is particularly relevant for operators acquiring expired domains for rebranding purposes.

Monitoring after the move

Once the move is underway, the documentation identifies several Search Console features for tracking progress. The Sitemaps report shows how many URLs from each submitted sitemap have been indexed. The Index Coverage report shows a drop in indexed URL counts on the old site alongside an increasing count on the new site. Search queries in the Performance report begin showing the new URLs receiving impressions and clicks as indexing catches up.

According to the site move guide, the visibility of content in Search "may fluctuate temporarily during the move." This is expected behavior - not a signal that something has gone wrong. Ranking settles over time as Googlebot recrawls both properties and the indexing infrastructure fully processes the new URL structure.

The Sitemaps report may show warnings for the old-site sitemap about URLs redirecting. According to Google, "this is normal and you can ignore these warnings: you are, in fact, moving to new URLs after all." That clarification is useful. It prevents premature action - such as removing the old sitemap or disabling redirects early - based on warning messages that are functioning as intended.

Google's documentation mentions third-party tools alongside Search Console for monitoring. The guide specifically names Aleyda Solis' site migration checklists and the Screaming Frog tool guide as resources for operators managing more complex moves.

Common mistakes and how to avoid them

The documentation dedicates a section to troubleshooting failures, several of which have a direct relationship to the new subdomain-variants guidance. The most common mistake is noindex or robots.txt blocks left in place from the development phase. If a site was blocked from crawling during pre-launch preparation and that block was not removed before the live switch, Googlebot will be unable to index the new site regardless of how well the redirects are configured.

Incorrect redirects are the second major failure point. The guide notes that misdirected redirects - sending old URLs to wrong or non-existent destinations on the new site - are frequently observed. The URL Inspection Tool in Search Console can test individual URLs. For large URL sets, the guide recommends command-line tools or scripts to test redirect behavior in bulk.

Insufficient server capacity is a less obvious but consequential failure mode. After a migration, Googlebot crawls the new site more heavily than usual. This happens because any crawl of the old site triggers a redirect to the new site, effectively doubling the crawl demand on the new server. Operators with tight server margins should communicate with their hosting provider ahead of the move.

The context this update adds - that all subdomain variants of the old domain require their own Change of Address submissions - means operators should now also audit which subdomain properties are registered in Search Console before beginning the verification step. Properties that exist in Google's index but lack a Search Console entry cannot have a Change of Address submitted for them, which creates a gap in the migration signal even if physical redirects are in place.

The June 17 update does not restructure the site move guide in any fundamental way. It adds a specific, previously missing instruction to an existing process. But that kind of targeted clarification is often more valuable than broad guidance - it addresses a concrete failure mode that the documentation previously left unaddressed.

The Google Search Central documentation changelog has seen a sustained pace of updates through 2025 and into 2026, as Google has worked to align written guidance with actual system behavior across crawling, indexing, and structured data.

Timeline

  • August 31, 2011 - Google announces that example.com and www.example.com will be treated as the same site for internal/external link reporting purposes in Webmaster Tools, per an early policy shift documented in SEO records.
  • March 2024 - Google removes subdomain-level tracking from AdSense for Search site reporting, consolidating performance data at the top-level domain, per PPC Land coverage.
  • December 10, 2025 - Google Search Console adds weekly and monthly aggregation views, improving how operators track traffic trends during and after site migrations, as covered by PPC Land.
  • December 20, 2025 - Google clarifies JavaScript rendering behavior for pages with non-200 HTTP status codes, including redirect responses, in a Search Central documentation update covered by PPC Land.
  • June 5, 2026 - Google adds a new standalone page on evaluating third-party SEO tools to Search Central documentation, covered by PPC Land.
  • June 15, 2026 - Google adds a note to its AI optimization guide clarifying that llms.txt files are not required for Google Search and will have no positive or negative effect on visibility or rankings. The same date, Google removes documentation for the FAQ rich result feature, which stopped appearing in Search results following a May 2026 deprecation notice.
  • June 17, 2026 - Google updates its site move guide to include explicit instructions for submitting Change of Address requests for all subdomain variants - including www and non-www versions - of the old domain during domain migrations. The documentation page was last updated June 17, 2026 UTC.

Summary

Who: Google Search Central, the division responsible for Google's official documentation for website owners, developers, and SEO professionals.

What: Google updated its site move guide to explicitly require the use of the Change of Address tool for all subdomain variants - including www and non-www - of the old domain when executing a domain migration. The change adds a specific instruction to an existing process but does not alter how Google's indexing or redirect systems work in practice.

When: The documentation update was published on June 17, 2026, according to the official Google Search Central documentation changelog. The page was last updated June 17, 2026 UTC.

Where: The updated guidance appears in the "Move a site with URL changes" documentation on Google Search Central, under the "Start the site move" section covering Change of Address submission. The Change of Address tool itself is accessible through Google Search Console.

Why: According to Google, domain migrations work best when all variants of a site are migrated properly. The update addresses a practical gap in the written guidance: operators executing a domain move could follow the prior documentation without ever being instructed to submit Change of Address requests for the www or non-www variant of the old domain, potentially leaving part of the migration signal incomplete and slowing the transfer of ranking signals from old URLs to the new domain.