Heading Tags (H1 to H6): How to Structure Content

Heading tags — H1 through H6 — are the skeleton of a page: the outline search engines parse, screen readers navigate, snippet systems quote from, and every human scanner actually reads. Most heading advice fossilised around 2010 myths ("exactly one H1 or else", "stuff keywords in H2s"), so this guide does both jobs: the real rules that matter, and the burial of the folklore that doesn't.

What headings do in 2020s SEO

Three real functions. Structure signal: the H-hierarchy tells crawlers how ideas nest — which sections answer which subtopics, feeding passage-level ranking and snippet extraction directly. Relevance confirmation: heading text is weighted above body text (below the title) when matching queries — headings that name subtopics in searchers' language earn long-tail rankings body text alone misses. Scannability: readers decide in seconds whether a page answers them, and they decide by scanning headings — engagement that quality systems observe downstream.

The rules worth following

One H1 that states the page's topic

The H1 is the on-page headline — normally your post title, containing the main keyword, agreeing with the title tag's promise. One per page remains the clean convention: not because two breaks anything technically (HTML5 permits it; Google copes), but because one topic per page is the whole on-page contract, and a second H1 usually means a second topic that deserves its own page.

H2s that could stand as a table of contents

The working test for your H2 row: read them alone, in order — do they outline the complete argument? Every article in this series is built that way, and that's also precisely what generates the "In this article" jump-link boxes and gives snippet systems their extraction map. Name subtopics plainly ("What a fair price looks like") rather than cleverly ("Show me the money") — headings are navigation first, prose second.

H3s nest under H2s, and hierarchy doesn't skip

H3s subdivide the H2 above them; jumping H2→H4 for styling reasons scrambles the outline you're trying to transmit. If you want smaller text, use CSS — tags encode structure, not font size. (The reverse sin is equal: styling a bold paragraph to look like a heading gives scanners the visual without giving parsers the signal.)

Keywords where they're honest

The main keyword belongs in the H1 and naturally in one or two H2s — where the section genuinely covers it. Question-form headings ("How many backlinks do you need?") double as query matches and snippet triggers. What doesn't work: the same phrase drummed through six headings, which reads as the stuffing it is and repels the humans the headings were for. The placement guide covers the full map.

Structuring a page in practice

The reliable pattern, visible on this very page: H1 (topic) → intro paragraphs → H2 per major section, in the order a smart reader would ask the questions → H3s for the items inside a section (rules, steps, patterns) → an FAQ block of H3 questions at the end for the long tail. Draft the heading outline before writing — if the outline doesn't convince, no prose will save it, and if it does, the article writes itself between the lines.

The folklore, buried

• "Multiple H1s tank rankings": Google has said plainly it handles multiple H1s fine. Keep one anyway — for editorial discipline, not fear.
• "H2 keyword density matters": no such metric; see the density autopsy.
• "Headings must be under 70 characters": invented. Clarity has a natural length; respect that instead.
• "H tags are a top-3 ranking factor": they're a meaningful relevance and structure signal, well below content quality and links. Weight your effort accordingly.

Frequently asked questions

Should the H1 be identical to the title tag?

Same promise, freely different words — the title sells within pixel limits, the H1 confirms without them. Divergent meaning is what causes rewrites and bounces; see the title guide's alignment rule.

Do H5 and H6 ever matter?

Structurally they're valid; practically, content needing five nesting levels usually needs splitting into a cluster instead. If you're reaching for H5, reconsider the architecture.

How many headings per article?

One per genuine idea — this ~1,300-word page carries about a dozen. A heading every 150–300 words keeps scan-rhythm without fragmenting the argument; let the outline's logic, not a quota, decide. Next element down the skeleton: the URL itself — and as ever, structure spends the authority that links supply, with us on call for the supply side.