Validators · 100% free

Schema.org JSON-LD Validator

Paste any JSON-LD block and validate structure, required fields and common errors across all schema.org types.

Google Bing AI search
What this catches: JSON parse errors, missing @context and @type, malformed nested objects, URL-shaped values without schemes. For schema-type-specific required-field validation (Product, Article, Recipe, etc.) also run through Google's Rich Results Test.

About this tool

Broader than our Product Schema Validator, accepts any schema.org @type and flags JSON parse errors, missing @context, undefined types, malformed nested objects, and other common issues that prevent rich results from triggering.

Structural vs eligibility validation

This validator catches structural problems — bad JSON, missing @context/@type, malformed nested objects, URL-shaped values without schemes. It does not check whether your schema is eligible for a specific rich result (e.g. Product, Recipe, JobPosting) — for that, run it through Google's Rich Results Test after it passes here.

For Product-specific validation

Use our Product Schema Validator for Google Merchant Listings eligibility, or our Product Schema for AI Agents Validator for the extended shipping + return policy fields agents need.

Frequently asked questions

Does this replace Google's Rich Results Test? +

No, it complements it. This validator catches structural issues (bad JSON, missing @context/@type, malformed nested objects) that prevent any rich result from triggering. Google's Rich Results Test checks rich-result-specific eligibility per type (Product, Recipe, Article). Run both.

What does 'URL-shaped value missing scheme' mean? +

A field like `url: 'example.com/page'` is a URL without http:// or https:// prefix. Google requires absolute URLs. Either add the scheme or use a relative path without 'example.com'.

Why must @context be schema.org? +

@context defines the vocabulary the JSON-LD uses. Google reads only schema.org-defined types. Using a different @context (e.g. your own vocabulary) means none of the markup translates to SEO rich results.

Can I have multiple JSON-LD blocks on one page? +

Yes, totally fine. Common pattern: one Organization block sitewide, plus per-page Product/Article/BreadcrumbList blocks. Google merges them. Some implementations wrap them in a single @graph; either approach validates.

More free tools

See all tools →
Free forever · No card

Why wait? Try it free today.

Stop managing feeds manually. Start optimising with AI in 30 seconds.

  • 100% free forever, no credit card required
  • 1 brand, 1 feed, 100,000 products per feed
  • Full AI Product Optimisation, Rule Engine, and 200+ channel exports
  • Pay only for AI credits when you need them