Heading Hierarchy

Heading hierarchy is the structural skeleton of a webpage. Used well, it tells search engines, AI systems, and screen readers what the page is about and how its sections relate. Used badly, it scrambles the signal and hurts both rankings and accessibility.

The basic rules

One H1 per page. The H1 is the page’s primary heading. It should reflect the page topic, match the search intent the page targets, and align (without necessarily duplicating) the title tag.

H2s define major sections. Each H2 introduces a distinct section of the page. They should make sense read in sequence as a table of contents.

H3s nest under H2s. When a section needs subdivision, H3s break it down. Don’t skip levels (jumping from H1 directly to H3) and don’t use H3s as standalone styling for visually emphasised text.

Lower levels exist when needed. H4 to H6 are valid HTML elements. In practice, most pages don’t need them. If you’re nesting beyond H3, the section is probably better split into multiple pages.

Why heading hierarchy matters

For search engines. Google uses headings as primary signals about page structure and topic coverage. A well-structured page with clear H2s covering the expected sub-topics for a query is easier to rank for that query.

For AI retrieval. AI Overviews and answer engines extract specific passages from pages. They favour pages where headings clearly mark the boundaries of self-contained sections. A question-shaped H2 followed by a direct answer in the first sentence of the section is the format most likely to be retrieved.

For accessibility. Screen reader users navigate by headings. A page with proper hierarchy is meaningfully more usable; a page with broken or skipped headings is harder to navigate. Accessibility is a baseline expectation, not a separate consideration.

For readers. Most users scan before they read. Clear, descriptive headings let scanners decide whether to engage with a section. Cryptic or clever headings cost engagement.

Heading patterns that work

Question-shaped H2s for informational content. Headings like “What is X?”, “How does X work?”, and “When should you use X?” map cleanly onto how people search and how AI systems extract passages. Use this pattern for pages targeting informational intent.

Statement-shaped H2s for opinion or analysis content. “Why X is overrated”, “The case for Y”, and “The limits of Z” work better for analytical pieces. Forcing every heading into a question form is unnatural.

Parallel structure within a section. When an H2 introduces a comparison (for example, three approaches to a problem), the H3s introducing each approach should be parallel: same grammatical form, same level of specificity. Mixing forms makes the structure harder to scan.

Headings as a table of contents. Read the headings in order, ignoring everything else. They should form a coherent outline of the page. If they don’t, the structure needs work.

Heading patterns to avoid

• Multiple H1s. Modern HTML5 technically permits multiple H1s within sectioning elements, but search engines and accessibility tools still treat the first H1 as canonical. One H1 per page is the safe rule.
• Skipping levels. H1 directly to H3, or H2 directly to H4, breaks the document outline.
• Using headings for styling. H2s aren’t a font-size choice. If you want emphasised non-heading text, use <strong> or CSS classes.
• Generic headings. “Introduction”, “Conclusion”, “More information”, and “Other things to consider” are wasted opportunities. Headings should describe the section’s content.
• Keyword-stuffed headings. Repetitive keywords across H2s look manipulative and read poorly. One natural use of the target keyword in headings is enough.

H1 vs title tag

The H1 and title tag don’t need to be identical, but they should be consistent. The title tag is the SERP-facing label optimised for click-through; the H1 is the on-page headline optimised for the reader who has already arrived.

Common patterns:

• Identical. Acceptable. Often the simplest option.
• Title tag = H1 + brand suffix. Common and effective. Title tag adds ” | Site Name” for SERP recognition; H1 omits it.
• Title tag and H1 substantively different. Use sparingly. Significant divergence often signals a page targeting different intents in different places, which usually performs worse than a focused page.

Frequently asked questions

Does the order of H2s matter for SEO? Yes, indirectly. The order should match the logical flow a reader expects. AI retrieval systems also treat ordering as a structural signal, with earlier sections weighted slightly more for general topic association.

Can I use the same H2 text on multiple pages? Yes. Headings aren’t unique identifiers; they’re structural and semantic markers. Multiple pages can use “What is X?” as an H2 without conflict.

Are headings still important if I have schema markup? Yes. Schema markup and HTML headings serve different purposes. Schema declares structured data explicitly; headings define document structure. Both contribute to how content is parsed.