30 checks in Content Quality & Entity Semantics. AI-assisted Scored in the Deep Audit's AI analysis pass.
| ID | Check | Passes when |
|---|---|---|
| 3.11.01 | Validate website content follows a consistent documentation structure (headings hierarchy, section clarity) | Consistent H1-H6 hierarchy across pages |
| 3.11.02 | Validate cross-references between pages use descriptive anchor text and contextual linking | No generic "click here" links |
| 3.11.03 | Validate documentation pages include table of contents or page-level navigation | TOC present on pages > 1500 words |
| 3.11.04 | Validate documentation has a clear entry point (index/overview page) that maps the full content hierarchy | Entry point page present |
| 3.11.05 | Validate documentation pages have clear breadcrumbs reflecting content hierarchy | Breadcrumbs present and accurate |
| 3.11.06 | Validate documentation sections have consistent formatting patterns (intro, body, summary) | Consistent patterns |
| 3.11.07 | Validate documentation uses versioning or update timestamps visible to readers and AI | Dates or version info present |
| 3.11.08 | Validate documentation depth matches topic complexity (simple topics concise, complex topics thorough) | Appropriate depth |
| 3.11.09 | Validate documentation avoids orphan pages (all doc pages reachable from the hierarchy) | Zero orphan doc pages |
| 3.11.10 | Compute Documentation Structure & Hierarchy composite score | Finalized |
| ID | Check | Passes when |
|---|---|---|
| 3.11.11 | Validate content categories, tags, and taxonomies are machine-parseable and consistent across the site | Consistent taxonomy |
| 3.11.12 | Validate category pages have proper meta descriptions and structured data | Category schema present |
| 3.11.13 | Validate tag naming follows a consistent convention (no duplicates, no typos, no overlaps) | Clean taxonomy |
| 3.11.14 | Validate taxonomy depth is manageable (not > 4 levels deep) | Depth <= 4 |
| 3.11.15 | Validate taxonomy is reflected in URL structure | URLs mirror taxonomy |
| 3.11.16 | Validate content-to-category mapping is complete (no uncategorized content) | Zero uncategorized pages |
| 3.11.17 | Validate taxonomy supports AI extraction (categories mentioned in structured data) | Category data in schema |
| 3.11.18 | Validate related content links are accurate and contextually relevant | Relevant related links |
| 3.11.19 | Validate faceted navigation does not create duplicate content or crawl traps | Canonical tags on faceted pages |
| 3.11.20 | Compute Content Taxonomy & Coherence composite score | Finalized |
| ID | Check | Passes when |
|---|---|---|
| 3.11.21 | If business exposes APIs, validate documentation follows OpenAPI/Swagger standards | OpenAPI spec present and valid |
| 3.11.22 | Validate API documentation is auto-discoverable (linked from site, referenced in structured data) | Discoverable |
| 3.11.23 | Validate API documentation includes request/response examples | Examples present |
| 3.11.24 | If business has a help center or knowledge base, validate it uses FAQ schema and QA pairs | FAQ/QA schema present |
| 3.11.25 | Validate knowledge base articles have clear hierarchy (category > subcategory > article) | Clear hierarchy |
| 3.11.26 | Validate knowledge base search functionality returns relevant results | Relevant search results |
| 3.11.27 | Validate knowledge base articles are updated within the last 12 months | Fresh content |
| 3.11.28 | Validate knowledge base content is extractable by AI (not behind login walls or JS rendering) | Publicly crawlable |
| 3.11.29 | Validate knowledge base uses consistent formatting that AI models can parse (headings, lists, code blocks) | AI-parseable format |
| 3.11.30 | Compute API & Knowledge Base AI-Readiness composite score | Finalized |
← 3.10 AI Agent Readiness3.12 Context Engineering for Web Content →
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).