Heading Hierarchy SEO Rule

Validate proper heading hierarchy from H1 through H6 without skipping levels for semantic structure

What This Rule Checks

Validates sequential heading hierarchy (no skipping from H2 to H4), checks that the hierarchy starts with H1, detects multiple H1 tags, and warns about deep nesting beyond H4.

Why It Matters for SEO & GEO

A proper heading hierarchy helps search engines understand content structure and relationships. Skipped levels confuse both crawlers and assistive technologies.

How to Fix

Use headings in sequential order (H1, then H2, then H3). Never skip levels. Start with H1. Keep nesting to H1-H4 for most content. Treat headings as a content outline.

Examples

Bad

<h1>Title</h1><h3>Skipped H2</h3><h5>Skipped H4</h5>

Good

<h1>Title</h1><h2>Section</h2><h3>Subsection</h3>

How VibeLinter Checks Heading Hierarchy

VibeLinter’s headings/hierarchy rule performs these checks on every page:

Skipped levels detection — Flags when heading levels are skipped (e.g., H2 followed by H4 without an H3)
Starting level — Reports when the heading hierarchy starts with something other than H1
Multiple H1 detection — Notes when multiple H1 tags exist in the heading hierarchy
Deep nesting — Issues an info-level alert when headings go deeper than H4, suggesting structural simplification

Configuration

// vibelinter.config.cjs
module.exports = {
  rules: {
    'headings/hierarchy': {
      enabled: true,
      severity: 'warning',
      checkSkippedLevels: true
    }
  }
}

SEO Impact

Proper heading hierarchy affects:

Content understanding — Search engines use heading structure to understand topic relationships and content depth
Featured snippets — Well-structured headings increase chances of appearing in featured snippets and answer boxes
Accessibility compliance — Screen readers navigate by headings; skipped levels create confusion
GEO (Generative Engine Optimization) — AI models parse heading hierarchies to build content outlines; clear structure helps AI accurately represent your content in generated answers