Websites

You Probably Don't Need a Website Rebuild to Rank Better

October 5, 2026

Man on a paved street tapping a map with a pin on his phone

When a resident hands you a chart note with a formatting error (a misplaced heading, an inconsistent date format), you don’t discard the note.

You read past the formatting to the clinical content, because that’s what the note is for. A reasonably competent reader gets the information out regardless of how the page looks.

Search engines read your website’s code about the same way. Worth knowing before you spend real money assuming otherwise.

What “crawling” actually is

Most of the website-rebuild pitch rests on an assumption nobody bothers to say out loud.

Google inspects your site’s code the way a code reviewer would, grading it on structure and cleanliness and general technical polish, and then rewards the sites that pass. It’s a natural thing to assume.

Everywhere else in your professional life, quality gets judged that way. Board review, peer review, chart audits. Someone competent looks closely and grades the work.

A crawler’s job is narrower. It fetches the page, pulls out the text, and works out what the page is about. It’ll render JavaScript-heavy pages when it has to. It moves through the markup fast and takes the words.

A page with clumsy code and a page with textbook-clean code, saying the same thing about the same condition, get read the same way.

The crawler doesn’t care that one of them would pass a code review.

That matters, because “your code is holding you back” is one of the most common reasons a practice gets sold a full rebuild.

It’s a plausible-sounding diagnosis, hard for a non-developer to check. And it points at a large, expensive fix.

All of which can be true while the code is perfectly fine.

What a rebuild won’t fix

A migration to a new platform, on its own, won’t:

What moves rankings for an independent practice is content depth on the conditions you actually treat, plus a small number of relevant sites linking to you, plus a Google profile that somebody actually maintains. And reviews that arrive steadily.

You can do every one of those on the platform you already have.

They all take the unglamorous work of writing and asking and maintaining, which is slower and sounds a lot less impressive than “we’re rebuilding your website.”

It’s also the work that shows up in a search result.

When a rebuild is the right call

Your platform can genuinely be the problem. When it is, the signs are specific and they’re the kind of thing you can check yourself.

Speed. If your site takes more than a few seconds to load on a phone in a parking lot with two bars of signal, that’s a real problem, and it’s one you can measure, and Google uses page-loading experience as a ranking input.

A patient who gives up waiting never becomes a contact, whatever your content says.

Mobile usability. Many patients researching a practice are on a phone.

If yours needs pinch-zooming to read a paragraph, or buries your phone number three scrolls down, you’re losing bookings that better content on a better platform would have kept.

Accessibility. A site that can’t be navigated by keyboard or read by a screen reader is failing a meaningful share of your patients, and it carries growing legal exposure on top of that, which has nothing to do with search rankings at all.

A genuine structural ceiling. If you can’t publish a new page without emailing someone and waiting a week, or you’re structurally blocked from adding the basic schema markup that identifies your practice and your credentials, then the platform itself is capping what any content work can accomplish.

Two or more of those true, and a rebuild is solving a real problem, and the platform decision deserves its own conversation.

If none of them are true and the pitch is still that your code needs to be cleaner, ask what specifically is broken.

A vague answer is itself the answer.

Ask four questions about your own site

Before you agree to a rebuild sold on code quality, spend twenty minutes on the things that actually correlate with rankings.

How many pages on your site go into real depth on one specific condition you treat? A line in a generic services list doesn’t count. When did you last add or update one of them?

Does your Google Business Profile show your correct hours and specialties, and has it picked up a review in the last month?

Is there a real bio page for you, with your credentials, linked from every piece of content you publish?

If those come back thin, that’s the work, and you can start on it with the platform you already have.

Questions practices ask about this

How do I know if my site is slow enough to be a real problem?

Test it on your own phone, off wifi, away from the office, then run the page through Google's free PageSpeed Insights and read the field data section rather than the lab score, since field data comes from real Chrome users. Largest Contentful Paint over about 2.5 seconds on mobile is Google's own line for needing work. Check your three busiest pages, not only the homepage.

What should I ask a vendor who says my code is holding back my rankings?

Ask them to name the specific thing that's broken and to show you how you can check it. A solid answer points at something verifiable, like load time on a phone off wifi, keyboard navigation, or pages you can't publish without waiting on someone. A vague answer about clean code and modern architecture, with nothing you can test yourself, tells you plenty.

If I skip the rebuild and write condition pages instead, how long before anything changes?

Months is the realistic horizon, and the range is wide because it depends on your market and how much you publish. A new page is often crawled and indexed within days to a few weeks. Google Business Profile edits like hours, categories, and services usually register faster. Ranking movement comes with no promised schedule, so plan for steady output, roughly a page or two a month, instead of one weekend of work.

Can I write the condition pages myself or do I need to hire someone?

You can write them yourself, and the raw material is already in your head, since you answer the same patient questions all day. A practical approach is to dictate 10 or 15 minutes per condition, covering what patients ask before they book and the answers you repeat constantly, then hand the recording to whoever edits, formats, and publishes it. The thinking is the part only you can do.

Photograph: Theo Decker / Pexels