JSON-LD checker.
Paste JSON-LD or an HTML snippet that contains it. The tool finds syntax errors with the line and column, lists every item and its type, and checks Article, FAQPage, LocalBusiness, Product, BreadcrumbList, and Organization for missing properties. It is a quick lint and does not replace Google's Rich Results Test.
Paste JSON-LD, or a page snippet with script tags of the type application/ld+json.
This is a lint of the text you paste, not Google's Rich Results Test. It does not fetch pages or confirm that markup matches what visitors see. Rules follow Google's documentation for each type, linked under Sources below.
This tool runs in your browser. Nothing you enter is sent anywhere or stored.
How to use it
- Paste your markup Paste the JSON-LD itself or a larger HTML snippet. Every script tag with the type application/ld+json is read.
- Fix syntax first A syntax error shows the line and column with the text around it. Select Show in editor to jump to the spot.
- Read each item Every item lists its type and what is missing, split into errors, warnings, and notes.
- Test it for real Run the live page through Google's Rich Results Test, which shows what Google can use.
Why it matters
Structured data fails in 2 ways. It cannot be read at all, because of a stray comma or a curly quote pasted from a document, or it reads fine but leaves out what a search engine looks for. Syntax comes first, since 1 comma error makes the whole block unreadable. The checker points to the exact line and column, and its messages name the usual causes.
After syntax, it checks the content. Every top-level item should say what it is with @type, and the block should declare @context as schema.org. Then it follows Google's documentation for 5 types: Product needs a name and at least 1 of review, aggregateRating, or offers; BreadcrumbList needs at least 2 items with a position and name; LocalBusiness needs a name and an address; Article and Organization have no required properties, only recommended ones. FAQPage is checked against the schema.org definition, because Google removed its FAQ rich result documentation and says that feature no longer appears in Search.
Treat the result as a lint. A clean report means the markup is readable and carries the common properties, not that Google will show a rich result. The tool does not fetch pages, does not know your page content, and cannot judge whether the markup matches what visitors see, which Google requires. Confirm with the Rich Results Test or the Schema Markup Validator before you rely on it.
Sources
Questions
Is this the same as Google's Rich Results Test?
No. The Rich Results Test reads a live page and shows what Google can use. This checker only reads text you paste and applies a short list of rules.
Why is a missing recommended property only a warning?
Google documents these as recommended, so the markup works without them. Adding them gives search engines more to go on.
Does it handle several blocks and @graph?
Yes. Every script block is checked on its own, and every entry in an @graph is listed as its own item.
Why does it object to my curly quotes?
JSON only accepts straight double quotes. Word processors and some editors swap them for curly ones, which breaks the code.
Keep going
Read the Doily guides for step-by-step playbooks. To track results over time, see Doily's SEO tools.
