SEO Tools

JSON-LD validator.

Paste JSON-LD or a whole <script type="application/ld+json"> block. Check the JSON, @context, @type, and the required properties Google lists for Article, Product, FAQPage, BreadcrumbList, and Organization.

Format check onlyNo uploadSources checked 30 September 2026
Advertisement

JSON-LD

Worked example: a Product with a name and image but none of review, aggregateRating, or offers. It fails Google's product snippet rule. Add an offers object and it passes.

Privacy note: parsing happens in this browser. Nothing is sent anywhere, and no URL is fetched.

Result

Paste JSON-LD and press Validate.

Advertisement

What this checks

Syntax and context

Parses the JSON, accepts a single object, an array, or an @graph, and flags a missing @type or an @context that does not point at schema.org.

Required properties

Product: name plus one of review, aggregateRating, offers. BreadcrumbList: itemListElement with position, name, and item (optional on the last crumb). Article and Organization have no required properties; missing recommended ones show as warnings.

FAQPage

Google removed its FAQ rich result documentation in June 2026 because the feature no longer shows in Search. This tool still checks the Question and Answer structure, but a pass earns no Google rich result.

Format check only. Passing here does not guarantee a rich result, and Google may still refuse markup that does not match visible page content. Confirm with Google's Rich Results Test.

Advertisement

JSON-LD questions

Will a pass get me a rich result?

No. The tool checks syntax and the properties Google documents. Eligibility also depends on content quality, page visibility, and Google's own choices. Use the Rich Results Test for Google's verdict.

Why does Article show warnings but no errors?

Google's Article documentation says there are no required properties, only recommended ones such as headline, image, datePublished, dateModified, and author. Missing ones are flagged as warnings.

Can I paste the whole script tag?

Yes. Every application/ld+json script block in pasted HTML is extracted and checked separately.

What about other types like Recipe or Event?

They are parsed and given a note, but no required-property check is built in for them. Only the five types above are checked.

Where should I put JSON-LD on the page?

Put each block in a script element with type application/ld+json, usually in the head or the body; Google's documentation shows it in the head, and says it can also read JSON-LD injected dynamically with JavaScript. You can have several blocks on one page or combine entities in a single block with an @graph array.

Why does my JSON-LD say invalid JSON?

The usual causes are a trailing comma after the last property, a comment, single quotes, curly quotes pasted from a word processor, or an unescaped double quote inside a text value. Fix the first reported error and re-run, because one broken character can hide everything after it.

Does the markup have to match what visitors see on the page?

Yes. Google's structured data policies say not to mark up content that is not visible to readers of the page, and that the markup should represent the main content. A validator can only check format, so reading the page against the markup is your job.

Sources (checked 30 September 2026)

What JSON-LD is and where it goes

JSON-LD is a way of writing linked data as JSON. In SEO it is the usual format for schema.org structured data: a <script type="application/ld+json"> block holds a JSON object that describes the page, such as an article, a product or an organization. Google's documentation lists JSON-LD, Microdata and RDFa as supported formats, says all three are equally fine as long as the markup is valid and implemented per the feature's documentation, and recommends JSON-LD where it is the easiest to implement and maintain. It also says Google can read JSON-LD that is injected dynamically by JavaScript. Because the data sits in its own script block instead of being woven through your HTML, it is easy to generate, and just as easy to break with a stray comma.

A minimal valid example

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to read a mortgage statement",
  "datePublished": "2026-10-01T09:00:00-04:00",
  "author": { "@type": "Person", "name": "A. Writer" }
}
</script>

@context says which vocabulary the keys come from, @type says what kind of thing is being described, and the remaining keys are properties of that type. Pasting this into the validator gives no errors. Google's Article documentation says Article has no required properties, only recommended ones, so removing author would produce a warning rather than an error. Dates use ISO 8601 format, and Google recommends including timezone information.

The three layers of checking

  1. Syntax. Is it valid JSON at all? The most frequent failures are trailing commas after the last property, comments (JSON has none), single quotes instead of double quotes, curly "smart" quotes pasted from a word processor, and unescaped double quotes inside a text value. Nothing else can be checked until this layer passes.
  2. Vocabulary. Does it declare a schema.org @context and a recognizable @type? JSON keys are case-sensitive, so "article" is not "Article", and a missing @type leaves the data describing nothing in particular.
  3. Feature requirements. If you want a specific Google result, the feature's documentation lists required and recommended properties. For Product snippets, Google's documentation requires name plus one of review, aggregateRating or offers. For breadcrumbs, each list item needs a position and a name. This tool checks those for the five types it supports and reports missing recommended properties as warnings.

Errors, warnings and what a pass means

An error means the markup is broken or a required property is absent, so the feature the markup is for cannot work. A warning means a recommended property is missing: the markup is valid but less complete. A pass from this tool means the JSON parses and the checked properties are present. It does not mean Google will show a rich result. Google's structured data policies say markup must represent the visible main content of the page, must not describe content that readers cannot see, and that issues can lead to a manual action, which removes eligibility for rich results without changing how the page ranks. Whether the markup matches the page is something no format checker can determine for you.

Which validator to use when

Worked example of a failing paste

Paste a Product block with "name": "Trail shoe" and nothing else. The JSON parses and @type is present, but the Product check reports an error: Google's documentation needs one of review, aggregateRating or offers alongside name. Add "offers": {"@type": "Offer", "price": 89.00, "priceCurrency": "CAD"} and the error clears; missing recommended fields such as image remain as warnings. Google's Product documentation describes priceCurrency as using the ISO 4217 format, so write CAD, not a symbol.

What this tool does not cover

It does not fetch URLs, render JavaScript, compare the markup with what the page shows, or check types beyond Article, Product, BreadcrumbList, Organization and FAQPage. Other types such as Recipe or Event are parsed and noted but have no property rules here. For those, use the Rich Results Test and the matching Google guide. To build a block rather than check one, try the Schema Generator; for general JSON syntax errors, the JSON Validator pinpoints the exact line.