Consolidating Overlapping Doctor Bios and Department Pages Without Losing Rankings

This post is for the content or SEO lead at a hospital where a department page and several doctor pages describe the same procedure in nearly the same words. It gives a way to decide which pages to merge, which to rewrite and which to leave alone, using Search Console data to see where your own pages compete.

The pattern is easy to recognise. A bariatric surgery department page explains the procedure, the preparation, the recovery and the risks. Five surgeons each have a profile page that repeats most of that, because the profile template came with a "procedures I perform" block and someone filled it with the department copy. Now six URLs say the same thing, and a search for the procedure produces a shifting set of results from your own site.

Duplicate content is often discussed as if it triggered a penalty. Google's own explanation is more practical. Its guidance on consolidating duplicate URLs describes the problem as one of choice: when several URLs offer the same content, Google picks one version to show, and it may not pick the one you prefer. Your goal is to make that choice obvious, and to make sure each page you keep has a reason to exist.

Separate three different problems

"Duplicate content" covers three situations that need different fixes.

1. Exact or near-exact duplicates: the same URL reachable several ways, or two pages with identical text. Fix with redirects or canonical tags.
2. Overlapping content serving the same intent: a department page and a doctor page both trying to be the answer to "knee replacement surgery". Fix by merging or by giving each page a distinct job.
3. Similar wording serving different intents: a doctor page and a department page share boilerplate sentences but answer different questions ("who is Dr X?" versus "what is the procedure?"). Fix by rewriting, not merging.

Most hospital sites have a mix. Mislabeling type 3 as type 1 is how teams accidentally delete doctor pages that were bringing in name searches.

Step 1: Map pages to queries

The question is not whether two pages look similar. It is whether they compete for the same queries.

In Search Console, export Performance data with both query and page dimensions for the last 6 to 12 months. For the API, request the query and page dimensions together. Then for each target procedure:

• List every URL on your site that receives impressions for the procedure term and its variants.
• Note impressions, clicks and average position per URL.
• Mark which URL Google seems to prefer, and whether that changes over time.

A symptom of overlap is that several URLs each get a small share of impressions for the same query, and the ranking page changes from week to week. Another is a doctor page outranking your department page for a generic procedure term, which means a page built to present a person is being asked to explain a treatment.

For name queries, the opposite should hold: the doctor's profile should win for the doctor's name, and the department page should not.

Step 2: Assign jobs

Give each page type a job, then check that the content matches.

This is a role split, not a template. Our provider page optimisation and condition and treatment SEO services use the same logic: one canonical explanation per procedure, and individual doctor pages that link to it.

Procedure descriptions are clinical statements and need review by a qualified clinician before publication. When you consolidate, choose the version that has been reviewed most recently, and have it re-reviewed if you combine text from several sources.

Step 3: Merge or differentiate

Apply these rules for each cluster of overlapping pages.

Merge when:

• Two pages target the same intent, and neither has unique value.
• One page is clearly stronger on links, impressions and content quality, and the other adds nothing the stronger page lacks.
• The weaker page has no name-based demand (it is not a doctor's page that people search by name).

How to merge: move any unique, useful content into the surviving page, then 301 redirect the retired URL to it. Google's site move documentation notes that redirecting several older pages to a single new page is acceptable when content has been consolidated there, and warns against redirecting many unrelated URLs to an irrelevant destination.

Differentiate when:

• The pages serve distinct intents, even if the topic is shared.
• The page represents a person who is searched by name.
• Removing it would remove a path patients use to book.

How to differentiate: rewrite the weaker page so that its unique value is front and centre. For a doctor page, that means the doctor's training, the number and kind of cases they handle where this can be stated factually and approved, their approach as stated by them, languages, locations and consultation process. Replace the shared procedure explanation with a short summary and a link to the procedure page.

Do nothing when:

• Overlap is limited to a sentence or two of standard boilerplate, such as a registration number or an accreditation line.

What not to do

• Do not canonicalise every doctor page to the department page. A canonical tag asks Google to treat one URL as the representative of a set of duplicates. A doctor page is not a duplicate of a department page, and treating it as one removes the page from consideration for name searches. See Google's canonicalization guidance.
• Do not noindex pages to hide the problem unless you are certain they should not appear in search at all. A noindexed doctor page is invisible to patients searching by name.
• Do not rewrite by swapping synonyms. Rephrasing the same paragraph five ways produces five thin pages. Google's guidance on people-first content asks whether the page offers original information or analysis, and thin variations do not.
• Do not use a spun or machine-generated variant for each doctor. Clinical text that no one has reviewed carries risk beyond SEO.

If you want a wider view of why thin medical pages struggle, our post on Google's helpful content update and thin medical pages covers the quality side. This article is about the mechanical question of what to do with overlapping URLs.

Worked example, hypothetical

A 250-bed hospital in Chennai has a Cardiac Sciences department with one page on coronary angioplasty and six cardiologist profiles. Each profile includes a 300-word section on angioplasty copied from the department page.

Search Console shows, for the query "angioplasty cost in Chennai", impressions split across the department page, two doctor pages and a blog post. The ranking URL alternates.

Decision:

• The department page remains the owner for the generic procedure explanation, expanded and clinically reviewed.
• The blog post, which adds a cost-factor table the department page lacks, is merged into the department page and 301 redirected there.
• The six doctor pages lose the copied section. Each now has a three-line summary of the doctor's angioplasty practice (approved by the doctor), a link to the department page, and unique content on training, interests and consultation days.
• Name queries remain with the doctor pages.

After four to six weeks, the team checks the same query-and-page export. The success condition is clearer: one URL receiving most impressions for the procedure term, and doctor pages receiving name impressions. If the doctor pages lost name-query impressions, the rewrite removed something patients were looking for, and the team restores it.

No ranking improvement is promised. The expected benefit is a clearer signal and less internal competition.

Handling pages with different geography

A variant of the same problem appears with multi-location hospitals: one procedure page per branch with identical copy and a changed city name. If the content is the same, Google may choose one and ignore the rest. The fix is the same: one reviewed procedure explanation, and branch-specific pages that carry what is actually different, such as the doctors at that branch, the equipment, timings, parking and directions. Our multi-location SEO service covers this structure.

Redirects and the long tail

When you merge pages, plan the clean-up.

• Update internal links to point at the surviving URL directly, not through a redirect.
• Remove retired URLs from the XML sitemap.
• Keep redirects in place for as long as practical. Google's guidance for site moves suggests keeping them for at least a year.
• Check that the surviving page includes the content that earned the old page its impressions, such as a table or a FAQ block.
• Re-check structured data on the surviving page so it describes the page accurately.
• Monitor the Pages report for soft 404 or redirect errors on the retired URLs.

Checklist

• Export query and page data and identify clusters of URLs competing for the same term.
• Classify each cluster as duplicate, overlapping or merely similar.
• Assign a job to each page type and rewrite to match.
• Merge only where intent matches and no name demand exists.
• Keep doctor pages distinct and unique, and link them to the canonical procedure explanation.
• Send rewritten clinical text for review before publishing.
• 301 retired URLs to the most relevant surviving page and update internal links.
• Re-run the same export after four to six weeks and compare.

If the cluster list runs into dozens of procedures, a technical SEO audit can include this analysis for the whole site.