What Is Heading Structure (H1-H6)?
Heading structure is the hierarchy of HTML heading tags, H1 through H6, that organizes a web page's content into a logical outline. The H1 is the main title of the page, H2s are major sections, H3s are subsections beneath them, and so on down to H6. A clear heading hierarchy helps readers scan, helps screen readers navigate, and helps search engines and AI systems understand how a page's content is organized. Proper headings improve accessibility, usability, and SEO all at once.
- Six levels
- H1 through H6, forming a nested outline (HTML spec)
- One H1 convention
- One primary H1 per page is the widely recommended practice (industry-typical)
- Accessibility role
- Screen readers let users navigate by heading level (WCAG / W3C)
- SEO role
- Headings help search engines parse content structure and context (Google Search Central)
What is heading structure? #
Heading structure is the way a page's content is broken into a nested hierarchy using HTML heading tags. HTML provides six levels, from H1 down to H6, and together they form an outline of the page much like the headings and subheadings in a well-organized document. The H1 is the page's main title, describing the overall topic. H2s mark the major sections of that topic, H3s break those sections into subsections, and the deeper levels handle further nesting when needed. Most pages only need H1 through H3. The point of the hierarchy is meaning, not just appearance: headings tell browsers, assistive technologies, and search engines how the content is organized and which parts belong to which. When headings are used correctly, a page reads like a clear outline. When they are misused, applied for visual size rather than structure, that outline breaks down, confusing both people and machines. Good heading structure is a shared foundation for accessibility, usability, and /wiki/what-is-local-seo.
What does each heading level do? #
Each level in the hierarchy has a role. The H1 is the single most important heading, the title of the page, and it should describe the whole page's subject clearly; convention is one H1 per page. H2s divide the page into its main sections, the big chunks a reader would expect from a table of contents. H3s sit under H2s to break a section into smaller parts, and H4 through H6 nest further for deeply detailed content, though most pages rarely go past H3. The key rule is that levels should nest logically, without skipping: an H3 belongs under an H2, not directly under an H1 with no H2 in between. Think of it like a legal outline where numbered points contain lettered sub-points. When the nesting is clean, the outline makes sense read aloud or scanned. When levels are skipped or used out of order, the structure becomes ambiguous, which hurts screen reader users most and muddies the signal to search engines about how content relates.
Why does heading structure matter for SEO? #
Search engines use headings to understand what a page is about and how its content is organized. The H1 gives strong context about the primary topic, and H2s and H3s reveal the subtopics and questions the page covers, helping search engines match the page to relevant queries. Well-structured headings that naturally include relevant keywords, phrased the way people actually search, make it easier for a page to rank for those subtopics. Headings also improve the on-page signals indirectly: a clearly structured page is easier to read, so visitors stay longer and engage more, which supports performance. This matters even more for AI-driven search, where systems parse headings to extract and summarize answers; a page with a clean question-and-answer heading structure is easier to lift into an AI Overview, as discussed in /wiki/ai-search-optimization. Headings are not a magic ranking lever, but they are a genuine part of how machines comprehend a page, and neglecting them leaves comprehension and rankings on the table.
How do headings help accessibility? #
For people who use screen readers, headings are the primary way to navigate a page. Screen reader users can pull up a list of all headings and jump between them, or move heading by heading, to find the section they want without listening to every word. This only works if headings are real HTML heading tags used in a logical order. If a designer styles bold text to look like a heading without using a heading tag, a screen reader user cannot navigate to it, and the page becomes far harder to use. Skipped levels also cause confusion, because the user cannot tell how sections relate. Proper heading structure is a core requirement of accessibility standards and a recurring finding when we run checks with our /tools/ada-compliance-checker. Beyond screen readers, clear headings help everyone, including people with cognitive differences who rely on visual structure to process content. Accessible headings and good SEO reinforce each other, which is why /wiki/what-is-ada-website-compliance and heading structure go hand in hand.
What are common heading mistakes? #
Several heading mistakes appear again and again. The most common is using headings for visual size instead of meaning, for example choosing an H4 because the designer wanted smaller text, which breaks the logical outline. Another is having multiple H1s or no H1 at all; while HTML5 technically permits multiple H1s in some contexts, one clear H1 per page remains the safest, most widely supported practice. Skipping levels, such as jumping from an H2 straight to an H4, confuses the hierarchy and hurts screen reader navigation. Stuffing keywords into every heading makes them read unnaturally and adds no value. Using headings on non-heading content, like applying an H2 to a caption, misleads assistive technology. And burying the actual page topic in a vague H1 like 'Welcome' wastes the strongest structural signal. The fix for all of these is to think of headings as an outline of meaning: each one should truthfully label the content beneath it and nest in logical order.
How should I structure headings on a page? #
Start with a single, descriptive H1 that states the page's main topic, ideally including the primary keyword naturally; this often aligns closely with the page's title tag, though the two are separate, as covered in /wiki/what-is-a-title-tag. Then break the page into major sections with H2s, each one a clear label or question that a reader would scan for. Under any H2 that needs more detail, use H3s for subsections, keeping the nesting orderly. Only reach for H4 through H6 on genuinely deep content. Write headings for humans first: clear, specific, and scannable, so a reader can grasp the page's shape by reading only the headings. Where it fits naturally, phrase headings as the questions people ask, because that matches how people search and how AI systems extract answers. A well-structured page reads like a good table of contents, guiding the eye from the big picture down to the details without any level feeling out of place.
How do headings affect readability and engagement? #
Most people do not read web pages word for word; they scan. Headings are the anchors that make scanning work, letting a visitor jump to the part they care about and quickly judge whether a page will answer their question. A wall of text with no headings feels daunting and drives people away, while a page broken into clearly labeled sections invites them in and keeps them moving. This directly affects engagement metrics: pages that are easy to scan hold attention longer and convert better. Headings also set expectations, so a reader who sees a relevant subheading trusts that the answer is close. For local businesses, whose visitors are often in a hurry to find a service, phone number, or price, scannable structure is not a nicety but a practical driver of conversions. Good headings pair naturally with other readability practices, such as short paragraphs and plain language, discussed in /wiki/what-is-a-readability-score, to make content approachable for real visitors.
How do I check and fix heading structure? #
Auditing heading structure is straightforward. You can inspect a page's headings using browser developer tools or a heading-outline browser extension that lists every heading and its level, revealing skipped levels, missing H1s, or multiple H1s at a glance. Accessibility tools, including our /tools/ada-compliance-checker, flag heading problems as part of a broader review. Look for a single clear H1, logical nesting without skipped levels, headings that describe their content rather than just style text, and no important content masquerading as a heading or vice versa. Fixing issues usually means changing a heading's level to restore order, converting styled text into real heading tags, or rewriting vague headings to be specific. On sites built in a content management system, editors sometimes introduce heading errors over time, so periodic checks help, and cleaning up headings is a common step in a /services/website-redesign. The payoff is a page that is more accessible, more scannable, and easier for search engines and AI to understand.
<h1>Emergency Plumbing Services in Austin, TX</h1>
<h2>Services We Offer</h2>
<h3>Burst Pipe Repair</h3>
<h3>Water Heater Replacement</h3>
<h2>Our Service Area</h2>
<h2>Frequently Asked Questions</h2>
<h3>Do you offer same-day service?</h3>
<h3>What are your rates?</h3>FAQ
Can a page have more than one H1?
HTML5 technically allows multiple H1s in certain sectioning contexts, but one clear H1 per page remains the safest and most widely supported practice for SEO and accessibility. A single H1 states the page's main topic unambiguously. Using several H1s risks diluting that signal and confusing screen readers and search engines, so most professionals stick with one.
Do headings affect SEO rankings?
Headings are not a direct ranking lever, but they help search engines understand a page's topic and structure, which supports ranking for relevant subtopics. Naturally including target phrases in headings, phrased the way people search, aids comprehension. Clean heading structure also improves readability and engagement, which indirectly benefits performance, and it helps AI systems extract answers.
Why can't I just use bold text instead of headings?
Bold text looks like a heading but carries no structural meaning. Screen readers cannot navigate to it, and search engines do not treat it as a section label. Using real heading tags provides the outline that assistive technology and search engines rely on. Reserve bold for emphasis within text and use heading tags for actual section titles.
Is it bad to skip heading levels?
Yes. Jumping from an H2 to an H4 without an H3 breaks the logical nesting and confuses screen reader users who navigate by level. Headings should descend in order, with each level nested under the one above it. If a heading looks too large or small, adjust its styling with CSS rather than choosing a different level for appearance.
How many heading levels should I use?
Use as many as the content genuinely needs, but most pages only require H1 through H3. The H1 is the title, H2s are major sections, and H3s are subsections. Reach for H4 through H6 only on deeply detailed content. Over-nesting rarely helps and often signals that a page could be split or simplified for clarity.
Should headings match my title tag?
They can be similar but do not have to match exactly. The title tag is metadata shown in search results and browser tabs, while the H1 is the visible on-page headline. A common approach uses an SEO-tuned title tag and a slightly more natural H1. Both should clearly convey the page's main topic to their respective audiences.
Was this helpful?