30 checks in Core Web Vitals & Performance. Automated Its subsection has a live automated checker in the engine.
| ID | Check | Passes when |
|---|---|---|
| 4.7.01 | Validate primary business entity declared within first 200 words of homepage | Entity present early |
| 4.7.02 | Validate primary entity includes name, type, location, and description | Complete entity declaration |
| 4.7.03 | Validate entity description is factual and non-promotional (AI-compatible) | Factual |
| 4.7.04 | Validate entity attributes are consistent across all pages | Consistent |
| 4.7.05 | Validate structured data (JSON-LD) matches visible entity content | Aligned |
| 4.7.06 | Validate entity relationships are explicitly stated (parent company, subsidiaries, founders) | Explicit |
| 4.7.07 | Validate key facts are formatted as standalone sentences (not buried in paragraphs) | Extractable |
| 4.7.08 | Validate key data points use consistent formatting (dates, numbers, currencies) | Consistent format |
| 4.7.09 | Validate lists of services/products use <ul>/<ol> markup (not comma-separated prose) | List markup |
| 4.7.10 | Validate comparison data uses <table> markup (not paragraph descriptions) | Table markup |
| 4.7.11 | Validate each page has a clear topical focus (one primary entity/topic per page) | Focused |
| 4.7.12 | Validate section headings accurately describe the content below them | Accurate headings |
| 4.7.13 | Validate acronyms and abbreviations are defined on first use | Defined |
| 4.7.14 | Validate technical terms include inline definitions or glossary links | Defined |
| 4.7.15 | Validate contact information is in machine-parseable format (not image-only) | Text-based |
| 4.7.16 | Validate hours of operation in machine-parseable format | Structured |
| 4.7.17 | Validate address in machine-parseable format (not image or PDF) | Text-based |
| 4.7.18 | Validate pricing information in machine-extractable format | Structured |
| 4.7.19 | Validate date formats are unambiguous (ISO 8601 or clearly formatted) | Unambiguous |
| 4.7.20 | Validate geographic coordinates available in metadata or schema | Present |
| 4.7.21 | Validate key claims have supporting evidence within the same content block | Evidence present |
| 4.7.22 | Validate content avoids ambiguous pronouns when referencing entities | Clear references |
| 4.7.23 | Validate page-level summary or abstract present for long-form content | Summary present |
| 4.7.24 | Validate content sections are independently comprehensible (context-complete) | Self-contained |
| 4.7.25 | Validate no critical information is conveyed only through images | Text alternative present |
| 4.7.26 | Validate no critical information is conveyed only through video | Transcript present |
| 4.7.27 | Validate entity attributes match Knowledge Graph entries (if entity exists) | Consistent with KG |
| 4.7.28 | Validate disambiguation signals present for common entity names | Disambiguated |
| 4.7.29 | Validate content readability score appropriate for target audience | Appropriate level |
| 4.7.30 | Compute AI-First Entity Formatting Score | Finalized |
← 4.6 Mobile Performance & Device Adaptation Suite4.8 Brand Trust 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).