Websites for clinics and practices.

Trust comes before convenience, which inverts the whole page

Most business websites are built around an action. Buy this, book that, get a quote. A patient looking for a doctor is doing something different first: deciding whether you are competent and whether they will be treated well. Until that question is answered, no button matters. A beautifully designed booking flow on a page that has not established who you are gets no clicks, and the practice concludes the website doesn't work.

So the hierarchy is unusual. Qualifications, where you trained, syndicate registration, hospital affiliations, how long you have practised, what you actually specialise in — that is not About-page material, it is the first thing on the page. A patient scrolling for thirty seconds should have finished the trust question before they reach anything asking them to act.

This is also what search engines and AI assistants are looking for when they assess a medical page, and it is the one category where they are explicitly stricter. A page making health claims with no identifiable, credentialed author behind it is treated as a low-quality result, and correctly so. Naming the practitioner, their qualifications and their registration is both the honest thing and the thing that ranks.

The design consequence is quieter than most businesses expect. Editorial type, generous space, no motion for its own sake, no stock photograph of a smiling model in a white coat. Competence reads as restraint. A loud template actively undercuts the thing a practice is selling.

An appointment request is not a booking, and the difference is honesty

Practices ask for online booking, and what they usually mean is that patients should be able to arrange an appointment without a phone call. Those are not the same thing, and conflating them is the most common way a clinic website fails.

Real booking means the website knows your calendar. It knows Dr. so-and-so is in on Tuesdays, that the eleven o'clock slot is gone, that a first consultation needs forty minutes and a follow-up needs fifteen. That requires the site to talk to whatever system actually holds the schedule. If the schedule lives in a paper diary at reception, or in one person's head, no website can know any of it.

What a site can do honestly is take a request: preferred day, preferred time of day, new patient or returning, and a phone number. Reception confirms. The patient gets a clear message saying exactly that — requested, not booked, someone will call — and nobody turns up to a slot that was never real. That last sentence is the entire reason to care about the distinction.

If you do run scheduling software, connecting it is possible and quoted separately. The wrong order is buying a booking widget first and finding out afterwards that it cannot see the diary. We establish which situation you are in on the first call, before anything is designed.

Why we will not put a symptoms field on your website

This is the one place on this site where our advice is to collect less than you could, and it is worth explaining rather than asserting.

When somebody submits a form on a static website, the contents do not go straight to your inbox. They pass through a third-party form-processing service, which forwards them and also retains a copy, and which may log technical details of the submission. For an enquiry about a website — a name, an email, a description of a project — that is entirely appropriate, and it is exactly how our own contact form works.

Health information is a different category. A free-text box inviting a patient to describe their symptoms produces medical data about an identifiable person, sitting in a third-party account that was never chosen or assessed for that purpose, forwarded by email, and readable by anyone with access to the inbox. Nobody intends this. It happens because a form field is easy to add and the consequence is invisible.

So the form asks for what is needed to make contact: name, phone number, whether they are a new patient, and when suits them. The clinical conversation happens on the phone or in the room, where it belongs. If a practice genuinely needs intake information before a visit, that requires a system built for medical data with an agreement to match — which is a real project with a real budget, not a field on a contact page. We will tell you that plainly rather than quietly adding the box.

We are describing how we build websites here, not giving legal or regulatory advice. Your obligations as a practitioner are yours and your syndicate's to determine.

What you can advertise, and whose consent the photographs need

Two constraints specific to this category decide site architecture, and both are better known before design than after.

The first is advertising. Google restricts promotion of a range of health services and treatments, and what is allowed differs by country and by treatment. The practical effect is that a clinic often cannot run ads for the specific procedure that is most profitable, while it can perfectly well publish a thorough page about it on its own site. That pushes the strategy toward search visibility and structured, credentialed content rather than paid traffic — a different build emphasis from a restaurant or a retailer. What is permitted for your specialty is worth confirming before a page is built around ad traffic that may never be approved.

The second is imagery. Before-and-after photographs are the most persuasive content an aesthetic or dental practice has, and every one of them is identifiable medical information about a patient. Consent for use on a public website is specific, it is the practice's to obtain and hold, and it is not implied by consent to treatment. We will build the gallery; we will also ask whether the consent exists, and we will not use an image you cannot account for.

Language matters more here than the trilingual question on the Lebanon page. Patients search using everyday words and sometimes the wrong ones, while the profession writes in clinical terms — and in Lebanon that runs across Arabic, French and English at once, with French clinical vocabulary common in practice and English common online. A page written only in correct clinical terminology is invisible to the patient who does not know it. Both belong: the everyday phrasing to be found, the precise term to be trusted.