**Headings are your page's table of contents — a clean H1→H2→H3 outline helps engines and AI pull the right section.** This check looks at whether your headings form a logical hierarchy with no skipped levels and enough sub-headings to break content into scannable sections. A muddled or sparse structure makes the page harder to parse, harder to navigate, and harder to extract a relevant chunk from.
It collects your page's headings and checks they form a sensible outline:
- Logical order — H1 → H2 → H3 without skipping levels (no jumping from H2 straight to H4).
- Enough structure — sufficient sub-headings to break the content into scannable sections, one topic per section.
- Descriptive headings — headings that actually label what each section contains.
Three or more headings in a logical order with no skipped levels passes; skipped levels or too few headings is a warning; effectively no sub-structure on substantial content is a fail.
GEObubbly collects the page's headings, verifies their order and that no levels are skipped, and assesses whether there's enough sectioning for the content length. It's a core Content Structure & Quality check worth 2 points, because clean hierarchy serves accessibility, readability and machine extraction at once.
Headings are the page's table of contents. A good structure goes H1 → H2 → H3 without skipping levels (don't jump from H2 straight to H4) and uses enough sub-headings to break content into scannable sections — one topic per section. This serves two audiences. Screen-reader users navigate by headings, so a clean outline is an accessibility win. And machines build a structural model from headings: well-organised sections with descriptive headings make it far easier for a search or AI engine to understand the page and extract a relevant chunk. Common failures are skipped levels (often a styling shortcut where someone picks a heading tag for its size) and a long page with almost no sub-headings — a wall of text. Both reduce how cleanly the page can be parsed and quoted. Use heading tags for structure, not appearance, and label each section clearly. Clean hierarchy underpins extractability and works with a single strong H1 across Content Structure & Quality and GEO / LLM Readiness.
A heading hierarchy is the nested structure of your H1 to H6 tags — one H1 for the page topic, H2s for main sections, H3s for sub-points — forming a logical outline like a table of contents. It matters because screen-reader users navigate by headings, and search and AI engines build a structural model of the page from them. A clean hierarchy makes the page easy to understand, scan and extract sections from; a muddled or flat one makes all three harder. Good hierarchy is a foundational signal of well-organised, accessible content.
Yes, it's a problem to skip levels — for example jumping from an H2 straight to an H4 without an H3 in between. Skipped levels break the logical outline, which confuses screen-reader navigation and muddies the document model engines build from your headings. It usually happens when someone chooses a heading tag for its visual size rather than its place in the structure. The fix is to use heading tags for hierarchy, not appearance, and control size with CSS — keep the sequence H1 → H2 → H3 without gaps.
There's no fixed number, but a substantial page should have enough headings to break the content into scannable, single-topic sections — typically at least three, and more for longer content. Too few headings produces a wall-of-text that's hard to read and hard for engines to extract sections from; far too many, with a heading every sentence, fragments the content. Aim for a heading wherever a genuine new section or sub-topic begins, so the outline maps the real structure of the page.
Yes. AI answer engines use your heading structure to understand which section addresses which question and to pull the right passage to quote. Descriptive, logically nested headings — especially question-style ones — make it easy for an engine to match a query to the relevant chunk of your page. A page with clean hierarchy and well-labelled sections is far more extractable and citable than one that's a single undivided block. So headings serve both classic SEO comprehension and GEO extractability.
No — choose heading tags for their place in the document structure, not for how big they look, and use CSS to control appearance. Picking an <h4> just because you want smaller text, or skipping straight to an <h3> for visual reasons, breaks the logical outline that screen readers and engines rely on. Keep the hierarchy meaningful (H1 → H2 → H3 in order) and style each level however you like. Separating structure from presentation keeps the page both accessible and machine-readable.