Search Console Change of Address: What the Tool Does and Does Not Do

01

Definition

Search Console’s Change of Address tool is a domain-migration signal. It tells Google that an old domain-level property has moved to a new domain-level location and helps transfer Search signals from the old property to the new one.

Use it after the site move has been implemented and old URLs redirect to their new destinations. Google says the request causes its systems to emphasize crawling and indexing the new site, forward various signals, and prefer the new site when determining canonicals. The relationship remains active for 180 days. ^[1]

The tool does not perform the migration. It does not:

• configure DNS
• create redirects
• create an old-to-new URL map
• copy content
• remove noindex
• update canonicals
• update sitemaps
• rewrite internal links
• preserve analytics
• repair server errors
• guarantee rankings

It supplements a technically complete move.

02

Mechanism

Eligible moves

Use the tool when moving:

example.com → example.net
shop.example.com → store.example.org
example.com → example.org/new/location/

The source property must be at the domain or hostname level rather than a path-level property. The destination may include a path when an entire source site is moving there. ^[1]

Moves that do not use the tool

Do not use it for:

HTTP → HTTPS
www.example.com → example.com
example.com/old-path → example.com/new-path
hosting provider A → hosting provider B with unchanged URLs
CDN changes with unchanged URLs
individual page moves

For HTTP-to-HTTPS, Google detects the URL move through redirects and normal site-move signals. For internal path changes, use redirects and updated sitemaps. For unchanged URLs, follow the hosting-move process. ^[1]

This distinction matters because the tool operates at property scope. It cannot express that only 417 selected pages moved while the rest stayed behind.

Verification requirements

The same Google account must be an owner of both the old and new properties. Verify all relevant variants before migration.

For a real-world domain, that may include:

example.com
www.example.com
en.example.com
m.example.com
new-example.net
www.new-example.net

The tool does not automatically move all lower-level subdomains beneath a property. Google recommends submitting requests for relevant old subdomains and www or non-www variants, even when some are not actively used, and ensuring those properties are verified. ^{[1] [2]}

Pre-move checks

The tool performs checks such as:

• ownership of source and destination
• eligibility of property scope
• presence of redirects on sampled URLs
• apparent destination consistency

Critical failures must be fixed. Noncritical findings may appear as warnings.

Passing the tool’s sample checks does not certify the entire redirect matrix. A homepage redirect can pass while thousands of deep URLs fail. Full mapping validation remains the site owner’s job.

The 180-day signal window

After submission, Search Console displays move notifications for 180 days. During that period, Google treats the old and new properties as related for the requested move and directs processing toward the new site. ^[1]

This does not mean redirects should be removed on day 181. Google’s site-move guide recommends keeping redirects for at least one year, and users may continue following old links indefinitely. ^[2]

Think of the tool as a time-bounded explicit signal layered on top of durable HTTP behavior.

Old URLs can remain visible

The tool does not erase the old site from Google’s index. Old URLs can continue appearing when they remain available or when no equivalent new page exists. Redirects and coherent canonicals reduce old-URL appearances when a replacement exists. ^[1]

That behavior is rational: a property-level request cannot invent page equivalence. If an old article was not moved, Google may still regard the old URL as the only available source.

Multiple and chained moves

Google advises against chained address changes such as:

A → B
then immediately B → C

It also advises caution when combining several old sites into one new site. Move sites separately and allow signals to stabilize where practical. ^[1]

The tool cannot turn an organizational consolidation into a clean page graph when several source domains contain duplicates, conflicts, or unrelated content.

Cancellation

A Change of Address request can be canceled during its 180-day period.

Google’s documented cancellation sequence includes:

1. remove old-to-new permanent redirects
2. add permanent redirects from the new site back to the old site
3. cancel the move in the old property
4. repeat for each affected source property

Cancellation is therefore another migration, not an undo button that restores the previous world without routing changes. ^[1]

03

Examples

Eligible domain move

A company changes from oldbrand.com to newbrand.com. Every old canonical page redirects directly to its new equivalent. Both properties are verified.

Submit Change of Address from the old domain after launch. Continue monitoring both properties and keep redirects active well beyond the tool window.

HTTP to HTTPS

A site changes:

http://example.com/page
→ https://example.com/page

Do not use Change of Address. Configure permanent redirects, update canonicals and internal links, verify both protocol properties when relevant, and monitor the move.

Path-only redesign

A documentation site changes:

example.com/docs/v1/page
→ example.com/guides/page

Do not use the tool. The property hostname is unchanged. Use page-level redirects and a tested URL mapping.

Hosting provider move

The visible URLs remain identical, but DNS points to a new infrastructure provider.

Do not use Change of Address. Prepare the new host, lower DNS TTL in advance, move traffic, and monitor both old and new servers.

Several subdomains move

The old estate includes:

www.old.com
shop.old.com
fr.old.com

The move is not fully described by one casual request from old.com. Verify the relevant properties and submit eligible moves for the actual source hosts according to Search Console’s requirements.

One domain absorbed into a section

An entire microsite at campaign.example moves into main.example/archive/campaign/.

This can qualify because a domain-level source is moving to a path within another domain. The underlying page redirects and mappings still must be correct.

04

Boundaries

Change of Address is a Google Search tool. Other search engines, browsers, users, link checkers, applications, and bookmarks rely on HTTP redirects and updated links.

The tool does not make a bad migration good. Irrelevant redirects, blocked destination pages, conflicting canonicals, missing content, and server errors remain bad after a successful submission.

Do not submit the request before redirects are active. Do not submit it merely because the new domain has been purchased. Do not assume one request covers all subdomains. Do not remove redirects when the 180-day notification disappears.

The correct model is:

Mapping + redirects + updated site signals + verification + Change of Address + monitoring

The tool is one term in that expression, not the expression itself.

Continue with Hosting and CDN Migration SEO for unchanged URLs, Domain Migration SEO for the full move, and URL Migration Redirect Mapping for page-level equivalence.

References

Sources behind this record

1. Change of Address tool — Google Search Console Help (accessed August 2, 2026)
2. How to move a site — Google Search Central (accessed August 2, 2026)

Corrections

Correction history

No corrections recorded.

To report an error, use the public corrections path.