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
SEO

Programmatic Cost Pages Without Thin Content: Inputs That Make Each City Unique

Which structured inputs justify a separate treatment cost page for each city, and which should merge into one. A decision framework with fields, rules and failure modes for hospital chains and multi-branch clinics.

Programmatic Cost Pages Without Thin Content: Inputs That Make Each City Unique

"Knee replacement cost in Bengaluru", "knee replacement cost in Hyderabad", "knee replacement cost in Nagpur". A hospital chain with branches in twelve cities and thirty procedures can produce three hundred and sixty of these pages in an afternoon with a template and a spreadsheet. Whether it should is a different question.

This article is for SEO leads and web teams at hospital groups and multi-branch clinics who already know the basics of programmatic pages and need a decision rule. The question is narrow: which structured inputs make a cost page for one city genuinely different from another, and which inputs are only decorative. Anything in the second group should be merged, not multiplied.

We covered the general case in location pages at scale. Here we go deeper on cost pages specifically, because price is the one piece of data that is both highly searched and easy to get wrong.

What Google is likely to treat as thin

Google's spam policies describe two relevant patterns. Scaled content abuse is "when many pages are generated for the primary purpose of manipulating search rankings", whatever the generation method. Doorway abuse is "when sites or pages are created to rank for specific, similar search queries". A set of city cost pages that differ only by the city name and a changed number meets both descriptions uncomfortably well.

The policy is about purpose and value, not templates. A template is fine. Hospitals have used templates for years. What matters is whether each resulting page tells a visitor something they could not get from the page for the neighbouring city.

The inputs that can justify a separate page

We think about cost-page inputs in three groups. Think of each as a column in your content table.

Group A: price drivers that really vary by location

FieldWhy it can differ by city
room_category and tariffRoom types and rates differ by branch
implant_tierThe implants stocked or the choices offered at that site
stay_nightsTypical length of stay can differ with clinical protocols and facilities
payer_mixWhich insurers, TPAs or schemes are empanelled at that branch
surgeon_teamWhich departments and specialists operate there
facility_equipmentWhether a particular technology is available

Group B: local context that helps the reader decide

Travel and stay logistics for patients from outside the city, local airport and rail access, languages spoken, branch-specific package inclusions, and the process for getting a written estimate at that branch.

Group C: decorative inputs

City population, the city name repeated in headings, generic "why choose us in [city]" paragraphs, and stock text about the state. These add words, not information.

The rule is simple: a page needs at least two Group A or B inputs that differ in substance from the nearest sibling page, and those inputs must be backed by data you hold for that branch. Otherwise it merges.

The swap test

Before building, take a draft page for City A and replace City A with City B in the text, the table and the schema. Read it. If everything still makes sense and nothing in the numbers or inclusions is wrong, the pages are not different. Merge them into one page for the procedure with a branch comparison table, or keep a single page with a selector.

A second test is the reader's next action. If the visitor in City A and City B would do the same thing (call the same central number, request the same estimate) then one page serves both.

A worked example, clearly hypothetical

This example is invented to show the logic. The numbers are not real prices and do not describe any hospital.

Imagine a chain with branches in three cities offering unilateral knee replacement. The data table holds:

BranchRoom categoriesImplant tiers offeredTypical stay (nights)Insurers empanelledHypothetical package range
City AShared, single, deluxeStandard, premium418₹X1 to ₹X2
City BShared, single, deluxeStandard, premium417₹X1 to ₹X2
City CSingle, deluxePremium only39₹Y1 to ₹Y2

Branches A and B have the same room categories, implant tiers, stay and range. Their insurer lists differ by one name. That is not a reason for two pages. Merge them: one page for "knee replacement cost in [region or chain]" with a branch table and a note on insurer empanelment.

Branch C genuinely differs: no shared room, one implant tier, a shorter stay and a different range. This justifies its own page, because a visitor deciding between options would find different answers.

The result is two pages instead of three, and each is defensible. Multiply by thirty procedures and the saving in thin pages is large.

The data model behind the page

To make this repeatable, store the inputs as fields instead of writing prose per page. A workable table for a cost page includes:

  • procedure_id, branch_id, last_verified_date
  • room_category (list), implant_tier (list), stay_nights_typical
  • price_low, price_high, price_basis (package, estimate range, or case-by-case)
  • inclusions (list) and exclusions (list)
  • payer_list and scheme_list, each with a verified date
  • estimate_route (how a patient gets a written estimate at this branch)
  • clinical_reviewer and clinical_review_date for the explanatory text

A build script can then apply the rule automatically: if two branches have identical Group A fields, emit one page and set the other branch's URL to redirect or canonicalise to it. Google's guidance on consolidating duplicate URLs explains canonical signals; a redirect is the stronger choice when the second URL has no reason to exist.

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

Book my free audit

Legal and advertising guardrails

Cost pages touch regulation as well as SEO.

Under the Clinical Establishments rules, establishments are required to display the rates charged for their services and facilities in a conspicuous place, in English and the local language, as described in a government release. A web page is not a statutory display, but it should not contradict the rate card. Ensure the marketing team reads the same source of truth as the billing team.

The NMC's October 2026 notice allows hospitals to disclose charges factually, but bars discounts, limited-period offers, free-procedure inducements and solicitation. Keep pages free of "starting from" bait, countdowns and "book this week" language. Our NMC summary has the detail.

Consumer-law guidance on misleading advertising also applies. The CCPA guidelines on misleading advertisements address bait pricing and free claims. A "from ₹X" headline that few patients actually pay can look like bait, so show the range and the basis.

Failure modes we see

  • Stale prices. A page that was true last April and is now wrong. Fix: last_verified_date shown on the page, and a build check that fails if it is older than the interval you set.
  • Range collisions. City B's range sits inside City A's. Pages look different but say the same thing. Fix: merge or add a real differentiator such as inclusions.
  • Invented local copy. Paragraphs about a city's healthcare reputation or traffic. Fix: delete. Local context should be logistical and verifiable.
  • Schema that outruns the page. Structured data claiming offers or prices the visible page does not show. Keep markup consistent with visible content.
  • One-size clinical text. Identical explanatory text on 300 pages. Fix: write the procedure explanation once, put it on a central procedure page, and link to it.
  • No path to a number. A page that gives a range but no way to get a written estimate. The range should lead to the estimate route.

How to audit what you already have

For a chain with existing cost pages, a quick audit runs like this.

  1. Export all cost URLs and their Search Console impressions and clicks for 16 months.
  2. Crawl them and extract the price range, room categories and the first 200 words of body text.
  3. Compare each page with its nearest sibling for the same procedure. Flag pairs whose extracted fields match or whose text overlaps heavily.
  4. For flagged pairs, apply the swap test and decide: merge, differentiate, or keep with a documented reason.
  5. Check for orphaned pages that receive no internal links.
  6. Confirm every page has a price date and an estimate route.

An audit across several chains would also compare the number of cost pages per procedure with the number of distinct branch inputs. We have not published such a comparison and the numbers would be specific to each group, so treat this as a method. The ratio is the signal: many pages from few real inputs is the pattern to fix.

Governance once the pages are live

A cost-page programme fails slowly, usually after the team that built it has moved on. Three habits keep it honest.

Name an owner for the data, not the pages. The person who owns the billing rate card, or the revenue cycle team, should own the price fields. Marketing owns the wording. When a tariff changes, the field changes once and every dependent page rebuilds.

Build the check into the pipeline. A build step that compares last_verified_date with today and fails when it is older than your interval is cheap. So is a check that flags any two pages whose Group A fields are identical. Both catch problems before Google or a patient does.

Keep a change log. Record each price or inclusion change with the date and source. If a patient or regulator questions what the site said last spring, you can answer. It also helps when you decide which pages deserve a visible "updated" note.

Finally, resist adding new cities because a competitor has them. A new branch earns a page when it has its own rate card, rooms and insurer list. Until then it belongs in the branch comparison table on the main procedure page.

Where to start

  • Pick one procedure with the highest cost-query impressions
  • Build the field table for every branch and mark which fields differ
  • Apply the two-input rule and the swap test
  • Merge pages that fail, redirect the extra URLs and keep one comparison table
  • Add price date, inclusions, exclusions and estimate route to survivors
  • Only then extend to the next procedure

For templates and build planning, see our programmatic SEO service and the geo pages service.

Filed underprogrammatic SEO cost pagestreatment cost page city wisehospital cost pages thin contentprogrammatic SEO healthcarecost of treatment in city pages

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 · 15 pages

The Patient Acquisition Blueprint

A 90-day plan from first search to booked appointment.

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

Free seo 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 programmatic cost pages without thin content inputs that make.

Explore client work →