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 Directory Architecture: Filters, Facets and URLs That Search Engines Can Crawl

Design a doctor directory search engines can crawl: which specialty, city and language combinations to index, URL and canonical rules, robots control and 404s for empty filters.

Doctor Directory Architecture: Filters, Facets and URLs That Search Engines Can Crawl

This post is for the SEO lead, product owner or developer who is building or rescuing a doctor directory for a hospital, a hospital group or a referral platform. A directory is the part of a healthcare site where filtering and URLs collide. Patients want to filter by specialty, city, language, gender, availability and insurance. Each filter can generate a URL. Combine five filters across hundreds of doctors and you can produce millions of URLs, almost all of them useless to search engines and some of them harmful.

It answers a design question: which filter combinations should have their own crawlable, indexable URL, which should exist only for users, and what rules keep the two apart? The approach is deliberate URL design with a small set of indexable landing pages, canonical rules that match, and crawl control for everything else. It assumes you control the application code or can brief the developers who do. The examples are hypothetical and use no real clinicians.

The problem: faceted URL explosion

Google describes the issue in its guidance on managing crawling of faceted navigation: crawlers may access a very large number of faceted URLs before deciding they are not useful, which slows discovery of the new and important pages. For a hospital, the cost is visible: new doctor profiles take longer to be found, and crawl effort goes to pages like "female, Tamil-speaking, available today, accepts insurer X, sorted by experience, page 4".

The same guidance sets out the toolbox. If faceted URLs do not need to appear in search, block crawling with robots.txt, and allow a single listing page with no filters. If filtering uses URL fragments (after #), it has no effect on crawling either way. The nofollow attribute is weaker because every link to a filtered URL must carry it. Canonical tags pointing filtered URLs at the unfiltered page may over time reduce crawling of the non-canonical versions but are less effective than robots.txt. If you do want faceted URLs crawled and indexed, use the standard & to separate parameters rather than commas, semicolons or brackets, keep filter order consistent for path-based filters and avoid duplicate filters. Return an HTTP 404 for combinations that produce no results.

We use those rules as the backbone of the design below.

Decide the indexable set first

Start from demand, not from the filter list. A directory has three kinds of page:

  1. Profile pages: one per doctor. These are indexable. Each doctor has one canonical profile, and listings link to it.
  2. Landing listings: combinations that match a real search intent and have enough doctors to be useful. These are indexable.
  3. Filter states: everything else. Users can use them; search engines should not spend time on them.

Which combinations deserve landing pages? Use evidence from Search Console and keyword research. For each candidate (specialty, specialty plus city, specialty plus city plus language), check whether people search the phrase and whether you have enough listings to give a helpful page. A rule of thumb that you should tune: a combination becomes indexable when it has demand and at least a minimum number of doctors, say five, with real, published profiles. Below that, the page is thin and better served by the parent listing.

A typical resulting set:

CombinationIndexable?Example URL
All doctorsYes, as the directory home/doctors
SpecialtyYes/doctors/cardiology
Specialty and cityYes, if enough doctors/doctors/cardiology/pune
Specialty, city, languageOnly for high-demand languages with enough doctors/doctors/cardiology/pune/marathi-speaking
City onlyOptional, if a general city page makes sense/doctors/in/pune
Gender, availability, insurance, sort, page sizeNofilter state only

"Language" needs care. Here it means languages a doctor speaks with patients, not the language of the website. A site that publishes pages in several languages is a separate multilingual setup with its own hreflang considerations; see our multilingual SEO service. Do not conflate the two when naming URL segments.

URL structure rules

Use paths for indexable combinations and query parameters for filter states. Path segments signal a stable landing page; parameters signal a state. This makes it easy to write rules: anything with a query string is a filter state.

Fix the segment order. /doctors/{specialty}/{city}/{language} always, never /doctors/{city}/{specialty}. Google's guidance asks for consistent filter order in path-based filters. Redirect any other order to the canonical order with a 301.

Use lowercase, hyphenated slugs from controlled vocabularies. Specialties, cities and languages come from reference lists, not free text. Keep slug aliases (for example "ent" and "ear-nose-throat") redirecting to one canonical slug.

Use standard parameter syntax for states. ?available=today&gender=female&sort=experience, with & separators and = between key and value. No comma-joined values, no brackets.

Do not allow duplicate or contradictory filters. ?gender=female&gender=male should return a clean response, either ignoring the duplicate or returning 404, and never create a new indexable URL.

Canonical rules

Canonicals should reinforce the design, not substitute for it.

URL typeCanonical
Landing listing, first pageSelf-referencing, absolute URL
Landing listing with filter parametersThe landing listing without parameters
Paginated landing listing, page 2 and beyondSelf-referencing (each page lists different doctors)
Non-qualifying combination (too few doctors)Redirect or canonical to the parent listing
Profile pageSelf-referencing at /doctors/{slug}

Google's guidance on consolidating duplicate URLs calls rel="canonical" a strong signal and redirects a strong signal as well, advises absolute paths, and notes that Google makes the final choice by content similarity. So a canonical on a filter state is a request. If the filter state differs a lot from the landing page (it shows a different set of doctors), Google may ignore it. This is one reason to also stop crawling of filter states.

Do not point the canonical of page 2 at page 1. Page 2 lists different doctors; a canonical to page 1 hides those profiles from the crawl path. Give each page of a paginated listing its own canonical, a distinct title suffix and normal crawlable links to the next page.

Crawl control

Apply layers, in order of strength:

  1. Do not generate links you do not want followed. Filters should be implemented as buttons that update state, or as links with rel="nofollow" if they must be links. Only landing listings should have plain <a href> links in navigation and facets.
  2. robots.txt disallow for filter parameters. Disallow patterns such as the query parameters used for availability, gender, insurance and sort. Per Google's guidance, there is often no good reason to allow crawling of filtered items.
  3. Canonicals on any filter URL that still gets through.
  4. Noindex only for pages that must be crawled but not indexed. Remember a page blocked in robots.txt cannot be crawled, so a noindex on it will not be seen. Pick one mechanism per URL class.

Test the robots.txt rules before release with a crawler or the testing tools in Search Console, and re-test after every change to the parameter list.

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

Book my free audit

Empty and invalid combinations return 404

When a user selects a combination with zero results, the page can show "No doctors match, try removing a filter", but the HTTP status for a path-based landing URL should be 404 if that combination has no doctors, per Google's guidance. For query-parameter states, the application can return 200 with a message for the user, since those are blocked from crawling anyway. Do not redirect empty results to the home page; that creates soft errors and confuses crawlers.

This also keeps the sitemap honest: a landing page enters the sitemap when it qualifies and leaves when it falls below the threshold or the doctors leave.

Make landing pages worth indexing

An indexable listing needs more than a grid of cards. Give each qualifying combination:

  • a unique H1 and title built from the combination ("Cardiologists in Pune")
  • a short introduction reviewed by the provider's clinical team where it describes care, with no outcome claims
  • the list of doctors, each linking to its canonical profile
  • navigation to parent and sibling listings (other cities for the same specialty, other specialties in the same city)
  • an FAQ if real patient questions support it

Avoid auto-generated filler. Listing pages for programmatic combinations need real value to avoid being thin; our programmatic SEO glossary entry and programmatic SEO service discuss where that line sits.

Structured data

Each profile can carry Physician markup. According to schema.org's Physician type, Physician includes medicalSpecialty, availableService and hospitalAffiliation. Generate the values from the same data as the visible page. Listing pages can use a simple ItemList of profile links, but only if you keep it consistent with what users see. Markup does not substitute for the architecture above. Our provider page optimisation service describes how this fits on profile pages.

Failure modes seen in directory builds

  • Client-only filtering with no URLs: everything works for users, but no landing pages exist, so there is nothing to rank. Add real routes for the qualifying combinations.
  • Every filter is a link: the crawler follows thousands of states. Change the markup, then add robots rules.
  • Canonical to the unfiltered page used as the only control: it reduces crawling over time but does not stop it.
  • Mixed ordering: /pune/cardiology and /cardiology/pune both resolve with different canonicals.
  • Thin combinations in the sitemap: pages with one doctor get submitted and then ignored.
  • Soft 404s: empty combinations return 200 with a generic message.
  • Search result pages indexed: internal free-text search should stay out of the index.

Audit and test

Before launch and each quarter:

  1. Crawl the site from the home page with a standard crawler. List URLs discovered. Any query string or non-qualifying path in the list is a leak.
  2. Compare the sitemap with the set of qualifying combinations. They should match.
  3. Request an empty combination and a duplicate-parameter URL. Check status codes.
  4. Review Search Console indexing for the /doctors path: look at "discovered, not indexed" and "crawled, not indexed" counts by pattern.
  5. Check crawl stats for requests going to filter parameters.

For a deeper technical review of an existing directory, see our technical SEO audit.

Checklist

DecisionRule
Indexable setDemand plus minimum doctors, reviewed quarterly
Segment orderFixed, with 301 for other orders
StatesQuery parameters, & separated, blocked in robots.txt
CanonicalsAbsolute, self-referencing on landings, never page 2 to page 1
Empty combinations404 for path URLs
SitemapQualifying landings and profiles only
Landing contentUnique title, H1, reviewed intro, canonical profile links
Filed underdoctor directory website architecturefaceted navigation SEOdoctor directory SEOfind a doctor page URLscanonical filters directory

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 · Healthcare websites

Work relevant to doctor directory architecture filters facets and urls that.

Explore client work →