JSON-LD Schema Validator
Validate structured data markup for schema.org compliance and required fields.
Schema Validator Features
Fast, accurate structured data validation in your browser.
Validates required fields for Article, Product, FAQPage, HowTo, and 15+ schema types.
Enter a URL to automatically extract and validate all JSON-LD blocks on the page.
Shows errors, warnings, and detected schema types in an easy-to-read report.
Key Takeaways
- Paste JSON-LD mode parses and checks your markup entirely on your device, while Fetch from URL mode retrieves a live page's HTML through a third-party proxy, so use paste mode for unpublished drafts and snippets.
- The validator checks JSON syntax, @type and @context presence, and required fields for a curated set of common types like Article, Product, FAQPage, HowTo, Recipe, Event, and LocalBusiness, including nested objects such as Offer, Review, and ListItem.
- Errors (missing required fields and misspelled properties) block valid output and should be fixed first, while warnings like a missing @context on a top-level object are advisory; note that property names are case sensitive, so datePublished and datepublished are not the same.
- Run this tool for fast structural checks, then use Google's Rich Results Test for the final word, since it validates against Google's full rich result rules that go beyond the required-field checks done here.
How to Validate JSON-LD Structured Data
Paste markup or fetch a page
On the Paste JSON-LD tab, drop in the contents of a script type "application/ld+json" block, a single object, or an array of objects. Or switch to the Fetch from URL tab and enter a live page address to pull every JSON-LD block from its HTML automatically.
Click Validate Schema
The validator parses the JSON, confirms each object has an @type, checks that top-level objects declare @context, and verifies the required fields for known types such as Article, Product, FAQPage, HowTo, Recipe, Event, and LocalBusiness. It walks nested objects and arrays too, so embedded Offer, Review, or ListItem entries are checked as well.
Review types, errors, and warnings
Read the summary line for a pass or fail count, scan the detected type badges, then work down the issue list. Fix every error (missing required fields and misspelled properties) first, then address warnings, and re-run until the report is clean.
What Each Check Means
The validator raises two severity levels. Errors block valid output and should be fixed first; warnings are advisory and often safe to leave, but reviewing them improves coverage. Here is what triggers each message.
| Check | Severity | What triggers it |
|---|---|---|
| Invalid JSON | Stops validation | The text cannot be parsed, for example a trailing comma or unbalanced bracket. |
| Missing required field | Error | A known type lacks a field it needs, such as Article without headline, author, or datePublished. |
| Unknown property with close match | Error | A property is misspelled within two edits of a real one, so a did you mean suggestion is shown. |
| Missing @type | Warning | An object has no @type, so required fields cannot be checked. |
| Missing @context | Warning | A top-level object omits @context, expected to be https://schema.org. |
| Unrecognized type or property | Warning | The type is not in the curated list, or a property has no close-matching known field. |
Which Mode and Tool to Use
Paste JSON-LD mode
Use this while writing or editing markup. Your pasted JSON is parsed and checked entirely on your device, so it is ideal for drafts, snippets, and code you are not ready to publish.
Fetch from URL mode
Use this to audit a page already live. The tool retrieves the HTML through a third-party proxy, extracts every JSON-LD script block, and validates them together. Pages behind logins or heavy JavaScript rendering may return nothing to check.
This validator
Best for fast structural checks: JSON syntax, @type and @context presence, required fields, and typo detection across a curated set of common schema types and their nested objects.
Google Rich Results Test
Use it alongside this tool for the final word. It validates against Google's own rich result rules and full property sets, which go beyond the required-field checks performed here.
Common Problems and Fixes
Invalid JSON message appears
The markup could not be parsed. Look for trailing commas, unquoted keys, or unescaped quotes inside string values. Copy only the JSON inside the script tag, not the surrounding HTML, then validate again.
Missing @context warning on valid markup
This warning fires only on top-level objects. Add "@context": "https://schema.org" to each root object. Nested objects inherit context and do not need it repeated.
Did you mean suggestion on a real property
The checker flags properties that are not in its known list for that type but are within two edits of one, like datepublished instead of datePublished. Schema.org property names are case sensitive, so match the exact spelling and capitalization.
URL fetch returns no schema
The page may have no JSON-LD, may inject it with JavaScript after load, or may block the proxy used to retrieve it. View the page source to confirm a script type application/ld+json block exists, or copy that block and use the paste mode instead.
About JSON-LD Schema Validator
This tool validates JSON-LD structured data against schema.org requirements. Paste your markup or enter a URL to check for syntax errors, missing required fields, and unknown schema types.
Frequently Asked Questions
Is this tool free to use?
Yes, this tool is completely free.
No account or registration is required.
You can use it as many times as you like.
Is my data private?
JSON input is processed entirely in your browser.
URL fetching uses a proxy to retrieve the page content.
We do not store or log any submitted data.
What is the difference between errors and warnings?
Errors indicate missing required fields that search engines expect.
Warnings indicate best practices that should be followed but are not strictly required.
Fix all errors before submitting to Google Search Console.
Why is my schema type showing as unknown?
The validator checks a curated list of common schema types.
Less common types may not have required field definitions built in.
Unknown type warnings do not mean the schema is invalid.
How do I fix missing required fields?
Add the missing property to your JSON-LD object.
Refer to schema.org documentation for acceptable values.
Re-run the validator after making changes.
Does it work on mobile?
Yes, the tool is fully responsive.
It works on phones, tablets, and desktops.
No app download is needed.
What browsers are supported?
All modern browsers are supported.
This includes Chrome, Firefox, Safari, and Edge.
Keep your browser updated for best results.
Should I also use Googles Rich Results Test?
Yes. This tool provides quick local validation.
Googles Rich Results Test provides official validation against Googles requirements.
Use both for the most thorough validation.
Sources and References
Format and tool details on this page are based on the official specifications and documentation below.
- JSON Schema specification- json-schema.org
- RFC 8259: The JSON Data Interchange Format- IETF
- JSON- MDN Web Docs