Webmaster tools
Edit raw JSON-LD and inspect a formatted copy, term hints and the nodes visible in this input.
Your JSON-LD stays in this browser tab. No URL or remote context is fetched.
Schema.org vocabulary snapshot 30.1
Strict JSON, visible nodes and term existence only; no Google eligibility check.
Nodes: 2 · Notes: 0
Schema.org 30.1 term lookup applied.
No issues found.
Showing 2 of 2
A template can emit valid JSON yet miss a type, misspell a property or point to another entity that is hard to see in one code block. This JSON-LD validator puts those separate observations beside the original text before you publish.
You can check JSON-LD online here with a frozen Schema.org vocabulary list and local processing. It does not decide Google eligibility; use the official Rich Results Test after this preflight.
See a readable copy and an honest explanation of what the local checks can establish.
The JSON-LD validator lists nodes from a top-level array, nested objects or @graph and shows explicit @id references. A target absent from the pasted fragment is labelled outside this input, not invalid.
Schema.org 30.1 term hints identify names missing from the bundled snapshot. A custom context is left unchecked, and a hint never claims that Google would reject a rich result.
Paste JSON-LD text, including a top-level array or @graph. This page does not extract scripts from HTML or fetch a URL; copy the code inside the script tag first.
Auto-check runs 350 ms after edits and prints two-space JSON beside syntax, structure and Schema.org 30.1 hints. Turn it off for a manual check with Ctrl/Cmd+Enter.
Copy or download the current formatted text only while the result is fresh. Open Schema.org Validator for generic markup checks or Google Rich Results Test for Google-specific eligibility.
Duplicate JSON keys and malformed punctuation are errors with a line and column. The input line is highlighted, while valid numbers and object key order survive formatting.
The structured data tester compares plain Schema.org types and properties with the bundled 30.1 current-term list. Custom mappings and other remote contexts are not judged by that lookup.
Nodes show their source path, @type and @id. Explicit references show whether their target is also present in this paste; the list is not JSON-LD expansion or a canonical RDF graph.
No. This JSON-LD validator checks local syntax and a fixed vocabulary snapshot; the Google tool applies current feature requirements to code or a page. The official link opens without transmitting your draft.
An error means strict JSON could not be parsed or the root is not an object or array. Warnings describe missing structure or terms absent from the 30.1 snapshot; fix the source and compare with official tools.
Yes, as a visible input summary. It lists @graph nodes and explicit @id links but does not expand contexts, generate triples or claim full JSON-LD 1.1 validation.
Yes, JSON-LD can use an array or @graph for multiple entities. This page summarizes the nodes in the pasted fragment; it does not fetch other script blocks from your page.
Test the deployed URL in Google Rich Results Test and inspect Search Console. A green local JSON-LD validator result cannot confirm what Google crawls or displays.
Found a missing case?
Start with the linked-node sample, then run the JSON-LD validator on your own markup and take the fresh formatted result to the official tests.