Multi-specialty hospital websites, department by department

Who is a multi-specialty hospital website actually for?

Not for the hospital. For eight different patients who have nothing in common.

A multi-specialty hospital is several practices sharing a building, a reception and a name. The woman looking for a gynaecologist, the man with a knee that has stopped bending, the parent with a feverish child at ten at night, and the family who have just been told someone needs an angiography are four completely different searches with four completely different fears.

None of them searched for a hospital. They searched for their problem, and your building happened to contain the answer.

This is the thing most hospital websites get wrong. They are organised around the institution, with a Departments dropdown and a paragraph about infrastructure. That structure describes the hospital accurately and answers nobody.

Why is one Services page the most expensive mistake here?

Because a page can only answer one search properly.

A page carries one title, one description and one main heading. Google reads those to decide what it is about. A single Departments page listing eight specialties is, as far as search is concerned, a page about nothing in particular, competing against eight practices that each have a whole site about the one thing.

Eight department pages can answer eight searches, each named the way that patient names it, each explaining what is treated, who treats it, when they sit and what happens at the first visit.

For a hospital this is not a content exercise. It is the difference between appearing for “orthopedic doctor near me” and appearing only when someone already knows your name.

Do consultants need their own pages?

The ones a patient might search by name, which is most of them.

Referral here travels by name. A GP says go and see this doctor at that hospital, and the patient searches the doctor, not the institution. If there is no page for that name, one of three things happens: they land on your homepage and hunt, they land on a third-party directory listing you do not control and cannot correct, or they land on a competitor who does have a page.

A consultant page also solves an internal problem. It gives the department page somewhere credible to point, it lets you publish sitting timings that are actually current, and it means a doctor joining or leaving is a page change rather than a site-wide edit.

What happens when a hospital has more than one branch?

Each branch is treated as its own place, because Google treats it that way and so do patients.

That means a page per branch, a Google Business Profile per branch, and local groundwork per branch. Departments and doctors are then linked from whichever branch they actually sit at, so a patient in one town is never sent to a consultant who only visits the other.

The failure to avoid is a single Contact page listing three addresses. It reads as convenient and it is quietly damaging: the branches compete with each other for the same searches, and the map result weakens for all three at once.

What does the enquiry path look like at this size?

Different from a single-doctor practice, because the question is usually which department rather than whether to come.

A small clinic can send everything to one WhatsApp number. A hospital that does the same creates a bottleneck at reception and a slow answer at the worst moment. The path has to route: department enquiries where that department can answer them, appointment requests where they can be booked, and emergencies to a number that is answered rather than a form that is read tomorrow.

Getting that right is most of the work, and it is why this is the one package we quote rather than publish. Scope comes first, then the number, fixed in writing. Start with a free written review, which will tell you how many of your departments are currently findable at all. The local SEO groundwork page explains how the department and branch structure is planned, and Google Business Profile management covers running a listing per location without them cannibalising each other.