Heading Structure: What H1-H6 Actually Do for SEO

Somewhere along the way, heading tags turned into a checklist item: cram a keyword into every H2, stack five headings above the fold, treat H1 like a ranking lever with a dial you can turn up. Google has addressed this directly, more than once, and the answer isn't what most SEO advice implies. Google's own SEO Starter Guide says headings exist to "help users navigate your pages" — a sentence about readers, not rankings.

That doesn't mean heading structure is optional. It means the reason it matters is different from the reason most people think it matters. Get the structure right and you help two audiences that both depend on it: screen reader users navigating your page by heading alone, and Google's systems trying to figure out what each section of your content is actually about. Get it wrong and you don't get penalized so much as you get skipped — by both.

Quick Navigation

• What Google Actually Says About Headings
• The Correct Heading Pattern
• Why Heading Order Matters for Accessibility
• Headings, Featured Snippets, and People Also Ask
• Common Heading Mistakes
• How to Check Your Own Heading Structure
• Frequently Asked Questions

---

What Google Actually Says About Headings

Google's SEO Starter Guide states there's "no magical, ideal amount of headings a given page should have," and adds a blunt gut check: "if you think it's too much, then it probably is." That single line kills the keyword-stuffing version of heading strategy on its own.

John Mueller, Google's Search Advocate, has repeated the same point for years without much variation. In a widely reported 2020 discussion covered by Search Engine Journal, Mueller called heading strategy "a bit overrated," explaining that "it's not so much that suddenly your page ranks higher because you have those keywords there." Asked directly whether H1, H2, and H3 order matters to Google, he said ordering "isn't really that relevant" from Google's point of view. In 2024, per Search Engine Roundtable's coverage of a Reddit thread, Mueller put it even more plainly: headings "are great for SEO & accessibility, but they're not going to make or break your sites rankings."

What headings do instead, according to Mueller, is help Google "better understand the content on the pages" — framing which block of text belongs to which topic. That's a comprehension aid, not a scoring input. A heading tells Google's systems "here's a section, and here's roughly what it covers," the same way it tells a human reader skimming the page. Keyword placement inside that heading isn't the mechanism. The organization is.

This reframes the entire question. You're not writing headings to satisfy an algorithm's keyword scanner. You're writing them to make a page legible — to software parsing structure and to a person deciding whether to keep reading.

The Correct Heading Pattern

One H1 per page, matching the page's main topic. H2s for each major section under it. H3s nested under whichever H2 they support. No level skipped on the way down.

That's the whole pattern, and it maps directly onto how people actually read a page. The H1 is the headline — one sentence answering "what is this page about." Every H2 below it should complete the sentence "this page covers ___." If an H2 doesn't fit that test, it's either misplaced or the page is covering something it shouldn't.

H3s exist to break one H2's territory into pieces, not to introduce a new topic. A page about heading structure might have an H2 called "Common Heading Mistakes" with H3s for "Visual-Only Headings," "Multiple H1 Tags," and "Skipped Levels" underneath it — each one a subset of the mistake category above it, not a standalone idea competing with it. Skip a level (an H2 followed directly by an H4, with no H3 in between) and you've broken that containment. The H4 now floats without a clear parent, which confuses both a screen reader's outline view and a human skimming for the section they want.

Brass-SEO's Page Audit checks this directly: it pulls a page's live title tag, meta description, and full H1/H2 structure, and flags a missing H1 as an issue on the spot. It's the same check described above, run automatically against your actual page.

Why Heading Order Matters for Accessibility

Heading structure is a navigation tool for screen reader users, and the data on this is specific: in WebAIM's Screen Reader User Survey #10 (fielded December 2023 and January 2024), 71.6% of respondents said navigating through a page's headings is how they find information on a long page — the single most common method, ahead of using the browser's Find feature or reading straight through. Among experienced screen reader users, that number rises to 78%. Separately, 88.8% of respondents rated headings as very or somewhat useful for navigation.

Here's the mechanism behind that number. Screen readers let a user jump directly to a specific heading level: press a key and the reader lands on the next H2, skipping past everything else on the page. That only works if your markup matches your visual layout. If a section that looks like a subsection is actually marked up as an H2 — or a heading is skipped so an H4 has no H3 parent — the person using that shortcut lands somewhere structurally wrong, even though the page looks completely normal on screen.

That's a real, immediate cost, and it happens independent of anything Google does with the same markup. Sighted readers get the same benefit in a softer form: skimming down a page by scanning headings only works if the headings actually represent the hierarchy they show. A heading that's really body text with bold styling breaks that scan for a sighted skimmer the same way it breaks navigation for a screen reader user. It's just less visible when it happens.

Headings, Featured Snippets, and People Also Ask

Google's own documentation on featured snippets says only this about selection: "Google systems determine whether a page would make a good featured snippet for a user's search request, and if so, elevates it." There's no way to manually request or mark a page for snippet placement, and Google doesn't publish the underlying mechanics.

What's widely observed, without being confirmed as an algorithmic rule, is that a heading phrased as a question followed immediately by a concise, direct answer tends to get pulled more often than a scattered answer buried three paragraphs into a longer section. That's not a trick. It's the same clarity that helps a human reader and a screen reader outline — Google's system just has an easier time lifting a self-contained answer when the page itself has already drawn a clean box around it with a heading.

The FAQ section at the bottom of this post follows that exact shape on purpose: a question as the heading, a direct answer as the first sentence beneath it. That structure exists because it's genuinely the clearest way to write a Q&A section, not because it's a snippet-hacking tactic. The two happen to align.

Common Heading Mistakes

The most common heading mistake has nothing to do with hierarchy. It's using a heading tag purely to make text look bigger. Somebody bolds and enlarges a line of body copy in their CMS, and the editor wraps it in an <h3> because that's what the "bigger text" button does. Now a screen reader announces "heading level 3" for a sentence that isn't structurally a heading, and the page's outline includes a phantom section that doesn't organize anything.

Multiple H1 tags are next, and here the nuance matters: Google's Mueller has confirmed rankings aren't penalized for multiple H1s on a page. That's a real statement about ranking impact, not an endorsement of the practice. A page's H1 exists to answer one question — what is this page about — and a page with three H1s answers that question three times, which defeats the point of having a main heading at all. A person scanning the page's outline (or a screen reader user jumping straight to the H1) should land on one clear statement of the page's topic, not a coin flip between several.

Skipped levels round out the list: an H2 followed directly by an H4 with no H3 between them. Visually this often looks fine, because font-size differences hide the gap. Structurally it's a broken outline — the H4 has no parent to nest under, and both search engines parsing the DOM and screen readers building a heading tree have to guess what the skipped level would have connected.

How to Check Your Own Heading Structure

Right-click any page, choose "View Page Source," and search for <h1, <h2, <h3, and so on. You'll see every heading tag on the page in document order, which is the fastest way to spot a missing H1, a duplicate one, or a level that jumps from two to four with nothing in between. Most browsers also support accessibility inspection panels (built into Chrome, Firefox, and Safari's developer tools) that render the heading outline as an actual nested tree, closer to how a screen reader interprets it.

If you'd rather not dig through source code, Brass-SEO's Page Audit runs this check for you against a live URL, alongside the title tag, meta description, and the GSC and GA4 data tied to that page.

Heading structure inside a single page is only half the picture. The same organizing logic scales up to how an entire site is built: a pillar page orienting readers to a broad topic, with cluster posts going deep on each piece underneath it, mirrors the H1-to-H2-to-H3 relationship at the site level instead of the page level. Content Architecture covers how that structure fits together across a whole site, and Topic Clusters: How to Structure Content So Google Gets It walks through building one from scratch. A single page with clean heading structure is doing its job. A page that also sits correctly inside a larger cluster is doing two jobs at once.

---

Frequently Asked Questions

Do I need exactly one H1 tag on every page?

That's the correct pattern, and Google's own guidance treats each page as needing "a unique h1 heading." John Mueller has also confirmed that Google's ranking systems don't penalize multiple H1 tags, so a second H1 won't hurt your search rankings directly. It still weakens the page for a human or screen reader user trying to answer "what is this page about" at a glance, since a clear single H1 is what makes that question answerable in one look.

Does adding my target keyword to every H2 help me rank higher?

No, not by itself. John Mueller has said directly that keyword placement in headings doesn't make a page "suddenly rank higher" — Google uses headings to understand what a section is about, not as a keyword-density signal to score. Write headings that describe the section accurately; if your target keyword fits naturally, use it, but stuffing it into every heading adds no ranking benefit and often makes the headings worse for the reader.

Can skipping a heading level, like going from H2 straight to H4, hurt my SEO?

Google hasn't stated that skipped heading levels carry a direct ranking penalty. The more immediate cost is structural and accessibility-related: a skipped level breaks the page's outline for screen reader users navigating by heading level, and it removes the clear parent-child relationship that helps any reader (or crawler) understand how a section nests inside the one above it.

Do headings affect whether my content gets a featured snippet or shows in People Also Ask?

Google's featured snippet documentation says its systems determine snippet eligibility automatically, without confirming which structural signals drive that decision. What's commonly observed is that a heading phrased as a question, followed immediately by a short, direct answer, tends to get pulled more often than an answer buried mid-paragraph. That's the same clarity that helps any reader scanning the page, which is likely why the pattern shows up in snippets even without Google confirming it as a formal rule.

How do I check whether my site's heading structure is correct?

View a page's source code and search for <h1> through <h6> tags to see them in document order, or use your browser's built-in accessibility inspector to view the heading outline as a tree. Brass-SEO's Page Audit runs the same check automatically against a live URL, flagging a missing H1 and showing you the full H1/H2 structure alongside your title tag and meta description.