Clinic website design: bookings, clinician pages and GDPR-compliant forms
A clinic website answers the three questions a patient asks before booking: which treatments and clinicians, how to book, where and when. ALTAI Digital builds clinic sites around those three jobs. Bookings arrive by web form or WhatsApp. Every treatment and every clinician gets a page of its own. Forms that collect health information carry a privacy notice and explicit consent under GDPR Article 9. The site is linked to the Google Business Profile and opens in under three seconds on a phone. Delivery takes four weeks.
Private clinics in the Netherlands and the UK are found the same way, whether dental, dermatology, physiotherapy, aesthetic or psychology practices. A patient searches on a phone, looks at the Google Business Profile and its reviews, then calls or books. At that moment the site has one job: show which treatments and clinicians are available and take the booking. Both should happen without a phone call during clinic hours. A site that stops at a brochure sends the booking back to the reception desk, and reception is busiest when the phone rings.
A clinic site also carries a rule that other business sites do not. Under GDPR Article 9, health data is a special category of personal data. If a booking or enquiry form asks about symptoms or a condition, that field needs explicit consent and a privacy notice. The notice says what is collected, why and for how long. A form that does not make that distinction stores the answer like any other text and keeps no record of consent. We separate health fields, record consent with a timestamp, and leave the field out of forms that do not need it.
The wording is bound too. In the UK, advertising falls under ASA rules and health claims under the CAP code. In practice those rules restrict outcome claims, so a treatment page describes what the treatment involves rather than promising a result. Registration details belong on the site as well: CQC registration for providers in England, BIG registration for health professionals in the Netherlands. A site that shows them plainly answers a question before it is asked. It also reads more credibly than a page full of promises.
Below is the scope of a clinic site build, the four-week process and the questions we are asked most. We work from Rotterdam and Istanbul. The site is written in English and, for Dutch practices, in Dutch as well. The number of treatments and clinicians sets the page count. A two-clinician dental practice and a twelve-clinician physiotherapy group get the same structure at different sizes. Pricing is given after the discovery call, once that count is clear.
What goes wrong today
- 01
Bookings depend on the reception phone
During clinic hours nobody is free to answer, and whoever answers cannot see every clinician's diary. A patient who cannot get through books with the next practice in the results. Requests sent after hours land nowhere and are forgotten by morning.
- 02
Treatments and clinicians on a single page
The clinic offers six treatments, but the site lists them as headings. A patient searching for a treatment or a clinician by name does not find that list. Without a page per treatment and per clinician, the clinic is absent from those searches.
- 03
Health data collected without consent
The enquiry form has a symptoms box but no privacy notice and no consent tick. Under GDPR Article 9, health data is a special category and needs explicit consent. A form that does not separate that field keeps no record of who agreed and when.
- 04
Wording that promises results
Treatment pages written like adverts promise outcomes and compare the clinic with others. In the UK, advertising rules restrict outcome claims for health services. A page that describes the treatment, the clinician and the process stays within the rules and reads more credibly.
- 05
Business Profile and site out of step
One set of hours on the profile, another on the site; an old number on the map. The patient does not know which to trust and does not call. The booking link on the profile is empty, so the map never leads to a booking.
- 06
Pages that are slow on a phone
Patients search for a clinic on a phone and open the site there. An old site loads slowly and hides the booking button below several scrolls. If the page has not opened in three seconds, the patient moves to the next result.
Scope of the build
Bookings by web form and WhatsApp
The patient picks treatment, clinician, date and time. The request lands on the clinic's screen and in WhatsApp; confirmation takes one tap. After-hours requests wait in the queue for the morning. Booked slots are closed against each clinician's diary, and a reminder goes out the day before.
A page per treatment and per clinician
Each treatment gets its own page: what it involves, how a first appointment runs, which clinicians provide it. Each clinician gets a page: qualifications, registration number, treatments, working days and a booking link. A new clinician is added from the admin screen in a few minutes.
GDPR forms: privacy notice and explicit consent
If a form asks for health information, it carries a privacy notice and an explicit consent tick. The consent is recorded with date and time. Forms that need no health data ask only for name, phone and treatment. Cookie notice and privacy page are part of the same build.
Wording within advertising rules
Treatment and clinician pages are written as information, not adverts: what the treatment is, who provides it, what happens at the first visit. Outcome claims and comparisons with other clinics are left out. Texts are shown to the clinic before launch; the final say stays with the practice.
Registration details and Google Business Profile
CQC registration for providers in England and BIG registration for professionals in the Netherlands are shown where a patient looks for them. The site is linked to the Google Business Profile. Address, hours and phone are maintained from one list, and the booking link is added to the profile.
Speed and phone layout
Pages are coded from scratch in Next.js and open in under three seconds on a phone. The booking button, phone number and WhatsApp link sit on the first screen of every page. Clinician photos are resized on upload and sit next to the relevant treatment.
Admin screen and handover
Clinicians, treatments, opening hours and notices are edited from an admin screen without technical knowledge. Domain and hosting are registered in the clinic's name and the source code stays with the clinic. Reception staff get a half-hour walkthrough; a measurement report follows at the end of month one.
How the build runs
- 01
Discovery (1 week)
Treatment list, clinician profiles, opening hours and the booking flow are collected. The current site and Business Profile are measured, and we settle whether any form needs health data.
- 02
Design and writing (2 weeks)
Treatment and clinician pages are written; the booking form, WhatsApp line and consent texts are set up. An interim preview is shared at the end of week two.
- 03
Corrections and launch (1 week)
Corrections are applied and wording is read once more against advertising rules. Domain and hosting are registered to the clinic and the site goes live.
- 04
Connection and measurement
Search Console and the Business Profile are connected, pages are submitted for indexing, booking notifications are tested. A measurement report follows at the end of month one.
Clinic site with bookings
- Home, treatment pages, clinician pages, booking, about and location, contact
- Web-form and WhatsApp bookings with reminders
- Wording within advertising rules, approved by the clinic before launch
- GDPR privacy notice, explicit consent on health fields, cookie notice
- Google Business Profile and Search Console connection
- Domain and hosting in the clinic's name, source code with the clinic
Pricing is given after the discovery call, once the scope is clear.
Products used in this build
Online booking and scheduling
Online booking for clinics, salons and hotels; reminders and cancellation handling close the empty slot.
WhatsApp Business integration
Notifications, order tracking and customer conversations gather in the business account; the history stays with the company.
Request handling
Requests from five channels collect in one list, the draft reply arrives ready, and the decision to send stays with you.
Web and mobile development
Code written from scratch: web with Next.js, mobile with React Native and Swift; the repository is yours from day one.
Terms used on this page
- Special category data
- Special category data is personal data that GDPR Article 9 protects more strictly, health data included. A symptoms field on a booking form falls into it.
- Explicit consent
- Explicit consent is the patient's clear, recorded agreement to the processing of health information given on a form. The site stores it with a date and time alongside the request.
- Clinician page
- A clinician page is the page a patient finds when searching a clinician by name. It carries qualifications, registration number, treatments, working days and a booking link.
- Booking module
- A booking module is the part of the site that takes treatment, clinician, date and time and sends the request to the clinic. It closes booked slots against each diary.
- Google Business Profile
- Google Business Profile is the clinic's listing on Google Maps and in search, carrying address, hours, phone and reviews. Linked to the site, it is maintained from one source.
clinic websiteFrequently asked questions
Four weeks: one for discovery, two for design and writing, one for corrections and launch. If clinician profiles, photos and opening hours arrive in week one, the schedule holds. A practice with ten clinicians may need an extra week of writing.
Small and mid-sized practices do not. A web form and WhatsApp drop the request on the clinic's screen and confirmation goes out with one tap. Practices that want several diaries, closed slots and reminders get a booking module on the same site. A connection to an existing patient system is assessed at discovery.
What the treatment is, who provides it and what a first appointment involves. In the UK, advertising falls under ASA rules and health claims under the CAP code; both restrict outcome claims. We write treatment pages as information, not promises, and show them to the clinic before launch. The final wording is the clinic's decision.
Name, phone, treatment, date and time are not health data. Symptoms, a diagnosis or a treatment history are health data. Under GDPR Article 9 they are a special category and need explicit consent and a privacy notice. If the field is needed, the form carries both; if not, the field is not there.
Yes. Patients search for a clinician by name, and a name that appears only in a list is not found. A clinician page carries qualifications, registration number, treatments, working days and a booking link. It describes training and experience, not results. When a clinician leaves, the page is closed from the admin screen.
We measure first: speed, phone layout, treatment and clinician pages, the booking flow and how the forms handle health data. Wording that promises outcomes is rewritten either way. The decision between repair and rebuild is made on the discovery call with the measurements in hand.
Pricing depends on the number of treatments and clinicians, the booking scope and whether any form collects health data. It is given after the discovery call, in euros or pounds sterling. The scope of the clinic site with bookings is listed in the package above; discovery narrows or widens it.
The Business Profile is linked to the site during the build; hours, phone and address are maintained from one list. The booking link is added to the profile, so a patient goes from the map straight to the booking page. A clinic without a profile gets one set up during the build, verification included.
The process first, the proposal after
In a short discovery call we map the process together and tell you plainly whether it is worth automating. If it is not, we say that too.
30 minutes · no preparation needed
