Quick answer
A schema markup validator reads the structured data on a page, usually JSON-LD, and checks it against the fields search engines require. Enter a URL or paste your JSON-LD above to see every schema type, any syntax errors and the missing required properties that stop a page from getting rich results.
Enter a page address, or paste the JSON-LD you are about to publish. The validator finds every structured data block, lists the schema types inside them, and checks the types that can earn rich results in Google, such as Product, Article, Recipe, Event and FAQPage, against the properties Google requires and recommends. It is free, needs no account and allows 30 checks an hour.
What the schema markup validator checks
Structured data is code that describes a page in a fixed vocabulary from schema.org: this page is a product, it costs this much, it has these reviews. Search engines use it to understand the page and, for some types, to show rich results such as prices, ratings or event dates in the listing.
The validator reports three kinds of finding:
- Syntax errors. A missing comma or quote makes the whole JSON-LD block unreadable, and Google ignores all of it. These are the first thing to fix.
- Missing required properties. Each rich result type has fields it can't do without. A Product needs a name and at least one of offers, review or aggregateRating; an Event needs a name, start date and location. Without them, the page isn't eligible for that rich result.
- Missing recommended properties. These don't block eligibility, but they make the result richer: an image, a brand, a price valid until date. They are shown as suggestions, not errors.
It also checks the details that most often trip people up: dates must be in ISO 8601 format (2026-10-22), and URL fields must be absolute addresses that start with https://.
How to read the results
A green result means the markup is valid and every rich result type on the page has its required fields. Amber means the markup is valid but either none of it is a rich result type, or recommended fields are missing. Red means something stops Google from using it: broken JSON or a required field that isn't there.
A valid result doesn't guarantee a rich result. Google decides case by case, based on the page's quality and the search. FAQ rich results, for example, are now shown mainly for government and health sites. Valid markup makes a page eligible; it doesn't make it certain. Our guide to schema markup for AI search covers which types are worth the effort today.
Common errors and how to fix them
Invalid JSON. Usually a trailing comma after the last item in a list, straight quotes replaced by curly ones by a word processor, or two blocks pasted together without a wrapping array. Paste the block into the validator after each change until the syntax error disappears.
Product without offers, review or rating. Add an offers object with price, priceCurrency and availability. If the product isn't for sale online, use review or aggregateRating instead, but only with reviews that are visible on the page.
Relative URLs. Fields such as image, url and logo must be full addresses. /images/shoe.jpg should be https://example.com/images/shoe.jpg.
Dates in the wrong format. 22/10/2026 or October 22 won't be read. Use 2026-10-22, or a full timestamp such as 2026-10-22T09:00:00+00:00.
Markup that doesn't match the page. Structured data has to describe what visitors can see. Marking up reviews, prices or questions that aren't on the page breaks Google's guidelines and can lead to a manual action.
Microdata and RDFa
Most sites use JSON-LD, which Google recommends because it sits in one block separate from the page's HTML. If the validator finds itemscope or typeof attributes, the page also uses microdata or RDFa. Those formats still work, but this tool checks JSON-LD only, so check them in Google's Rich Results Test as well.
Beyond one page
Structured data errors rarely affect a single page: they come from a template, so every product or article page shares them. Seotific's full audit checks structured data on every page it crawls, groups the errors by cause, and ranks them with the rest of the page's issues. Its schema generator writes valid JSON-LD for 12 types when you need to start from scratch.
Check your own page
Seotific audits a URL against the keyword it should rank for and lists the fixes in order of impact. Free plan, no card.
Run a free auditFrequently asked questions
What is a schema markup validator?
A schema markup validator is a tool that reads the structured data on a page, or code you paste in, and checks whether it is valid JSON-LD and whether each schema type includes the properties search engines require for rich results.
Is schema markup a ranking factor?
Not directly. Structured data helps search engines understand a page and can make it eligible for rich results, which often earn more clicks. Google has said it doesn't use structured data as a general ranking boost.
Why is my valid markup not showing rich results?
Eligibility isn't a guarantee. Google chooses when to show rich results based on the search, the page's quality and its own policies. Some types, such as FAQ and HowTo, are now shown for far fewer sites than before.
Can I validate JSON-LD before publishing it?
Yes. Paste the JSON-LD, with or without its script tag, into the box above and run the check. It is validated the same way as markup read from a live page.