B1 — Chapter 2 - Structure

Criterion b1-un-seul-h1-par-page : Only one H1 per page — guide + checklist

PART 1 - Fundamentals Chapter 2 - Structure Keyword : un seul h1 par page

This criterion seems “simple”, but it creates a lot of gaps in production.

Criterion **B1 — Only one H1 per page** is part of our SEO checklist (335 criteria).Here you have a **practical** method to check and correct it — with a concrete example.

What exactly this criterion covers

This criterion seems “simple”, but it creates a lot of gaps in production.

**B1 — Only one H1 per page** (Chapter 2 - Structure): A single H1 consistent with the Title tag, containing the main keyword

Why it matters (SEO + UX)

Why it matters: it’s a lever for CTR and perception in SERP.When it is poorly applied, we often observe: ambiguity (bad associated query), duplication between pages, or loss of performance on Core Web Vitals.

On sites generated in volume, this criterion also serves as a **safeguard**: a stable rule avoids 1,000 errors at once.

How to check (step by step)

Approach: crawl check (list + export).Recommended tool: **Web Developer Toolbar**.

  1. Open the source code and locate the element concerned (tag/structure).
  2. Controls hierarchy and consistency with H1 + intro.
  3. Run a crawl to detect pages that violate the criterion.

Tip: first isolate 10 “representative” URLs (top pages + generated pages) before scaling the correction.

How to correct properly

Strategy: Apply a rule, then check neighboring pages.

  • Rewrite the plan: H1 clear, H2 = sub-questions, H3 = details.
  • Adds a differentiating element (scope, method, example) to avoid duplication.
  • Checks consistency with the intention (info / comparison / action).

Next: re-crawl 50–200 URLs, then monitor Search Console over 7–14 days (impressions/CTR/indexing).

Concrete example (illustrative)

Example (illustrative):

  • **Context**: FAQ page for insurance in Lille
  • **Before**: generic H1 + sections without hierarchy (inconsistent H2/H3).
  • **After**: H1 intention-oriented + H2 by sub-questions (case: FAQ page — insurance).
  • **Note**: Objective: make the plan “scannable” and aligned with intent.

Checklist to tick

  • [ ] Hn hierarchical
  • [ ] Respects: main key
  • [ ] Summary/scanability
  • [ ] Intent aligned sections
  • [ ] Avoid repetitions
FAQ

Frequently asked questions — B1

What is the most common error on “Only one H1 per page”?

Correct an isolated page without correcting the template/import: the error returns to the next generation.

Which tool is the fastest to control at scale?

For this type of criteria, a crawl (e.g. Screaming Frog) + a targeted check in Web Developer Toolbar is generally the fastest combo.

How to prevent this from happening again on 10K pages generated?

Freeze an auto-generation rule (title/structure/schema/URLs) + add an automatic check (crawl or test) before import into production.

Ready to go from theory to action?

Validate this criterion with an audit, then deepen the method in the Academy.

Audit with the tool → Learn in the Academy →