We respect your privacy.

We use strictly necessary cookies to keep you signed in and to protect against CSRF. With your permission we also use a small amount of first-party analytics to improve the product. We do not sell your data and we do not use third-party advertising trackers. See our cookie policy and privacy policy .

← All learn topics

Rule site.duplicate-h1s

Multiple pages share the same H1

site.duplicate-h1s is a check in Crawlmind's site audit that grades medium-impact issues of this kind. This page explains why the rule matters and the exact fix.

Impact: mediumEffort: mediumFixable: 1-click

Why it matters

When two or more pages have an identical H1, search engines and AI engines treat them as competing for the same topical cluster. Result: neither page gets the full benefit of the topic, both get diluted internal-link equity, and answer engines pick effectively at random when asked a related question. Most often this happens because a template renders the section name as the H1 instead of the page-specific content.

The fix

Audit pattern:

```sh
curl -s https://example.com/sitemap.xml \
  | grep -oE "<loc>[^<]+</loc>" | sed "s/<[^>]*>//g" \
  | xargs -I{} sh -c 'echo "$(curl -s {} | grep -oE \"<h1[^>]*>[^<]+</h1>\" | head -1) {}"' \
  | sort | uniq -c -w 60 | sort -rn
```

Fix one of two ways:

1. **The pages should be one page.** Consolidate, set a canonical, redirect duplicates.
2. **The pages are legitimately distinct.** Make each H1 unique. The H1 should be the page-specific phrase, not the section name.

Good:

```html
<!-- /blog/why-we-built-crawlmind -->
<h1>Why we built Crawlmind</h1>

<!-- /blog/should-you-block-gptbot -->
<h1>Should you block GPTBot? An honest breakdown</h1>
```

Bad (both pages get the same H1 because the template emits the section title):

```html
<h1>Blog</h1>
```

References