In one paragraph
No H2 subheadings on page means this check found enough source text to expect sections but no H2 element. Review whether the main content actually needs subdivision and whether existing visual labels use semantic headings. Add descriptive H2s where they improve navigation, not as keyword decoration. A short focused page does not need artificial sections merely to satisfy a heuristic.
Why it matters
Headings let readers scan the document and let assistive-technology users move between meaningful sections. A descriptive label such as Delivery times and costs communicates more than a vague decorative phrase. The benefit comes from useful organisation rather than the literal presence of a particular number of tags.
Use heading levels to express relationships and CSS to control appearance. Main sections under the page topic commonly use H2, with H3 for their subsections. A visually large div is not automatically a heading, while an existing programmatic heading may be meaningful even if this specific HTML-element counter does not recognise it.
Google's starter guidance does not prescribe a ranking reward for a particular heading count or order. Keep semantic structure clear for people rather than claiming that adding H2s alone will raise the page's position.
How WebAuditOS evaluates this finding
The supplied rule counts source body text after removing scripts, styles, noscript, and template content. Below 1,200 characters is not graded. At or above that amount, any H2 passes and no H2 warns informationally. Error and unparseable responses are not graded.
The count can include navigation, footers, consent text, and CSS-hidden content. An H2 in a footer can pass a long unstructured article, while a short page with a large menu can warn. It inspects static markup and does not recognise role-based heading semantics as literal H2 elements. These limits matter when deciding whether the main text needs editing.
How to fix it
- Inspect the main content separately from shared navigation and boilerplate. Determine whether it contains several meaningful topics or one short task. Do not let a mega-menu's text total dictate the structure of a tiny form.
- Identify natural section boundaries in the reader's journey. For a practical guide, those might include the problem, diagnosis, repair, verification, and limitations. Use only sections supported by actual useful content.
- Mark main sections semantically. For example:
<h1>Shipping information</h1>
<h2>Delivery times</h2>
<h2>Costs and available services</h2>
<h3>International destinations</h3>This is an illustrative outline, not content to paste on an unrelated page. Make the subordinate relationship accurate.
- Fix the shared title component if a theme or builder emits styled paragraphs instead of headings. Preserve the intended visual class and choose the appropriate HTML level rather than relying on browser default typography.
- Review existing H3 or H4 labels that skip directly from the main topic. Adjust the hierarchy when it expresses the document better, but do not change levels blindly across unrelated sidebar and navigation components.
- Avoid turning every price, badge, or decorative label into a heading. Too many low-value entries can make heading navigation less useful even when the page passes a simple presence test.
- Test desktop and mobile styling, table-of-contents anchors, and assistive heading navigation where practical. Descriptive section text should remain meaningful when read in an outline.
- Rescan and review the actual structure. A passing footer H2 does not resolve an unstructured main article, while a justified short page can remain simple without extra filler.
What the fix can break
Global H2 styles can change margins, size, and wrapping after an element conversion. Test narrow layouts and component grids rather than assuming a semantic edit is visually neutral.
Renaming headings can affect generated anchors and inbound fragment links. Preserve stable identifiers or appropriate compatibility where those links matter.
Do not expand a concise task page into a padded article just to cross a content or heading target. The best structure follows the real information need, not a scanner score.
Questions
Does every page need an H2?
No. A short single-purpose page may not need sections. The documented rule has a text threshold, and even that threshold includes boilerplate.
Why did an article with only a footer H2 pass?
The rule counts H2 elements anywhere in the inspected source. It does not validate the main article's outline.
Can styled text replace semantic headings?
Visual appearance alone does not communicate the same structure to software. Use appropriate heading markup for actual sections.
Which related checks help?
Review H1, JavaScript-rendered content, and the indexing checklist.