JSON-LD Validator & Generator
Validate JSON-LD structured data against schema.org rules. Checks syntax, required fields per type (Article, Product, FAQ, Breadcrumb, HowTo, Organization, and more), and renders a rich-result preview. Includes a generator for common types.
Waiting for input
How to use
- 1 Paste your JSON-LD, or pick a type in the Generator tab and fill the form.
- 2 Read the syntax errors, missing-field warnings, and the rich-result preview.
- 3 Copy the validated JSON-LD script and embed it in your page head.
Related tools
About this tool
JSON-LD is Google's recommended format for structured data. By embedding a small JSON payload you tell search engines what a page actually is — a product, a recipe, a how-to, an FAQ — so the page can earn rich-result treatment in search (star ratings, prices, breadcrumbs, FAQ accordions). Malformed JSON-LD silently disables rich results and, in extreme cases, can trigger a manual action.
This validator checks two layers: the JSON syntax itself (parse errors, missing quotes, trailing commas) and the schema.org shape (@context, @type, and per-type required fields — e.g. Article needs headline/author/datePublished, Product needs name plus offers or aggregateRating, FAQPage.mainEntity must be an array of Question objects). Once validation passes, the tool renders a rough preview of how the rich result may appear.
If you don't want to hand-write JSON-LD, switch to the Generator tab, pick a type, fill the form, and get a compliant snippet ready to paste into your page head.
Frequently asked questions
How is this different from Google's official Rich Results Test? +
Google's tool (search.google.com/test/rich-results) requires a live URL and only validates the limited set of types Google itself supports. This tool runs entirely in your browser — you can paste a snippet without deploying — covers a wider range of schema.org types, and previews the rich result locally. The recommended workflow is to validate locally here, then submit to Google's tool as a final check.
JSON-LD, Microdata, or RDFa — which should I use? +
JSON-LD, full stop. Google has explicitly recommended it since 2017 because it decouples structured data from HTML markup and is far easier to maintain. Microdata requires sprinkling itemprop attributes throughout your templates, and RDFa is effectively dead in the SEO world. This tool handles JSON-LD only.
What happens if I misspell @type? +
If @type is not a recognized schema.org type, Google ignores the entire structured-data block. Case matters too — 'article' instead of 'Article' will silently fail. This tool ships with a whitelist of the most common types and suggests corrections for typos.
Why does FAQPage.mainEntity have to be an array of Question objects? +
schema.org requires FAQPage.mainEntity to be an array of Question objects, each with an acceptedAnswer property containing an Answer object. Skipping a nesting level or using the wrong field name will cause Google to silently drop your FAQ rich result. This validator inspects the nesting and pinpoints the offending field.
My JSON-LD validates fine but Google still does not show a rich result — why? +
Common reasons: (1) the site lacks the overall quality signals Google uses to trust structured data; (2) that rich-result type is restricted by country or language (HowTo, for instance, is English-only); (3) the structured data does not match the visible page content, which Google cross-checks; (4) a manual action was applied. Check the Manual Actions report in Google Search Console to rule out the last one.