Schema Markup Validator
Paste your JSON-LD to validate it instantly, or enter a URL to extract and validate all schema blocks on the page. Catches syntax errors, missing required fields, and Schema.org compliance issues.
How to Use the Schema Markup Validator
The tool has two modes. Use Validate JSON-LD to paste your schema markup directly and get instant feedback. Use Extract from URL to fetch any live page and automatically pull out all <script type="application/ld+json"> blocks, then validate each one.
What This Validator Checks
Parses the input as JSON. Any syntax error (missing comma, unmatched bracket, unquoted key) is reported immediately.
Confirms the required "@context" (should be "https://schema.org") and "@type" fields are present.
For known types (Article, Product, FAQPage, LocalBusiness, Event, etc.), checks that all required fields exist according to Schema.org.
Verifies each mainEntity item is a Question with a "name" and an acceptedAnswer with a "text" value.
Warns if Product offers are missing "price" or "priceCurrency" — both are required for Google rich results.
Lists all detected properties so you can confirm every field you intended is present in the output.
Supported Schema Types
For any other schema type, the validator still checks JSON syntax, @context, and @type — it just will not check type-specific required fields.
Common Schema Mistakes to Avoid
- •Using http:// instead of https:// in @context — always use "https://schema.org".
- •Trailing commas in JSON — valid in JavaScript but not in JSON; they cause parse errors.
- •Nesting FAQPage inside another schema — it should be a top-level block.
- •Marking up content that is not visible on the page — Google may penalize this as spam.
- •Forgetting priceCurrency on Product offers — Google requires it for rich results.
- •Placing the schema script tag inside a JavaScript module with defer/async — Google may not execute it.
Frequently Asked Questions
What is schema markup and why does it matter?
Schema markup is structured data written in JSON-LD (or other formats) that you add to your pages to tell search engines what your content means — not just what it says. For example, a Product schema tells Google that the page is about a product with a specific price and availability, rather than just a page with those words on it. Properly implemented schema enables rich results in Google SERPs, such as star ratings, FAQ dropdowns, product prices, event dates, and How-To steps — all of which significantly improve click-through rates.
What's the difference between JSON-LD, Microdata, and RDFa?
All three are structured data formats that implement Schema.org vocabulary, but they differ in how they embed the data. Microdata and RDFa are woven directly into your HTML tags as attributes, which makes them harder to maintain and error-prone. JSON-LD sits in a separate <script type="application/ld+json"> tag in your <head> or <body>, completely decoupled from the visible HTML. Google officially recommends JSON-LD because it is the easiest to implement, maintain, and update without touching your page's visual markup.
My schema validates here but Google still shows errors in Search Console — why?
This tool checks two things: valid JSON syntax and the presence of required Schema.org fields. Google's rich result checks go further — they also verify that the schema accurately reflects the visible page content. For example, a Product schema with a price that does not appear anywhere on the rendered page will fail Google's quality checks even if the markup is technically valid. Other common reasons for Search Console errors include: the schema is in a section Google can not crawl, JavaScript rendering issues prevent the script tag from being seen, or the structured data is on a noindexed page.
What schema types get rich results in Google?
Google officially supports rich results for the following schema types (among others): FAQPage (FAQ dropdowns in SERPs), HowTo (step-by-step guides), Product (prices, availability, ratings), Recipe (ingredients, cook time, calories), Review and AggregateRating, Event (date, location, ticket links), Article and NewsArticle, LocalBusiness (opening hours, address), JobPosting, VideoObject, and Course. Always check Google's rich results documentation for the latest supported types, as the list evolves and some types are restricted to certain sites.
Related Tools
Need a Full Technical SEO Audit?
Our SEO experts can implement and validate schema across your entire site, fix structured data errors, and build a roadmap for earning rich results in Google.
Get a Free SEO Audit