Resources
How to Switch Your Practice Website Without Losing Google Rankings, Directory Links or Email
A practice-specific website migration checklist: map old URLs, set 301 redirects, protect email DNS records, and update Business Profile and directory links.
By ClinicSite Editorial Team, Healthcare Practice Web Architecture · Published September 19, 2026
Generic migration checklists cover the search-engine side. A practice has extra things to lose: the website link on its Google Business Profile, directory profiles that link to a specific clinician page, booking and patient-portal links, and the email that runs on the same domain. This plan covers both, in the order you should do them.
Before you touch DNS: inventory URLs, inbound links and what ranks today
Do this while the old site is still live. Once the domain points elsewhere, some of this information is much harder to get.
1. List every URL on the old site. Google's site-move guide suggests starting with your important URLs: check your sitemaps, your analytics or server logs for the most-visited pages, and the Links report in Search Console for pages with internal and external links (Google Search Central). Include PDFs (new-patient paperwork, fee schedules) and images, which Google says should move like any other content.
2. Make sure Search Console will keep working. Google warns that verification can break when a site moves. If you verified with an HTML file, a meta tag or Google Analytics, that method may disappear with the old site. A Domain property is verified with a DNS record, which does not depend on the website itself (verification help). Set that up now.
3. Export what ranks. In Search Console, export the Performance report by page and by query, and the Links report's top linked pages (Links report). These tell you which URLs matter most.
4. List the links you do not control. For a practice, these usually include:
Google Business Profile: website link, and any appointment link
Therapist and doctor directories (for example Psychology Today, Zocdoc, Healthgrades)
Insurer provider directories
Hospital, group or referral-partner pages
Social profiles, email signatures, appointment reminder templates, voicemail, printed cards and QR codes
5. List what is embedded. Booking widgets, patient-portal buttons, contact or intake forms, chat widgets, analytics tags and maps. Each needs a decision on the new site.
6. Export your DNS records. Save a copy of every record at your current DNS host: MX, TXT (SPF, DKIM, DMARC and verification strings), CNAMEs for subdomains such as a patient portal, and A records. You will need this list in step three.
Map every old URL to a new one (provider pages first)
Build a simple table and fill it in before launch:
| Old URL | Why it matters (visits, links, directory) | New URL | Action | Tested |
|---|---|---|---|---|
| /our-team/dr-lee | Linked from two directory profiles | /team | 301 | |
| /services/implants | Top page in Search Console | /services | 301 | |
| /new-patient-forms.pdf | Linked in reminder emails | (none) | Update reminders, then 404 |
Work in this priority order: home page, clinician and provider pages, service pages, location and contact pages, insurance and fees pages, downloadable forms, then posts with external links. Provider pages come first because directory profiles and referrers may link to them directly.
Rules for the mapping:
Use server-side permanent redirects (301 or 308) where technically possible, as Google recommends (redirects guide). Google's site-move guide says permanent redirects do not cause a loss in PageRank.
Redirect to the closest equivalent page, not everything to the home page.
Avoid chains. Google advises redirecting straight to the final destination.
Let removed content return 404 or 410 if there is no equivalent page, per Google's guide.
Keep the same path where the new platform allows it. A URL that does not change needs no redirect.
Who sets up the redirects depends entirely on the new platform. Before you commit, ask your new provider in writing: can it serve permanent redirects from paths that no longer exist on the new site, and who enters them? Then plan to test every mapped URL yourself, or have your developer do it, after launch.
Domains, DNS and email: what changes and what must not
Same domain or new domain? If you keep your domain and only the page paths change, redirects and an updated sitemap are enough. If the domain itself changes, Google's Change of Address tool applies, after the redirects are live (Change of Address).
Two ways to point a domain at a new website:
| Method | What moves | Email risk |
|---|---|---|
| Edit specific records (A and CNAME) at your current DNS host | Only the website records | Low, if you leave MX and TXT records alone |
| Change nameservers to the new provider | The whole DNS zone | High: every email and verification record must exist at the new provider first |
SimplePractice's Professional Website, for example, uses the first method: an A record and a www CNAME, and it says an external MX record should not be affected "as long as your DNS settings are set up correctly" (SimplePractice). Other platforms use the second. Cloudflare's own setup guide warns that its automatic record scan "is not guaranteed to find all existing DNS records" and tells you to check email records in particular (Cloudflare).
Email checklist before any nameserver change:
MX records for your email provider
SPF, DKIM and DMARC records
Verification TXT records (Google Workspace, Microsoft 365, Search Console)
CNAMEs for subdomains: patient portal, booking, email autodiscover
Who owns the registrar login, and whether the domain is registered to the practice
Cutover day checklist
Pick a day early in the week when staff can answer calls, not the day before a holiday. Google also suggests timing a move for a lower-traffic period.
Confirm every DNS record from your export exists wherever DNS will live after the switch.
Remove any noindex tags or robots.txt blocks used while building the new site.
Point the domain.
Check that the site loads over HTTPS on both the bare domain and www.
Test redirects for every row in your mapping table. Google suggests the URL Inspection tool or a crawler.
Send email to and from the practice address, from an outside account.
Click every booking, portal and phone link.
Submit the new sitemap in Search Console.
If the domain changed, submit a Change of Address for the old domain.
Keep an offline copy of the old site's content and your mapping table.
After launch: Search Console, Business Profile, directories, insurer listings
Google Business Profile. Update the website link. Google notes that some business categories can also add links for appointments (Business Profile help).
Directories. Update the website field in each profile you listed. Point clinician profiles at the matching clinician page if one exists.
Insurer directories. Each insurer has its own process for updating provider details. Find yours and allow time.
Inbound links. Google recommends asking the sites that link to you to update their links, prioritizing by the visits each link sends.
Your own channels. Email signatures, reminder templates, voicemail scripts, social profiles and printed material.
Keep redirects for at least a year. Google recommends this as a minimum and suggests keeping them indefinitely from a user's point of view.
Monitor. Watch Search Console's indexing, Sitemaps and Performance reports. Old URLs should drop out as new ones are indexed.
What a "dip" looks like and how long it lasts (no promises)
Google's guidance is direct: "Expect temporary fluctuation in site ranking during the move," and "a small to medium-sized website can take a few weeks for most pages to move." Its Change of Address documentation adds that combining a move with a redesign of content and URL structure will "probably" cause some traffic loss while Google reassesses the pages.
Switching platforms usually changes the design and the URLs at once, so you are in that category. You reduce the risk by keeping the content and paths of your most important pages as close to the old ones as you can.
Normal: old URLs losing impressions while new URLs gain them. Not normal: a spike in "Not found" errors, pages excluded by noindex, or redirects landing on the wrong page. Those are fixable, and Search Console is where you will see them.
How ClinicSite's capture and rebuild options fit a migration
ClinicSite offers two starting points, and each has migration consequences worth knowing (AI website builder, keep your current design):
Rebuild. ClinicSite reads up to three public pages and builds a multi-page site from the facts it finds. Pages with no source material are left out. If your old site has 20 pages, the other 17 will not appear unless you add them in the Builder, so they need a destination in your mapping table.
Capture. ClinicSite fetches the real HTML and CSS of your page and opens it in the Builder. Scripts are stripped and forms are made inert, so booking widgets, chat bubbles and analytics tags from the old site will not work. Images are copied to ClinicSite storage.
What carries over. ClinicSite says built pages carry over the meta title and description from your existing site, but no JSON-LD structured data is produced. Published sites run no third-party analytics, so plan to monitor through Search Console verified by DNS.
Domains. You can bring your own domain by pointing its nameservers at Cloudflare, or register a managed .clinic domain through Spaceship after confirming the domain and price (FAQ). The nameserver route moves your whole DNS zone, so confirm with ClinicSite support that your email and verification records will be in place before you switch. A new .clinic domain is a domain change, so redirects from the old domain and Google's Change of Address both apply.
Redirects. Ask ClinicSite support whether your old URL paths can be redirected before you point your domain, and test every mapped URL yourself after launch.
Your current site stays live and unchanged until you point the domain, so you can build and check everything first.
What we do not claim
We do not claim any migration, on any platform, preserves rankings.
We have not confirmed that ClinicSite serves redirects from old URL paths. Treat redirects as something you or your developer must confirm and test.
We do not claim ClinicSite copies your existing DNS records. Confirm before changing nameservers.
If you want to see what a rebuilt version of your current site looks like before planning any of this, the free preview at /start needs no account or card and does not touch your existing site.
Related Practitioner Guides
Protect MX email records and domain ownership during cutover with our medical practice domain and DNS migration guide.
Measure how heavy page builders slow mobile LCP and hurt conversions in our WordPress plugin speed audit for clinics.
Check 2026 seat pricing, redirect tiers, and BAA limits in our Webflow vs. Framer medical website comparison.
Sequence NPI verification, GBP setup, and launch QA with our 30-day new clinic website launch checklist.
Sources
Google Search Central: How to move a site (last updated 2026-08-20)
Search Console Help: Verify your site ownership (DNS record required for Domain properties)
Google Business Profile Help: Edit your Business Profile (website and appointment links)
Cloudflare DNS: Set up a primary zone (quick scan not guaranteed to find all records; email records)
SimplePractice: Custom domain FAQs (record-level connection; MX records)
ClinicSite: Keep your current design (capture strips scripts, forms inert, images rehosted)
Frequently asked questions
- Will I lose my Google rankings if I change website platforms?
- You might see temporary changes. Google says to expect ranking fluctuation during a move, and that redesigning content and URLs at the same time will probably cost some traffic while pages are reassessed. Mapping every old URL, using 301 redirects, and keeping important pages' content close to the original reduces the risk. Nobody can promise rankings stay the same.
- Do I need redirects if I keep the same domain?
- Yes, for any page whose path changes. If /our-team/dr-lee becomes /team, the old address needs a permanent redirect to the new one, or visitors and directory links land on an error page. Pages whose path stays exactly the same need no redirect. Google's Change of Address tool is not needed for same-domain moves.
- How long should I keep redirects in place?
- Google recommends keeping redirects for at least one year, so it can transfer signals and recrawl links that point to the old URLs. It also suggests keeping them indefinitely from a visitor's perspective, while updating your own links and high-traffic external links to point directly at the new addresses.
- Will switching websites break my practice email?
- It can, if your domain's DNS moves and the email records do not come with it. Before changing nameservers, export your MX, SPF, DKIM, DMARC and verification records and confirm they exist at the new DNS provider. If you only edit the website's A and CNAME records, email records are usually left alone. Test sending and receiving on cutover day.
- Do I need Google's Change of Address tool?
- Only if your domain or subdomain changes, for example from oldpractice.com to newpractice.clinic. Google says not to use it for moves within the same domain, for switching between www and non-www, or for HTTP to HTTPS. Set up the redirects first, then submit the change in Search Console for the old site.
- What should I update after the new site launches?
- Start with your Google Business Profile website and appointment links, then each directory profile, insurer directories, and the sites that send you the most visits. Update email signatures, reminder templates and printed material too. Submit the new sitemap in Search Console and watch its indexing reports for "Not found" errors over the following weeks.
- How long does it take Google to pick up the new site?
- Google says a small to medium-sized website can take a few weeks for most pages to move, and larger sites longer. Speed depends on how many URLs you have and how fast your server responds. Submitting an updated sitemap helps discovery. Search Console's indexing and Sitemaps reports show progress page by page.
Related
- Webflow vs Framer for Medical Practice Websites: 2026 Costs, Redirects and HIPAA LimitsWebflow Premium is $25/mo, Framer Pro $30/mo plus $40 per editor, and Framer Basic has no 301 redirects. A 2026 cost, SEO and HIPAA breakdown for clinics.
- Psychiatric and Ketamine Clinic Website Examples: 6 Blueprints That Book Safely6 annotated psychiatry, TMS, Spravato and IV ketamine website blueprints: REMS 2-hour monitoring copy, off-label wording, 988 placement and LCP under 2.5s.
- New Medical Practice Website Launch Checklist (2026)A 30-day website launch checklist for new medical practices: domain, core pages, online booking, local SEO, accessibility, and QA before opening day.
- How Much Does a Medical Practice Website Cost in 2026? Three-Year Totals by ApproachWhat a U.S. medical, dental or therapy practice website costs over three years by approach, with dated vendor prices, hidden costs and a staff-time worksheet.
- All resourcesEvery ClinicSite guide in one place.
See what your clinic site could look like
Paste your current website address. You get a full generated replacement to look at, free, with no account and no card.
Free preview with no card. Previews are deleted after 7 days.