Clinic website redesign without killing local SEO
Clinic website redesign SEO: keep URLs, NAP, GBP handoffs, and service pages intact so a rebuild does not quietly wreck local visibility.
Owner-led clinics in Spain rebuild the website for a cleaner look, then notice Maps and organic softens for a few quiet weeks. The new homepage looks sharper. The phone still rings less from Google. The usual cause is not “Google hates redesigns.” It is broken URLs, thin service pages, and a Google Business Profile still pointing at paths that no longer exist.
This piece is for dental, physio, aesthetic, vet, and similar clinics with a street address. Classical SEO lane: redesign without wrecking local visibility. Not GEO. If conversion after the tap is the bottleneck, start with how a clinic website converts appointments. For Maps versus site roles, see Google Business Profile vs clinic website.
What typically breaks in a redesign
Most damage is boring and preventable.
URL changes without redirects. /servicios/endodoncia becomes /treatments/root-canal or vanishes into a generic hub. Bookmarks, old ads, review links, and Google’s index still hit the old path. Soft 404s and homepage dumps bleed equity.
A thin new homepage that replaced depth. Agencies ship a hero video, three stock cards, and “we care.” The old site had treatment copy, FAQs, and clear CTAs. People who used to land on a useful page now land on a manifesto.
Orphaned service pages. Navigation shrinks to Home / About / Contact. Treatment URLs still exist but nothing links to them, or they were deleted “to simplify.” Those pages often carried the converting queries.
GBP still pointing at old paths. The profile website field, service links, or posts still send traffic to URLs that 404. Maps wins the tap; the handoff dies.
Lost FAQs. Reception’s sticky-note answers lived on the old pages. The new site has an empty accordion or nothing. Phone tag returns the week after launch. Q&A depth: clinic FAQ pages that cut phone tag. Do not delete what already worked.
A form nobody monitors. Notifications go to a dead inbox. WhatsApp looks modern; nobody owns the reply window. An ugly site that still rang the desk phone beats a pretty one nobody answers.
Pre-redesign inventory
Export before anyone touches Figma.
- Full URL list of the live site (sitemap, crawl, or CMS export). Flag treatment, contact, blog, and booking URLs.
- Top service pages by calls and by Search Console if you have it. Ask reception which treatment pages they send people to.
- GBP website link and any service or post links that open your domain. Screenshot category, services, hours, phone.
- NAP block: trading name, street address, +34 primary phone, hours as patients see them on Maps and on the site.
- Booking paths: which form, which WhatsApp, who answers, what happens on Fridays.
- FAQs and copy you will not rewrite from scratch: for parity, not nostalgia.
Dental NAP and service+city depth: local SEO for dental clinics in Spain.
Redirect map: 301s for every important URL
Build a spreadsheet before cutover: old URL → new URL → 301. Include homepage variants and trailing-slash cases.
Keep treatment URL structure when you can. If /tratamientos/implantes already ranks and people share it, prefer keeping that path over inventing English marketing slugs nobody searched. Pretty URLs that break history lose to boring ones that keep it.
Every indexed service page gets a one-to-one 301 to the best matching new page, not to the homepage. Retired treatments redirect to the closest real service or a clear “we no longer offer X” page. Test the map on staging with a crawl. After launch, sample Search Console coverage and the GBP website tap on a phone.
Skip the redirect map and a “successful” redesign often feels like a quiet traffic collapse.
Content parity: service pages must stay useful
A redesign is not permission to replace treatment pages with three lines of brand copy. Parity means the new page still answers what reception answers: what the service is, who it is for, what the first visit includes, how to book here, who treats, practical facts, and a few real FAQs.
Use the usefulness standard in clinic service pages that get found and booked. If the old page had that depth, the new one needs equal or better depth on day one. Shipping the shell and “we’ll add content later” is how local visibility dies while design gets invoiced.
Keep working URLs for posts and FAQ blocks you already published, or 301 them into the new IA. Review themes that informed those FAQs still matter: Google reviews for clinics that help local search. If a clinician would not sign the new page, it is not ready.
GBP and NAP continuity in launch week
Treat launch week as a Maps week, not only a design week.
Update the website field on Google Business Profile the same day hosting flips. Align service names on the profile with the new H2s and with how reception names treatments. Keep one trading name and one +34 across GBP, site header/footer, and directories you still control. Redesigns often introduce a stylised lockup that does not match the Maps name. Confirm hours match. After cutover, tap “website” from the Maps card on mobile: live page, working CTA, no staging banner.
Handoff detail lives in the GBP guide above. Continuity means the same facts, same phone, updated links.
Soft launch checklist (mobile first)
Before you announce on Instagram, run this on a real phone on 4G:
- Homepage and two top service URLs load without a broken menu.
- Phone number is tappable above the fold; it dials the desk number you want.
- Booking CTA is honest: form, WhatsApp, or call. State who answers and when.
- Form test reaches a monitored inbox. WhatsApp test gets a human reply in the advertised window.
- GBP website tap lands correctly. Sample three old URLs from the redirect map.
- NAP in footer matches Maps. No leftover old phone in a forgotten widget.
- Reception has the new paths bookmarked and knows which FAQs moved where.
If any fail, delay the fanfare. An unanswered form on a pretty site burns trust faster than a dated template that still connected the call.
Honest limits
A redesign does not invent demand. Neighbourhood competition, reviews, category fit, and whether someone picks up still decide outcomes. Bad redirects and a thin brochure rebuild hurt more than an ugly old site that answered questions and kept stable URLs.
Nobody can promise that a new theme recovers positions you never earned. The useful bar is narrower: after launch, can a patient from Maps still reach the right treatment page, see the same phone and hours, and book without phone tag?
This is not a rebrand pitch. It is a constraint list: inventory, redirects, content parity, GBP continuity, answered CTAs.
If you want a second look before or right after cutover (redirect map, service-page parity, GBP handoff, whether the form reaches a person), request a free audit. Bring the old URL export, the planned new sitemap, and how reception handles web enquiries today. That usually shows whether the next hour goes to three 301s, one treatment-page rewrite, or stopping a homepage-only rebuild before it ships.