60 checks in Content Quality & Entity Semantics. Automated Its subsection has a live automated checker in the engine.
| ID | Check | Passes when |
|---|---|---|
| 3.1.01 | Extract all H1 tags from raw HTML | Exactly 1 |
| 3.1.02 | Extract all H1 tags from DOM | Exactly 1 |
| 3.1.03 | Compare raw HTML vs DOM H1 | Identical |
| 3.1.04 | Validate H1 appears before main content | True |
| 3.1.05 | Validate H1 contains primary keyword/topic | True |
| 3.1.06 | Validate H1 length (20–70 chars) | Within range |
| 3.1.07 | Extract all H2 tags | Present |
| 3.1.08 | Validate H2s reflect subtopics | Strong topical alignment |
| 3.1.09 | Validate logical ordering of H2s | No jumps |
| 3.1.10 | Validate content follows the corresponding H2 | True |
| 3.1.11 | Extract all H3 tags | Present |
| 3.1.12 | Validate H3s appear only under relevant H2s | Correct nested structure |
| 3.1.13 | Extract all H4–H6 tags | Present if needed |
| 3.1.14 | Ensure no heading skips (H1→H3) | Sequential hierarchy |
| 3.1.15 | Validate no duplicate H1s | None |
| 3.1.16 | Ensure headings are visible (not display:none) | Visible |
| 3.1.17 | Validate headings are not inside <footer> or <nav> | Proper placement |
| 3.1.18 | Validate <main> element exists | Present |
| 3.1.19 | Validate <main> is unique | Only 1 |
| 3.1.20 | Validate <header> and <footer> elements exist | Present |
| 3.1.21 | Validate <article> or <section> used for structured content | Correct usage |
| 3.1.22 | Validate <aside> used only for side content | Correct usage |
| 3.1.23 | Identify missing ARIA roles where needed | Proper roles |
| 3.1.24 | Validate no conflicting ARIA roles | None |
| 3.1.25 | Validate semantic HTML for nav menus | Proper <nav> |
| 3.1.26 | Validate breadcrumb markup and placement | Present & valid |
| 3.1.27 | Validate breadcrumbs match URL hierarchy | Consistent |
| 3.1.28 | Identify headings that are used purely for styling | Avoid |
| 3.1.29 | Identify <div> or <span> acting as headings without <h#> | Fix |
| 3.1.30 | Validate heading density (1 H1, 3–10 H2s, etc.) | Balanced |
| 3.1.31 | Validate sectioning with <section> includes heading | Yes |
| 3.1.32 | Validate articles (<article>) include H1/H2 | Yes |
| 3.1.33 | Validate HTML5 semantic tags are not misnested | Correct nesting |
| 3.1.34 | Validate landmark roles are unique (banner, main, contentinfo) | True |
| 3.1.35 | Validate correct layout for UX: hero → sections → footer | Logical flow |
| 3.1.36 | Validate header structure supports anchor-based TOC | Consistent headings |
| 3.1.37 | Validate headings include entities (brand, location, service) | Present where relevant |
| 3.1.38 | Validate headings reflect intent (commercial/informational) | Relevant intent |
| 3.1.39 | Validate canonical topic signal appears in H1 | Yes |
| 3.1.40 | Validate H2s reflect topical subclusters | Strong cluster mapping |
| 3.1.41 | Validate heading repetition is avoided | No duplicates |
| 3.1.42 | Validate semantic structure matches visual structure | True |
| 3.1.43 | Validate role="heading" elements match logical levels | Correct |
| 3.1.44 | Validate tabbed/accordion content preserves semantic headings | True |
| 3.1.45 | Validate content in each header block is indexable | Not hidden by JS |
| 3.1.46 | Validate headings are not duplicated across pages (template collision) | Unique |
| 3.1.47 | Identify headings that contradict page topic | Avoid |
| 3.1.48 | Ensure no empty headings (<h2></h2>) | None |
| 3.1.49 | Validate HTML comment–inserted heading placeholders | None |
| 3.1.50 | Validate AI-overviews-friendly header segmentation | Clear topical segments |
| 3.1.51 | Validate scroll-depth sections match semantic headers | Consistent |
| 3.1.52 | Identify decorative images as headings | Avoid |
| 3.1.53 | Validate all important content appears under an H2 or H3 | True |
| 3.1.54 | Validate CTA blocks have supporting headers | Yes |
| 3.1.55 | Validate structured-data “headline” matches H1 | Consistent |
| 3.1.56 | Validate page outline extraction (HTML5 Outline Algorithm) | Logical outline |
| 3.1.57 | Detect JS rewriting H1/H2/H3 post-load | None |
| 3.1.58 | Validate consistent semantic structure across similar page types | Template integrity |
| 3.1.59 | Validate multi-language header structure alignment | Structural consistency |
| 3.1.60 | Compute header-structure composite score | >= 90% |
3.2 Content Depth, Topicality & Coverage Suite →
A Deep Audit scores every check here that applies to your page, then an AI pass of up to 150 checks. Included on Pro and Ultra, or $9 for one audit.
See plansMachine-readable: catalog totals and the full catalog as JSON (IDs, section, weight, status).