Why it matters
Schema.org's own validator checks the vocabulary but ignores Google's requirements; Google's Rich Results Test checks its own rules for some types and needs a public URL. Most sites end up using both, and neither reads every format the same way.
This validator reads JSON-LD, Microdata and RDFa from pasted HTML into one model. It checks every type and property against the full schema.org vocabulary, bundled as a dated snapshot of the published release, so it catches a property on the wrong type, a misspelt name or a value of the wrong kind. It then applies Google's documented rich result rules, shared with the structured data validator, and writes the whole lot as clean JSON-LD.
How to use it
- Paste a page's HTML or a JSON-LD object.
- Read the items found and the problems for each.
- Check the eligibility table for rich results.
- Copy the clean JSON-LD, add any missing required properties, and test the live page with Google too.
FAQ
Is this the same as Google's Rich Results Test?
No. It applies Google's documented rules offline, plus the full schema.org vocabulary, which Google's test doesn't check. Google decides what it shows; test the live page there too.
Which formats does it read?
JSON-LD, Microdata and RDFa Lite, all from the same pasted HTML.
Why is a valid schema.org property flagged?
Each property belongs to certain types. author, for example, belongs to CreativeWork, so using it on a Product is flagged even though author is a real property.
Is anything fetched?
No. It reads only what you paste.
Credits and licences
Vocabulary from schema.org (CC BY-SA 3.0).
