Enter a page URL to auto-detect every schema block, or paste your JSON-LD directly. This schema validator tool supports Article, Product, FAQPage, LocalBusiness, Recipe, Event and 15+ more types.
Something went wrong. Please try again.
Enter a URL or paste JSON-LD above to begin validation.
Enter your page URL for automatic detection, or paste raw JSON-LD schema markup directly into the validator.
The tool detects all JSON-LD, Microdata and RDFa structured data blocks present on the page.
Each schema block is checked against Google's rich result requirements, required fields, value formats, nesting rules.
Get a quality score, prioritised issue list with fixes, then retest after making changes to confirm it's perfect.
Schema markup is code you add to a page that tells search engines what the content actually means. A human reads a page and knows it is a recipe. A search engine reads HTML and sees a heading and a list. Schema names it explicitly. This is a Recipe, this is the cook time, this is the rating. A schema validator reads that code back and checks it is correct.
There are three formats. JSON-LD sits in a script tag and is what Google recommends. Microdata and RDFa are woven into your HTML attributes and are older. This tool reads all three, because plenty of sites still run them.
Schema does not improve rankings on its own. Google is explicit about that in its structured data documentation. What it does is make you eligible for rich results, and help machines understand you.
Written by Chirag Arora, digital marketing consultant with 17+ years of hands-on SEO experience across 500+ projects. He designed this validator and the other 22 free tools on this site. Verify on LinkedIn.
| Tool | The question it answers | Covers | Sign-in |
|---|---|---|---|
| This tool | Is my markup there, and is it structurally sound? | JSON-LD, Microdata, RDFa on any URL | No |
| Schema Markup Validator (validator.schema.org) | Is it valid against the schema.org standard? | Every schema.org type, no Google-specific checks | No |
| Google Rich Results Test | Can Google actually show a rich result for this? | Only the types Google supports for rich results | No |
| Google Search Console | Is it working across my whole site, over time? | Your verified site only | Yes |
| Structured Data Testing Tool | Retired | Google deprecated it and moved it to validator.schema.org | Gone |
These answer different questions, which is why people get confused when one passes and another complains. Google's own advice is to start with the Rich Results Test for rich result eligibility and use the Schema Markup Validator for generic schema.org validation. Use this tool first to see what markup is on the page at all, then chain the others.
Article · NewsArticle · BlogPosting · VideoObject · Recipe · Course · Review
LocalBusiness · Organization · Person · Product · JobPosting · Event
FAQPage · BreadcrumbList · WebSite · SpeakableSpecification · SearchAction
Google's preferred format. Place it in the <head> or <body>, doesn't require touching your HTML content.
Schema markup must match the visible page content exactly. Google will penalise misleading or invisible schema that isn't reflected on the page.
Use @id to create a knowledge graph. Link your Author, Organization and Website schemas for maximum Google trust.
A validator reports two kinds of finding, and they are not equal. An error means a required property is missing or malformed, and it can stop the markup being eligible for a rich result, so fix every error first. A warning flags a recommended property you left out, which still works but leaves value on the table, like skipping the image on a Product. Clear the errors, then decide which warnings are worth the effort for your page type. If you run WordPress, you rarely write this by hand. Plugins such as Yoast SEO and Rank Math output LocalBusiness, Article and FAQ markup for you, and the job then is to paste your live URL here and confirm the plugin produced clean, complete markup rather than assuming it did.
This free schema validator tool works as a schema markup checker for any URL, telling you what is there, what is broken and what is missing. Use it as a schema.org validator online with no account and nothing to install. It handles JSON-LD, Microdata and RDFa. Every error is named with the property it belongs to, and required fields are flagged before a rich result can show. It runs online with no account and nothing to install.
The commonest schema problem I see across 500+ projects is not invalid code. It is markup that is technically perfect and quietly lying. A Product with a price that does not match the page. Review stars marked up for reviews that do not exist. An FAQPage where the questions are not visible to a human. All of it validates cleanly and all of it puts you at risk, because Google checks markup against what the page shows. A validator cannot catch that. Only reading your own page can.
The second commonest is two plugins writing competing markup for the same page, so Google picks one and it is rarely the one you wanted. Run the validator to see everything on the page at once, then remove whichever is the duplicate. Then check how the page itself is built with the free on-page SEO analyzer, and find what it could rank for with the free keyword research tool. The rest are in the free SEO tools hub.
It helps to keep two ideas apart. JSON-LD is the format your markup is written in, Schema.org is the vocabulary of types and properties it uses, and there are two reference checkers for them, Google's Rich Results Test for whether a page qualifies for a Google feature, and the Schema.org Validator for pure vocabulary and syntax. A clean pass is necessary but never a guarantee, Google still weighs content quality and only shows a rich result when the page truly earns it. Most failures come down to a handful of things, a missing required property, a value in the wrong shape such as a price with no currency or a date that is not ISO 8601, or markup that describes something not visible on the page. The quiet danger is a template error, one broken field in a CMS can silently disable rich results across hundreds of pages at once.
The page is fetched from our own server, exactly as a search engine would, then parsed for JSON-LD script blocks, Microdata attributes and RDFa. Everything reported is read straight from your markup, so nothing is guessed. Required and recommended properties are checked against the schema.org vocabulary for each type found. One important limit. This reads the HTML your server returns, so markup injected later by JavaScript will not appear here. That is worth knowing rather than working around, because Google renders JavaScript but AI crawlers generally do not, so schema that only exists after render is invisible to a growing share of the machines reading your site.
Crawl your website and generate a complete, Google-ready XML sitemap instantly.
Launch ToolComplete on-page SEO audit, title tags, meta, headings, keyword density and 50+ factors.
Launch ToolGenerate perfectly optimised title tags, meta descriptions and Open Graph tags.
Launch ToolCommon questions about this free tool, answered clearly.
Schema makes you eligible for rich results, but it does not guarantee them. Google decides based on quality and the schema type. Some types, like FAQ rich results, were retired in 2026, though the markup still helps search and AI understand your page.
Use JSON-LD. Google recommends it and it is the easiest format to add and maintain. It sits in a single script tag instead of being mixed into your HTML.
Yes. Structured data helps AI tools understand your entities, authors and facts, which improves how accurately they describe and cite you. It is one of the clearest signals you can give them.
Google retired it. It was deprecated in favour of the Rich Results Test, and after the SEO community pushed back Google moved the original tool to schema.org, where it now lives as the Schema Markup Validator at validator.schema.org. The split is deliberate. The Rich Results Test checks whether Google can show a rich result, and the Schema Markup Validator checks whether your markup is valid schema.org. If you are still searching for the old tool, those two together are what replaced it.
No, and they answer different questions. This tool reads your page and shows you what markup is on it and whether it is structurally sound, including types Google does not use for rich results. The Rich Results Test only checks the types Google supports and tells you whether a rich result is possible. Markup can be perfectly valid here and still produce no rich result, usually because a required property is missing or the type is not one Google displays.
Not directly, and anyone who tells you otherwise is selling something. Google has said repeatedly that structured data is not a ranking factor. What it does is make you eligible for rich results, which change how your listing looks and can lift click-through, and it helps machines understand what your page is about. That second part matters more every year as AI search grows.
This free tool validates the markup. If you would rather have someone design the schema properly across your whole site, here are a few honest reasons businesses hire me as their SEO and digital marketing consultant in India.
Valid markup that contradicts your visible content is worse than no markup. I check what your schema claims against what the page actually shows, which is the part a validator cannot do for you.
I started as a technical SEO trainee, not in a management seat, and I still write the JSON-LD myself. You get direct expertise, not a spec handed to someone else to implement.
The schema validator you just used, I designed it, along with 22 other free SEO tools on this site. It is a direct look at how I audit markup before you ever become a client.
Two plugins writing competing schema for the same page is the commonest mess I inherit. Google picks one and it is rarely the one you wanted. I find the duplicates and cut them.
Messages get a reply within 24 hours on business days, and WhatsApp is the fastest way to reach me for anything urgent. You are not waiting in a support queue.
AI crawlers do not run JavaScript, so schema injected after render is invisible to them. I make sure your markup exists in the HTML your server sends, not just in the browser.
"Our product rich results vanished overnight and nobody knew why. Chirag found two plugins writing competing Product schema. Removed one, stars were back within a fortnight."
"He found our FAQ schema was marked up for questions that were not actually on the page. That is a manual action waiting to happen. His 17+ years of experience really shows."
"As a small business, we started with Chirag's free schema tool, then hired him. Ranked Page 1 for our main terms within 3 months. Practical, no fluff, real value."
Featured on leading media platforms. Watch interviews, expert commentary and digital marketing insights covered by top news channels and podcasts.
CMD Club Meet 2025 at Club Capri, Gurgaon : A Brief of ClipsTrust
YouTube · Business Meet
How to Build Customer 🔥Trust 🔥 - Biggest Challenges Today
Eventra vlogs
Digital Marketing Beginner to Advanced Journey | Podcast b/w Chirag Arora & Pankaj
YouTube · Podcast Episode