The share link contains your schema — share it only where you'd share the schema itself.
About the JSON-LD validator
JSON-LD (JSON for Linking Data) adds a @context to ordinary JSON so its keys map to globally unique IRIs, turning a plain document into linked data. It's the format behind most schema.org structured data on the web. This tool validates a JSON-LD document by expanding it — the canonical operation that resolves every term against its context and surfaces malformed constructs.
Validation runs in two steps: first the document is parsed as JSON (a syntax error here is reported with its line number), then it is expanded with the JSON-LD algorithm. A document with an inline @context validates fully; a malformed JSON-LD construct is rejected with a clear message. Because the tool makes no network calls, a document that points at a remote context (a URL) can't be resolved — inline the context to validate it.
This checks JSON-LD / jsonld validity by expansion; it does not assess whether your markup is eligible for Google's Rich Results — that's a separate concern from linked-data validity. As with every tool here, everything runs in your browser and nothing is uploaded.
JSON-LD validation FAQ
Why does a remote @context (e.g. schema.org) fail?
For privacy, this validator makes no network calls, so a remote @context referenced by URL can't be fetched and resolved. Inline the context — paste the context object directly into your document — and it will validate.
How do I inline a @context?
Replace the URL value of @context with an object that maps each term you use to its IRI (for example { "name": "http://schema.org/name" }). With the terms defined inline, expansion can resolve every key without any network access.
Is my schema.org markup valid for Google?
This tool checks JSON-LD and linked-data validity by expansion — that the document is well-formed and its terms resolve. It does not assess Google Rich Results eligibility, which depends on Google's own required-property rules and is a separate check.
What is JSON-LD validation?
It's confirming that a JSON-LD document is well-formed and that expanding it — resolving every term against its context into a normalized form — succeeds without errors. Expansion is the standard way to verify a linked-data document is structurally valid.