Open from URL works only for sites that allow cross-site requests (CORS). For other pages open view-source:https://… in your browser, copy the HTML and paste it here.
No input yet.
Paste JSON-LD or HTML, open a file or load the example.
Schema markup validator for JSON-LD, microdata and RDFa
This JSON-LD validator checks structured data against the schema.org vocabulary and Google's rich result rules. Paste JSON-LD or a page's HTML – every script block, microdata and RDFa item is read and each problem is shown with its path and line.
Last updated:
How it works
Paste or open
Paste JSON-LD or a page's HTML source, drop several files for a batch check, or open a URL.
Read every block
Every JSON-LD script is parsed on its own; microdata and RDFa Lite items are checked with the same rules.
Fix what is listed
Each message names the path, such as $.offers.price, and the line; click it to jump there in the editor.
Features
Syntax first, with a position
Trailing commas, single quotes, comments and unquoted keys are reported with line, column and a plain explanation.
schema.org vocabulary 30.1
Unknown types and properties with "did you mean" hints for typos such as Prodcut, properties on the wrong type, and text where a URL, date, number or value such as InStock is expected.
Google rich result requirements
For products, reviews, articles, breadcrumbs, events, local businesses, organizations, recipes, apps, videos and profile pages: missing required properties are errors, recommended ones warnings.
Retired features said plainly
FAQ markup is valid schema.org but Google stopped showing FAQ rich results on 7 May 2026; How-to rich results were removed in 2023. The report says so instead of promising stars.
Batch check, nothing uploaded
Check many files in one go with a summary table and an item tree; nothing leaves your browser.
Limits & privacy
Files can be up to 10 MB each; a batch can hold 50 files and 50 MB in total.
Contexts other than schema.org are not downloaded, so their terms are listed as not checked. JavaScript is not executed – markup inserted by scripts is only visible in Google’s tools. Google’s requirements were checked on 2026-10-23; meeting them makes a page eligible, not guaranteed a rich result.
The schema.org vocabulary (version 30.1) is © the schema.org sponsors, used under CC BY-SA 3.0 – see licenses. Your markup is never uploaded; see the privacy page.
FAQ
What is the difference between this and Google's Rich Results Test?
The Rich Results Test fetches your live page and renders JavaScript. This validator checks the markup you paste, offline – useful before a page is public.
Why does it say a property is not expected on my type?
schema.org lists each property for certain types. Elsewhere it is usually ignored; the message names the types it belongs to.
Can I validate a page by URL?
Only when the site allows cross-origin requests (CORS). Otherwise open view-source: in your browser, copy the HTML and paste it here.
Does it check microdata and RDFa too?
Yes. itemscope/itemprop and RDFa Lite items are checked with the same rules; positions point to the HTML elements.
Why is my FAQ markup not eligible?
Google stopped showing FAQ rich results on 7 May 2026. The markup is still valid schema.org.