SchemaValid
ENDE

Schema Validator

Paste any JSON-LD code and check whether it is valid JSON and valid schema.org markup — instantly, in your browser, free of charge.

Why validate your structured data

A single missing comma, an unclosed bracket, or a forgotten @type can silently break your JSON-LD — search engines will simply ignore the markup instead of showing an error on your site. Validating before you publish catches these mistakes early, so the rich results, Knowledge Panels or AI citations you built the markup for actually have a chance to appear. This tool runs the same two checks that matter most: is the code syntactically valid JSON, and does it contain the @context and @type properties every schema.org type needs to be recognized.

What this tool checks — and what it doesn't

This validator performs two layers of checking. First, JSON syntax: braces, quotes, commas and brackets must all be balanced and correctly placed, exactly what JSON.parse enforces. Second, schema.org completeness at a basic level: the code must have an @context (normally "https://schema.org") and an @type identifying what is being described — either directly on the top-level object (e.g. Organization, Product, Recipe) or, for the common @graph pattern that bundles several entities in one script tag (e.g. an Organization cross-linked with a WebSite), an @type on each entry inside @graph. This tool does not check whether every property required for a specific type's rich results is present — for that deeper, type-specific validation, use Google's Rich Results Test after your syntax and structure are confirmed valid here. Everything runs locally in your browser; your code is never sent anywhere.

Example of valid JSON-LD

A minimal but valid piece of schema.org markup needs at least @context and @type, plus whichever properties matter for that type. A correct Organization example looks like this:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "ACME Corporation",
  "url": "https://www.example.com"
}

Frequently asked questions

Does this replace Google's Rich Results Test?
No. This tool catches JSON syntax errors and confirms the basic @context/@type structure instantly, which is useful while you're writing markup. Google's Rich Results Test goes further and checks whether a specific type has everything needed to actually qualify for rich results — use both together.
What does "valid JSON, but not valid schema.org markup" mean?
It means your code has no syntax errors and JSON.parse succeeds, but the top-level object is missing @context, @type, or both. Those two properties are what tell search engines this JSON is meant to be schema.org structured data in the first place.
Is my pasted code sent to a server?
No. Validation runs entirely in your browser using JSON.parse — nothing you paste is uploaded, stored, or tied to an account. You can safely paste code from unpublished or private pages.
Can @type be more than one value?
Yes. schema.org allows @type to be an array when an item genuinely belongs to multiple types at once. This tool detects both a single string and an array, and lists every detected type when validation succeeds.
My page has multiple JSON-LD script blocks — can I check them all at once?
Paste and check one script block at a time. This tool validates a single top-level JSON-LD object, so for a page with several separate script tags, copy the contents of each one in individually for a clear per-block result.

Related tools