Schema.org Validator

Checks only whether JSON-LD has `@context` equal to `https://schema.org` and a nonempty `@type`. It does not validate type-specific properties or value types.

Schema Org Validator · Client runtimeSandboxed
Formatted results will render here in real time.

About this schema.org validator

Checks only whether JSON-LD has `@context` equal to `https://schema.org` and a nonempty `@type`. It does not validate type-specific properties or value types Validates and converts interface schemas client-side without transmitting private endpoint specifications.

API contract & interface schema logic

Compiles, validates, and simulates JSON Schemas adhering to IETF JSON Schema Draft-04, Draft-07, 2019-09, and 2020-12 standards via embedded Ajv validation engines. Performs structural type inference from concrete JSON instances, generating strict schemas complete with required arrays, type declarations, format annotations (e.g. date-time, uri, email, uuid), and constraint metadata. In reverse, it evaluates schema constraints to synthesize realistic mock JSON data payloads.

Worked schema conversion scenario

Scenario: An SEO analyst checks two basic fields in a JSON-LD object.

Sample input:

{"@context":"https://schema.org","@type":"WebApplication","name":"CZOA Tools"}

Processing: Checks only that @context is https://schema.org and @type is a nonempty string; it does not validate Schema.org types, properties, or rich-result eligibility.

Illustrative output:

{ "valid": true, "issues": [], "type": "WebApplication" }

Schema version & syntax constraints

Only these two fields are checked; it does not validate Schema.org type definitions, properties or values.

API specifications and schema models in Schema.org Validator reflect OpenAPI and JSON Schema standards. Verify generated schemas against your runtime validator.

Client-side schema processing boundary

Schema analysis and protocol mapping in Schema.org Validator execute locally in the browser tab without uploading endpoint definitions.

OpenAPI Specification & JSON Schema standards

OpenAPI Specification standards and JSON Schema draft definitions:

Schema.org Validator verification · Audit standards

How to use it

  1. Paste a JSON-LD object.
  2. Check whether @context equals https://schema.org and @type is present.
  3. Read valid, issues and type in JSON.

Frequently asked questions

What does Schema.org Validator actually validate?+

It parses JSON and reports valid only when `@context` is exactly `https://schema.org` and `@type` is a nonempty string. It returns the type value and an `issues` list for either local rule.

Can you show an input and its result?+

A JSON object containing `"@context": "https://schema.org"` and `"@type": "WebSite"` returns `valid: true`, `type: "WebSite"`, and no issues.

Which schema.org checks are absent?+

It does not validate whether the type exists, whether properties belong to it, cardinality, value formats, nesting, URLs, language, JSON-LD syntax beyond JSON.parse, Google rich-result rules or live page markup.

Does valid true mean rich results will appear?+

No. It only passes two local conditions. Search-engine crawl, rendering, guidelines, data quality, site trust and result presentation require separate evidence.