80 checks in Content Quality & Entity Semantics. AI-assisted Scored in the Deep Audit's AI analysis pass.
| ID | Check | Passes when |
|---|---|---|
| 3.4.01 | Validate page includes a clear, concise 1–2 sentence summary at top | Summary present |
| 3.4.02 | Extract summary block and evaluate factual correctness | Accurate |
| 3.4.03 | Ensure summary includes primary entity + topic | Yes |
| 3.4.04 | Confirm summary contains no marketing fluff | Purely factual |
| 3.4.05 | Validate presence of short sections (<300 words each) | AI‑friendly segmentation |
| 3.4.06 | Validate content is chunked with clear headings every 150–300 words | Strong chunking |
| 3.4.07 | Validate each chunk begins with a clear topic sentence | Present |
| 3.4.08 | Validate each chunk ends with a takeaway | Present |
| 3.4.09 | Identify missing “key point” bullets | Include bullets |
| 3.4.10 | Validate bullet lists are simple, factual, short | AI‑compliant |
| 3.4.11 | Validate numbering correctness on numbered lists | No broken lists |
| 3.4.12 | Validate presence of definition blocks (e.g., “What is X?”) | Yes |
| 3.4.13 | Validate “What is X?” block appears high on page | Early placement |
| 3.4.14 | Validate presence of “How X works” block | Yes |
| 3.4.15 | Validate presence of “Why X matters” block | Yes |
| 3.4.16 | Validate presence of process/steps enumerations | Yes |
| 3.4.17 | Validate presence of pros/cons | Yes |
| 3.4.18 | Validate presence of comparisons (X vs Y) | Present |
| 3.4.19 | Validate presence of FAQ tailored to query variations | Yes |
| 3.4.20 | Validate FAQ answers are <75 words | Concise |
| 3.4.21 | Validate FAQ answers contain no marketing pitch | Purely factual |
| 3.4.22 | Validate FAQ answers include entity and topic | Yes |
| 3.4.23 | Identify question‑answer pairs relevant to the topic cluster | Strong coverage |
| 3.4.24 | Validate question formatting starts with “What,” “Why,” “How,” “Can,” etc. | Correct |
| 3.4.25 | Validate examples included for complex topics | Present |
| 3.4.26 | Validate analogies are used appropriately | Clear |
| 3.4.27 | Validate content complies with AI‑safe phrasing (no speculative claims) | Compliant |
| 3.4.28 | Validate elimination of future predictions (“AI will…”) unless supported | Accurate |
| 3.4.29 | Detect hallucinated facts or outdated info | None |
| 3.4.30 | Validate citations for any statistics | Present |
| 3.4.31 | Validate structured data for Q&A is present (FAQPage) | Yes |
| 3.4.32 | Validate structured data consistency with on‑page answers | Identical |
| 3.4.33 | Validate “People Also Ask” question inclusion | Covered |
| 3.4.34 | Validate snippetable definition paragraphs (<45 words) | Present |
| 3.4.35 | Validate direct‑answer paragraphs (<35 words) | Snippet‑ready |
| 3.4.36 | Validate readability of direct‑answer paragraphs | Very clear |
| 3.4.37 | Validate AI‑overview continuity: sections flow logically | Yes |
| 3.4.38 | Validate minimal pronoun chaining (he/she/it confusion) | Clean |
| 3.4.39 | Validate absence of ambiguous references (“this,” “that”) | Avoid |
| 3.4.40 | Validate entity‑explicit writing (refer to subjects by name) | Strong |
| 3.4.41 | Validate numerical data formatting (simple & clear) | Clean |
| 3.4.42 | Validate presence of data tables | Present |
| 3.4.43 | Validate presence of process flow diagrams or list structures | Present |
| 3.4.44 | Validate top‑level sections cover query variations | Broad coverage |
| 3.4.45 | Validate no contradictory statements across sections | None |
| 3.4.46 | Validate duplicate sentences removed | Clean |
| 3.4.47 | Validate overly long sections (>350 words) split into chunks | Chunked |
| 3.4.48 | Validate internal semantic linking in each chunk | Present |
| 3.4.49 | Validate each chunk has ≥1 outbound contextual link | Present |
| 3.4.50 | Validate no chunk is too short (<60 words) unless definition | Balanced |
| 3.4.51 | Validate content includes alternative phrasing for ambiguous terms | Clarified |
| 3.4.52 | Validate inclusion of user scenarios | Present |
| 3.4.53 | Validate inclusion of edge‑case examples | Present |
| 3.4.54 | Validate error‑case descriptions (what can go wrong) | Present |
| 3.4.55 | Validate risk/concern section | Present |
| 3.4.56 | Validate trust terminology for sensitive subjects | Present |
| 3.4.57 | Validate content avoids reductive oversimplifications | Balanced |
| 3.4.58 | Validate clean fact‑to‑fact transitions | Strong |
| 3.4.59 | Validate each section can stand alone if extracted | Self‑contained |
| 3.4.60 | Validate minimal dependency between sections | Independent |
| 3.4.61 | Validate semantic embedding of each chunk | Embeddings created |
| 3.4.62 | Validate chunk‑level embedding similarity to topic | ≥ 0.70 |
| 3.4.63 | Validate chunk‑level similarity to competitor pages | Comparable or higher |
| 3.4.64 | Validate multi‑intent sectioning (How? Why? What if? When? Who?) | Present |
| 3.4.65 | Validate option comparison tables | Present |
| 3.4.66 | Validate do/don't lists where applicable | Present |
| 3.4.67 | Validate full AI‑overview readiness score | >= 90% |
| 3.4.68 | Validate multi‑modal AI‑overview readiness (text, images, lists) | Strong |
| 3.4.69 | Validate zero hallucinations, contradictions, or factual gaps | Zero issues |
| 3.4.70 | Compute AI‑overview composite score | >= 92% |
| ID | Check | Passes when |
|---|---|---|
| 3.4.71 | Validate robots.txt does NOT block GPTBot user agent | Allowed |
| 3.4.72 | Validate robots.txt does NOT block ClaudeBot user agent | Allowed |
| 3.4.73 | Validate robots.txt does NOT block PerplexityBot user agent | Allowed |
| 3.4.74 | Validate robots.txt does NOT block CCBot (Common Crawl) user agent | Allowed |
| 3.4.75 | Validate content includes at least 1 cited statistic with source | Present |
| 3.4.76 | Validate content includes at least 1 direct quote from an authority | Present |
| 3.4.77 | Validate all statistics include publication year and source name | Sourced |
| 3.4.78 | Validate content freshness (published or updated within last 12 months) | Fresh |
| 3.4.79 | Validate page can be reached within 3 clicks from homepage | Shallow depth |
| 3.4.80 | Validate content uses concise, direct-answer format for key claims | Direct |
← 3.3 Entity Extraction, Disambiguation & E-E-A-T Signals Suite3.5 Media, Alt, Captions & Multimodal Signals 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).