What structure does for a page
For readers. Most people do not read a page top to bottom; they scan the headings, decide whether the page has what they want, and jump to it. A page with vague headings ("Introduction", "More information") fails that scan and loses the visitor the title earned.
For search engines. Google's starter guide describes headings as a way to convey the hierarchy and the subject of a page's parts, and its documentation on snippets and featured results shows that it extracts passages that answer a query — which is easier when the passage sits under a heading that names the question. Heading text is also one of the sources Google documents for title links when the title elementThe HTML title element that names a page and usually supplies its title link in search results. is poor.
For accessibility. Screen readersSoftware that announces a page's text, headings, labels and messages to people who cannot see the screen, and reports what the page provides. navigate by heading level. A correct hierarchy is a navigation aid; a decorative one (H3s used for small text, H1s for emphasis) is a maze.
What structure does not do is rank a page by itself. A clear outline over thin contentPages that offer little original value of their own, such as near-empty templates, near-duplicates or copies with only a word or place changed. is a clear outline over thin content. Structure makes good content usable and visible; the content section covers making it good.
The hierarchy
| Level | Role | How many | Rule |
|---|---|---|---|
| H1 | The page's headline: what it is about | One | Matches the title's meaning; states the topic plainly |
| H2 | Sections: the questions the page answers | As many as there are distinct sections, typically four to ten on a guide | Each reads as a complete statement of what the section covers |
| H3 | Parts within a section | As needed | Only under an H2; never used to skip a level |
| H4 and below | Rare on content pages | Avoid | A need for H4s usually means the page should be split |
Levels are nested, not skipped: an H3 follows an H2, not an H1 directly. Styling is separate from level; a heading is chosen for what it is in the outline, and CSS makes it look right. This site's content validator rejects skipped levels and multiple H1s for exactly these reasons.
Writing headings
A heading is a promise about what follows. The rules:
- Make each one specific. "How crawl budget is allocated" over "Crawl budget"; "Why platform and analytics numbers disagree" over "Discrepancies".
- Use the reader's words. The phrases people search and the questions they ask (from the results page and people-also-ask) are the natural headings for the sections that answer them. This is where the search intent work becomes the outline.
- Keep them parallel. Sections of the same kind get headings of the same shape — all questions, all noun phrases, all imperatives — so the outline reads cleanly.
- Front-load. The distinctive words first; readers scanning a list of headings read the first few words of each.
- No decoration, no repetition. A heading that repeats the H1 with a keyword variation is filler; one that exists for styling is a structural lie.
- Short enough to scan. A heading that needs a second line is usually a sentence that belongs in the section.
Building an outline from the results page
The most reliable way to structure a page is to let the query's intentThe goal behind a search query: to learn, to find a site, to compare or to act. dictate it:
- Collect the sub-questions. From the results page: the headings of the top-ranking pages, the people-also-ask questions, the related searches, the sub-topics a featured snippetA highlighted extract from one page shown as a direct answer in search results. covers.
- Group and order them. By the reader's logic — what they need to know first, what depends on what — not by how the competing pages happen to be ordered.
- Add what is missing. The questions the competitors do not answer, from your own knowledge of the topic and from customer questions; this is where the page becomes better than what ranks rather than a copy of it.
- Decide each section's format. A comparison is a table; a process is numbered steps; options are a list; a concept is prose with an example. Format follows what the section does.
- Write the H2s as the finished headings before writing the sections, and read them as a list: do they summarise the page?
The content brief tutorial packages this outline as the brief handed to a writer.
Inside the sections
Lead with the answer. The first sentences under a heading give what the heading promised; the detail follows. This serves scanning readers, serves extraction into snippets, and keeps sections honest.
Paragraphs. One idea each, a few sentences, with the point in the first sentence. Walls of text are abandoned on phones.
Lists. For items that are genuinely parallel and separable. A list of sentences that argue a sequence is prose pretending to be a list; a list of options with a sentence each is right.
Tables. For comparing things across the same attributes. A table with one column of prose is a list. Tables need a header row and short cells, and they must work at phone width — this site scrolls wide tables horizontally inside a container rather than breaking the layout.
Numbered steps. For procedures where order matters, with each step a complete instruction.
Examples. Labelled, concrete, and placed where the concept they illustrate is explained. On this site illustrative examples carry a visible label so they are never mistaken for results.
Emphasis. Bold for the few phrases a scanner should catch, never for whole sentences.
Summaries. A short "in short" block at the top answers the query for people who will not read further, and it is also the passage most likely to be extracted. A closing "what to do next" turns readers into the next page's readers.
An outline before and after
Before: a page on choosing a mattress with headings "Introduction", "Types", "Things to consider", "Our recommendations", "Conclusion". After reading the results page: "How to choose a mattress in five decisions", then H2s for each decision in the reader's words — "Firmness: what your sleeping position needs", "Materials: foam, spring, hybrid and latex compared" (a table), "Size and room fit", "Trial periods and returns: what to check", "Budget: where the price differences actually come from" — then "Questions people ask" with the people-also-ask items as H3s, and a short closing section pointing to the retailer's range. The content is largely the same; the outline now tells both reader and engine what each part answers.
Structure and other on-page elements
The H1 and the title element say the same thing at different lengths. Headings are the natural anchors for in-page tables of contents (which this site generates server-side from the H2s and H3s) and for jump links from other pages. Section headings and the questions under them are the visible content that FAQ or other structured data must match. And images within sections carry their own structure through alt text and captions — the image SEO guide covers it.
Structure by page type
The outline a query wants depends on what kind of page serves it:
| Page type | Typical structure |
|---|---|
| Guide or explainer | Short answer; what it is; how it works; how to do it; edge cases; mistakes; next step |
| Tutorial | Prerequisites; numbered steps with a heading each; verification; troubleshooting |
| Comparison | The short verdict; the criteria; a side-by-side table; each option in depth; who each suits |
| Category page | Range introduction; refinements; the grid; buying guidance; related guides |
| Product page | Name and key facts; images; price and availability; description; specifications; reviews; questions |
| Location page | Name and area; contact and hours; services; team; directions; reviews |
| Hub | What the subject is; its parts with a section per supporting page; definitions; next step |
Each is a template decision, made once and applied consistently, so that writers fill structure rather than invent it and readers find the same things in the same places across the site.
Accessibility and headings
Heading structure is one of the most consulted accessibility properties of a page. Screen-reader users list headings to navigate; skipped levels, empty headings and decorative headings break that navigation. The same hierarchy that helps search engines helps them, which is a reason to get it right that has nothing to do with rankings. The SEO page checker reports the heading outline of any live URL so the hierarchy can be checked without reading the source.
Heading structure is easiest to judge as part of a wider review, and the on-page SEO audit sets out the checks for intent, titles, headings, images and internal links together.
A main heading that disagrees with the title is one reason Google replaces the title in results; the page on why Google rewrites title tags covers that and the other causes.
Common mistakes
- Headings as styling. Levels chosen for font size rather than structure.
- Generic headings. "Overview", "Details", "More" — no information for scanners or engines.
- Skipped levels and multiple H1s. Confusing outlines, broken navigation.
- Keyword-stuffed headings. The same phrase in every H2.
- Preamble before the answer. The section's point buried under context.
- The wrong format for the job. Prose where a table was needed; a list where an argument was.
- Copying competitors' outlines. The outline that ranks is the floor, not the ceiling.
The search intent guide is where the outline's questions come from; the author's on-page SEO expertise page describes structure as part of the working checklist.
