This post is for clinic groups, day-care chains and hospitals with more than one site who are deciding how to structure treatment pages. The question it answers is practical: should there be one page for each procedure, one for each procedure in each city, or something in between, and what stops that structure from turning into a pile of near-duplicate pages that Google ignores or penalises?
Our answer is a three-level architecture with one firm rule for each level. A procedure has one page that explains it. A city gets its own version of that page only when the organisation has a real, operating service there. And every page has a job that no other page on the site does. The rest of the post shows how to apply that, with a decision table, an example for a hypothetical three-city group and the failure modes to avoid.
It builds on our earlier piece on hospital service-line pages, which covers the department-level page and its structure. Here the focus is narrower: the layer below it, where procedure meets place.
Why "near me" changes the structure
Local intent is strong in healthcare, and it is one of the few areas where classic results are holding. BrightEdge's January 2026 healthcare report put AI Overview coverage for healthcare queries at 88% as of December 2025, with 93% for educational queries such as conditions, symptoms and treatments. The same report says Google tested AI answers on "near me" queries and pulled back, and that these stay in the local pack.
That divides healthcare queries into two types with different homes. Educational queries ("what is a knee replacement", "how is a hernia repaired") are heavily summarised, so the procedure page has to win by being the clearest and most trustworthy source, not by volume of text. Local-intent queries ("knee replacement in Jaipur", "hernia surgery near me") are resolved largely by map results, Business Profiles and location pages. A single page cannot serve both well. One page needs to explain, and another needs to locate.
The three levels
Level 1: the procedure page. One per procedure, for the whole organisation. It explains what the procedure is, who it may suit, how assessment works, what recovery generally involves, what risks the clinical team discusses, and what the next step is. It is written and reviewed by clinicians. It links to every location that offers the procedure and to the doctors who perform it.
Level 2: the procedure-in-city page. One per procedure per city, but only where there is a genuine service. It answers questions the procedure page cannot: who performs it in this city, at which facility, on which days, with what appointment route, and what local practicalities matter (parking, referral process, insurers accepted at this facility, languages spoken). It does not repeat the procedure explanation. It links up to the Level 1 page for it.
Level 3: the facility and doctor pages. The address, hours, map and Business Profile for each site, and individual doctor profiles. These are the entities Level 2 pages point to, and they are what local results ultimately surface.
The test for each level is whether a different person with a different question needs it. If not, it is the same page repeated.
The doorway problem
Google's spam policies define doorway abuse as pages created to rank for specific, similar queries. Its examples include multiple pages targeted at specific regions or cities that funnel users to one page, and near-duplicate pages that sit between users and the useful content instead of forming a clear, browsable structure.
Treatment-by-city pages are exactly the shape that triggers this concern when done lazily. A template with the procedure name and city swapped, the same body paragraphs and a single phone number is a doorway. A page that tells a reader in Jaipur which surgeon operates at the Jaipur centre, on which days and how to book is not.
This is why the rule at Level 2 is strict: no real service in the city, no page. A group with a flagship hospital in one city and a diagnostics collection point in another does not have a "knee replacement in the second city" service, whatever the search volume says. If patients from that city travel to the flagship, say so on the flagship's page, and on a "travelling for treatment" section of the procedure page, instead of building a city page that implies a service you do not run.
A decision table for each procedure-city pair
Use a simple gate. Create a Level 2 page only if every answer is yes.
| Question | If no |
|---|---|
| Is the procedure performed at a facility in this city, by named clinicians? | Do not create the page. Mention the city under travel information on the facility that does perform it. |
| Is there something specific to say about this city that is not true of the others? | Merge into the facility page, or into the procedure page's location section. |
| Is there a distinct booking route, phone number or appointment process? | Add it, or hold the page until it exists. |
| Can a clinician at that site review and own the page? | Hold the page. Content without an owner goes stale. |
| Does a Business Profile exist for that facility and say the same thing? | Fix the profile first. |
If the first question is the only yes, you have a facility page, not a procedure-in-city page.
A hypothetical example
Take a hypothetical day-surgery group with centres in three cities, A, B and C. Its services are hernia repair, piles surgery, cataract surgery and knee arthroscopy. The matrix of procedures and cities has twelve cells. The audit shows:
| Procedure | City A | City B | City C |
|---|---|---|---|
| Hernia repair | Yes, two surgeons | Yes, one surgeon | No |
| Piles surgery | Yes | Yes | Yes |
| Cataract surgery | No | Yes | Yes |
| Knee arthroscopy | Yes | No | No |
Applying the gate, the group would build four Level 1 pages, one per procedure, and eight Level 2 pages, one per "Yes". It would not build the four "No" cells. For City C and hernia repair, the hernia procedure page includes a short, honest line: patients from City C are seen for hernia repair at the City A or B centre, with a link to each.
If the group later opens a hernia clinic in City C, the Level 2 page is created at that point, with the surgeon's name and the actual schedule. The number of pages tracks the number of real services.
