90 checks in Schema, Local, Trust, Deep Audit. Automated Its subsection has a live automated checker in the engine.
| ID | Check | Passes when |
|---|---|---|
| 6.3.01 | Detect BlogPosting or Article schema | Present |
| 6.3.02 | Validate correct schema type (BlogPosting, NewsArticle, Article) | Accurate |
| 6.3.03 | Validate headline present and matches on-page H1/H2 | Consistent |
| 6.3.04 | Validate description present and meaningful | Clear |
| 6.3.05 | Validate articleBody present or extractable | Present |
| 6.3.06 | Validate articleBody accuracy vs on-page content | High match |
| 6.3.07 | Validate wordCount property if used | Accurate |
| 6.3.08 | Validate mainEntityOfPage present | Present |
| 6.3.09 | Validate datePublished exists and is valid ISO format | Correct |
| 6.3.10 | Validate dateModified exists and >= datePublished | Correct |
| 6.3.11 | Validate author schema present | Present |
| 6.3.12 | Validate author is Person or Organization with correct fields | Valid |
| 6.3.13 | Validate author name matches on-page byline | Consistent |
| 6.3.14 | Validate publisher schema present | Present |
| 6.3.15 | Validate publisher includes logo via ImageObject | Logo present |
| 6.3.16 | Validate publisher name consistency across site | Consistent |
| 6.3.17 | Validate image/featuredImage property present | Present |
| 6.3.18 | Validate featured image accessible (200 status) | OK |
| 6.3.19 | Validate ImageObject includes width/height if possible | Included |
| 6.3.20 | Validate ImageObject includes caption (if applicable) | Present |
| 6.3.21 | Validate keywords/tags included | Present |
| 6.3.22 | Validate genre property (e.g., analysis, blog, guide) | Present |
| 6.3.23 | Validate canonical alignment with article schema URL | Perfect match |
| 6.3.24 | Validate sameAs references (e.g., social author profiles) | Present |
| 6.3.25 | Validate citation property for referenced sources | Included where relevant |
| 6.3.26 | Validate mentions property (entities/topics referenced) | Present |
| 6.3.27 | Validate articleSection (topical category) | Present |
| 6.3.28 | Validate about (entities) present for semantic understanding | Present |
| 6.3.29 | Validate alternativeHeadline if present | Accurate |
| 6.3.30 | Validate full schema passes Google Rich Results Test | Pass |
| 6.3.31 | Validate structured data matches on-page headings hierarchy | Accurate |
| 6.3.32 | Validate article schema includes readingTime if available | Present |
| 6.3.33 | Validate inclusion of speakable specification for voice agents (if used) | Present |
| 6.3.34 | Validate accessibility of the article for screen readers | Correct |
| 6.3.35 | Validate learningResourceType (tutorial, guide, review) | Accurate |
| 6.3.36 | Validate temporalCoverage if relevant | Present |
| 6.3.37 | Validate references property for external sources | Included |
| 6.3.38 | Validate associatedMedia (images, videos) | Included |
| 6.3.39 | Validate review or rating schema if article includes evaluations | Present |
| 6.3.40 | Validate discussionUrl if comments available | Correct |
| 6.3.41 | Validate commentCount if comments active | Present |
| 6.3.42 | Validate isPartOf property linking to blog/collection index | Present |
| 6.3.43 | Validate breadcrumb structured data coherence | Consistent |
| 6.3.44 | Validate locationCreated if relevant | Correct |
| 6.3.45 | Validate contentLocation for context-based articles | Present |
| 6.3.46 | Validate translator property if content translated | Correct |
| 6.3.47 | Validate editor property if editorially reviewed | Present |
| 6.3.48 | Validate alternativeHeadline matches intent | Accurate |
| 6.3.49 | Validate that article schema entity references (via about/mentions) match topical content | High-match |
| 6.3.50 | Validate the presence of named entities (organizations, people, locations, technologies) | Present |
| 6.3.51 | Validate that semantic entity linking aligns with the article’s main topic | Correct |
| 6.3.52 | Validate citation graph consistency across site | Consistent |
| 6.3.53 | Validate article structured data completeness score >= 90% | High |
| 6.3.54 | Validate structured data identical across raw HTML and rendered DOM | Stable |
| 6.3.55 | Validate no conflicting authorship metadata (meta tags vs JSON-LD) | Clean |
| 6.3.56 | Validate that dateModified aligns with sitemap lastmod | Consistent |
| 6.3.57 | Validate that featured image schema aligns with OG:image | Exact match |
| 6.3.58 | Validate that structured data includes multiple image resolutions (if available) | Present |
| 6.3.59 | Validate that article schema correctly references any VideoObject | Present |
| 6.3.60 | Validate full schema passes Schema.org validator | Full pass |
| 6.3.61 | Validate structured data matches canonical URL signals | Exact |
| 6.3.62 | Detect conflicting publication dates across meta tags, schema, AMP, or RSS | None |
| 6.3.63 | Validate no contradictory author values (schema vs OG vs meta) | None |
| 6.3.64 | Validate no contradictory publisher values | Clean |
| 6.3.65 | Validate absence of outdated AMP article schema | None |
| 6.3.66 | Validate article schema does not include deprecated fields | Clean |
| 6.3.67 | Validate articleBody is not overly truncated in JSON-LD | Correct |
| 6.3.68 | Validate articleBody contains structured paragraphs or text blocks | Present |
| 6.3.69 | Validate references to multimedia (charts, tables, diagrams) if present | Included |
| 6.3.70 | Validate supporting content (FAQs, summaries, highlights) reflected in schema | Present |
| 6.3.71 | Validate correct representation of article intent (informational, transactional, editorial) | Accurate |
| 6.3.72 | Validate alignment between article schema and Page Topic/Entity | Strong match |
| 6.3.73 | Validate AI-readiness of entity linking | Machine-readable |
| 6.3.74 | Validate Named Entities extracted via NLP appear in schema | High overlap |
| 6.3.75 | Validate presence of isPartOf linking article → category → main website | Present |
| 6.3.76 | Validate outbound references included if article mentions authoritative sources | Present |
| 6.3.77 | Validate multiple author scenario correctness (multiple Person objects) | Accurate |
| 6.3.78 | Validate article schema accessibility by headless crawlers | Accessible |
| 6.3.79 | Validate JSON-LD appears before <body> close | Correct placement |
| 6.3.80 | Validate article structured data is crawlable even when JS disabled | Yes |
| 6.3.81 | Validate structured data adheres to site-wide consistency conventions | Consistent |
| 6.3.82 | Validate article schema references mainOrganization via publisher | Linking correct |
| 6.3.83 | Validate inclusion of sameAs for article author (LinkedIn, Twitter, website) | Present |
| 6.3.84 | Validate no duplicate Article or BlogPosting schemas per page | None |
| 6.3.85 | Validate article passes Google Search Console rich data tests | Pass |
| 6.3.86 | Validate article passes Schema.org validator with no errors | Pass |
| 6.3.87 | Validate article JSON-LD minifies cleanly without breaking | Clean |
| 6.3.88 | Validate schema objects follow naming conventions and stable @id | Correct |
| 6.3.89 | Compute article schema completeness score | >= 90% |
| 6.3.90 | Compute full Article/BlogPosting composite score | >= 90% |
← 6.2 Service / Product / Offering Schema Suite6.4 FAQ / HowTo / Q&A Schema 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).