Schema validator: is your page's JSON-LD correct?
Enter a page address: we read its JSON-LD structured data, recognise the schema.org types and check every entity. You see what is invalid and which recommended properties are missing. The test runs from the queue of our full audit.
What it checks
How many JSON-LD blocks there are and whether they are valid JSON, the types found (Organization, FAQPage, Product and so on) and, for each entity, errors and warnings: a missing type, an absent recommended property, questions without an answer. We also flag blocks without a schema.org context.
We read JSON-LD only, not microdata or RDFa.
How to read the result
An error means the entity is incomplete or broken and should be fixed. A warning is a recommended property that is missing: the page works, but the data is poorer than it could be.
No blocks found means the page declares no structured data in JSON-LD. A result with no errors says the markup is well formed, not that Google will show rich results: that is Google's decision.
One check only? Here is the full picture.
This tool reads one part of the audit. The full SEO audit measures the homepage with Lighthouse, checks whether AI assistants can read it and, for the cities we have scanned, compares it with their sites.
The short answers.
The report says something's off.
We can fix it.
SEO errors, slow pages, sites invisible to AI: these are exactly the problems we solve for businesses and professionals every day.