# Heading Structure for SEO: How to Build an H1–H3 Outline That Works > Good heading structure means one descriptive H1 for the page topic, H2s for its main sections and H3s for subsections, without skipping levels on the way down. Google says heading order doesn't matter for Search, but headings help readers scan, let screen reader users jump between sections, and are one source Google uses for title links. - Canonical URL: https://backlnk.com/blog/heading-structure-seo - Byline: Jordan Lee - First published: 2026-11-01 - Topics: On-Page SEO - Evidence: observed results from our own data or tests; external research (cited); editorial interpretation; hypothetical, illustrative examples (labelled) — not real results Which heading rules are documented and which are myths, how to nest H1–H3 for readers, screen readers and Google, and a step-by-step way to audit and fix a page outline. Headings attract more conflicting advice than almost any other markup. One camp insists on exactly one H1, no skipped levels and a keyword in every H2; another says Google ignores headings entirely. Both are partly right, and the confusion produces headings chosen for their font size or stuffed with phrases instead of describing their sections. A better question is “who reads headings, and what do they need?” Three audiences do: people scanning a page, people using screen readers and other assistive technology, and search engines working out what a page is about. Their needs overlap far more than the debates suggest. This guide separates what is documented from what is folklore. By the end you will be able to build an H1–H3 outline that works for all three audiences, decide when more than one H1 is acceptable, find and fix skipped levels, write headings that make sense on their own, and judge readability scores for what they are. **Key takeaways** - Use one visible H1 that names the page topic, H2s for the main sections and H3s for subsections. Going back up a level when a section ends is normal. - Google says heading order doesn’t matter for Search and that there is no ideal number of headings. Correct nesting matters to screen reader users, who navigate by heading. - Google lists heading elements among its sources for title links, and one clear main heading helps it pick the right one. - Choose a heading level by its place in the outline, never by its font size. - WCAG 2.2 requires that headings, where you use them, describe their topic or purpose. - Readability formulas measure sentence and word length only. Treat a score as a prompt to reread, not as a target. ## What headings do, and for whom A heading labels the section that follows it. That single job serves three audiences, and each uses it differently. | Audience | How they use headings | What the documentation says | | --- | --- | --- | | People scanning | Skim the headings to decide where to start reading | Google’s [SEO Starter Guide](https://developers.google.com/search/docs/fundamentals/seo-starter-guide) advises breaking long content “into paragraphs and sections” and providing “headings to help users navigate your pages.” | | Screen reader users | Jump from heading to heading, or open a list of all headings | [MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/Heading_Elements) calls heading-to-heading navigation “a common navigation technique.” [W3C](https://www.w3.org/WAI/tutorials/page-structure/headings/) notes that browsers, plug-ins and assistive technologies can use headings to provide in-page navigation. | | Google Search | Understand the topic and generate the result’s title link | Google lists “heading elements, such as

elements” among its [title link sources](https://developers.google.com/search/docs/appearance/title-link), and says keywords that appear “in the headings or body text” may make a page [more relevant](https://www.google.com/search/howsearchworks/how-search-works/ranking-results/). | Google’s guidance on [helpful, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) adds a quality angle. It asks whether “the main heading or page title” provides “a descriptive, helpful summary of the content” and avoids “exaggerating or being shocking in nature,” and its description of a page’s main content includes “the visible title and headings throughout a page that summarize its topic.” > **Common myth:** **“Google ranks pages by their heading order.”** Google’s SEO Starter Guide lists the number and order of headings among the things not to focus on. Semantic order is “fantastic for screen readers,” it says, “but from Google Search perspective, it doesn’t matter if you’re using them out of order,” and there is “no magical, ideal amount of headings.” Fix your heading order for readers, not for rankings. ## The hierarchy: how H1, H2 and H3 nest Heading levels form an outline. W3C’s page structure tutorial puts the rule in one sentence: headings with an equal or higher rank start a new section, and headings with a lower rank start subsections of the section above. For most articles and landing pages, three levels are enough: - H1: the page topic, usually matching the title the reader clicked. - H2: the main sections, the ones a reader would list as “what this page covers.” - H3: subsections inside one H2, such as the options, cases or stages that section breaks down. *article-outline.html* ```

How to Start a Compost Bin

What can go in a compost bin

Green materials

Brown materials

Setting up the bin

Choosing a location

Layering

Common problems and fixes

``` The indentation is only there for you; browsers and screen readers take the level from the element itself. The move from “Layering” back up to an H2 is not a skipped level: W3C says it is fine to jump back up when a subsection closes, for example from an H4 to a new H2. ### Headings in sidebars, footers and navigation W3C advises keeping the rank of headings in fixed regions such as sidebars the same on every page, because consistency matters more there. It shows two valid patterns for the main heading: the H1 as the first heading in the document with everything else one rank lower, or navigation headings first and the H1 labeling the main content. For content pages we recommend the second, because it makes the page’s own title the H1, which also matches Google’s title link advice below. > **Note:** **Imperfect HTML is not fatal.** Google’s [guide to generative AI search](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) says perfectly semantic HTML isn’t required, because “the web in general is not valid HTML, and Google can understand it,” while calling semantic HTML “generally a good idea” because it helps screen readers. Correct headings are first an accessibility fix. ## One H1 or several? This is the most common heading question, and the answer has two parts. **What HTML allows.** According to MDN, the HTML standard permits several `

` elements as long as they are not nested, but this “is not considered a best practice”; MDN recommends a single `

` “that describes the content of the page.” The old pattern of nesting H1s inside nested sectioning elements such as `
` is now non-conforming, and the default styling that made such nested H1s look smaller was removed from the HTML standard in May 2025. **What Google says.** Google gives no number, but its title link documentation explains why one clear main heading helps. When “there’s more than one large, prominent heading, and it isn’t clear which text is the main title of the page,” Google “may use the first heading as the text for the title link.” Its fix is to make the main title stand out, for example by “putting the title text in the first visible `

` element on the page.” The practical rule: give each page one visible H1 that states its topic in the reader’s words, and keep it consistent with the `` element. The two can be worded differently, since the title often adds the site name, but they should name the same subject. Google’s documentation shows that when a `<title>` is obsolete or inaccurate, it may build the title link from the visible title or other prominent headings instead. Each page also needs its own H1. If dozens of URLs share one heading because they carry the same template and nearly the same text, the problem is duplication, which our guide to [duplicate content](https://backlnk.com/blog/duplicate-content-seo) covers. > **Pro tip:** **Check what your theme outputs.** Many themes wrap the site name or logo in an H1 on every page. W3C shows that pattern as valid, but the page title must then still be a real heading, not a styled `<div>`. For articles and landing pages, making the page title the H1 keeps the main heading unique to each page. ## Skipped levels, fake headings and other outline errors A skipped level is a downward jump of more than one rank, such as an H2 followed directly by an H4. W3C calls this confusing and says it “should be avoided where possible.” MDN explains why: someone navigating by heading “may be left wondering where the missing heading is.” Moving back up is different. After an H4, a new H2 simply closes the open subsections, and W3C explicitly says that is fine; a checker that flags every upward jump is misreading the rule. *skipped-level.html* ``` <!-- Skipped level: the H2 is followed directly by an H4 --> <h2>Pricing</h2> <h4>Monthly plans</h4> <!-- Fixed: use the next level down and make it smaller with CSS --> <h2>Pricing</h2> <h3 class="subtle">Monthly plans</h3> ``` ### Why outline errors happen Almost always because someone picked a level for its look. MDN is direct: “Do not use heading elements to resize text,” use the CSS `font-size` property instead. The reverse error is as common: text that looks like a heading but is a bold paragraph. W3C’s [technique H42](https://www.w3.org/WAI/WCAG22/Techniques/html/H42) tests both directions: heading markup is used when content is a heading, at the appropriate level, and not used when it isn’t. Its related techniques include failure F2 of success criterion 1.3.1, conveying information through text presentation alone without the appropriate markup. **Do** - Pick each level from the heading’s place in the outline. - Change size, weight and spacing with CSS. - Use a real heading element for every visible section title. - Keep sidebar and footer headings at the same level on every page. **Avoid** - Choosing an H4 because it “looks right” under an H2. - Bold or oversized paragraphs posing as headings. - Headings used for taglines, decoration or button labels. - Empty heading elements left behind by a page builder. Is a skipped level an SEO problem? Not according to Google, which says heading order doesn’t matter for Search. It is a usability and accessibility problem, and usually a quick template fix. ## How to write descriptive headings WCAG 2.2 success criterion 2.4.6 (Level AA) requires that “headings and labels describe topic or purpose.” Its [Understanding document](https://www.w3.org/WAI/WCAG22/Understanding/headings-and-labels) explains that descriptive headings especially help people whose disabilities make reading slow and people with limited short-term memory, because section titles “make it possible to predict what each section contains.” They don’t need to be long: “A word, or even a single character, may suffice if it provides an appropriate cue.” The criterion doesn’t require headings; it requires that the ones you provide are descriptive. A practical test, which is Backlnk’s editorial rule rather than a standard: read only your headings, in order, the way a screen reader’s heading list presents them. If the list reads like a useful table of contents, the headings work. If it reads “Overview, Details, More information, Conclusion,” it tells the reader nothing. - Name the subject. “Choosing a location” beats “Step two.” - Front-load the distinctive words. Scanners read the start of a heading, so put the word that sets this section apart first. - Ask a question only if the section answers it, directly below the heading. - Keep sibling headings parallel. After “Green materials” comes “Brown materials,” not “What about cardboard?” - Write for the reader, not the keyword. Google’s Starter Guide notes that keyword stuffing is against its spam policies. Use the words your readers use, once. *Illustrative example:* A hypothetical returns page on example.com, with the same outline written two ways. **Descriptive** - H1: Returns and refunds at Example Store - H2: How long you have to return an item - H2: Items that can’t be returned - H2: How to start a return - H2: When your refund arrives **Vague** - H1: Policies - H2: Overview - H2: Exceptions - H2: Process - H2: Best returns policy, free returns, easy refunds ## Section length, scannability and readability scores ### How long should a section be? There is no official number. Google’s Starter Guide says the length of content “alone doesn’t matter for ranking purposes” and that there is “no magical word count target.” What matters is whether readers can find their way, which is why the same guide recommends breaking long content into sections with headings. Backlnk’s Page Structure & Readability Auditor uses three disclosed thresholds as prompts, not rules: a paragraph over 150 words, more than 600 words under one heading without a subheading, and a sentence over 35 words. A long section can be exactly right, such as a legal clause that must stay whole; the flag only asks you to look. ### What readability scores measure Formulas such as Flesch Reading Ease compute a score from two surface features: average sentence length and average syllables per word. They know nothing about accuracy, structure, or whether a term is the right one for the audience. Backlnk’s auditor scores English with Flesch Reading Ease and uses published adaptations for German, Spanish, French and Dutch; other languages get no score rather than an English formula. WCAG is cautious too. [Success criterion 3.1.5](https://www.w3.org/WAI/WCAG22/Understanding/reading-level) (Level AAA) asks for supplemental content when text requires reading ability beyond lower secondary education, seven to nine years of school. Its Understanding document notes that the working group “could not find a way to test” whether the clearest, simplest language had been achieved, and uses reading level to make the criterion testable. The Google pages cited here ask for text that is “easy-to-read and well organized” but name no formula or target score. We ran Backlnk’s auditor on W3C’s own headings tutorial on 31 October 2026. It is a short, carefully structured page, and its outline passed every structure check. Its readability score still came out as “fairly difficult”: - **9** — headings: one H1, no skipped levels, and H3 → H2 returns correctly not flagged - **12.1** — words per sentence on average, with no sentence over 35 words - **55** — Flesch Reading Ease (“fairly difficult”), driven by 1.65 estimated syllables per word The sentences are short. The score is pulled down by necessary vocabulary such as “assistive technologies” and “navigation,” the very words the page exists to explain. > **Watch out:** **Don’t rewrite for the formula.** Swapping precise terms for shorter, vaguer ones raises a readability score while making the page less useful. Use a low score as a reason to look for long sentences and unexplained jargon, and judge each change by whether your reader understands more. ## How to check your headings with the Page Structure & Readability Auditor The [Page Structure & Readability Auditor](https://backlnk.com/tools/page-structure-auditor) checks one page and gives the exact location of every finding: 1. **Run the audit.** Enter the page URL. If your headings are inserted by JavaScript, use the rendered mode so the tool sees what a browser sees. 2. **Read the outline.** Every heading is listed in order with its level. Skipped levels are marked; returns to a higher level after a section closes are not flagged. 3. **Check the H1 finding.** A missing H1 is reported as an issue. More than one H1 is a low-severity warning, because several H1s can be legitimate when they mark genuinely separate page regions. 4. **Look for empty headings and long blocks.** Empty headings, sections over 600 words without a subheading and paragraphs over 150 words are listed with their location. 5. **Review readability last.** For English, German, Spanish, French and Dutch you get a score, the average sentence length and every sentence over 35 words. 6. **Fix and re-run.** Correct levels in the template or editor, move visual differences into CSS, and run the audit again. The report also covers the main landmark, page language, title, image alt attributes, link names and table header cells. These observations reference WCAG 2.2 but are not a conformance audit, and a page without `<article>` or `<section>` elements is not marked down for it. To run this check alongside Backlnk’s other tests, use the free [full audit](https://backlnk.com/tools/full-audit), delivered by email. - One visible H1 that states the page topic and agrees with the title element. - H2s for the main sections, H3s only inside an H2. - No downward jump of more than one level. - Every visible section title is a real heading, and no heading exists only for styling. - The headings alone read like a useful table of contents. - No empty headings and no repeated keyword strings. - Sidebar and footer headings use the same levels on every page. ## Next step Pick one important page, run it through the Page Structure & Readability Auditor, and read only its headings from top to bottom. Fix the levels first, then the wording. Once every page has a clear outline, the next question is whether the page as a whole serves one clear purpose, which is where search intent comes in. ## Frequently asked questions ### Is it bad to have more than one H1 on a page? It is not invalid, but it is rarely helpful. HTML allows several H1 elements as long as they are not nested, while MDN recommends a single H1 that describes the page. Google gives no ideal number of headings, but says that when several headings look equally prominent it may use the first one for the title link. One visible H1 per page avoids that ambiguity. ### Do skipped heading levels hurt SEO? Google says heading order doesn't matter for Google Search. Skipped levels matter for accessibility: W3C advises against jumping down more than one level, such as from H2 to H4, because it confuses people who navigate by heading. Returning to a higher level when a section ends is fine. ### Should the H1 be the same as the title tag? They don't have to be identical, but they should name the same topic, and the title often adds the site name. Google uses both the title element and heading elements as sources for title links and may rely on the visible main heading when the title element is inaccurate or outdated. ### How long can a section be before it needs a subheading? There is no official limit, and Google says content length alone doesn't matter for ranking. Backlnk's Page Structure and Readability Auditor flags more than 600 words under one heading without a subheading as a disclosed heuristic: a prompt to check whether readers can still find their way. ### Do readability scores affect Google rankings? The Google documentation cited in this guide asks for text that is easy to read and well organized but doesn't name any readability formula or target score. Formulas such as Flesch Reading Ease measure only sentence length and word length, so use them as editing prompts rather than goals. ## Sources - [Headings (Page Structure Tutorial)](https://www.w3.org/WAI/tutorials/page-structure/headings/), W3C Web Accessibility Initiative (accessed 2026-10-31) - [Understanding SC 2.4.6 Headings and Labels (Level AA)](https://www.w3.org/WAI/WCAG22/Understanding/headings-and-labels), W3C Web Accessibility Initiative (accessed 2026-10-31) - [Technique H42: Using h1-h6 to identify headings](https://www.w3.org/WAI/WCAG22/Techniques/html/H42), W3C Web Accessibility Initiative (accessed 2026-10-31) - [Understanding SC 3.1.5 Reading Level (Level AAA)](https://www.w3.org/WAI/WCAG22/Understanding/reading-level), W3C Web Accessibility Initiative (accessed 2026-10-31) - [The h1 to h6 HTML section heading elements](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/Heading_Elements), MDN Web Docs (accessed 2026-10-31) - [Search Engine Optimization (SEO) Starter Guide](https://developers.google.com/search/docs/fundamentals/seo-starter-guide), Google Search Central (accessed 2026-10-31) - [Influencing your title links in search results](https://developers.google.com/search/docs/appearance/title-link), Google Search Central (accessed 2026-10-31) - [Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content), Google Search Central (accessed 2026-10-31) - [Automatically generating and ranking results](https://www.google.com/search/howsearchworks/how-search-works/ranking-results/), Google (accessed 2026-10-31) - [Optimizing your website for generative AI features on Google Search](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide), Google Search Central (accessed 2026-10-31)