A schema markup validator checks the structured data on your page for syntax errors and missing properties. This one reads every JSON-LD block, lists each type and tests it against Google's rich result rules. Developers, SEOs and site owners use it to confirm markup before and after publishing.
- How to use the schema markup validator
- What this schema checker tests
- Required vs recommended properties
- FAQ and HowTo rich results have changed
- Common schema markup mistakes
- Validator, rich results test and structured data testing tool
- FAQ
- Related tools
How to use the schema markup validator
- Choose a mode. Paste your JSON-LD into the box, or enter the URL of a live page and let the tool pull the markup from it.
- Press validate. The tool finds every
<script type="application/ld+json">block, including blocks that use@graphto hold several entities. - Fix syntax errors first. If the JSON does not parse, you get the problem described in plain words. Nothing else can be checked until it parses.
- Read the type list. Every entity found is listed with its schema.org type, and each type is checked against Google's rich result properties.
- Work through the findings. Missing required properties block a rich result. Missing recommended properties are optional but worth adding when you have the data.
- Edit your markup, paste it again and repeat until the page shows no errors.
The validator reads JSON-LD only. If your page uses Microdata or RDFa, convert it to JSON-LD or test it with a tool that supports those formats. Google recommends JSON-LD.
What this schema checker tests
Catches trailing commas, missing quotes and broken brackets, which stop Google from reading the block at all.
Pages often carry several JSON-LD scripts from a theme, an SEO plugin and a review app. All of them are extracted and checked, and @graph arrays are unpacked entity by entity.
Lists each type it finds, so you can see at a glance whether your plugin really output the Product or LocalBusiness you expected.
Flags properties Google lists as required for a rich result on that type. Without them the page is not eligible.
Shows the extra fields that make a result richer, such as ratings, images and dates. They are warnings, not errors.
Article, BlogPosting, NewsArticle, Product with Offer, AggregateRating and Review, LocalBusiness and subtypes, Organization, BreadcrumbList, FAQPage, Event, Recipe, VideoObject, JobPosting, SoftwareApplication, Person and WebSite.
Required vs recommended properties
Google splits properties into two groups on each structured data feature page. Required properties must be present for the page to qualify for that rich result. Recommended properties are not mandatory, but adding them gives Google more to work with. A page can pass with warnings and still be eligible.
| Type | Properties Google commonly requires |
|---|---|
| Product snippet | name, plus one of offers, review or aggregateRating |
| LocalBusiness | name and address |
| BreadcrumbList | itemListElement with position and name |
| Event | name, startDate and location |
| Recipe | name and image |
| VideoObject | name, thumbnailUrl and uploadDate |
| JobPosting | title, description, datePosted, hiringOrganization and a location |
Article markup is different. Google lists no strictly required properties for it, only recommended ones such as headline, image, datePublished, dateModified and author. Fill them all in anyway. Check the current feature page for your type, because Google updates these lists.
FAQ and HowTo rich results have changed
Two types trip people up. In August 2023 Google limited FAQ rich results to well-known, authoritative government and health websites. For most other sites the FAQ markup is still valid schema.org, but Google will not show the expandable answers in search. HowTo rich results were removed from Search entirely.
The validator still reads both types and tells you when a type no longer produces a Google rich result. That way you do not spend a week fixing markup that has no visible payoff. Valid FAQ markup is harmless, and other search engines and AI systems can still read it. Just do not expect extra SERP real estate from it.
Common schema markup mistakes
The same problems come up again and again.
- Markup that does not match the page. Google's structured data policies say not to mark up content that readers cannot see. If your JSON-LD lists a 4.8 rating and no rating appears on the page, expect a manual action risk.
- Duplicate entities from plugins. A theme and an SEO plugin each output an Organization or WebSite block. Two conflicting versions confuse parsers. Keep one source.
- Wrong value formats. Dates should be ISO 8601, prices should be plain numbers with a separate
priceCurrency, and URLs should be absolute. - Empty strings and placeholders. An empty
imageorpricefield adds noise and can trigger errors. Remove fields you cannot fill. - Self-serving reviews. Review markup on your own business page about your own business is not eligible for review snippets.
A clean validation result does not guarantee a rich result. Google decides case by case, based on quality and relevance. Validation tells you the markup is eligible, not that it will be shown.
Validator, rich results test and structured data testing tool
People search for this job under several names: schema checker, JSON-LD validator, rich results test, and the old structured data testing tool, which Google retired in favor of newer tests. They overlap, but they answer different questions.
| Check | What it answers |
|---|---|
| Syntax and schema.org validity | Is the JSON-LD well formed, and are the types and properties real schema.org terms? |
| Google rich result eligibility | Does this page carry the properties Google asks for on this feature? |
| Live indexing status | Has Google crawled and understood the page? Use Search Console for this. |
This tool covers the first two for JSON-LD. Use Search Console's enhancement reports afterwards to see how Google reads your live pages over time. Rank Ray's Schema Markup Generator builds clean markup for the common types, and this validator is the quickest way to confirm it before you publish.
Frequently asked questions
What is a schema markup validator?
A schema markup validator reads the structured data on a page and checks it for errors. It confirms the JSON-LD parses, lists the schema.org types it found, and compares each type with the required and recommended properties Google documents for rich results. Fix errors first, then warnings.
How do I test JSON-LD for errors?
Paste the JSON-LD into the validator, or enter the page URL. Syntax errors appear first, such as a missing comma or quote. After that the tool lists each type and the properties it is missing. Correct the markup, paste it again, and repeat until no errors remain.
Is a schema checker the same as Google's Rich Results Test?
No. A schema checker verifies syntax and property rules on the markup you supply. Google's Rich Results Test also shows whether Google can render the page and which rich result it may qualify for. Use both: the checker for fast iteration, Google's test as a final confirmation before launch.
Why does my valid schema not show rich results?
Valid markup only makes a page eligible. Google also weighs content quality, relevance and its own feature policies. FAQ results, for example, are limited to well-known government and health sites. Check that the markup matches visible content, then give Google time to recrawl the page.
Does this tool check Microdata or RDFa?
No. It reads JSON-LD only, including blocks that use @graph. Google supports JSON-LD, Microdata and RDFa, but recommends JSON-LD because it is easier to maintain. If your site uses Microdata, convert it to a JSON-LD block and validate the result.
Should I fix warnings or only errors?
Fix every error, since missing required properties make a page ineligible. Treat warnings as a to-do list. Add recommended properties when you have accurate data, such as an image, date or rating. Never invent values just to clear a warning.