Google Search Console Change of Address for Domain Moves: When to Use It and a Practical Checklist

Who this guide is for

This guide is for Indian website owners, WordPress operators, and technical SEO practitioners who are moving a site from one domain or subdomain to another—and need a clear answer to when Google Search Console’s Change of Address tool applies, what must be done before you open it, and how to monitor the move without guessing.

Domain and URL examples below (such as oldbrand.in → newbrand.in) are hypothetical illustrations, not real client projects, traffic numbers, or rankings.

What the Change of Address tool does

Google’s Search Console Help page for the Change of Address tool explains that you use it when you move a website from one domain or subdomain to another (for example, example.com to example.org). The tool tells Google about the change and helps migrate Google Search results from the old site to the new site. Use it after you have moved and redirected the site.

When you file a change of address request, Search Console Help states that Google is told to emphasize crawling and indexing the new site over the old site, to forward various signals from the old site to the new site, and to prefer the new site when determining canonical pages. Those actions continue for 180 days after you start the migration in Search Console.

The tool also runs a quick check before sending the move request, confirming ownership of both sites and checking for 301 redirects on a few pages.

When not to use Change of Address

Do not open Change of Address for every kind of “migration.” Search Console Help lists these exclusions explicitly (Change of Address tool):

Situation Use Change of Address? What Google points you to instead
HTTP → HTTPS on the same hostnames No Follow site-move-with-URL-changes guidance; Google will figure out HTTPS moves without this tool
Moving some paths inside the same site (/oldpath/ → /newpath/) No Add redirects and update sitemaps
www ↔ non-www on the same domain No Use canonical tagging and/or redirects
Hosting or CDN change with no user-visible URL change No Follow changing your web hosting
Domain or subdomain change (a.com → b.com, or a.example.com → b.example.com) Yes (after redirects) Change of Address + site moves with URL changes

You can use the tool to migrate from one domain to a path on another domain (for example, example.com to example3.com/new/location/), per the same Help page.

Decision worksheet (copy and fill)

Question Your answer Likely path
Will visitors see a different domain or subdomain in the address bar? If yes → URL-change move; Change of Address may apply
Are URLs unchanged and only hosting/CDN changing? No Change of Address; follow hosting-change guide
Is this only HTTP → HTTPS? No Change of Address
Is this only www vs non-www? No Change of Address
Are you combining a domain change with a redesign and a new permalink structure in one night? Prefer separating changes; see “one thing at a time” below

How this relates to redirects and hosting moves

Change of Address is a Search Console signal for domain/subdomain moves. It does not replace permanent redirects, and it is not the same job as Bing Webmaster Tools site verification.

For how permanent redirects behave and when to choose 301 vs temporary redirects, see the 301 redirects guide. Here the focus is when Change of Address applies, the official pre-work, Search Console requirements, and monitoring after a domain or subdomain move.

Google’s documentation on site moves with URL changes recommends server-side permanent redirects such as HTTP 301 or 308 when technically possible, advises against long redirect chains, and states that 301 and other permanent redirects do not cause a loss in PageRank. Search Console Help for Change of Address specifically asks for a 301 from the old homepage to the new homepage (and recommends 301s for canonical pages) as pre-work.

Best practices before you touch Search Console

Google’s site-move documentation asks operators to plan carefully (site moves with URL changes):

  1. 1. Change only one major thing at a time when you can. Example given by Google: if you want a new domain, a new CMS, and a new layout, do them sequentially (domain first, then layout), not all at once.
  2. 2. Expect temporary ranking fluctuation while Google recrawls and reindexes. For medium-sized sites, Google says it can take a few weeks or more for new URLs to gradually replace old ones in Search; larger sites can take longer. Speed depends on URL count and server speed—there is no fixed crawl frequency.
  3. 3. Be patient. A move is considered complete only after Googlebot has visited every URL on the old and new sites at least once.
  4. 4. Prefer moving small/medium sites all at once; large sites may move in sections for easier monitoring.

Search Console Help also warns (Change of Address tool):

  • Don’t chain site moves (A→B, then immediately B→C).
  • Try not to combine multiple old sites into one new location in one step if that creates confusion and traffic loss; moving one site at a time and waiting for traffic to stabilize can be safer.
  • Keeping similar site architecture on the new location helps pass signals more directly; combining a domain move with a full redesign of content and URL structure will probably cause some traffic loss while Google reassesses pages.

Requirements to use Change of Address

From Search Console Help (Change of Address tool):

  1. 1. You must be an owner of both the old and new properties in Search Console, managed with the same Google account.
  2. 2. Open the tool only on a property that Help calls domain level: a supported site property with no path / subpath in the property URL. Help’s examples include example.com, m.example.com, and http://example.com. You cannot use it on a path-level property such as http://example.com/petstore/. Help also phrases this as a property with no path segments (for example example.com, not example.com/petstore).
  3. 3. That “domain level” wording is not the same thing as Search Console’s product label Domain property (the DNS-verified property type in the Search Console UI). Do not treat the two phrases as interchangeable, and do not assume extra compatibility rules beyond what Change of Address Help states. Follow Help’s supported examples and the no-path requirement.
  4. 4. Specifying example.com does not automatically move subdomains such as www.example.com or m.example.com. Paths under the chosen hostname are affected.
  5. 5. When moving from one domain to another, use the tool for all subdomain variants of the old domain you need (including www and non-www), even unused variants, and verify those variants in Search Console. Help also notes that if you want to migrate a Domain property for A.com → B.com and a subdomain to a different destination (for example m.A.com → m.C.com), create a property for that subdomain and migrate it separately.
  6. 6. Specifying http://example.com also moves https://example.com for that source property (the tool moves all protocols of the source property).

Search Console ownership worksheet

Property to verify (no path in the property URL) Verified? Same Google account as destination? Notes
Old root hostname (Help example style: example.com) Must be owner
Old www variant if used Separate from apex if it is a separate property
Other old subdomains in use (for example m.example.com) Migrate separately if destinations differ
New root / target hostname Must be owner on same account
New www (if used)

Step 1 — Pre-work (before the tool)

Search Console Help requires pre-work for all site moves (Change of Address tool):

  1. 1. Implement a 301 redirect from your old homepage to your new homepage; Google also recommends 301 redirects for the canonical pages on the old site.
  2. 2. Read and follow the broader site-move recommendations in Google’s site moves with URL changes documentation.
  3. 3. Complete other pre-move actions from that documentation (prepare the new site, URL mapping, redirect strategy, testing).
  4. 4. Only then use Change of Address on eligible no-path (Help: “domain level”) properties.

Prepare the new site (official checklist themes)

Google’s site-move guide asks you to prepare and test the new site thoroughly, including items such as (site moves with URL changes):

  • Set up the CMS and import content; transfer images and downloads that already earn traffic or links.
  • Configure TLS if moving to HTTPS.
  • Set robots.txt rules that correctly reflect what should be crawlable after launch—not leftover “block everything” staging rules.
  • Remove temporary noindex rules when the move starts.
  • Return proper 404 or 410 responses for content that is intentionally not moving.
  • Verify old and new sites (and variants) in Search Console; ensure verification tokens still work after the move.
  • If you previously uploaded a disavow file on the old Search Console property, re-upload it on the new property as well—disavow lists are property-specific and do not automatically follow a move (site moves with URL changes).
  • On a newly purchased destination domain, check for leftover manual actions and URL removals from a previous owner.
  • Ensure the new server can handle temporarily heavier Googlebot crawl load after migration.

Build a URL mapping worksheet

Old URL New URL Redirect type planned Content still exists? Priority (traffic / links / conversions)
301 / 308 / other Yes / consolidated / retired High / Med / Low

Google recommends listing important old URLs from sitemaps, analytics, server logs, CMS exports, and links reported in Search Console, and including embedded resources (images, videos, JS, CSS) in the plan (site moves with URL changes).

Update the new site so that:

  • Each new URL has a self-referencing rel="canonical" where appropriate.
  • Hreflang annotations (if used) point to new URLs.
  • Internal links on the new site use new URLs.
  • You save a sitemap of new URLs and a list of external sites linking to old URLs.

Redirect strategy notes

  • Prefer server-side permanent redirects (301 or 308) when possible.
  • Avoid chaining many hops; Googlebot can follow multiple hops, but Google advises redirecting to the final destination directly and keeping chains short (ideally no more than 3 and fewer than 5).
  • Do not redirect many unrelated old URLs to a single irrelevant destination such as the new homepage; that can confuse users and may be treated like a soft 404. Consolidated content is a different case: multiple old URLs may redirect to one new consolidated page.
  • Test redirects with Search Console’s URL Inspection tool for samples, and with scripts/crawlers for large sets.

For WordPress operators: implement redirects at the server or a maintained redirect layer your host supports, and keep a documented map. This guide does not prescribe a specific plugin screen, because plugin UIs change and are not Google’s product documentation.

Step 2 — Run Change of Address

After pre-work and requirements are met (Change of Address tool):

  1. 1. Open the Change of Address tool on an old property that meets Help’s domain level rule: no path segments in the property URL (for example example.com, not example.com/petstore).
  2. 2. Follow the tool’s instructions. It runs pre-move checks. Critical failures must be fixed before continuing; non-critical warnings can allow continuation with recommendations.
  3. 3. When critical checks pass, Search Console shows notifications that the move is in progress on sites being migrated from or to—for 180 days.
  4. 4. Monitor traffic as described in Google’s site-move documentation.
  5. 5. Maintain redirects for at least 180 days—longer if you still see Google Search traffic to old URLs. Search Console Help also recommends continuing to pay for the old domain for at least a year so others cannot buy and misuse an abandoned domain. After the 180-day period, Google does not recognize a relationship between the old and new sites via this tool process, and treats the old site as unrelated if it is still present and crawlable.

Separately, Google’s site-move documentation advises keeping redirects as long as possible, generally at least 1 year, to allow signal transfer and link reassignment, and notes that from a user perspective you may keep redirects indefinitely while updating high-volume links to point directly at new URLs (site moves with URL changes). Treat the 180-day figure as the Change of Address Help minimum for tool-related maintenance, and the “generally at least 1 year” figure as the broader site-move redirect guidance—not as competing “ranking guarantees.”

Google’s site-move guide says to submit the new sitemap in Search Console, and that you can remove the old sitemap once Google is using the new one. Update internal links, high-value external links, profile links, and ad landing pages to the new URLs when you can (site moves with URL changes).

Monitoring worksheet

Signal Old property New property What “healthy progress” looks like (directional)
Homepage 301 Old home → new home in one hop
Sample high-value URLs Correct permanent redirects
Sitemaps index counts Old indexed counts trend down; new trend up over time
Index / coverage errors No unexpected error spikes
Search queries / pages New URLs gradually earn impressions/clicks
Analytics sessions Old declines; new rises
Server capacity / latency New host handles crawl + users

Search Console Help notes that Google does not erase the old site from the index automatically; old URLs can still appear if they remain available and lack equivalents. Redirects plus rel=canonical on equivalents can reduce old URLs in Search.

Cancelling a Change of Address request

Within 180 days, Search Console Help says you can cancel (Change of Address tool):

  1. 1. Remove the 301 redirects that pointed old → new (otherwise Google may keep following them).
  2. 2. Add 301 redirects from the new site back to the old site.
  3. 3. Open Change of Address on the old site and click Cancel Move; repeat for every old site you no longer want to move.

Hosting-only moves (no Change of Address)

If users still see the same URLs and you are only changing host or CDN, follow Google’s changing your web hosting guide instead: copy and test on the new infrastructure, ensure Googlebot can access it, consider lowering DNS TTL ahead of the cutover, remove temporary crawl/index blocks, update DNS, monitor old vs new traffic, then shut down the old host when traffic there reaches zero. That workflow does not use Change of Address.

Hypothetical India examples

Example A — Domain rebrand (Change of Address applies)

A Kolkata services company moves oldname.co.in to newname.in with the same WordPress content tree and a full 301 map. Owners verify both domains (and www variants) in one Google account, launch redirects, pass Change of Address checks, submit the new sitemap, and monitor both properties for several weeks. They do not redesign permalinks on the same night.

Example B — Host migration only (no Change of Address)

A shop moves from one Indian host to another but keeps https://www.example.in/... unchanged. The team follows the hosting-change guide, lowers DNS TTL in advance, tests the new stack, updates DNS, and watches logs. Change of Address is not used.

Example C — HTTPS upgrade only (no Change of Address)

A site enables HTTPS and redirects HTTP URLs to HTTPS equivalents. The team uses site-move-with-URL-changes practices and redirect hygiene, without Change of Address.

Common mistakes

  • Using Change of Address for HTTPS-only or www-only changes
  • Opening the tool before homepage (and key page) 301s work
  • Verifying old and new properties under different Google accounts
  • Forgetting www / other subdomain variants of the old domain
  • Leaving staging noindex or disallow-all robots rules on the new live site
  • Redirecting everything to the new homepage
  • Combining domain change, redesign, and permalink rewrite in one launch without a map
  • Dropping redirects after a few days because “Search Console said 180 days” while old URLs still receive links or traffic—read both the 180-day Help note and the broader “generally at least 1 year” site-move guidance
  • Ignoring server capacity when Googlebot crawl temporarily increases

14-day operational plan (example for a domain move)

Days 1–3 — Baseline and map

  1. 1. Export important URLs from sitemap, analytics, and Search Console links.
  2. 2. Freeze non-essential content changes.
  3. 3. Draft the old→new map and mark consolidated or retired URLs.

Days 4–6 — New site readiness

  1. 1. Build/test the destination site.
  2. 2. Confirm canonicals, internal links, robots.txt, and indexability for launch.
  3. 3. Verify Search Console properties on the same account.

Days 7–8 — Redirects live

  1. 1. Enable server-side permanent redirects.
  2. 2. Spot-check homepage and high-value URLs.
  3. 3. Submit the new sitemap.

Days 9–10 — Change of Address

  1. 1. Run the tool on each required old domain-level variant.
  2. 2. Fix any critical pre-check failures.
  3. 3. Record the start date for the 180-day notification window.

Days 11–14 — Monitor and communicate

  1. 1. Compare Search Console and analytics on old vs new.
  2. 2. Update high-traffic profile and campaign links.
  3. 3. Schedule weekly checks for the next month; keep redirects in place.

Frequently asked questions

Does Change of Address guarantee rankings will stay the same?

No. Google’s site-move documentation says temporary ranking fluctuation is expected while URLs are reprocessed. Change of Address helps Google emphasize the new site and forward signals for 180 days; it is not a ranking lock.

Do I need Change of Address for a WordPress host change on the same domain?

No. Use the hosting-change (no URL change) documentation.

How long should redirects stay up?

Search Console Help: maintain redirects at least 180 days for Change of Address migrations, longer if Google Search traffic to old URLs continues; consider keeping the old domain registered at least a year. Site-move documentation: keep redirects as long as possible, generally at least one year. Align your maintenance plan with both statements.

Will permanent redirects lose PageRank?

Google’s site-move documentation states that 301 and other permanent redirects do not cause a loss in PageRank.

What if critical pre-checks fail?

Fix the underlying ownership or redirect issues the tool reports before continuing. The Help page requires critical failures to be resolved first.

Closing

Use Change of Address only for eligible domain or subdomain moves, and only after redirects and Search Console ownership are ready. Pair it with Google’s site-move documentation, keep redirects long enough, monitor both properties, and use the hosting-change guide when URLs do not change. For redirect mechanics on individual URLs, continue with the 301 redirects guide.

Related on this site: Technical SEO Services in India (2026), Canonical tags guide, and Contact.

References

  1. 1. Google Search Console Help — Change of Address tool — https://support.google.com/webmasters/answer/9370220
  2. 2. Google Search Central — Site moves with URL changes — https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes
  3. 3. Google Search Central — Changing your web hosting (site move with no URL changes) — https://developers.google.com/search/docs/crawling-indexing/site-move-no-url-changes

Leave a Reply

Share Your Love