Four minutes for the patient.
One email for you.
Everything on a Clinic Sites build serves one journey: a person with a problem finds you, trusts you and books the right clinician. No phone call, no form, no wait until morning.

Every condition page earns the booking
This is the repeatable structure. We build it once, brilliantly, then roll it out across every condition your clinic treats.
Named for the symptom
The page targets the words patients type, like “heel pain”, “pelvic pain” and “shin splints”, not the clinical taxonomy you would use at a conference. Title, headings and schema all agree on what this page answers.
Answers first
What it is, why it happens, whether it is serious, what happens if you ignore it. Written to be quoted by an AI assistant and trusted by a person at 9:41 pm.
How we treat it
Your actual approach, your equipment, your philosophy. This is where a reader decides you are the clinic that gets it.
The practitioner who owns it
Each condition has a lead clinician, chosen by you and changed whenever you like. Their face, their credentials, their story on the page.
Next available, live
Their real availability, straight from your Cliniko diary. Wed 8:20 am is an answer; “call to book” is homework.
Plain answers about the plumbing
No middleware to babysit, no patient data copied out of Cliniko. The site reads what it needs, when it needs it.
- What the site reads
- Available appointment times, per practitioner, per appointment type. The same availability your online booking page shows.
- How it connects
- A restricted Cliniko API key with the minimum permissions needed. Patient records never leave Cliniko, and the site stores none.
- Where the booking happens
- In Cliniko's own booking flow, so reminders, forms and cancellations behave exactly as they do today.
- When Cliniko is slow or down
- Times are cached briefly and degrade gracefully to your booking link. The page never breaks because an API had a bad morning.
An interface for decisions, humans for everything else
You get a simple priorities interface, and a supporting team who make changes for you. Most members never log in at all. They just email.
You send
“Emma's diary is drowning. Shift new ankle and knee work to Marcus for a while?”
We do
Marcus becomes the lead on those condition pages, his availability shows first, and the change is live before the next patient searches.
You see
A monthly report in plain English: what ranked, what got cited by AI assistants, who got booked, and what we are doing next.
From area check to live in about six weeks
- Day 0
Area check
One email. We confirm your discipline and service area are open, and hold them while we talk.
- Week 1
Discovery
Your conditions, your team, your priorities, your brand. We map the caseload you want more of.
- Weeks 2 to 5
Design and build
A site designed from your identity, never a re skinned template, with the condition journey built in and the Cliniko integration wired to your diary.
- Week 6
Launch
Live, indexed, measured. Search Console, analytics and AI visibility baselines from day one.
- Every month after
The SEO commitment
New content, technical upkeep, reporting and priority changes. The site keeps earning its keep. That is the membership.
Next: the part patients feel
The journey only converts because every page ends in a real, bookable time. See how the live availability works.
See Availability