Schema Markup Validator: Free JSON-LD Structured Data Testing Tool

This schema markup validator checks your JSON-LD structured data against three layers of rules: JSON syntax, schema.org vocabulary, and Google Rich Results requirements. Paste your code above and get instant validation results with clear explanations and fix suggestions.

Unlike tools that only check syntax, this validator tells you why a property is required, what Google expects for rich result eligibility, and how to fix each issue — with ready-to-use code examples.

How to Use This Schema Validator

1. Paste your JSON-LD code into the editor on the left. You can also click Paste to read from your clipboard, or click Example to load a sample Article schema.
2. Review results instantly. Validation runs in real time as you type. The right panel shows detected schema types, a property checklist, and any errors or warnings.
3. Click any error or warning to expand it. You will see a description of the problem, a code example showing the fix, and a link to the relevant Google documentation.

There is no submit button and no server processing. Everything runs locally in your browser, so your code never leaves your machine.

What This Tool Checks

The validator performs three levels of checks on your structured data. Specifically, each level builds on the previous one.

1. JSON Syntax Validation

First, the tool parses your input as JSON. If the syntax is invalid — trailing commas, missing brackets, unquoted keys — you will see a specific error with the line number, a description of the problem, and a suggestion for fixing it. Schema validation cannot proceed until the JSON is well-formed.

2. Schema.org Vocabulary Checks

Next, the validator confirms that your @context points to schema.org and that your @type is a recognized type. It also checks that nested objects (such as author, offers, or address) have valid @type properties and correct structure.

3. Google Rich Results Requirements

Finally, the tool checks every property against Google's structured data documentation. It distinguishes between:

• Required properties (red errors) — Google will not generate rich results without these.
• Recommended properties (yellow warnings) — Adding these improves the quality and likelihood of rich results.

In addition, the validator checks value formats: ISO 8601 dates, valid URLs, correct enum values, and ISO 8601 durations. As a result, you catch formatting issues that other validators miss.

Supported Schema Types

This schema markup validator currently supports 14 schema types that are eligible for Google Rich Results. These cover the majority of structured data used by websites.

Subtypes are also supported. For example, NewsArticle and BlogPosting validate as Article, while Restaurant validates as LocalBusiness.

Common Schema Markup Errors and How to Fix Them

After validating thousands of JSON-LD snippets, these are the errors that appear most often. Fortunately, most of them are easy to fix once you know what to look for.

Missing @context

Every JSON-LD block must begin with "@context": "https://schema.org". Without it, search engines cannot interpret the structured data. In fact, this is the most fundamental requirement of any JSON-LD implementation.

{
  "@context": "https://schema.org",
  "@type": "Article",
  ...
}

Missing Required Properties

Google requires specific properties for each schema type. For example, an Article requires headline and image. Similarly, a Product requires name plus at least one of offers, review, or aggregateRating. If these are absent, Google will not generate rich results for your page.

Invalid Date Formats

Dates must follow ISO 8601 format. For instance, common mistakes include using "February 24, 2026" or "24/02/2026" instead of the correct "2026-02-24". Similarly, durations should use the ISO format: "PT1H30M" for 1 hour and 30 minutes, not "90 minutes".

Trailing Commas in JSON

JSON does not allow a comma after the last property in an object or array. This is one of the most common syntax errors, especially for developers who write JavaScript. Consequently, {"name": "Test",} will fail to parse.

Missing @type in Nested Objects

Nested objects like author, publisher, and offers need their own @type. For example, an author should be {"@type": "Person", "name": "..."}, not just {"name": "..."}. While some search engines may still process incomplete nested objects, adding @type ensures compatibility across all platforms.

Relative URLs Instead of Absolute

URLs in structured data should be fully qualified. Use "https://example.com/image.jpg" instead of "/image.jpg". Google explicitly requires absolute URLs for properties like image, url, and logo.

JSON-LD Best Practices for Structured Data

Following these best practices will help you get the most out of your schema markup implementation. As a result, you will avoid common pitfalls and maximize your chances of earning rich results.

• Use JSON-LD format. Google recommends JSON-LD over Microdata and RDFa. It is easier to implement and maintain because the structured data lives in a separate <script> block rather than being mixed into HTML attributes.
• Place JSON-LD in the <head>. Although Google can read JSON-LD anywhere in the HTML, placing it in the <head> ensures it is parsed early and avoids issues with JavaScript-rendered content.
• Include all recommended properties. Required properties are the minimum for eligibility. However, adding recommended properties improves the richness and likelihood of your result appearing. More complete markup generally outperforms the bare minimum.
• Use specific types over generic ones. If you run a restaurant, use Restaurant instead of the generic LocalBusiness. More specific types provide richer signals to search engines.
• Validate before and after deployment. Test your markup during development, then re-check the live page. JavaScript rendering, CMS modifications, and caching can alter what search engines actually see.
• Combine multiple schema types per page. A typical page might need Article + BreadcrumbList + Organization. Use an @graph array to include multiple types cleanly. This validator supports @graph out of the box.
• Keep structured data consistent with visible content. Google penalizes markup that contradicts what users see on the page. The name, description, and other properties must match the actual page content.

This Tool vs. Google Rich Results Test

Both tools validate structured data, but they serve different purposes. Therefore, understanding when to use each one will save you time.

Recommended workflow: Use this schema markup validator during development to write and debug your JSON-LD code with instant feedback. Then use the Google Rich Results Test on the live page to verify how Googlebot renders and interprets your markup.

Why Schema Markup Matters for SEO

Schema markup helps search engines understand the content and context of your pages. Without it, Google has to infer what your page is about from text alone. With structured data, you are telling Google exactly what entities exist on the page and how they relate to each other.

The practical benefits are significant. Pages with valid structured data can earn rich results — enhanced search listings with star ratings, prices, FAQ dropdowns, recipe cards, event dates, and more. These rich results typically achieve higher click-through rates than standard blue links.

Moreover, structured data is becoming increasingly important for AI-driven search. As search engines generate AI summaries and answer boxes, they rely more heavily on structured data to extract and verify facts. Consequently, pages with comprehensive, accurate schema markup are more likely to be cited and featured.

That said, schema markup is not a ranking factor by itself. It does not directly boost your position in search results. Instead, it qualifies your pages for enhanced presentation that can indirectly improve performance through higher CTR and engagement. For a deeper understanding of how search engines process your site, see our guide on crawl budget and how it affects your site.

Frequently Asked Questions