BYTETOOLS

JSON-LD Validator

Validate JSON-LD structured data in your browser: syntax errors with line numbers plus required and recommended property checks for 20 schema types.

This is a syntax and required-property lint that runs locally in your browser — it is not Google's Rich Results Test and cannot predict whether a rich result will actually be shown.

What is the JSON-LD Validator?

The JSON-LD Validator checks your structured data before you publish it. Paste raw JSON-LD or an entire script tag — even a whole head section with several blocks — and it reports syntax errors with line numbers, then lints each entity against a built-in rule table covering about twenty common schema.

  • Syntax validation with line numbers for parse errors
  • Required and recommended property lint for ~20 schema.org types
  • Reads raw JSON or full script tags — multiple blocks checked separately
  • @graph, entity arrays and @context handling
  • Severity-tagged results: errors, warnings and info
  • Runs entirely locally — your markup never leaves the browser

How to use the JSON-LD Validator

  1. 1

    Paste your JSON-LD — raw, or inside its script tag.

  2. 2

    Read the error and warning counts at the top.

  3. 3

    Fix any syntax errors first, using the reported line numbers.

  4. 4

    Work through missing required properties, then the recommended ones.

  5. 5

    Re-paste and re-check until the block comes back clean.

About the JSON-LD Validator

The JSON-LD Validator checks your structured data before you publish it. Paste raw JSON-LD or an entire script tag — even a whole head section with several blocks — and it reports syntax errors with line numbers, then lints each entity against a built-in rule table covering about twenty common schema.org types.

For known types such as Article, Product, JobPosting, Recipe, Event, FAQPage and LocalBusiness, missing required properties are flagged as errors and missing recommended properties as warnings. @graph arrays, arrays of entities and @context checks are all handled.

To be clear about scope: this is a syntax and required-property lint that runs 100% locally in your browser — it is not Google's Rich Results Test and cannot promise a rich result will appear. It is the fast pre-flight check you run before pasting markup into your CMS.

Frequently asked questions

Is this the same as Google's Rich Results Test?

No. Google's test fetches your live page and evaluates rich-result eligibility with Google's own rules. This tool is a local lint: it validates JSON syntax and checks required and recommended properties from a built-in table, instantly and without sending your markup anywhere.

Which schema types does the validator know?

About twenty of the most-used types: Article and its subtypes, Product, Recipe, Event, FAQPage, QAPage, HowTo, JobPosting, LocalBusiness, Organization, Person, BreadcrumbList, ItemList, WebSite, VideoObject, Review, Course, Book, Service and SoftwareApplication. Unknown types still get full syntax checking.

What is the difference between an error and a warning here?

Errors are things that break validity or eligibility: unparseable JSON, a missing @type, or a required property that is absent. Warnings are missing recommended properties and @context oddities — the markup works, but adding them usually improves results.

Can I paste a whole head section with several JSON-LD blocks?

Yes. The validator finds every script tag with type application/ld+json in what you paste and checks each block separately, so you can audit a page's entire structured data in one go.

Why does valid markup still not show a rich result?

Validity is only the entry ticket. Google also weighs content quality, whether the markup matches the visible page, site reputation and per-query decisions. Clean markup from this lint removes the technical blockers; the rest is ordinary SEO.

Related tools