All The Validators logoAll The Validators

web validator

JSON-LD Schema Validator

Validate JSON-LD snippets in HTML or raw JSON for @context and @type, locally.

Results

Processing…
Status
Processing...
Details
Processing...
Blocks found
Processing...
Invalid blocks
Processing...
Types
Processing...

How to use this validator

  1. Paste HTML with JSON-LD scripts or raw JSON-LD.
  2. Run validate to extract/parse blocks and check for @context and @type.
  3. If invalid, add missing fields or fix malformed JSON and re-validate.

Rules & checks

Extracts <script type="application/ld+json"> blocks from HTML or parses raw JSON-LD.

Requires @context and @type on each JSON-LD object.

Lists types found and flags invalid blocks; no network calls.

Inputs explained

  • HTML or JSON-LD

    Paste full HTML with <script type="application/ld+json"> blocks or raw JSON-LD. Use https://schema.org as @context and include @type.

When to use it

  • QA CMS templates for schema.org output
  • Validate JSON-LD snippets before pushing to production
  • Check marketplace/blog schema blocks from contributors

Common errors

  • Missing @context or @type
  • Invalid JSON syntax in script blocks
  • Wrong @context URL (non-HTTPS schema.org)

Limitations

  • Presence and basic field check; does not validate full schema.org compliance or required properties per type.
  • Does not fetch remote contexts or linked data.

Tips

  • Keep one JSON-LD block per entity when possible
  • Ensure @context uses https://schema.org or a valid context URL
  • Prettify JSON-LD to spot missing commas/braces

Examples

Valid Article

  • <script type="application/ld+json">{"@context":"https://schema.org","@type":"Article","headline":"Test"}</script> -> Valid

Missing @type

  • {"@context":"https://schema.org"} -> Invalid (missing @type)

Invalid JSON

  • <script type="application/ld+json">{bad json}</script> -> Parse error surfaced

Deep dive

This JSON-LD validator extracts script blocks and checks for @context and @type entirely in your browser, surfacing malformed JSON and missing required fields.

Use it to keep structured data valid before publishing; pair with full schema validators in CI for deeper property checks.

FAQs

Is anything uploaded?
No. Parsing happens locally and clears on refresh.
Do you validate against full schema.org?
This checks top-level presence. Use deeper schema tests for required properties per type.
Do you fetch contexts?
No. Contexts are not fetched; keep them standard (https://schema.org).

Related validators

web

OpenGraph & Twitter Card Validator

Validate OpenGraph and Twitter card meta tags locally—required tags, URL formats, and missing fields before you publish.

web

HTML Meta Validator

Validate document-level meta basics: charset and html lang.

web

Canonical & hreflang Validator

Validate canonical and hreflang tags to avoid duplicate-content and localization issues.

All parsing/validation is done in your browser. No data is sent, logged, or stored.

Presence and basic parsing check; not a full schema.org conformance test.