Fixing Your Heading Hierarchy

Last updated: June 24, 2026

RAG systems chunk pages by heading hierarchy. A flat or broken structure means the engine can't isolate the right chunk to cite, so it either quotes the whole page (too long, gets down-weighted) or quotes nothing. This article covers the rules for a clean, AI-readable heading structure.

Why hierarchy matters for AI

When a RAG system retrieves a page, it doesn't read top to bottom. It extracts chunks defined by heading boundaries. A well-structured page looks like this to the engine:

H1: Main topic

 H2: Question 1  → chunk 1

  H3: Sub-point  → sub-chunk

 H2: Question 2  → chunk 2

 H2: Question 3  → chunk 3

A broken page, with a skipped H2, an H4 floating under the H1, or bolded text standing in for a heading, gives the engine no way to decide where chunks begin and end.

The 4 rules

Rule 1: Exactly one H1 per page. The H1 is the page's title statement and should match or paraphrase the target prompt. One per page, and a real <h1> tag, not a <div class="h1">.

Rule 2: H2s in question format. Phrase your H2s as the reader would ask them. Not "Features," "Use Cases," or "Why Choose Us," but "What features does Rankscale support?", "Who should use Rankscale?", "Why use Rankscale over [alternative]?" Question-format H2s double as FAQ candidates the engine can extract as direct answers.

Rule 3: H3s are scannable sub-points. H3s break an H2 section into short, specific, parallel sub-points. If the H3s under an H2 don't logically belong together, your H2 is too broad.

Rule 4: Never skip a level. H1 → H2 → H3 → H4. Never jump H1 → H3. Skipping breaks chunking logic and most accessibility tools flag it.

The diagnostic

  1. Run Page Audit V2.

  2. Read your scores on the HTML schema section.

  3. Improve based on the missing aspects and recommended actions.

Pass criteria: one H1 matching the topic, 3–8 question-format H2s, H3s grouped logically, no skipped levels, and no <div> or <span> masquerading as a heading with CSS.

The most common failure modes

  • Designer-built pages use styled <div> tags instead of real heading tags. The visual hierarchy looks right but the semantic hierarchy is absent.

  • CMS-autogenerated pages often wrap the title in <h2> and use <h1> for the site logo. Invert it.

  • Imported components like hero banners, CTAs, and testimonial widgets sometimes ship with their own H1. Audit every component.

Do this now

Run Page Audit V2 on your priority page. If you see more than one H1, skipped levels, or non-question H2s, file the rewrite ticket today. Fix time is typically one hour per page.

Related Articles

  • What Is an SEO Gap?

  • Making Your Content Chunkable for RAG

  • Writing Question-Format Headers

  • Adding JSON-LD Schema for AI Visibility