Schema markup validator
Paste JSON-LD or a page's HTML, or fetch a public URL. Every block is parsed and checked against schema.org basics and the properties Google requires for its rich results, right in your browser.
Or load a broken example to see what each check catches:
Results appear here. Nothing leaves your browser unless you fetch a URL or ask for an AI review.
What the validator checks
- Syntax: JSON parse errors with line and column, plus hints for trailing commas, curly quotes and single quotes.
- Structure:
@context,@type,@grapharrays and several blocks per page. - Google requirements: required and recommended properties for Article, Breadcrumb, Event, Job posting, Local business, Organization, Product (snippets and merchant listings), Recipe, Review, Software app, Video, Profile page, WebSite, Course list and the retired FAQ and How-to features.
- Formats: ISO 8601 dates and durations, time-zone offsets, ISO 4217 currencies, numeric prices, absolute URLs, rating ranges, and schema.org enumerations like
InStockandEventScheduled.
Fetching reads the raw HTML only. Markup injected by JavaScript (common with tag managers and some SEO plugins) won't appear. Test those pages in Google's Rich Results Test, which renders JavaScript.
Errors, warnings and notes
Errors are missing Google-required properties or values Google can't read. They make the item ineligible for its rich result.
Warnings are recommended properties that are missing, or values that are readable but risky. Search Console shows these as non-critical issues.
Notes are about status and context, such as a retired rich result or a type that has no Google feature.
Validating is not the same as ranking. Google's structured data guidelines say correct markup doesn't guarantee a rich result, and markup that misrepresents a page can lead to a manual action.
Validator questions
How is this different from Google's Rich Results Test?
The Rich Results Test is Google's official eligibility check and renders your page as Googlebot. This validator runs instantly in your browser on snippets or HTML, explains each issue in plain language, and flags recommended properties and format problems. Use both: this one while you write, Google's before you ship.
What happened to the Structured Data Testing Tool?
Google retired its Structured Data Testing Tool in 2021. Its schema.org checks moved to validator.schema.org (the Schema Markup Validator), and Google-specific checks live in the Rich Results Test.
Does it check Microdata and RDFa?
No, only JSON-LD, the format Google recommends. If a page uses Microdata, the validator will report that no JSON-LD blocks were found.
Is my markup sent anywhere?
Validation runs entirely in your browser. Only if you click "Fetch" is the URL requested by our server, and only if you click "AI review" is the markup sent to the AI model to write the explanation.
Why do warnings matter if the markup is valid?
Warnings are Google's recommended properties. Missing them doesn't block eligibility, but adding the ones that apply gives Google more to work with.