S SCHEMA.BIZ

Schema Markup Validator

Paste your JSON-LD structured data to validate it against schema.org and Google's rich result requirements. Get detailed error explanations and fix suggestions.

Paste your JSON-LD structured data below. You can include the <script> wrapper or just the JSON.

Supports JSON-LD (with or without <script> tags)

Free Schema Markup Validator & Tester

Creating structured data is only half the battle — if your JSON-LD markup contains errors, missing properties, or incorrect value types, search engines will either ignore it entirely or fail to generate the rich results you're aiming for. Our validator catches these issues before they reach Google, saving you the frustration of deploying broken markup.

This tool parses your JSON-LD markup, checks it against both the schema.org specification and Google's stricter rich result requirements, and gives you actionable feedback with code-level fix suggestions. Every check runs entirely in your browser — your code is never sent to any server.

What This Validator Checks

The validation engine runs three layers of checks on your structured data:

  • JSON syntax validation. Before anything else, the tool confirms your JSON is well-formed. Mismatched brackets, missing commas, unquoted property names, and trailing commas are the most common issues. The error message pinpoints the approximate location of the syntax problem.
  • Schema.org compliance. The validator checks that your declared @type is a recognized schema.org type, that the properties you've used are valid for that type, and that property values match the expected types (Text, URL, Date, Number, or nested objects). Missing required and recommended properties are flagged separately.
  • Google rich result requirements. Google's requirements are stricter than schema.org's baseline. For example, an Article technically only requires a headline for schema.org, but Google won't generate an Article rich result without also having an image, datePublished, and author. The validator checks these Google-specific rules and tells you exactly which rich result types your markup qualifies for.

Common Schema Markup Errors

After validating thousands of schemas, these are the errors we see most often:

  • Missing @context. Every top-level JSON-LD object needs "@context": "https://schema.org". Without it, search engines don't know what vocabulary you're using.
  • Incorrect property nesting. Properties like offers, author, and address require properly typed nested objects. A common mistake is putting the price directly on the Product instead of inside an Offer object.
  • Wrong date formats. Schema.org expects ISO 8601 dates like 2024-03-15 or 2024-03-15T09:00:00-05:00. Formats like "March 15, 2024" or "15/03/2024" will be rejected.
  • Missing required fields for rich results. Your schema might be valid per schema.org but still not qualify for Google's rich results. For example, a Product without an Offer containing price and priceCurrency won't get a product snippet.
  • Using http instead of https for schema.org URLs. While both work, Google recommends the https version. Availability values like InStock must use the full URL format: https://schema.org/InStock.

How This Compares to Google's Rich Results Test

Google's Rich Results Test is the authoritative tool for checking whether Google will generate rich results from your markup. However, our validator complements it in several ways:

  • Works offline and instantly. Our tool runs entirely in your browser with zero network requests. There's no rate limiting, no queuing, and no waiting for Google's servers to process your code.
  • More detailed explanations. Google's tool tells you what's wrong but often lacks context about why a property matters or how to fix it. Our validator explains the reasoning behind each check and provides copy-paste code suggestions.
  • Privacy. Your structured data never leaves your machine. If you're working with client schemas, proprietary product data, or pre-launch content, nothing is sent to an external service.
  • Development workflow. For rapid iteration during development, paste and validate instantly without switching tabs or waiting for Google's API. Then use Google's tool as a final verification before deployment.

We recommend using both tools: ours for rapid development and detailed explanations, and Google's Rich Results Test for final verification before going live.

Using the Validator

  1. Paste your JSON-LD code into the input area. You can include the <script> wrapper tags or just the raw JSON — the tool handles both.
  2. Click "Validate" to run the checks. Results appear immediately below the input area.
  3. Review the summary showing total errors, warnings, and passed checks at a glance.
  4. Check rich result eligibility to see which Google features your markup qualifies for and what's missing if it doesn't.
  5. Expand individual issues for detailed explanations, suggested fixes with example code, and links to the relevant documentation.
  6. Use the comparison view to see a side-by-side diff of your code versus the suggested corrections.
  7. Fix issues in the Generator — click "Fix in Generator" to load your schema into our JSON-LD Generator where you can edit it visually and re-export corrected markup.

Related Tools

Need to create structured data from scratch? Use our JSON-LD Schema Markup Generator to build valid markup with a visual form — no coding required. For learning about structured data concepts and best practices, visit the Learning Hub.