JSON-LD Validator
Paste your JSON-LD schema and get instant validation — @context check, @type verification, required-field enforcement for common schema types, plus a pretty-printed output.
How to use this tool3 quick steps
Find the JSON-LD on your page
View Source, search forapplication/ld+json— copy everything between<script>and</script>.Paste just the JSON
Paste the inner JSON only — no script tags. We validate JSON syntax + Schema.org type structure.Fix any errors
For Google rich results compatibility, also test in Google's Rich Results Test.
Use this with
Related schema & structured data tools
JSON-LD Validation Guide
Structured data that Google actually uses
Invalid JSON-LD is silently ignored by Google — no warning, no error, just no rich snippet. By the time you notice your FAQ accordion stopped appearing, you've already lost weeks of potential traffic. Validate before deploying, always.
The two required fields
Every JSON-LD object needs @context (always "https://schema.org") and @type (the schema name — Article, Product, FAQPage, etc.). Missing either means Google ignores the entire block.
Required fields per type
Each schema type has required fields for rich snippet eligibility. Article needs headline, author, datePublished. Product needs name and image. Miss any required field and the rich snippet won't render — even if the JSON is otherwise valid.
FAQPage validation
FAQPage has nested rules — mainEntity must be an array of Question objects, each with name (the question) and acceptedAnswer.text (the answer). Our validator checks each Q/A individually.
Multiple schemas per page
A page can have multiple <script> blocks — e.g., Article + BreadcrumbList + FAQPage on one blog post. Each block is independent and validates separately.
Script tag stripping
Paste the full <script type="application/ld+json">...</script> or just the JSON — we handle both. Makes it easy to grab structured data from 'View Source' and test it.
Always run Rich Results Test before deploy
Our validator catches syntax and required-field issues. Google's Rich Results Test additionally previews how the snippet will render. Do both before pushing structured data changes live.
Pro Tips
datePublished and dateModified must be ISO 8601 (YYYY-MM-DD or full timestamp). '2026-04-23' works; '04/23/2026' doesn't. Our validator accepts but format errors surface in Google's tester.
author should be a Person or Organization object with its own @type. Plain strings like 'author: "John"' work but give Google less info. Go with the full object.
Google requires the marked-up content to be visible on the page. FAQ schema on a page with no visible Q&A section is a policy violation — can suppress rich snippets site-wide.
Frequently Asked Questions
- Which schemas does this tool deep-check?
- We enforce required fields for the most common types: Article, NewsArticle, BlogPosting, Product, FAQPage, HowTo, Recipe, Event, LocalBusiness, Organization, Person, VideoObject, BreadcrumbList, Review. Others validate for @context and @type but not field requirements.
- Why does my JSON validate here but fail in Google's tester?
- We check JSON-LD SYNTAX and REQUIRED FIELDS. Google's Rich Results Test additionally checks VISUAL RICH SNIPPET ELIGIBILITY — things like image dimensions, URL accessibility, and content policy compliance. Run both.
- Can I validate raw JSON (without JSON-LD structure)?
- Yes — we'll parse any JSON. But without @context and @type, it's just generic data, not structured data. Google only recognizes schema.org JSON-LD.
- What if I have @type as an array?
- Supported in schema.org — e.g., @type: ["Product", "IndividualProduct"]. Our validator checks the first type for required fields. Google accepts array types but treats them independently.