Redesigning a Clinic Website Without Losing Your Google Rankings

You are about to replace the website of your clinic or practice, and one question comes up at every meeting: “Will we disappear from Google?” The honest answer is that a redesign does not cost you rankings by itself. Mistakes during the move do. Google’s own guidance on website redesign and SEO is clear that permanent redirects do not lose link value, so what you have to avoid is the long list of small things that quietly break the move.

In plain wordsRedirects are the “we have moved” sign on your old door. If the sign sends every patient to reception, nobody finds the doctor they came for.

Google’s documentation on site moves lists the same mistakes again and again, and a clinic site makes every one of them easy:

• Blocks left over from development. Many sites are hidden from Google while they are built, with noindex tags or a robots.txt that blocks everything. If those are still there on launch day, the new site will not be indexed.
• Redirects that point to the wrong place. Google says it often sees old addresses redirected to new addresses that do not exist.
• Everything redirected to the home page. If dozens of old pages all go to one unrelated page, Google can treat that as a soft 404 error, and a patient who clicked a doctor’s name lands on a generic page.
• Chains of redirects. Page A goes to B, B goes to C. Google can follow up to ten hops, but it advises sending visitors straight to the final address, and if that is impossible, keeping the chain to three hops at most.
• Old sitemaps. The sitemap still lists the old addresses.
• A server that cannot cope. After a move Google crawls your site more heavily than usual, because it follows the redirects as well as its normal crawling.
• Deleted pages that do not say so. Pages you removed on purpose should return a proper 404 or 410, not a blank page with a 200 status.

1. List your old addresses. Start with the ones that matter: pages in your sitemap, pages that get the most visits in your analytics or server logs, and pages with links to them in Search Console. Include images and PDFs (price lists, patient information) if people find them in Google.

2. Map every old address to a new one. This is the real work, and it is a table, not a setting: one row per old address, one new address per row. For a clinic that means doctors, services, prices, news, contact and branch pages, and every language version.

3. Build and test the new site on a copy. Fill it with the real content, check forms and booking, and prepare what robots.txt and indexing rules will look like on launch day.

4. Set up permanent redirects on the server. Google recommends server-side permanent redirects, such as 301 or 308, straight to the final address. Test them in bulk with a crawler or a script before launch.

5. Fix the details on the new pages. Each new page needs a canonical link pointing to itself, internal links must use the new addresses, the sitemap lists the new addresses, and, if the site has several languages, the language annotations use the new addresses too.

6. Launch one change at a time, at a quiet moment. Google’s advice is to avoid changing the domain, the CMS and the layout all at once, and to time the move for a period of lower traffic. A redesign on the same domain is already enough of a change.

7. Watch it. Watch Search Console (indexed pages, errors, search queries), your server logs for unexpected errors, and analytics. Also watch what a clinic cares about most: calls, booking requests and form submissions.

8. Keep the redirects. Google’s guidance is to keep them as long as possible, generally at least a year.

• Doctors come and go. A doctor who has left the clinic should not send visitors to the home page. If the page is gone for good, a proper 404 or 410 is correct. If you have merged it into a team page, redirect it there.
• Services are renamed and merged. Moving “Dental implants” and “Implantation” into one page is fine, provided both old addresses redirect to that page.
• Price lists and PDFs get links. People share and bookmark them. Redirect them or keep them.
• Several languages mean several sets of addresses. Every language version needs its own redirect, and the language annotations must be updated with the new addresses (see a multilingual clinic website).
• Booking and contact tracking. Make sure the new booking widget, the phone-click tracking and the forms report to the same analytics as before, or you will not be able to tell whether the move worked.
• Links you control. Update your address in your profiles, social media pages and any adverts that point to old pages. Google lists these as links to update straight after the move.

On a recent project we built a new site for a dental surgery clinic to replace an old one, in three languages. We built the theme from the designs, moved the content, and gave the new pages the same addresses as the old ones wherever we could, so that fewer redirects were needed. We set up redirects for the rest. On another clinic project, a reproductive-medicine clinic, we moved a site that was not on WordPress onto WordPress with doctors, services and a price list. In both cases the approach was the same: the list and the mapping first, the design second.

Not by itself. Google says 301 and other permanent redirects do not lose PageRank. What hurts is a move with mistakes in it: wrong redirects, leftover blocks, old sitemaps, missing pages. Expect small fluctuations for a few weeks even when everything is right.

For a medium-sized site, Google says it can take a few weeks or more for the new addresses to replace the old ones in search, and longer for bigger sites. It depends on how many addresses you have and how fast your server is.

Better not. Google advises changing one thing at a time. If you do change the domain, you also need to submit a Change of Address in Search Console for every variant of the old one.

As long as possible, and Google says generally at least one year. For visitors, you can keep them indefinitely.

No. Google warns that sending many old addresses to one unrelated page, such as the home page, can be treated as a soft 404 and confuses visitors. Each old page should go to its closest new page.

If you are handing this over, these are the specifics worth checking:

• Mapping. One CSV, old address to new address and status code. Build it from the sitemap, analytics, server logs and the links report in Search Console. Include images, PDFs, CSS and JavaScript files that have their own addresses.
• Redirects. Server-side 301 or 308, directly to the final address; chains of at most three hops, ideally none. Test the whole list with a crawler, and single addresses with the URL Inspection tool.
• Removed pages. A real 404 or 410. Consolidated pages redirect to the consolidated page, not to the home page.
• Before and after. Remove noindex and robots.txt blocks that were only needed for development. Each new page has a self-referencing canonical. Update internal links, the sitemap and hreflang annotations to the new addresses.
• Search Console and analytics. Verify every variant of the site (www and non-www, http and https, every language directory). Make sure the verification still works on the new site. Keep the analytics data continuous.
• Capacity. Expect heavier crawling by Google after the move, and check that the server and caching cope with it.
• Monitoring. Server logs for 404 spikes and for Googlebot behaviour; Search Console index and sitemap reports; bookings, calls and form submissions.
• Duration. Keep the redirect rules for at least a year.

We build clinic websites on WordPress with doctor and service pages, online booking and several languages, and we plan the old-to-new address mapping before the design starts. Tell us about your clinic: within two working days we send a structure review, an indicative timeline and a price, with no obligation. The price is fixed before work starts. See our clinic website page.