JSON-LD Validator

A JSON-LD validator parses the structured data you paste, reports JSON syntax errors and checks common required properties for types such as Article, Product, FAQPage and VideoObject. It is a fast first check before Google's Rich Results Test.

It runs entirely in your browser. Nothing you paste or upload is sent to a server or stored.

How to read the result and act on it

Paste your JSON-LD or page source and read the report from the top. Syntax errors come first: a missing comma, unclosed brace or stray quote stops the whole block from parsing, so fix these before anything else. Next, review the missing property messages for the detected types, such as Article, Product or FAQPage, and add the ones relevant to your page. Warnings about recommended fields are optional but useful. Once the markup passes here, test the live page in Google's Rich Results Test to confirm eligibility, and revalidate after every template change.

Common mistakes to avoid

Do not assume a clean result here means a rich result will appear. Eligibility depends on Google's own rules, content quality and whether the page is indexed. Another mistake is pasting curly quotes from a word processor, which breaks JSON. Avoid validating only one template and assuming all pages match, because dynamic fields can output empty values. Do not mark up content that users cannot see just to satisfy a validator. Also remember that a missing recommended property is not always an error, so prioritise required fields first.

What is the difference between a validator and the Rich Results Test?

A schema validator checks syntax and vocabulary. The Rich Results Test checks whether markup is eligible for specific Google features.

Why does my markup validate but show no rich result?

Eligibility depends on Google's policies, page quality and the type itself; many types no longer show rich results.

How do I fix a JSON-LD syntax error?

Look at the line mentioned in the error and check for missing commas, mismatched brackets, unescaped quotes or trailing commas. Paste the code into the validator again after each fix until it parses cleanly.

Where should JSON-LD be placed on a page?

Place it in a script tag with type application/ld+json, usually in the head or body of the page. Google can read it in either location, and it can also be injected by JavaScript if rendered.

• Structured Data Checker: Fetch a page and list the JSON-LD it contains, with parse errors and missing properties.
• Schema Markup Generator: Generate JSON-LD structured data for articles, products, FAQs and more.
• FAQ Schema Generator: Generate FAQPage JSON-LD from question and answer pairs.

Browse all 10 free schema tools, or see the full free SEO toolbox. If you would rather have this handled for you, take a look at our schema markup services and the results from real projects.