How to use the Schema Markup Validator
- Choose Fetch URL and enter a page address, or switch to Paste code to test a snippet before publishing.
- Click Validate (or press Ctrl+Enter).
- Review each entity card: errors block rich results, warnings are recommended properties that can improve them.
- Fix the markup — or build it from scratch with the Schema Markup Generator — and confirm in Google’s Rich Results Test.
What is a schema markup validator?
Schema markup (structured data) is machine-readable information about a page — that it describes a product with a price, an article with an author, or a business with an address — written with the schema.org vocabulary. A validator parses that markup, flags syntax errors and checks whether each entity contains the properties search engines need to show rich results such as product stars, breadcrumbs or event dates.
What this validator checks
- Syntax: every
<script type="application/ld+json">block is parsed separately, so one broken block (a trailing comma, an unescaped quote) is pinpointed without hiding the others. - Formats: JSON-LD (including
@graph), Microdata (itemscope/itemprop) and RDFa detection. - Required and recommended properties for around 30 common types — Article, Product, Offer, Organization, LocalBusiness, BreadcrumbList, FAQPage, Event, Recipe, VideoObject, JobPosting, Review and more — based on Google’s rich result documentation.
- Value sanity: ISO 8601 dates, numeric prices and absolute URLs for
url,imageandlogo. - Nested entities such as an Offer inside a Product or a PostalAddress inside a LocalBusiness are validated too.
Errors vs. warnings
An error means a property Google requires for that rich result is missing or invalid — the page is not eligible for that feature until it’s fixed. A warning is a recommended property: the markup is valid without it, but adding it gives search engines more to work with and can make the result richer.
Which validator should I use?
| Tool | Best for |
|---|---|
| This validator | Fast checks of live URLs or pasted snippets, readable per-entity reports, nested issues |
| Google Rich Results Test | Final confirmation of Google eligibility, including JavaScript-rendered markup |
| Schema.org Validator | Checking vocabulary correctness for any type, not only Google features |
Common structured data mistakes
- Marking up content that isn’t visible on the page — Google treats this as spammy structured data.
- Dates in local formats such as
25/10/2026instead of2026-10-25. - Prices with currency symbols (
"€89") instead of a number pluspriceCurrency. - Relative image URLs, or several conflicting Organization blocks injected by different plugins.
Tools that pair well with the Schema Markup Validator
- SEO Checker & Site Audit — Paste a URL to run up to 70 on-page SEO checks in seconds.
- Meta Tag Checker — See exactly how Google is likely to display your page: title and description measured in pixels, desktop and mobile previews, and every meta tag in the <head>.
- Open Graph Checker — Preview how your link will look when shared on Facebook, LinkedIn, X and Slack.
- JSON Formatter — Paste JSON to pretty-print, minify or validate it.
Frequently asked questions
Is this the same as Google’s Rich Results Test?
No. It applies Google’s documented required and recommended properties for common types and gives a quick, readable report, but only Google’s Rich Results Test can confirm eligibility — use it as the final check before you ship.
Does valid schema guarantee rich results?
No. Valid markup makes a page eligible, but Google decides whether to show a rich result based on content quality, relevance and its own policies.
Should I use JSON-LD or Microdata?
Google recommends JSON-LD because it sits in one script block, separate from your HTML, and is easier to maintain. Microdata is still supported and this tool validates both.
Why don’t my FAQ or HowTo rich results show anymore?
In 2023 Google limited FAQ rich results to well-known, authoritative government and health websites and stopped showing HowTo rich results. The markup is still valid, but most sites won’t get those features.
Does it find schema added by JavaScript or Google Tag Manager?
When fetching a URL it reads the HTML returned by the server, so markup injected later by JavaScript is not seen. Paste the rendered markup into the code tab, or use Google’s Rich Results Test, which renders JavaScript.