How is it different from validator.schema.org?

Validator.schema.org checks syntax and conformance to the Schema.org vocabulary. Our analyzer adds the Google layer: for each detected type it checks the required/recommended properties for rich results eligibility, flags conflicts, suggests missing types contextually, and cross-references our Schema.org releases watch.

What about Google's Rich Results Test?

Google's Rich Results Test only checks eligibility for the rich snippets Google supports (a small subset of Schema.org). Our analyzer covers a broader vocabulary, detects types you could add (even when they are not rich results), and gives an overall completeness score.

How is the completeness score computed?

For each detected Schema.org type: 70% of the score comes from required properties (Google), 30% from recommended properties (rich result bonus). The overall score is the average of each type's score. A score of 100 means all required and recommended properties are present for the targeted rich results.

Is the analyzed data stored?

A temporary 1-hour cache is kept per URL to avoid re-fetching. No data is stored permanently or shared. No sign-up is required. Up to 10 analyses per hour per IP to prevent abuse.

Structured data testing tool: JSON-LD and rich results audit

Audit the Schema.org markup of a URL: detected types, missing properties, Google rich results eligibility, contextual suggestions. Cross-referenced with our internal Schema.org watch.

Paste the full URL of a public page. The analyzer fetches the HTML, extracts every <script type="application/ld+json"> block, and compares them to the Google rich results reference.

What this tool adds

validator.schema.org

Checks syntax and conformance to the Schema.org vocabulary (all types).

Rich Results Test (Google)

Tests eligibility for the rich results Google supports (a subset of the vocabulary).

This tool

Completeness score 0-100 (per type and overall)
Broader coverage: also flags types outside rich results
Conflict detection (Article + BlogPosting on the same page)
Contextual suggestions of missing types
Corrected JSON-LD generator: missing properties pre-filled, ready to paste
Linked JSON-LD graph: entities connected by @id (mainEntityOfPage, breadcrumb attached)
Competitive comparison: your page against 3 competitors, opportunities highlighted
Risk detection: self-serving reviews, non-visible markup, SERP-restricted types
Cross-reference with the Schema.org releases watch
Nested entities tree + paste-HTML mode

Method and scoring

Parsing

Extraction of the <script type="application/ld+json"> blocks found in the HTML (including nested @graph), JSON decoding, then validation against an internal Google reference and cross-reference with the Schema.org watch. JSON-LD only (Microdata and RDFa not covered). No JavaScript execution: JSON-LD injected client-side (Google Tag Manager, JS) will not appear in "By URL" mode. In that case, use "Paste HTML" mode with the rendered HTML (the DOM, not the raw source).

Scoring

For each Google-supported type: 70% of the score comes from required properties, 30% from recommended ones (proportional). The overall "rich results completeness" score is the average of those types. Valid types that are outside Google rich results are flagged separately and do not count toward the score.

Coming soon

Consultant report PDF export (client deliverable)