Schema generator and validator
Reads the page, validates the markup it already has, and writes what is missing.
What this is actually checking
Generate Organization, Article, Product, FAQ, LocalBusiness and Breadcrumb JSON-LD from a real page, and validate the markup already there against the properties that gate rich results.
Generated from what the page actually contains, so the markup matches the visible content. Markup describing content that is not on the page is a manual action risk rather than a technicality, and it is the most common way structured data does harm.
Validation resolves @id before it complains. A node carrying an @id is a reference into your entity graph, not an incomplete copy of it, and a validator that proposes completing the reference writes a second conflicting definition and breaks what it was fixing.
The 5 checks behind it
- mediumNo structured data
Without schema the page cannot earn rich results and is harder for answer engines to parse.
- highStructured data is invalid
Invalid JSON-LD is ignored entirely, so the effort already spent earns nothing.
- mediumStructured data is missing required properties
Rich results need the required fields; without them the markup is decorative.
- highStructured data does not match the visible page
Markup that describes content a user cannot see is a manual action risk.
- mediumNo Organization or LocalBusiness markup on the homepage
This is the markup that tells every engine who the brand is.
Why does it not flag every missing optional property?
Because a validator that reports every optional property as a warning trains people to ignore it. Required here means no rich result without it.
Can I paste the output straight in?
Yes. It is a complete JSON-LD block. Read it first: it is generated from your page, so anything wrong on the page is wrong in the markup.