Skip to main content
NewNMC’s advertising guidelines for doctors are in force from 6 Oct 2026. See what to change, and get a free compliance auditNew NMC advertising rules for doctors: what to change
Website

Doctor Search Filters Patients Actually Use: Availability, Language, Insurance

Which doctor search filters earn use and which add noise? A reasoned shortlist, a GA4 event design and an analysis method for pruning filters without exposing patient data.

Doctor Search Filters Patients Actually Use: Availability, Language, Insurance

This post is for the product owner, UX lead or marketing manager at a hospital whose "Find a doctor" page has a long row of filters and no evidence about which ones patients use. Filters are cheap to add and expensive to keep. Each one adds code, test cases, data to maintain, URL complexity and visual noise. Hospital teams tend to add them in response to requests: a director wants a "Gender" filter, the insurance desk wants "Insurance", a campaign needs "Available today". Nobody removes them.

It answers two questions. Which filters tend to earn their place on a doctor search, and how do you find out for your own site? The first is a reasoned shortlist from how patients decide; the second is an analytics method you can run in a few weeks. We do not report usage numbers from client sites here. The right answer depends on your city, specialties and patient mix, and the method is what transfers.

For the search side of directory design, including which filter combinations should be indexable, see our companion material on medical SEO keywords patients search; this article covers the interface and the measurement.

How patients actually choose a doctor

Before choosing filters, consider the decision. A patient looking for a specialist usually has some of these constraints:

  • A need: a symptom, a condition or a procedure, not a specialty name. Patients often do not know which specialty to pick.
  • A place: a city, a locality or "near me", driven by travel time.
  • A time: "this week" or "tomorrow", especially for new problems.
  • A language: comfort speaking about health in a particular language. In multilingual cities this is a hard constraint. The Chennai piece on winning local search when patients search in two languages describes the same pattern from the search side.
  • Cost or coverage: whether the hospital works with a particular insurer or scheme, and what a consultation costs.
  • Trust: qualifications, years of practice, and sometimes gender, particularly for gynaecology, urology and some therapy services.

A filter earns a place when it matches one of these constraints and is answerable from data you can keep accurate. That second condition kills many filters. "Available today" is worthless if the data updates weekly. "Accepts insurance" is dangerous if the list is stale, because a patient who relies on it may face a bill. Never publish a coverage or availability filter you cannot maintain, and have the billing desk confirm the data owner.

A first-pass shortlist

Here is a reasoned starting point, not a measurement.

FilterWhy it may earn useCondition for keeping it
SpecialtyPrimary way to enterNeeds patient-friendly labels and synonyms (for example "heart" mapped to cardiology)
Location or branchTravel is a hard constraintNeeds accurate placements per branch
AvailabilityUrgency drives choiceOnly if updated at least daily; otherwise show the weekly timetable
LanguageHard constraint in many citiesNeeds verified data, reviewed by the doctor
GenderHard constraint for some specialtiesShow where relevant, hide elsewhere
Insurance or schemeCost is a major concernOnly with a named owner and review date
Consultation modeVideo or in personOnly if both are actually offered
Experience, rating, priceOften requested internallyTest before keeping; may add noise

Two cautions. Rating filters on doctors need care: public star ratings for individual doctors raise reputation and compliance questions, and the provider's compliance owner should review the approach. For doctors in India, the NMC advertising rules limit what can be claimed about doctors; our NMC advertising guidelines explainer covers the current position. Sorting doctors by "best" or "most experienced" invites exactly the kind of comparison that needs review.

Second, filters that look like personalisation (such as "recommended for you") should not be built until you have data and a clear explanation for the patient.

Measure before you prune

Instrument the filter panel so that every filter interaction becomes an event. With Google Analytics 4, a minimal event design:

EventFires whenParameters
doctor_search_viewSearch page loadsentry_source (nav, campaign, organic landing)
doctor_filter_applyA filter value is selectedfilter_name, filter_value_group (not free text), filters_active_count
doctor_filter_clearA filter is removed or resetfilter_name
doctor_results_viewResults renderresult_count_bucket (0, 1 to 5, 6 to 20, more than 20)
doctor_card_clickA doctor card is openedresult_position_bucket, filters_active_count
doctor_book_startBooking is started from a result or profilesource (card or profile)
doctor_book_completeBooking is submittedsource

Parameter names are yours to choose; the structure is the point. Event parameters must be registered as custom dimensions before they appear in reports, as Google describes in its help page on custom dimensions and metrics: the dimension is created in the Admin area under custom definitions with the scope set to Event and the exact event parameter name, and it can take 24 to 48 hours to appear after data is sent. Register the parameters on day one, not after the test period, because data sent before registration is not available under that dimension.

Rules for the data:

  • No personal data in events. Send filter names and grouped values. Never send typed search text that could contain names, phone numbers or conditions. If you log free-text queries for search improvement, do that in a separate system with its own review.
  • Bucket the values. Counts and positions in buckets keep cardinality low and avoid hitting dimension limits.
  • Respect consent. Tracking should follow the consent mode you have configured, and the provider's compliance owner should approve the event design.
  • Use server logs as a cross-check. If filters call an API with parameters, API logs show usage without relying on the browser tag.

Our analytics tracking build covers how we set up this layer.

Want this applied to your practice? Get a free website audit.

Book my free audit

Run the analysis

After two to four weeks (long enough to cover a few weekly cycles and a campaign or two), build a table for each filter:

MetricDefinitionWhat it tells you
ExposureSessions where the filter was visibleThe baseline
Use rateSessions where the filter was applied, divided by exposureWhether people notice it
Zero-result rateApplications that returned no doctorsWhether the filter creates dead ends
Next-step rateSessions with a card click after applying, versus sessions with a card click without itWhether the filter helps or hinders
Booking-start rateSessions reaching booking start after using it, versus those withoutWhether it leads to action
Combination frequencyWhich filters are used togetherWhich pairs deserve defaults or presets

Report each as a count and a rate with the date range. Caution applies to the comparisons. People who use filters are different from those who do not: they have stronger intent, so a higher booking-start rate among filter users does not prove the filter caused it. Treat it as a signal and, where traffic allows, confirm with an A/B test that hides the filter for half of users. Be conservative with small samples; a filter used twelve times tells you little either way.

How to read the results

  • Low use, low zero-results, no evidence of help: a candidate for removal. Move it into an "More filters" drawer first and see if anyone looks for it.
  • High use, high zero-result rate: the filter is wanted but the data behind it is thin. Fix the data (more doctors tagged with the language, say) or hide values with no results.
  • Used after zero results: people are backing out of dead ends. Show counts beside filter values and disable values with none.
  • High use among entry sources: a campaign landing page may need the filter pre-applied, for example a language campaign landing with the language already set.
  • Pairs used together: specialty plus branch, or specialty plus language, are candidates for presets or for indexable landing pages.

Use result counts as a quality gate, too. A search that returns more than twenty doctors with no narrowing is a problem the interface should solve by suggesting one filter, not by adding five.

Interface rules that reduce noise

  • Show the two or three most-used filters inline, and put the rest behind a "More filters" control.
  • Display counts next to values and remove values that would return nothing.
  • Keep applied filters visible as chips that can be removed individually.
  • Make the filter panel usable on a phone. Much of the traffic to healthcare sites is mobile, and a panel that takes the whole screen without a clear apply button costs usage. Test interaction speed too; slow filter responses hurt the experience, and the diagnosis method is described in the guidance on Interaction to Next Paint on web.dev.
  • Allow keyboard and screen reader use. Labels, focus order and error messages are covered by our accessible clinic appointment forms thinking on the booking side, which applies here too.
  • Offer a fallback for patients who do not know the specialty: a symptom or condition entry that suggests specialties, reviewed by the provider's clinicians so it does not read as diagnosis.

For comparison with other patient-facing tools, our piece on patient portal development features patients want takes the same evidence-first approach to a different part of the journey.

A pruning routine

  1. Instrument the filters and register the parameters.
  2. Collect for two to four weeks, ideally across a campaign.
  3. Score each filter with the table above.
  4. Decide with the doctors' coordinators and the contact centre, who hear what patients ask for.
  5. Change one thing at a time, so effects can be read.
  6. Review every six months; roster changes and new services alter usage.
  7. Document each removed filter and why, so it does not return as a feature request without evidence.

If you are rebuilding the directory itself, see our provider bio pages and appointment scheduling services for how the profile and booking steps connect to the search.

Filed underdoctor search filter UXfind a doctor filtershospital doctor searchGA4 filter trackingdoctor directory filters

About the author

Co-Founder & CTO · Gurugram, India

Arush builds the systems the rest of the company runs on — the patient-acquisition pipelines, the AI chatbots, the analytics that tie a single click to a booked appointment. If a campaign reports a number, it's because something his team built is tracking it.

Free guide · 13 pages

WhatsApp AI Chatbot for Hospitals (14-Day Deploy)

The 14-day WhatsApp booking-bot implementation playbook.

The Pioneers Brief — one essay, three benchmarks, one teardown, every Thursday. Subscribe free →

Free website audit

Your next chapter starts with a conversation.

Three quick questions. We come prepared with a plan for your specialty and city.

  • A 30-minute call with a healthcare specialist
  • Your top three growth opportunities, in writing
  • Honest advice — even if that means not hiring us
  • No obligation and no hard sell
You’ll speak with a senior strategist
Consultations are hosted by Arush Thapar’s team.
Step 1 of 3Takes 30 seconds

What do you want to improve first?

Details stay privateNo obligationReply within 1 working day

Client portfolio · SEO & search visibility

Work relevant to doctor search filters patients actually use availability.

Explore client work →