Paste any JSON-LD schema and instantly validate syntax, detect schema types, audit required vs recommended fields, and see which Google rich result features your markup qualifies for. Errors vs warnings clearly separated.
Paste any JSON-LD structured data into the editor — a complete script tag, the raw JSON object, or multiple schema blocks from a page. The tool accepts any valid or invalid JSON-LD and processes it immediately when you click Validate.
Errors are issues that block rich results entirely — missing required properties, invalid JSON syntax, wrong data types. Warnings are quality gaps that reduce result richness but do not block eligibility. Fix all errors first, then address warnings for maximum rich result quality.
The Rich Results panel shows which Google search features your schema qualifies for based on the type detected and properties present. Use the Test in Google button to confirm with Google's official Rich Results Test tool.
Errors are critical issues that prevent rich results entirely. Examples: missing @context, missing @type, missing required properties (like headline for Article or name for Product), invalid JSON syntax (missing commas, unclosed brackets). Warnings are quality issues — missing recommended properties that would improve the result but are not strictly required. Fix all errors before worrying about warnings.
This tool validates JSON-LD syntax and Schema.org compliance against published specifications. Google's Rich Results Test additionally checks that schema content matches visible page content, validates that images meet specific dimension requirements, and applies additional Google-specific policies. Always test with both tools — use this for development and Google's test for pre-launch confirmation.
The number one issue is invalid JSON syntax — specifically a trailing comma after the last property in an object or array. JSON (unlike JavaScript) does not allow trailing commas. Other common errors: unescaped quotes inside string values, mismatched brackets or braces, missing @context property, and using relative URLs where absolute URLs are required.
The @context property declares the vocabulary being used. Without it, JSON-LD parsers cannot interpret the property names. It must always be "https://schema.org" (not "http://") for Google to process the schema. It must appear in every root schema object, but child objects that are nested inside a parent do not need their own @context.
This tool runs entirely in your browser — no data is sent to any server. Your JSON-LD is validated client-side using JavaScript. This makes it safe to test schema from staging environments, internal pages, or draft content that should not be submitted to external services.
Validate schema after any content management system update, after installing or updating SEO plugins, after site migrations, after adding new page templates, and after any developer changes to head sections. Schema errors are silent — they do not cause visible page errors, making them easy to miss without regular auditing.
