Moving a Treatment Center Website to a New Domain: What Google’s Site Move Rules Actually Require

Treatment centers change domains more often than most businesses. A facility gets acquired and folded into a parent brand. A program renames itself after licensing changes. A group consolidates three single-location sites into one. Each of these is a site move in Google’s terms, and each one can quietly cost months of search visibility if the move is handled as a web design task instead of a search task.

Google publishes specific, testable requirements for this. The catch is that they live in two documents with two different timeframes, and the one tool that tells Google about a domain change trips up most organizations that have changed agencies or staff.

The two timeframes Google gives, and why both matter

When a website moves to a new domain, Google’s Search Console Help says the Change of Address tool shows a move-in-progress notice for 180 days, that redirects should stay live for at least 180 days, and that after that period Google treats the old and new sites as unrelated. Google’s separate site move documentation says to keep redirects “generally at least 1 year,” and the same Help article recommends paying for the old domain for at least a year so nobody else can buy it and misuse it. The practical rule is the stricter one: keep every redirect live and the old domain renewed for a minimum of 12 months, and treat 180 days as the point where Google stops connecting the two sites, not the point where the redirects can come down.

Both sources are current Google documentation: the Change of Address tool article in Search Console Help and the site moves and migrations guide on Google Search Central. We checked both on October 5, 2026. They do not contradict each other so much as answer different questions. The 180-day figure describes how long Google’s systems keep the old and new properties linked. The one-year figure describes how long it takes Google to recrawl the web and reassign links from other sites that still point at your old URLs.

What the Change of Address tool covers, and what it does not

The Change of Address tool in Search Console has one job: telling Google that a site has moved from one domain or subdomain to another. According to Google’s Help documentation, it is the wrong tool for several moves that people often assume it handles:

• HTTP to HTTPS: follow the site move guidelines, but skip the tool; Google works this change out on its own.
• Moving pages within one domain: a path change such as /old-programs/ to /programs/ needs redirects and an updated sitemap, not a change of address.
• www to non-www on the same domain: handle this with redirects and canonical tags.
• A hosting or CDN change with no URL change: Google documents this as a separate process entirely.

We worked through this distinction on our own site in September 2026, when we consolidated a set of city service pages and put ninety 301 redirects in place. Because every old and new URL lived on the same domain, the Change of Address tool did not apply at all. Redirects, an updated sitemap, and corrected internal links were the whole job. A domain change is different, and it is the only case where the tool earns its place.

The tool also has strict requirements. You must be a verified owner of both the old and new properties, and you must use the same Google account for both. It only works on domain-level properties, not path-level ones. It does not move subdomains below the one you specify, including www, so Google says to submit a request for every variant of the old domain, such as example.com, www.example.com, and any other subdomain, even ones you no longer use. Each of those variants has to be verified in Search Console first.

That ownership requirement is where most moves stall. When the old domain’s Search Console property was verified years ago by a former agency, a previous web developer, or a staff member who has since left, nobody on the current team may be able to prove ownership. We covered how to check this in our guide to who owns your Search Console and Google Business Profile. Run that audit before the move, not on launch day.

Why domain moves lose traffic

Google’s documentation says to expect temporary ranking fluctuation during any significant move, and that a small to medium site can take a few weeks for most pages to move. Losses that last longer than that usually trace back to a short list of specific mistakes.

• Redirecting everything to the home page: Google says sending many old URLs to one irrelevant destination can be treated as a soft 404, so the old page’s signals never arrive anywhere useful.
• Redirect chains: Googlebot follows up to 10 hops, but Google recommends redirecting straight to the final URL, and keeping any unavoidable chain to 3 hops or fewer.
• Combining the move with a redesign: Google’s Help article notes that keeping the same site architecture passes signals more directly, and that changing content and URL structure at the same time usually means some traffic loss while Google reassesses individual pages.
• Stale canonical and noindex tags: a leftover staging noindex tag, or a canonical tag still pointing at the old domain, tells Google not to index the new pages you just redirected to.
• Letting the old domain lapse: once the registration expires, every redirect stops working and the domain becomes available to anyone, including people who would use its history for purposes you would never want associated with a healthcare brand.

The redesign point matters most for treatment centers, because a rebrand usually arrives bundled with a new website. If you can, move the existing site to the new domain first with the same URLs, let it settle, and launch the redesign afterward.

A pre-move checklist you can work through this week

Each step maps to a specific requirement in Google’s documentation.

1. Export the old URL list. Download the URLs in your current XML sitemap and the indexed pages listed in Search Console. Google’s guide points to sitemaps as the most likely place your important URLs are already listed.
2. Build a one-to-one map. Every old URL gets a specific new destination. Only send several old URLs to one new page when that page actually consolidates their content.
3. Verify every variant. In Search Console, confirm that the same Google account owns the old domain, its www version, any other subdomains, and the new domain.
4. Use server-side permanent redirects. Google recommends 301 or 308 status codes. Client-side redirects are a last resort.
5. Update on-page signals. Canonical tags, hreflang annotations if you use them, internal links, and the new sitemap should all reference the new URLs.
6. Submit the Change of Address. Do this from the old domain-level property after the redirects are live, and repeat it for each variant.
7. Submit both sitemaps. Google suggests submitting the new sitemap and, temporarily, the old one, so you can watch indexed pages shift from the old URLs to the new ones.
8. Set two calendar reminders. One at 180 days to review any remaining Google traffic to the old URLs, and one at 12 months, ahead of the old domain’s renewal date.

The check to run on launch day

Take ten of your most important old URLs, including the home page, your main program pages, and your admissions or insurance page. Run each one through the URL Inspection tool in Search Console, or paste it into any HTTP header checker, and confirm three things: the status code is 301 or 308, there is exactly one hop, and the destination is the matching new page rather than the new home page. Then repeat the test on the www, non-www, and http versions of the old domain. Variants that nobody tested are the most common place we find broken redirects after a move.

What this means for healthcare brands specifically

A domain move also touches everything outside the website that carries the old address. Update the website field on every Google Business Profile, the final URLs in your paid advertising accounts, the links in directory and insurance network listings, and any analytics or call tracking setup that filters by hostname. For treatment centers running ads, a domain change can also mean updating the domain on file with any certification or verification program your ad platforms require, so build that lead time into the launch plan rather than discovering it when ads stop serving.

The moves that go smoothly are the ones planned as a search project, with a URL map, verified ownership, and a dated follow-up schedule. The ones that go badly are usually treated as a design launch with redirects added at the end. If you are planning a rebrand or consolidation, our SEO services and web design team plan the move and the launch together, so the search work is finished before the new site goes live.