Schema and JSON-LD structured data validator
The four ways markup fails, every one of them silent
Valid does not mean shown. Correct markup makes you eligible for a rich result, it does not earn you one.
Everything is computed in your browser. Nothing is stored.
Structured markup is an invisible block that tells a machine what the page contains. It fails in four ways, and none of them is visible from the page: JSON that does not parse, so absent rather than invalid; a missing required property, which makes the block ineligible without making it wrong; a date in a format schema.org does not accept; a malformed nested entity. Hence a validator.
How to use it
How it works
Start from an address or a paste
The tool reads the JSON-LD blocks of a live page, or validates what you paste in before you publish it.
Read it block by block
Syntax, @context, @type, required and recommended properties for each type, date formats.
Fix and revalidate
The pasted block stays editable: correct it in the field and the verdict updates immediately.
Worth knowing
Four things to keep in mind
JSON that does not parse is absent, not invalid
One comma too many and the block is not "incorrect": it does not exist. Nothing reads it, nothing flags it, and the page behaves exactly as if you had never written it.
Valid does not mean shown
Correct markup makes you eligible for a rich result. It does not grant you one: Google decides, and it often decides to show nothing.
Dates want ISO 8601
2026-08-17 works, 17/08/2026 does not. The second parses as ordinary text and gets ignored without a word, which is exactly the kind of failure a validator exists to catch.
Check what is served, not what you wrote
A plugin or a tag manager can inject its own version over yours. Validating from the address rather than from your source file shows what actually ships.
FAQ
Frequently asked questions
No, it is not a ranking factor. It makes you eligible for enriched displays and gives assistants an unambiguous description of the page, which shows up in click-through rate rather than in position.
The Rich Results Test says what Google will do with the markup, the schema.org validator says whether it conforms to the specification. This tool sits between the two: syntax, required properties and formats, without opening two tabs.
Properties whose absence does not make the block invalid, but which markedly improve the display you get. An image or a date on an article, for instance, are not required but change the render.
Yes. A page often carries three or four, and the tool handles them separately so an error is attached to the right block. A paste containing several objects separated by a blank line works too.
Also
Other tools in the same family
Also
What Lokvi does for you
Now imagine all of it running without you
Review collection, replies, posts and loyalty, on your Google Business listing, automatically.
No credit card required: create your account and explore your real data.
14 days free, then 29 €/month, no commitment.