URLs with Duplicate H1s: How to Fix Them

What this check flags

This check fires when the same H1 heading shows up on multiple different pages. The H1 is the single strongest on-page label for what a document is about — when a dozen pages all shout the same H1, you blur the topical signal, make pages look interchangeable to crawlers, and hand search engines a reason to confuse or cannibalise them. Unlike a repeated H2 within one page (a minor outline issue), duplicate H1s across pages weaken each page's individual identity.

A real failing example

A multi-location service business generated one page per city from a template — and the template hard-coded the H1:

/plumber-austin/     → <h1>Professional Plumbing Services</h1>
/plumber-dallas/     → <h1>Professional Plumbing Services</h1>
/plumber-houston/    → <h1>Professional Plumbing Services</h1>

Forty city pages, one identical H1. To a crawler they looked like forty copies of the same page — and the near-identical body text underneath didn't help. The fix was to make the H1 pull the location (and ideally a differentiator) from the template variable that already existed:

<h1>Professional Plumbing Services in {{city}}</h1>

/plumber-austin/   → <h1>Professional Plumbing Services in Austin</h1>
/plumber-dallas/   → <h1>Professional Plumbing Services in Dallas</h1>
/plumber-houston/  → <h1>Professional Plumbing Services in Houston</h1>

One template change, every page fixed. Each H1 now stated its own topic, and pairing that with genuinely local body content (service areas, local pricing, reviews) turned forty look-alikes into forty distinct pages. Rankings for "plumber [city]" queries improved as the pages stopped competing with each other.

H1 duplication vs. the neighbouring checks

Duplicate H1s rarely travel alone. When the H1 repeats, the title tag and body text are usually duplicated too, because they all come from the same template. Fixing the H1 is often the first thread you pull on a bigger templating problem — check the title and body while you're in there.

How to detect it

1. Screaming Frog. Crawl the site, open the H1 tab, and apply the Duplicate filter. It lists every H1 that appears on more than one URL, so you see the offending group in one view. Export it to hand the list to whoever owns the template.
2. Google Search Console. Duplicate H1s often accompany cannibalisation — in the Performance report, spot queries where several of your URLs collect impressions and swap positions, then check whether those pages share an H1.
3. curl / grep a URL set. Pull the H1 from a list of URLs and sort for repeats:

   for u in $(cat urls.txt); do
     echo "$(curl -s "$u" | grep -o '<h1[^>]*>[^<]*' | head -1)  $u"
   done | sort

   Identical H1 strings clustering together are your duplicates.

4. Heading analyzer. Run individual pages through a heading structure analyzer to confirm the H1 and compare across the template group.

How to fix it

1. Find the template. Duplicate H1s almost always mean a hard-coded heading in a shared template. Fix it there and every page inherits the correction — far better than editing pages one by one.
2. Inject a unique variable. Pull the location, product name, category, or other distinguishing value into the H1 ({{city}}, {{product}}) so each page states its own subject.
3. Keep one H1 per page. While fixing duplicates, confirm each page has exactly one H1 that matches its actual topic — not zero, not several.
4. Enrich the body too. A unique H1 on top of duplicated body text only half-solves the problem. Add genuinely distinct content so the whole page is unique, not just its heading.
5. Align H1 with title and intent. Make sure the fixed H1 reflects what the page is really for — see how to structure headings for SEO.

FAQ

Is a duplicate H1 across pages a ranking problem?

It's a moderate signal-dilution problem, not a penalty. Identical H1s make pages look interchangeable and often ride alongside duplicate titles and body text, which together cause cannibalisation. Fixing the H1 sharpens each page's topic and is usually part of untangling a broader templating issue.

Can two pages ever legitimately share an H1?

Rarely, and it's best avoided. Even genuinely similar pages (two product variants, two nearby locations) should differentiate the H1 so users and crawlers can tell them apart. If you can't think of a way to make the H1 unique, the pages may be too similar and belong in the duplicate content conversation instead.

How is this different from a duplicate H2?

A duplicate H2 is the same subheading repeated within one page — a minor outline/accessibility issue. A duplicate H1 is the same top-level heading repeated across different pages — a page-identity issue. Different scope, different weight.

Should each H1 include a keyword?

It should describe the page accurately, which for most pages naturally includes the primary term. Don't stuff keywords — a clear, unique, human-readable H1 that names the page's subject does the job. Uniqueness matters more than keyword density.

What if a page has no H1 at all?

That's a separate flag — every indexable page should have exactly one H1. While fixing duplicates, watch for pages with missing or multiple H1s and give each one a single, descriptive heading. See the H1 tag glossary entry.