Heading Structure and H1 Tags

Heading hierarchy (H1 through H6) matters for both search engines and the people reading your content. It helps crawlers understand page structure, improves accessibility for screen readers, and guides readers through your ideas logically.

What Headings Do

Headings are semantic HTML elements that structure content. They're not just visual styling. When you use an H2 tag, you're telling the browser and search engines "this is a major section of content." When you use H3, you're saying "this is a subsection of the H2 above it." This hierarchy helps crawlers understand your content's organizational logic.

Headings also serve accessibility. Screen reader users navigate pages by jumping between headings. If your heading structure is broken — say, you jump from H1 to H4 without intermediate levels — screen readers lose context. Users with cognitive disabilities rely on clear heading hierarchies to understand page organization.

The H1 Rule

Every page should have exactly one H1, and it should contain your primary keyword (or a close variant). Your H1 should answer the question: "What is this page about?" It typically matches your title tag closely or is a slightly expanded version of it.

Why one H1? Because a page has one primary topic. Multiple H1s confuse crawlers about which topic is primary. You can have multiple H2s, H3s, and lower-level headings, but keep H1 singular and focused.

Your H1 should closely match or mirror your title tag. If your title is "How to Make Sourdough Bread," your H1 might be "How to Make Sourdough Bread: A Beginner's Guide" or simply "How to Make Sourdough Bread." Don't change the primary topic between title and H1.

H2s as Section Signposts

H2 tags mark major content sections. Each H2 should be descriptive and ideally contain a secondary keyword or topic variant related to your primary keyword. For a page about sourdough bread, H2s might be "Ingredients You'll Need," "Step-by-Step Instructions," "Troubleshooting Common Problems," and "FAQs."

These H2 headings help readers scan your page and decide if the section interests them. They also help Google understand the range of subtopics you cover. A page with H2s about ingredients, instructions, troubleshooting, and storage signals comprehensive coverage of the topic.

You don't need to force keywords into H2s. "Common Keyword Here Problems" reads worse than "Troubleshooting Common Problems," and Google understands both. Write readable, descriptive H2s first. If keywords fit naturally, include them. If they don't, skip them.

H3s for Subsections

H3 tags sit under H2s. They're useful for breaking large sections into smaller, more digestible parts. Under "Step-by-Step Instructions," you might have H3s for "Day 1: Mixing," "Day 2: Bulk Fermentation," and "Day 3: Shaping and Baking." This hierarchical organization helps both readers and crawlers understand content structure.

Not every page needs H3s. Use them when a section is long (over 500 words) or covers multiple distinct concepts. Short, focused sections don't need subsection breaks.

The Hierarchy and Featured Snippets

Google often sources featured snippets from clearly structured content. If you want a paragraph to be extracted as a featured snippet, place it under a descriptive H2 or H3 that matches a common question. For example, if your H2 is "How Long Does Sourdough Take?" and the paragraph below answers that question directly, you're positioned well for a featured snippet.

Google uses heading structure to understand which content sections answer which questions. Clear hierarchy makes this pattern obvious.

Common Heading Mistakes

Using Multiple H1s

Some SEOs still push the "multiple H1s are okay" line. They're not wrong technically — HTML5 allows multiple H1s. But it confuses the semantic intent. Google treats additional H1s as weaker signals than the first one. If you need multiple headings, use H2s instead. Your code validates either way, but semantically, one H1 is clearer.

Skipping Levels

Jumping from H1 to H4 without intermediate H2 or H3 tags breaks hierarchy. If your page structure requires it, use CSS to style an H2 smaller instead of skipping to H4. Screen readers depend on logical hierarchy.

Using Headings for Visual Styling

This is the most common mistake. Someone needs a large, bold subtitle so they use an H3 tag and then styles an actual subsection as a paragraph. Use CSS to style divs or paragraphs visually, and reserve heading tags for semantic structure. If you need visual hierarchy without semantic meaning, use span or div with CSS classes.

No Headings at All

Some long-form content has paragraphs but no internal headings. This hurts scanability and accessibility. Break long content into sections with clear headings. Most readers scan before reading, and clear headings help them find relevant sections quickly.

Heading Structure Audit

Export your top 20 pages and check their heading structure. Does each page have exactly one H1? Are H2s descriptive and relevant? Are hierarchy levels correct (no jumping from H2 to H4)? Are headings using semantic tags or are they styled divs pretending to be headings?

Tools like SEMrush, Ahrefs, and Screaming Frog can crawl your site and flag heading issues. Use these to identify pages with broken hierarchies, then prioritize fixing high-traffic pages first.