A practice website conversion rate is meaningful only when you define the action and denominator. A phone-button click, a submitted inquiry and an attended appointment are different events. Calling all three conversions can make a report look healthy while hiding where prospective patients drop out.
Define the event before setting a target
For a website inquiry rate, divide valid website-originated inquiries by the relevant website visits or sessions, using one consistent traffic definition. Document whether repeat inquiries are deduplicated and how spam is removed. Keep click-to-call activity separate unless you can confirm that a real call occurred.
Build a small set of connected rates
Track inquiry-to-contact, contact-to-booking and booking-to-attendance alongside the website measure. Each rate points to a different part of the process. A high form completion rate with low contactability may indicate poor inquiry quality or a form problem. A strong booking rate with weak attendance calls for an examination of reminders, expectations and scheduling friction.
Use a worked example carefully
Suppose a hypothetical service page receives 500 sessions and produces 20 valid inquiries. Its inquiry rate is 4%. If eight of those inquiries become booked consultations, the inquiry-to-booking rate is 40%. These numbers are an illustration, not a benchmark or a claim about The Practice Catalyst's clients. They show why the two rates should not be treated as interchangeable.
Compare like with like
Separate paid and organic traffic when the volume supports useful analysis. Check device, service and location differences. Compare cohorts with similar follow-up time, especially when consultations are booked weeks after the initial inquiry. Small samples move sharply; report the counts beside every percentage.
Choose the next test from the weak step
If visitors rarely inquire, review the page's relevance, clarity and contact path. If inquiries rarely book, review response coverage, suitability and availability. Change one material element and record the date. A reasonable goal is improvement in a defined process under comparable conditions, rather than matching an internet average drawn from unrelated practices.
