Changing your practice website domain or host without losing search traffic

A practice changes its web address for ordinary reasons: a new name after a merger, a doctor’s name dropped from the brand, a shorter domain, or a move away from a website builder that holds the old site hostage. The new site may look better, but the old address carries years of search history, links from other sites, the website field on your Google Business Profile and the bookmarks of your patients. Handled carelessly, a domain change can send patients to error pages and drop the practice out of local search for weeks.

This guide is for practice owners and office managers planning a new domain or a new web host. It follows Google’s own site move documentation, then covers the parts that are specific to a medical practice: the forms and booking tools that may carry patient information, the old host that still holds copies of it, and the old domain you should keep. The name and brand side of a change is covered in our practice branding guide, telling patients about a move or a new name is in our guide to practice change announcements, and updating directories is in our directory listings guide.

The short version

• Decide first whether the address is changing. A new host with the same domain is a hosting move. A new domain is a site move with URL changes. Google treats them differently.
• Map each old page to its matching new page and use permanent (301 or 308) server-side redirects. Do not send old pages to the new home page in bulk.
• Verify both the old and new domains in Search Console, including www and non-www, then file a Change of Address for the old domain once the redirects are live.
• Keep the redirects for at least a year, and keep paying for the old domain for at least a year, as Google recommends. We recommend keeping it for good.
• Update the website field on your Google Business Profile, your ads, your directory listings and your own links.
• Any new form, chat or booking tool that receives patient information is a business associate and needs an agreement before it goes live (45 CFR 160.103, 164.502(e)).
• Before you close the old host, have it return or destroy patient information it holds, and document what happened to it.

Hosting move or domain change: know which one you have

Google separates two kinds of moves. Its page on changing your hosting covers a switch to a new hosting provider or a content distribution network that does not change the address patients see. Its page on site moves with URL changes covers a new domain name, a move from HTTP to HTTPS, merging domains, or changing the paths of pages. The work, and the risk, is larger for the second kind.

For a hosting move with the same domain, Google’s steps are short: copy the site to the new host and test it, lower the time to live (TTL) on your DNS records about a week ahead so the switch spreads faster, keep your Search Console verification working, remove any test blocks such as noindex, update DNS to point at the new host, then watch server logs on both hosts and shut down the old one once its traffic reaches zero. Google notes that a temporary drop in Googlebot’s crawl rate right after the switch is normal.

Google also advises changing one thing at a time. If you plan a new domain, a new content management system and a new design, its site move guide recommends doing them one after the other rather than together. For a practice, that can mean moving the current site to the new domain first and launching the redesign later, once search traffic has settled.

Map each old page to a new page

The heart of a domain change is the redirect map: a list of each old URL that matters and the new URL that replaces it. Google suggests building the list from your sitemaps, your analytics or server logs for the pages that get traffic, the Links report in Search Console, and your content management system’s list of pages. Include images and PDFs, such as new patient forms, that other sites or search results link to.

For a practice site, the pages that matter are easy to name: the home page, each service or treatment page, each location page, each provider bio, the new patient page, insurance and pricing pages, and any article that brings in visitors. Write the map down. It becomes the redirect rules, the checklist for testing and the list of links to update later.

Google’s guidance on what to do with the map is specific:

• Use server-side permanent redirects, such as 301 or 308, where your host allows them. Client-side redirects are a last resort.
• Redirect each old page to its direct equivalent. Google warns against sending a group of old URLs to one unrelated page such as the new home page, which it may treat as a soft 404. Old pages you merged into one new page may all point to that page.
• Old pages with no new equivalent should return a 404 or 410 on the new site.
• Avoid redirect chains. Googlebot follows up to 10 hops, but Google advises redirecting straight to the final page, and if a chain cannot be avoided, keeping it short.
• On a small or medium site, move all the URLs at once rather than in sections.

Google states that 301 and other permanent redirects do not cause a loss in PageRank. It also says to expect rankings to fluctuate while it recrawls, and that a small to medium site can take a few weeks for its pages to move in search results.

Search Console: both domains and the Change of Address tool

Google’s site move guide asks you to verify both the old and new sites in Search Console, including each variant: www and non-www, and HTTP and HTTPS where used. If you verify with an HTML file or a meta tag, carry it over to the new site so verification does not break. If a disavow file was uploaded for the old site, Google recommends uploading it again for the new one. For a newly bought domain, check for leftover manual actions or URL removals from the previous owner.

Once the redirects are live, file a Change of Address in Search Console from the old property. Google’s help page sets out the requirements: you must own both properties in Search Console, under the same Google account, and the tool works only on domain-level properties. It does not move subdomains, including www, so Google asks you to file for each variant of the old domain, even ones you do not actively use. The tool checks the home page redirect and a few other pages before accepting the request.

The tool does not apply to all moves. Google says not to use it for HTTP to HTTPS changes, for moving pages within the same domain, for switching between www and non-www, or for a hosting move with no visible URL change. Redirects and canonical tags handle those.

Google’s help page says notifications about the move show in Search Console for 180 days, and that after that period Google treats the old site as unrelated if it is still present and crawlable. Submit the new sitemap in Search Console, and keep the old one for a while so you can watch old URLs drop out as new ones are indexed. Google says warnings on the old sitemap about redirects are normal during a move.

Keep the redirects and the old domain

Google’s site move guide says to keep the redirects as long as possible, generally at least one year, and that from users’ point of view you may consider keeping them indefinitely. Its Change of Address page asks for at least 180 days, and longer while Google Search still sends traffic to the old URLs.

The same page recommends that you keep paying for the old domain for at least a year to prevent others from buying it and using it for malicious purposes. For a practice, the risk is plain: patients have the old address in reminder texts, printed cards, old emails and bookmarks. If the domain lapses and someone else buys it, those patients land on a site you do not control. No federal rule sets how long a practice must keep an old domain. We recommend keeping it, with auto-renew turned on and the renewal contact set to a practice email that someone reads.

If staff email addresses use the old domain, plan for them too. We recommend keeping mail on the old domain forwarding to the new addresses for as long as you keep the domain, and setting a reply that gives the new address.

Update the places that point to your old address

Redirects catch visitors, but Google asks site owners to update links directly, since each redirect slows the visitor down. Its guide names internal links, sites that link to you, profile links on social platforms, and ad campaigns. For a practice, add these:

• Google Business Profile. Google Business Profile Help says to enter the full website URL, including http:// or https://, and to make sure Googlebot is not blocked on the site. Google says certain business categories can add more links, such as for appointments.
• Google Ads and other ads. Change final URLs to the new pages, not to the redirecting old ones.
• Directories and health plan listings. Our directory listings guide covers the master record and which listings to check.
• Your own materials. Reminder and confirmation templates, email signatures, the patient portal, voicemail scripts, printed forms and signage.
• Structured data and canonical tags. Each new page should carry a self-referencing canonical tag, and your organization and location markup should list the new URL. Our schema markup guide covers the fields.

Forms, booking and chat on the new site

A website move is the moment when patient information can start flowing through tools no one has reviewed. The new site may come with a builder’s form plugin, a new booking widget, a chat tool or new analytics. Under 45 CFR 160.103, a vendor that creates, receives, maintains or transmits protected health information on behalf of a covered entity is a business associate. Under 45 CFR 164.502(e), a practice may let a business associate handle that information only after obtaining satisfactory assurance, documented in a written agreement that meets 164.504(e).

A web tool is not automatically a business associate. A host that serves only public pages and collects no patient information may not be. A form that asks for symptoms, an appointment request that names a reason for the visit, or a chat where patients type health details is another matter. Our guides to website hosting and HIPAA and contact and appointment forms go through the questions, and our tracking pixels guide covers analytics and ad tags that come along with a new theme.

No federal rule requires a practice to rebuild its forms during a move. We recommend listing each place the old site collected information, deciding for each one whether the new site needs it at all, and confirming the agreement for each tool that will receive patient information before the new site goes live, not after.

Close the old host properly

The old host, the old website builder or the old form service may still hold copies of form submissions, uploaded files or backups. If that vendor was a business associate, 45 CFR 164.504(e)(2)(ii)(J) requires the agreement to provide that at termination the business associate will, if feasible, return or destroy the protected health information it still maintains and keep no copies, or, if that is not feasible, extend the agreement’s protections to it. Under 45 CFR 164.310(d)(2)(i), a covered entity must have policies for the final disposition of electronic protected health information and the hardware or media that hold it.

No federal rule sets a timeline for closing an old website account. We recommend exporting what you are required to keep, asking the vendor in writing to return or destroy the rest, keeping their written answer, and only then closing the account. Keep the domain and the redirects running on a separate, low-cost setup if the old host was also your domain registrar.

Questions to ask your web team

• Is this a hosting move with the same domain, or a new domain with URL changes?
• Do we have a written map of old URLs to new URLs, including images and PDFs?
• Are the redirects server-side and permanent, one old page to one matching new page, with no chains?
• Are both domains and all their variants verified in Search Console under the same account?
• Who files the Change of Address, and when?
• Who owns the old domain registration, when does it renew, and is auto-renew on?
• Which forms, booking and chat tools on the new site receive patient information, and is there a signed agreement for each?
• What happens to form submissions and backups on the old host?

Use and avoid

• Use: 301 or 308 redirects from each old page to its matching new page.
• Avoid: sending all old pages to the new home page.
• Use: one change at a time, domain first and redesign later where you can.
• Avoid: launching a new domain, a new platform and a new design on the same day.
• Use: Change of Address for each verified variant of the old domain.
• Avoid: letting the old domain expire after the move.
• Use: a signed agreement for each new tool that receives patient information, before launch.
• Avoid: closing the old host account before its patient data is returned or destroyed.

An illustration

This example is invented. [Practice name], a two-location chiropractic practice, has used a domain built on the founder’s surname for years. After a new partner joins, the practice picks a new name and a new domain. Its web team builds the new site on the same content system, keeps the page structure, and writes a map of the old pages: the home page, two location pages, six service pages, three provider bios, a new patient page with a PDF intake form, and a handful of articles.

The team verifies both domains in Search Console, sets up 301 redirects page by page, tests them, then files a Change of Address from each variant of the old domain. The office manager updates the Business Profile website field for both locations, the ad final URLs and the reminder templates. The old site’s contact form had been sending messages through a form service; the practice asks that service in writing to delete stored submissions, keeps the reply, and closes the account. The old domain stays registered on auto-renew. The redesign waits two months.

Checklist

• Type of move confirmed: hosting only, or new domain with URL changes.
• Old to new URL map written, including images and PDFs.
• Server-side 301 or 308 redirects in place, one to one, no chains, tested.
• Pages with no new equivalent return 404 or 410.
• Old and new domains, with all variants, verified in Search Console.
• Change of Address filed for each old variant after redirects went live.
• New sitemap submitted; old sitemap kept to watch the move.
• Business Profile website field, ads, directories, templates and print updated.
• Agreement in place for each new tool that receives patient information.
• Old host asked in writing to return or destroy patient data; answer kept.
• Old domain kept with auto-renew; redirects kept for at least a year.

How we help

We build practice websites, local SEO, Google Ads and lead generation and an AI front desk for independent practices. For a domain change or a move to a new host, we write the redirect map, set up and test the redirects, handle Search Console and the Change of Address, update your Business Profile and ads, and review which forms and tools on the new site would receive patient information. Our tools are built with HIPAA in mind. We confirm in writing what a BAA covers before any patient information flows through a tool, and if it is not covered, we do not route patient information through it. We are not a healthcare provider and we do not give legal or medical advice. For the wider rules, see our healthcare marketing rules guide.

Sources

• Google Search Central: Site moves with URL changes (last updated August 20, 2026)
• Google Search Central: Changing your hosting (last updated December 10, 2025)
• Google Search Central: Redirects and Google Search (last updated April 14, 2026)
• Google Search Console Help: Change of Address tool
• Google Business Profile Help: Edit your Business Profile
• 45 CFR 160.103: Definitions (business associate)
• 45 CFR 164.502: Uses and disclosures of protected health information, general rules
• 45 CFR 164.504: Uses and disclosures, organizational requirements (business associate contracts)
• 45 CFR 164.310: Physical safeguards (disposal)

More in Local SEO and reviews for practices