Breakdown: Traffic Without Consultations

This is an educational teardown, not a client case study. Use it to train the habit of separating observation, hypothesis, evidence, and next action when a clinic says, "The site gets traffic, but consultations are weak."

Scenario

A single-location med spa receives organic visits to several treatment pages. The owner sees traffic in analytics, but the front desk reports few serious inquiries. The site has multiple CTAs, a booking widget, and long service copy, yet visitors seem to leave before contacting the clinic.

Observation vs interpretation

Observation	Possible interpretation	Evidence needed
Visitors land on service pages but do not complete forms.	The CTA may be too early, too vague, or too demanding.	Form analytics, click tracking, mobile recording, and field drop-off notes.
Hero copy names several services at once.	Patients may not know which path fits their concern.	Search query groups, heatmap, and support questions from front desk staff.
Reviews are on a separate page, not treatment pages.	Proof appears too late for high-consideration services.	Review themes matched to the target service page.
Booking button opens a generic scheduler.	The next step may not match service complexity.	Scheduler path QA and call notes from confused patients.

Small experiments before a redesign

Rewrite the top of one service page around patient concern, not the clinic's full service menu.
Add a mid-page proof block: provider context, consultation expectations, and two privacy-safe review themes.
Replace generic "Book now" with "Request a consultation" plus one sentence explaining what happens next.
Track calls, forms, scheduler starts, scheduler completions, and qualified consults separately.

What would make the experiment credible?

The same service page is measured before and after the edit.
Traffic source and seasonality are noted.
Front desk feedback is collected, not just form count.
The clinic defines what a useful consultation request looks like.

Avoid the easy story: traffic without consults is not automatically a design problem. It may be a measurement, trust, service clarity, pricing, or routing problem.