In this article
- Readiness: the user, the rules and the owner
- 1–6: organise departments, doctors, services, locations and emergencies
- 7–11: accessible appointment, contact and patient-information paths
- 12–16: governance, performance, privacy and update ownership
- Hospital website requirements checklist
- Mistakes, and what a good hospital site does
- Questions owners ask
Readiness: the user, the rules and the owner
Watch three people who do not work at the hospital use the current site on a phone to find a cardiologist, the emergency number and the way to book. Where they hesitate is the list. Read the professional code: the site may inform — departments, doctors with qualifications, services, facilities, hours, how to book — and may not solicit or claim superiority; anything naming a doctor or a result is approved by the medical director. Name the owner of the site: one person, with the authority to change a page within a day and the duty to check doctors’ availability monthly.
Budget for photographs of the real hospital and the real doctors. A hospital site built on stock images fails the trust test before the patient reads a word.
1–6: organise departments, doctors, services, locations and emergencies
1. The emergency number is at the top of every page, tappable, with the ambulance number beside it, and the emergency page says where to go and what to bring. 2. Departments are listed as patients search them, each with its own page: what it treats, the doctors, the procedures, the facilities, how to book. 3. Doctors have individual pages with name, photograph, qualifications as registered, specialty, languages, the days and hours they consult, and a booking link — and a search by name, specialty and day. 4. Services and procedures each have a page: what it is, for whom, what to expect, how long, what decides the cost, which doctors do it, and the questions patients ask. 5. Locations: each hospital or centre has its own page with the full address, map, hours, parking, the departments at that location and its own numbers. 6. Facilities and diagnostics — ICU, imaging, laboratory, pharmacy — are described with hours and how to access them, and health packages have a page with contents and how to book.
The navigation follows the patient’s question — find a doctor, find a department, book, emergency — not the organisation chart.
7–11: accessible appointment, contact and patient-information paths
7. Booking is one tap from every doctor and department page: a phone number, a WhatsApp link, and an online booking that shows real availability or a callback promise with a time. 8. Contact is complete on one page and repeated in the footer: numbers by purpose — appointments, emergency, enquiries, insurance — addresses, hours, and a form with three fields that says what happens next. 9. Patient information is organised for the visit: what to bring, admission and discharge process, visiting hours, insurance and cashless procedures with the empanelled insurers listed, billing, reports and how to collect them, and international-patient information if relevant. 10. The site works on a cheap phone on a mobile network in under three seconds, with the number and the emergency line visible without scrolling, text large enough to read while anxious, and no pop-ups. 11. Accessibility: readable contrast, alt text on images, forms that work with a screen reader, and the local language where the community needs it.
Items 7 and 10 decide most of the appointments. A hospital site that looks good on the administrator’s laptop and takes eight seconds on a patient’s phone has failed.
12–16: governance, performance, privacy and update ownership
12. Every doctor’s page has an owner who confirms availability monthly; a doctor who has left is removed within the week. 13. Content governance: a review date on every clinical page, a rule that the medical director approves anything naming a doctor, a treatment outcome or a claim, and no testimonials without written consent. 14. Privacy: forms collect only what booking needs, a plain privacy notice, no patient data in analytics or advertising tools, no retargeting audiences built from treatment pages, and the site over HTTPS. 15. Performance and search: the site indexed, fast, with structured data for the hospital, its locations and its physicians, the same identity as the Google profiles, and analytics with call tracking so appointment enquiries by source are counted. 16. Update ownership: one named person, a monthly check of numbers, hours and doctors, and a quarterly review of the patient paths with someone who does not work there.
Checks 12 to 16 are what separate a hospital site that is true from one that was true at launch.
Checklist · use it here or print it
Hospital website requirements checklist
Twenty-two requirements in five groups. The first group is what a patient in distress needs in ten seconds; the last is what keeps the site true a year later.
0 of 22 done
What you enter stays in this browser and is not sent to us.
Mistakes, and what a good hospital site does
The mistakes: the chairman on the home page and the emergency number in the footer; departments named as the organisation names them; doctors without photographs or hours; stock images; a booking form with twelve fields; patient data leaking into ad tools; doctors who left still listed; and nobody owning the site after launch. A safeguard: at 10 pm, on a phone, find a specific doctor’s consulting days and book — if it takes more than a minute, the site is failing its user.
A good hospital site gets a worried person to the right doctor and the number in under a minute, tells them what to expect, lets them book with a tap, and is true this month. This is the hospital website work we do — the patient-path structure, the department, doctor and service pages written for patients, the booking and contact paths, the privacy and performance setup, the schema, and the governance routine with a named owner — and the free audit starts with the three strangers on their phones.
Questions owners ask
Do we need online booking with live availability?
It helps, if the hospital can keep it accurate. A callback promise with a time, a WhatsApp link and a tappable number achieve most of the benefit for hospitals whose scheduling is not yet reliable enough to publish.
Should every doctor have a page?
Every consulting doctor, yes — name, photograph, qualifications as registered, specialty, days and hours, and a way to book. Patients search for doctors by name, and a doctor page is where trust is decided.
What should the home page contain?
The emergency number, find-a-doctor, the departments, book an appointment, the locations, and a sentence saying what the hospital is. The leadership message and the awards belong further in.
Can we show patient stories?
Only with written consent, without clinical detail, and with the medical director’s approval — and never as inducement. Reviews on the Google profile, asked for ethically, do most of the trust work.
How do we keep the site up to date?
A named owner, a monthly check of every doctor’s availability and every number, a review date on every clinical page, and a rule that a doctor who leaves is removed within the week.
What does GullySales do?
The patient-path structure, the department, doctor and service pages, the booking and contact paths, privacy-safe analytics with call tracking, the schema and search setup, and the governance routine with your named owner — within the professional code. Scoped in the free audit and priced in writing.