Skip to main content
ToolsHub

JSON-LD Validator

Fetch a URL or paste JSON-LD to lint schema.org types, required properties, and common structured-data mistakes.

Updated

We fetch public HTML from our servers. Private and local addresses are blocked. JavaScript is not executed.

No JSON-LD yet

Fetch a public page or paste JSON-LD to check schema.org types and required properties.

How to use JSON-LD Validator

The JSON-LD Validator checks schema.org structured data the way a crawler first sees it: either by fetching a public page or by linting JSON you paste. It reports each @type, missing required properties, and recommended fields for common rich-result types such as Article, FAQPage, Product, HowTo, LocalBusiness, and BreadcrumbList. It is the counterpart to the Schema Markup Generator — that tool builds markup from a form; this one tells you what is already on the page. It is not Google’s Rich Results Test.

  1. Choose Check a URL or Paste JSON-LD.
  2. Enter a public page URL, or paste JSON, a script tag, or HTML that contains application/ld+json.
  3. Click Validate. URL mode fetches HTML with SSRF protections; paste mode never leaves the browser.
  4. Read each document: types, missing required properties, and recommended fields.
  5. Fix the markup, republish, and re-run — or open the generator if you need a fresh block.

What this validator checks

Each JSON-LD script is parsed, @graph nodes are flattened, and every typed object is linted against a small required-property table. Article needs a headline and author; FAQPage needs Question items with accepted answers; Product should have a name plus offers, a review, or aggregateRating for rich-result eligibility; LocalBusiness needs a name and address; BreadcrumbList needs itemListElement entries. Missing schema.org @context is a warning. Invalid JSON is an error. Types without a table are reported as unchecked rather than marked valid — that is deliberate, so a random @type cannot hide behind a green tick.

How this differs from Google’s Rich Results Test

Google’s tester applies live eligibility rules, quality guidelines, and feature-specific constraints that change over time. This tool does not call Google, does not execute JavaScript, and does not promise a rich result. It answers a narrower question: is the JSON-LD parseable, and are the obvious required fields present? Use it while drafting or debugging, then confirm in Google’s Rich Results Test (or Search Console) before you treat the markup as shipped. Markup must still describe visible content; valid JSON-LD for content that is not on the page can violate Google’s structured data policies.

Tool vs Google tester
CheckToolsHubGoogle Rich Results Test
Parse JSON-LDYesYes
Required properties (common types)YesYes, plus extra rules
JavaScript-rendered markupNo (paste the output)Yes
Rich-result eligibilityNot claimedOfficial

Worked examples

Valid WebSite node

Inputs: {"@context":"https://schema.org","@type":"WebSite","name":"Example"}

Result: 0 errors — name present

Product missing name

Inputs: {"@type":"Product"}

Result: Error on name; warning that offers/review are missing

HTML paste

Inputs: <script type="application/ld+json">…</script>

Result: Script extracted and linted like a URL fetch

Glossary

JSON-LD
JSON for Linked Data — Google’s recommended way to embed schema.org in a script tag.
@graph
A JSON-LD array that holds several typed nodes in one script block.
schema.org
The shared vocabulary of types (Article, Product, FAQPage) used by search engines.
Rich result
An enhanced search listing such as FAQs, breadcrumbs, or product price snippets.
Rich Results Test
Google’s official checker for whether markup qualifies for those enhancements.

Related reading

Free · No spam

Get weekly tool tips & updates

New tools, power-user tips, and productivity hacks — delivered free every Friday.

No spam, ever. Unsubscribe with one click.

Related Developer Tools

Explore all Developer Tools.