Heading Structure

What Heading Structure Means, in Plain Language

Heading structure is the outline of a page, expressed in the heading elements of its HTML: one main heading, usually called H1, for the page's topic, then section headings, called H2, for its major parts, then subheadings, called H3, for the parts within those parts, and so on down to H6 for the finest divisions. Read in order, the headings alone should tell a reader what the page is about, what its main sections cover, and how those sections relate to each other, much as the contents page of a book tells a reader what the book contains before they read a single paragraph. A page with good heading structure can be understood at a glance; a page without it must be read from start to finish before its shape becomes clear, and most readers will not stay that long.

The structure serves two audiences at once, and both benefit from the same habits. For human readers, headings break a long page into scannable sections, letting a reader find the part they need, skip the part they do not, and return to a part they want to re-read, without scrolling through everything in between. For search engines and assistive technology, headings provide the same map in machine-readable form: they say which text is a section title and which is body text, and they show how sections nest inside each other. A screen reader, for example, can list a page's headings and let its user jump directly to the section they want, but only if the headings are real heading elements in a logical order, not merely large, bold text that looks like a heading to a sighted reader.

The distinction between real headings and styled text is the first thing to understand. In HTML, a heading is marked with an element, such as h2, which carries meaning that software can use. Large bold text marked as an ordinary paragraph carries no such meaning: it looks like a heading to a person, but to a search engine and to a screen reader it is just another paragraph. Google's Search Central SEO Starter Guide advises site owners to use headings to convey structure and meaning, and to use styling, through CSS, when they merely want larger text. That advice captures the rule in one line: headings are for structure, styling is for appearance, and confusing the two helps nobody.

What Heading Structure Is Not

Heading structure is not a place to stuff keywords, and it is not a ranking lever to be pulled harder for a better result. A heading that repeats the page's target phrase in every section, whether or not the section is about that phrase, reads as manipulation to a human and is recognised as such by search engines, which have long treated keyword stuffing in headings the same way they treat it in body text. A good heading says what its section contains, in the words a reader would use to describe it, and it earns its place by helping the reader navigate, not by repeating a phrase. The heading that helps the reader most is usually the heading that serves search best, because both are judging the same thing: whether the section delivers what its title promises.

How Heading Structure Works

A heading structure works as a tree. At the top sits the H1, the page's single main topic, which should match, in substance if not in exact words, the page's title and its promise to the reader. Beneath it sit the H2 elements, the major sections, each covering one substantial part of the topic. Beneath any H2 that needs it sit H3 elements, the subsections, each covering one part of that section. Deeper levels, H4 to H6, appear only in long, complex pages where a subsection itself has distinct parts. The rule that keeps the tree sound is nesting: a heading should sit under the heading above it in level, not jump from H1 straight to H3, and not promote a subsection to the level of a section merely because its author feels it is important. Importance is shown by the content, not by inflating the level.

That tree is read in two ways. A sighted reader reads it visually, scanning the headings down the page and judging, from their wording and size, where to stop and read. A screen reader user reads it as a list, jumping from heading to heading, and judging, from the wording alone, without the visual size cues, whether each section is the one they want. That second reading is why heading wording matters as much as heading level: a heading that says "More" or "Part 2" tells a visual reader nothing, and tells a list reader even less, while a heading that says "Common mistakes that break heading hierarchy" tells both readers exactly what follows. The Web Content Accessibility Guidelines capture this in success criterion 2.4.6, which requires that headings and labels describe their topic or purpose, because descriptive headings are what make navigation possible for readers who cannot scan visually.

Chart: A Sound Heading Tree, Top to Bottom

Source note: the nesting pattern follows Google's Search Central advice to use headings to convey structure, and the W3C accessibility guidance that headings should describe their topic or purpose. No ideal count is given, because Google's guidance gives none.

Why Heading Structure Matters

Heading structure matters first because readers scan before they read. A reader who arrives from search has a question, not a commitment to read everything, and their first act on a new page is usually to scan its headings to judge whether the page contains their answer and where it sits. A page whose headings announce its sections clearly will keep that reader; a page whose headings are vague, missing, or buried will lose them to the next result, however good its body text. The headings are, in effect, the page's second chance to earn the click that brought the reader there, and they are judged in seconds.

It matters also because it makes long pages usable. A short page can survive without much structure, because a reader can hold its whole shape in mind. A long guide cannot: without headings, a long page is a wall of text, and a wall of text is a page that will be skimmed badly or abandoned. Headings turn length from a liability into an asset, by letting a reader treat a long page as a set of short, findable sections, each with its own promise. That is why the longest, most useful guides are usually the most carefully headed: their length is only bearable because their structure is clear.

Common Heading Structure Mistakes

The first mistake is using styled text instead of real headings. A paragraph made large and bold may look like a heading, but it carries no heading meaning, so a screen reader will not list it, a search engine will not treat it as a section title, and a reader who navigates by headings will never find it. The fix is simple and non-negotiable: if text functions as a heading, mark it as a heading element, and use CSS only for its appearance. The reverse mistake, using a heading element merely to make text large, is equally harmful, because it pollutes the outline with entries that are not sections at all.

The third mistake is skipping levels or nesting illogically. A page that jumps from H1 to H3, or that places a subsection under the wrong section, breaks the tree, and a broken tree confuses the readers who navigate by it. Google's guidance notes that, from search's perspective, out-of-order headings do not carry a penalty, but that is a statement about ranking, not about usability: a screen reader user navigating a broken outline still suffers, and a human reader scanning a disordered page still struggles. The fix is to draft the outline before writing, and to check, after writing, that each heading sits under the heading it logically belongs to.

How to Apply Heading Structure Step by Step

Start with the outline, before the prose. Write the H1 as a single sentence stating the page's topic, then list the major sections as H2 elements, in the order a reader would need them, then list the subsections under each H2 as H3 elements, only where a section genuinely has distinct parts. Check the outline on its own: does it read as a sensible contents page, does each heading promise something distinct, and does the order follow the reader's journey from question to answer? An outline that fails that check will produce an article that fails it too, and fixing the outline now is far cheaper than restructuring a finished draft. The glossary entry on keyword research helps at this stage, because the sections a reader needs usually follow from the questions they actually search for.

Next, write each section to fulfil its heading, and no more. A section that wanders beyond its heading's promise breaks the contract the heading made, and a section that delivers only part of its promise leaves the reader feeling misled. If a section grows too long, split it under H3 subheadings rather than letting it sprawl; if a section stays short, leave it short, and do not invent subsections to fill it. The discipline is to let the heading govern the section, not the other way round: when the writing drifts, either the heading is wrong and should be rewritten, or the writing is off-topic and should move to its proper section.

Then check the levels mechanically, before publishing. List the page's headings in order, with their levels, and look for the faults that eyes miss in a formatted page: a missing H1, a second H1, a skipped level, a subsection under the wrong parent, or a heading used for styling. Many browsers and free tools can produce that list in seconds, and the check takes less time than fixing a published page. Pay special attention to headings added by templates, sidebars, and widgets, which can introduce extra H1 or H2 elements the author never wrote, and which can quietly break an otherwise sound outline. The entry on title tag covers the related question of the page's title, which should agree with the H1 in substance, and the entry on meta description covers the search snippet that introduces the page before a reader ever sees its headings.

After that, test the headings as a screen reader user would: read them alone, in order, without their paragraphs, and ask whether they tell the page's story. A heading list that reads as a coherent outline, with each entry distinct and descriptive, is a page that can be navigated by anyone. A list that reads as a string of vague labels, repeated phrases, or orphaned subsections is a page that needs its headings rewritten, however good its body text. This test is the single most valuable heading check a writer can run, because it simulates the experience of the readers who depend on headings most, and it catches vagueness that visual scanning forgives.

Now check the headings for the reader's questions, not only for the author's topics. A heading phrased as the reader's question, or as the answer the section provides, helps a scanning reader find their answer faster than a heading phrased as an internal topic label. That does not mean every heading must be a question; it means every heading should be judged by whether a reader with a question would recognise their question in it. The Rankenza guide to writing blog posts that rank on Google shows the same reader-first ordering applied to a whole article, and the guide to beginner's SEO blog writing checklist includes a heading check before publishing.

How Rankenza Handles Heading Structure

Rankenza's articles are outlined before they are written, from research into the top ten search results for their keyword, filtered by what the searcher actually wants. That research reveals the sections readers expect and the questions they ask, so the outline follows the reader's needs rather than the writer's habits. The draft is written in original words, reviewed by a human editor who checks that each section delivers what its heading promises, and given internal links from the customer's own sitemap, so that related sections on other pages are reachable from the headings that introduce them. Structure, in this approach, is not an afterthought applied to a finished draft; it is the plan the draft is written to.

Rankenza does not promise that good headings alone will rank a page, because no honest service could: headings help readers and search engines understand a page, but they cannot rescue a page whose content does not answer its reader's question. What it does offer is a low-risk way to test the approach: the first article is free, then $3.60 per article or $89 for 50 credits, with no subscription. A small business can read the draft, check its outline against its own readers' questions, and decide on evidence whether the structure serves them. The SEO Keyword Generator is a free starting point for finding the topics whose section structure is worth planning.

How This Looks on Rankenza

The comparison below is method against method, without inventing traffic or ranking figures for either side.

Typical approach: headings chosen after writing, or not at all; styled text used instead of real heading elements; several H1 elements or none; levels skipped; vague headings such as "Tips" or keyword-stuffed headings repeated in every section.

Rankenza's approach: top-10 search research first; outline filtered by what the searcher wants; original draft reviewed by a human editor; internal links drawn from the customer's own sitemap; first article free, then $3.60 per article or $89 for 50 credits. See it in practice in writing blog posts that rank on Google and try the first step in the SEO Keyword Generator.

Sources: What the Research Says

According to Google's Search Central SEO Starter Guide, site owners should use headings to convey structure and meaning, and should use styling when they merely want larger text, which is the distinction this entry is built on. The W3C's accessibility guidance, in success criterion 2.4.6, requires that headings and labels describe their topic or purpose, because descriptive headings let users, including screen reader users, find information and understand how parts of the content relate. Moz's Beginner's Guide to SEO describes heading structure in the same practical terms, as the organisation that helps both readers and search engines understand a page. Where this guide gives no ideal number of headings, that is deliberate: Google's guidance gives none, and a number invented here would mislead.

Frequently Asked Questions

How many H1 elements should a page have?

One, in practice. The page's main topic deserves a single, clear announcement, and everything else should sit beneath it as sections and subsections. Google's guidance does not present one H1 as a strict rule with a penalty for breaking it, but the practical recommendation, shared by accessibility practice, is one H1 per page, with the brand name kept out of the heading hierarchy and the article title carrying the H1. A page with several H1 elements leaves every audience unsure which topic is principal, and a page with none leaves them without a starting point.

Can I skip from H1 to H3?

It is better not to, even though Google's guidance notes that, from search's perspective, out-of-order headings do not carry a penalty. The penalty that matters is to the reader, especially a screen reader user who navigates by the heading tree: a skipped level breaks the tree and makes the page harder to navigate. The sound habit is to nest in order, H1, then H2, then H3, and to introduce an intermediate heading rather than skipping it when a subsection genuinely needs a parent section.

Should headings contain keywords?

They should contain the words that describe their section, which will often include relevant terms naturally, but they should not be stuffed with a target phrase. A heading's job is to tell the reader what follows, and a heading that repeats the same phrase in every section fails that job while reading as manipulation. Write the heading for the reader first, as a specific promise about its section, and let any relevant terms appear because they belong there, not because a quota demands them.