Booking that ends in a phone call
A contact form and a phone number are not a booking system. Patients search out of hours, on a phone, and want a confirmed slot in under a minute. Anything slower sends them to whoever answers first.
Private clinics lose patients in the gap between finding you and booking with you. I build WordPress sites for healthcare practices with real online scheduling, accessibility built to WCAG 2.2 AA, patient data handled to GDPR standards, and the local SEO that puts you in the map pack.
Choose a practitioner, pick a slot, done — no phone call.
A brochure site tells people you exist. It rarely gets them onto the schedule. These are the three failures I find in almost every clinic audit.
A contact form and a phone number are not a booking system. Patients search out of hours, on a phone, and want a confirmed slot in under a minute. Anything slower sends them to whoever answers first.
Most patients arrive through a local search on a map. Without structured data, consistent practice details and a maintained Google Business Profile, you sit below directories that then charge you for your own patients.
Analytics firing before consent, forms mailing unencrypted patient details, contrast and keyboard traps that lock out the people most likely to need care. Invisible until an inspection, a complaint, or a breach.
Everything a private practice needs to be found, trusted and booked — built to the standards your sector is actually held to.
Real availability, confirmed instantly, synced to how your front desk already works.
So the patient searching “dentist near me” at 22:00 finds you, not a directory.
Built to WCAG 2.2 AA and EN 301 549 — tested with a keyboard and a screen reader, not just a plugin.
Health data is a special category under Article 9. It gets treated that way from day one.
Several locations or a growing team, without three disconnected websites.
Fast on a phone in a waiting room, hardened against the attacks clinics actually face.
Healthcare sites carry obligations a restaurant site never will. Retrofitting them is expensive; building for them costs nothing extra.
Under GDPR Article 9, data concerning health sits in a protected class. Booking forms, symptom fields and uploaded reports are encrypted in transit and at rest, never emailed in plaintext, and retained only as long as you have a lawful basis to keep them.
GDPR Art. 9 · LOPDGDDNo analytics, pixel or embedded map loads until the patient has agreed to it. Consent is logged, revocable, and the site works fully if they decline — which is the part most cookie banners quietly get wrong.
ePrivacy · AEPD guidanceTested with keyboard navigation and a screen reader against EN 301 549, the European reference standard. Your patients skew older and more likely to have a visual, motor or cognitive impairment — accessibility here is core function, not decoration.
WCAG 2.2 AA · EN 301 549Hosting, backups and mail routed through EU providers with signed data processing agreements. Access is logged, credentials are least-privilege, and you get a written record of who processes what — the document you need when a patient asks.
EU hosting · DPA · audit logI build to these standards and document what was done — I'm an engineer, not your lawyer. For a formal assessment of your obligations, your DPO or legal counsel should have the final word.
More appointments booked online after replacing a contact form with real scheduling.
Typical mobile LCP — the phone in the waiting room is the real test.
WCAG 2.2 conformance target on every build, verified by manual testing.
Third-party trackers firing before the patient has given consent.
Median PageSpeed score across delivered sites — measured on live URLs, verifiable on request.
Doctoralia, Doctolib and Top Doctors bring real volume, and for a new practice that is worth paying for. The problem starts when they become the only channel: you pay per patient, forever, for people who were searching for you.
Patients book with you, and the relationship stays yours.
Fast to start, rented forever, and never quite yours.
Platform names are referenced for comparison only and belong to their respective owners. Directories are a legitimate acquisition channel, and the strongest practices usually run both — the point is that the channel you own should carry the majority, not the minority, of your bookings.
I review your booking flow, local visibility, accessibility and consent setup, then hand you a prioritised report — free, no pitch.
We map every patient journey and every field you collect, so scheduling fits your front desk and the data handling is defensible.
Built on staging with weekly demos, performance budgets from day one, and accessibility tested by keyboard and screen reader.
Migration, monitoring, an accessibility and data-handling report for your records, a 30-day warranty and an optional care plan.
Yes — that's the whole point. Availability is defined by you, per practitioner and per treatment type, with buffers, blackout periods and approval rules if you want them. Bookings land in the calendar your team already uses, so nobody is checking a second system.
Data concerning health is a special category under Article 9, so it's treated as such from the first line of code: encrypted in transit and at rest, never sent by plaintext email, stored on EU infrastructure under a signed data processing agreement, with least-privilege access and a documented retention period. You get that documentation in writing at handover.
Obligations depend on your country, your legal form and whether you provide services electronically, and the direction across the EU has been steadily toward wider coverage. Rather than argue the edge cases, I build every healthcare site to WCAG 2.2 AA against EN 301 549 and document the testing — so you're covered either way. For a formal determination, ask your legal counsel.
Alongside, usually. Directories are a real acquisition channel and switching them off on day one is bad advice. The goal is to shift the balance: patients who already know your name should book on your domain at no cost per booking, while the platform keeps bringing genuinely new discovery.
No, but it should be designed rather than improvised. Each location gets its own page, hours, team and structured data so it can rank locally, while sharing one design system and one place to update content. Multisite or a shared template depends on how independently your locations operate.
Often, yes. Booking, consent, accessibility and speed can usually be fixed in place if the foundation is sound. If a theme or plugin is the actual bottleneck I'll say so plainly, with the trade-offs and the cost of each path, before anyone commits to a rebuild.
Send me your URL. I'll review your booking flow, local visibility, accessibility and consent setup, then show you exactly where patients are dropping off and what it takes to fix it.
Most clinic audits come back within two business days.
Schedule discovery call
Start a project