- Free tools
- Schema Markup Validator
FREE SCHEMA MARKUP VALIDATOR AND CHECKER
Schema Markup Validator: find what stops your rich results
Enter a URL to check if a page has schema markup, or paste JSON-LD to validate it. Find JSON syntax errors, missing required properties and invalid values. Covers Product, Article, FAQPage, Organization, LocalBusiness, BreadcrumbList, Event and more. No signup.
- URL or JSON-LD
- No signup required
- Required and recommended checks
WHAT WE CHECK
Your structured data
Paste the JSON object, or the whole <script type="application/ld+json"> block. Several blocks are fine.
We fetch the page once, extract its JSON-LD blocks and validate them. Nothing is stored.
Pasted code is checked in your browser and never uploaded.
Results
Paste JSON-LD or enter a URL on the left and click “Validate schema.” Results appear here.
HOW IT WORKS
From JSON-LD to a clean fix list in seconds
Structured data fails quietly. A missing comma or a relative image URL can drop a page out of rich results without any warning in your CMS. This validator shows exactly where and why.
Paste code or a URL
Test a draft before it ships, or check a live page. The validator extracts every JSON-LD block, including @graph arrays and nested entities.
Read the checks
Each entity gets a status for its type: required properties, recommended properties and value formats, plus JSON errors with the exact line and column.
Fix and revalidate
Every issue names the property path and the fix. Edit the code in place and validate again until each entity passes.
WHAT THE VALIDATOR CHECKS
The errors that cost you rich results
Checks follow Schema.org vocabulary and Google’s structured data guidelines for each supported rich result type.
JSON parse errors
Trailing commas, unquoted keys, smart quotes pasted from a word processor and unclosed brackets, each reported with line and column.
Missing required properties
Product needs a name plus offers, review or aggregateRating. Event needs startDate and location. Missing ones block rich result eligibility.
Recommended properties
Flags gaps like a missing image on Article, availability on Offer or telephone on LocalBusiness that make results richer.
Value formats
Dates must be ISO 8601, priceCurrency a 3-letter ISO 4217 code, prices plain numbers without symbols, and URLs absolute.
Context and type
Catches a missing or wrong @context, missing @type, unknown types, and property names with the wrong case, like Name instead of name.
Nested entities and @graph
Validates every Offer, Question, ListItem, Person and Rating inside the main entity, and each item in an @graph, with its full property path.
SCHEMA CHECKER VS GOOGLE AND SCHEMA.ORG
Other validators tell you it failed. This tells you what to fix.
Google’s Rich Results Test is the final word on rich result eligibility, and the Schema.org Validator at validator.schema.org checks vocabulary for every type. This checker is faster for debugging drafts, explaining formats, and checking types Google doesn’t report on. Schema only helps when it matches the visible page, so pair it with fixes for thin content.
| What you get | Schema Markup Validator | Google Rich Results Test | Schema.org Validator |
|---|---|---|---|
| JSON errors with line and column | ✓ Exact position | General parse error | General parse error |
| Value format checks | ✓ Dates, currency, prices, URLs | Partial | Not checked |
| Types without rich results | ✓ Organization, WebSite, Person and more | Not reported | ✓ All types |
| Official eligibility verdict | Guideline based | ✓ Authoritative | No |
| Renders JavaScript | Server HTML only | ✓ | No |
| Missing required fields explained | ✓ With the fix | For rich result types | No |
Schema injected by JavaScript, for example through Google Tag Manager, won’t appear in URL checks. Paste the rendered JSON-LD instead.
FAQ
Schema markup checker questions
How do I check if a page has schema markup?
Switch to “Check a URL” above and enter the page address. The checker lists every JSON-LD block on the page and validates each one. To check by hand, view the page source and search for application/ld+json. Schema added later by JavaScript or Google Tag Manager only shows in the rendered page, so test those pages in Google’s Rich Results Test too.
How do I validate FAQPage schema?
FAQPage needs a mainEntity array of Question items. Each Question needs a name and an acceptedAnswer of type Answer with a text property, and the questions and answers must match the visible page. Paste the block above and the checker flags any missing piece.
What is the difference between this and Google’s Rich Results Test?
Google’s Rich Results Test only reports on the schema types that can earn rich results and needs a live URL or a code snippet. This validator also checks JSON syntax with line numbers, common property mistakes like wrong casing and relative URLs, and value formats such as dates, currencies and prices, so you can fix drafts before publishing.
Does valid schema guarantee rich results?
No. Valid structured data makes a page eligible, but Google decides whether to show a rich result based on content quality, policy and the search query. Markup must also describe content that is visible on the page.
Should I use JSON-LD, Microdata or RDFa?
Google recommends JSON-LD because it sits in one script block, separate from the visible HTML, which makes it easier to add and maintain. All three formats are supported.
Why did my FAQ rich results disappear?
In August 2023 Google limited FAQ rich results to well-known, authoritative government and health websites, and it removed HowTo rich results. FAQPage markup is still valid and can help other systems understand the page, but most sites no longer get the expandable result.
Is my code or URL stored?
No. Pasted JSON-LD is checked entirely in your browser. When you check a URL, the page is fetched once to extract its JSON-LD blocks and nothing is saved, as described in our Privacy Policy.
What does a missing required property mean?
Google lists required properties for each rich result type. If one is missing, the item is not eligible for that rich result. Recommended properties are optional, but adding them can make the result more complete.
Validate one page here. Audit structured data across every page with SiteAuditLint.
Schema breaks at the template level. One bad product template can strip rich results from thousands of pages, and only a crawl finds them all.
Run Free Site Audit