Auditor
Schema Coverage Auditor
Structured data tools grade you against Google's rich results. Answer engines read a narrower set and care about different fields. Paste your JSON-LD and this reports against what assistants actually use.
- Scoped to answer enginesNot generic rich results
- Names missing fieldsBy property
- Paste, never fetchNothing leaves the page
Check it
Paste it here
Result
- Valid JSON —
- Types found —
- FAQPage questions —
- Organization identity —
- Missing required fields —
- Do next —
Answer engines lean on FAQPage, Organization and BreadcrumbList far more than on the long tail of schema types. Getting those three right is worth more than adding a fourth.
What the result means
FAQPage is the type that gets quoted
A question and its answer, marked up as a pair, is the closest thing on the web to the shape an assistant wants. If you add one type, add this one.
Organization is how you get named
Without it, an answer can use your content and attribute it to nobody. It is the difference between being the source and being an anonymous input.
Markup does not fix thin content
Structured data tells a machine what your words are. It does not make the words answer anything. A perfectly marked-up page that says nothing still says nothing.
Three types cover most of the value
FAQPage, Organization and BreadcrumbList. The long tail of schema types is mostly irrelevant to assistants, whatever a generic validator scores you.
Questions
No, and it is not a replacement. That grades you against search features. This checks the narrower set of types answer engines lean on.
It makes your content easier to parse and attribute correctly. It is not a ranking lever, and anyone selling it as one is overselling.
View source and look for a script tag with type="application/ld+json". Copy everything between the tags.
Want this run against your whole site?
Tell us the page your assistant lives on and the questions you care about. A person runs them and sends back the raw answers.