It's 10 p.m. and a child's fever won't come down. The parent has never been to your clinic, but a neighbor mentioned it. They search for the name on a phone and want to know two things: are you open tomorrow morning, and how do they reach you?
If the answer is an old directory listing with a dead phone number, they call the next clinic on the list. You'll never know they looked.
A hospital gets the same visitor on a harder day. Someone is hunting for the emergency entrance, the visiting hours, or a place to park, and has no patience to search the whole website.
This post is for the doctor who runs a small clinic and for whoever looks after a hospital's public information. The job is the same: answer the question the visitor arrived with, quickly, on a phone.
Does a clinic or hospital really need a website?
A hospital, yes. Nobody phones the main line to ask where visitors park. A clinic is closer to a judgment call. We haven't found any rule that requires one, but we'd still say yes if you want patients you haven't met yet.
We also can't give you a reliable number for how many patients look a clinic up online first. The figures that circulate mostly come from website vendors, and the hospital surveys we found are years old. We'd rather not repeat them.
Check it yourself. Ask your reception how the last five new patients found you, and what they looked at before they called. If they mention a directory listing or an out-of-date page, that's what they found instead of you.
Some doctors can get by without much. If you see only referred patients and your appointment book is full, a short page with your address, hours, and phone number is enough. Its job is to hold up when a patient's family looks you up to check.
Is a Google listing enough?
A Google Business Profile is the listing with your map pin, hours, and phone number. It's the first thing to set up, and for many patients it's the only thing they'll see. Google's own guidelines don't even require a website for one. They ask for a phone number or a website that represents your location.
What a website adds is room and control. A listing has space for your hours and a phone number. It has no space for each doctor's qualifications, what a first visit involves, or what to do before a procedure.
The listing can also point to your site, which gives patients somewhere useful to go next. The same goes for a social media page or a doctor-directory profile. They're worth having, but it's space you rent, and the platform decides how it looks.
What should a clinic website show?
The things a patient needs to decide whether to book with you. Six questions cover most of it.
A clinic website answers six questions:
- Who are the doctors? A photo, qualifications, and the conditions each one treats. Patients like to know who they'll see before they walk in.
- What do you treat? A plain list of services, written the way a patient describes the problem, with a short page for each main one saying what a visit involves.
- When are you open? Weekly hours, plus holidays and lunch breaks, kept current.
- Where are you? The address, a map link, and a landmark or parking note so a first-time visitor can find the door.
- How do I book or reach you? A phone number that starts the call when tapped, and a clear way to ask for an appointment, on every page.
- What will it cost? Your fees, or at least which insurance and payment options you accept, if you're comfortable publishing them.
What does a hospital website need on top of that?
Everything above, plus answers for people who are visiting rather than choosing. They arrive with one specific job, often under stress, so the site has to get them there fast.
A hospital website answers six more:
- Where is the emergency department? Its location and phone number belong on the homepage and in the header, not inside a menu.
- When can I visit, and where do I park? Visiting hours, directions, and parking are what people look for most, and they're what ends up in a PDF from three years ago. Give them their own pages.
- Who treats this? A department and doctor directory. Patients look for a specialty, not a building, so let them search by what they need.
- How do I prepare for my visit? What to bring, where to check in, and who to call with questions.
- What do you accept, and who handles billing? Which insurance plans you accept and who to ask about a bill.
- Can I read it in my language? Pages in each language your patients speak, if there's more than one.
Keep urgent and planned visits on separate paths. Someone looking for the emergency entrance shouldn't have to scroll past a page about the new cardiology wing.
A hospital site also has many editors: admissions, nursing, the communications office. Deciding early who can change what, and who approves it, saves a lot of confusion later.
Anything that shows a patient their own records, such as test results or a patient portal, is a different project. That's a web application with secure logins, not a website, and we'd scope it separately.
Should patients be able to book online?
Eventually, probably. You don't need it on day one, and there are three steps, each a reasonable place to stop.
- A call button. Your number on every page, one tap to dial. No patient information is collected at all.
- An appointment request form. The patient leaves a name, number, and preferred time, and your reception calls back to confirm.
- Live booking. Patients pick an open slot themselves. That needs a booking system behind it, either one you already use and link to, or one built for you.
Unless you already have a booking system, we'd start at the second step. A request form is cheap, and it shows you how many patients actually want to book online before you pay for the third.
Keep the form to what a patient would leave in a voicemail: name, phone number, a preferred time, and a short reason for the visit. Tell them not to type their medical history into that box. You can ask the rest on the phone.
And a form is not an emergency channel. Put one line beside it with the emergency number, so nobody sits waiting for a reply to a message about chest pain.
Is it safe to take patient details through a website?
It can be, if it's planned for. The simplest setup is a static site: the pages are the same for everyone, and there's no patient database behind them. That's all many clinics need, and it's what we'd recommend first.
Things change once the site starts to hold patient information, such as bookings stored in a database or a login to see appointments. That's a dynamic site, with a backend and access control, and it's where we slow down and ask questions before building anything.
Many countries treat health information as especially sensitive. The UK's data regulator lists health data as a special category with stricter rules, and in the US, HIPAA sets rules for how many health providers and their vendors handle patient information. Which rules apply to you depends on where you and your patients are.
So we don't promise compliance here. We raise the data-protection requirements that apply to you in the discovery call, before any code is written, and we'd rather say "we need to check that" than give you a confident guess.
What if we already have a website?
Then test it as a patient would: on a phone, with no help from you. Five checks tell you most of what you need to know.
- Are the hours, address, and phone number right today, including holiday hours?
- Does the phone number start a call when you tap it?
- Does it open quickly on mobile data, and does the browser call it "Not secure"?
- Does the appointment form reach a real person, and how fast do they reply?
- Can your own staff change a doctor's profile or post a closure without calling the developer?
Old sites usually fail the last one first. A site that's hard to edit stops being edited, and a patient who turns up to a closed door doesn't blame the website.
Your front desk should be able to change the hours or post a notice from a private admin screen in about a minute. If that takes an email to someone outside the clinic, the hours will be wrong sooner or later. Whether a site like that needs a rebuild or a rework depends on what's there, and we'd look before recommending either.
What does a clinic or hospital website cost to run?
A clinic site is mostly text, photos, and a map, which is the inexpensive case. Our post Does Every Business Need a Website? walks through what's free to run and what still costs money.
The part that changes is logins and bookings. If the site starts to hold patient information, a paid plan may start to make sense, and you'd pay for it only when you need it. A hospital's public site, with many pages and editors, is a bigger build, but the running costs follow the same logic.
Where do I start?
Start with the six questions: doctors, services, hours, location, contact, and fees. That's a complete first site. A request form, then live booking, can be added later without a rebuild.
It helps to bring a few things to your first conversation with us:
- A list of your services, in the words your patients use
- Each doctor's name, qualifications, and a photo, with their agreement to publish them
- Your weekly hours and any holiday closures
- Your address and how a first-time visitor finds the door
- How patients book today, and who answers the phone
- For a hospital: the departments, visiting hours, and who will edit which pages
- The address of your current website, if you have one, and what you'd change about it
Who answers matters more than it looks. A request form that sits unanswered until tomorrow is worse than no form.
A few things people ask
Is there a legal requirement for a clinic to have a website?
We haven't found one. What differs by country is what a medical practice may say in its advertising and how it handles patient data. We don't give legal advice, so check the rules where you practice before the text is final.
Should doctors' names, photos, and qualifications be on the site?
Usually, yes, because patients like to know who they will see. Get each doctor's agreement first, and make sure the qualifications you list are ones you are allowed to advertise where you practice.
Can I add online booking later?
Yes, without rebuilding the site. Because bookings collect personal details, we review the data-protection rules that apply to you before building them. You can read more about how we work.
Can patients see their test results or records on the site?
That goes beyond a website. It is a web application with secure logins, and health-data requirements need to be reviewed first. We would scope it as its own project.
We already have a website. Do we have to start over?
Not necessarily. We look at what's there first. Sometimes the content is good and the build is the problem, and sometimes it's the other way around. We tell you plainly which it is before proposing anything.
Can my staff update hours and notices ourselves?
Yes. The site comes with an admin panel, a private screen where you update hours, doctor profiles, and announcements without writing code.
Will my clinic show up on Google?
We build search engine basics into every site, such as fast pages, clear titles, and a sitemap, so Google can read and understand it. No one can promise a ranking, and it takes time to build one. A complete Google Business Profile helps alongside it.
How much will it cost to build?
We can't give an honest number before we understand your practice, because it depends on how many pages you need, whether you want booking, and how much design work is involved. Tell us what you need and we'll send a written proposal within 48 hours of a discovery call.
If you're ready to talk, our Website & E-commerce Development service covers business websites with appointment, inquiry, and contact forms, an admin panel you can update without writing code, and search engine basics built in. We've built websites for doctors, clinics, and hospitals, as simple static sites and as dynamic ones with appointment booking and patient information behind a secure login. Tell us what you offer and how patients reach you today, and we'll tell you what to build first.