Dew Advisors
← SEO claims board Cluster 07 · 6 claims

Headings and semantic content structure

Heading order is clean, with one h1 per page. The finding is 7.4: every page nests repeated navigation inside <main>, which is one template decision and one fix. Three tool defects were caught in piloting. One would have produced a false Gap across all 25 pages.

2
Pass
0
Gap
2
Partial
1
N/A
1
Pending
7.1Pass
Heading rank encodes document depth: h1 is the top-level section, h2 a subsection, h3 a sub-subsection, and so on; authors should start at h1 and not skip levels. But Google treats heading ORDER as an accessibility feature, not a ranking factor.

Every page starts at h1 and skips no levels. The claim records that heading order is an accessibility feature rather than a ranking factor, so this is a conformance pass, not a ranking gain.

checked 2026-09-02result 25 Pass, identical in both viewstool structure-and-keyword-check
7.2Pass
A page should generally have a single h1 that describes the page's content (like its <title>); multiple h1s are permitted by the spec but not best practice. Google, however, sets no required count of headings.

Exactly one h1 per page on all 25. This was nearly missed: the h1 sits inside an <aside>, and the tool's first build excluded such wrappers and reported zero h1s site-wide. That false Gap was caught by hand-reading the pilot pages.

checked 2026-09-02result 25 Pass, identical in both viewstool structure-and-keyword-check
7.3Pending
Break long content into sections with descriptive headings so users (and parsers) can navigate; a <section> is a thematic grouping of content typically introduced by a heading and is appropriate only if it would appear in the document outline.

Heading coverage runs from roughly 300 to 2,000 words per heading. Whether the headings are descriptive is a judgement about the writing, not a structural fact, so no verdict was recorded.

result reported, no verdicttool structure-and-keyword-check
7.4Partial
Wrap the dominant, page-unique content in a single <main> element; it exposes a main landmark that assistive tech uses to jump to primary content, and repeated chrome (nav, sidebars, logos, copyright) must be excluded from it.

Every page has one <main>, and every page nests repeated navigation and sidebars inside it, so assistive technology jumping to <main> lands on navigation. It is uniform across all 25, so this is one template decision and one fix, not 25 page faults.

checked 2026-09-02result 25 Partial, identical in both viewstool structure-and-keyword-check
7.5Partial
Use <article> for a complete, self-contained composition that is independently distributable/reusable; reserve <nav> for major navigation blocks (not every group of links).

24 of 25 use <nav> only for blocks of 3 or more links, and one page wraps fewer. No page uses <article>, which is permissible for pages that are not self-contained compositions.

checked 2026-09-02result 24 Pass, 1 Partialtool structure-and-keyword-check
7.6N/A
Genuine tabular data belongs in <table> markup: rows/columns with <th> header cells (add scope so assistive tech associates them), a <caption> describing the table, and explicit thead/tbody; complex tables should be simplified or use id/headers association. Google's own richer path for machine-readable tabular data is Dataset/CSVW structured data, not a plain-<table> ranking bonus.

No <table> elements on all 25 pages, but 'no tables' is not 'no tabular data', since a grid built from <div>s would fail the claim while reporting zero tables. So the verdict was settled by hand, inspecting every view on the richest page. No view presents rows and columns with headers, so the claim has nothing to bind to.

checked 2026-09-02result site-level, inspected on the richest pagetool structure-and-keyword-check · manual inspection

Want this run on your site?

We test your site against the same claims, record a verdict and the evidence for each one, and tell you what to fix first.

Start a conversation