JSON-LD Structured Data Validator

Validate raw JSON-LD or full HTML locally, then inspect blocks, graph nodes, types, @id conflicts, URL issues, and practical field gaps before publishing.

Raw JSON-LD or HTMLinspect pasted markup or local files

Blocks, nodes & typesmap @graph and nested structured-data nodes

@id + URL diagnosticsfind duplicate identifiers and relative URLs

Pre-publish completenessreview common type field gaps without claiming eligibility

Validate JSON-LD structure locally

Paste a JSON-LD object, array, or @graph. This checks JSON syntax, Schema.org context/types, and a small practical set of common fields. It does not certify Google Rich Results eligibility.

JSON-LD

—Structured nodes

—Unique types

—Errors

—Warnings

Ready—

After publishing, use search-engine-specific testing and URL inspection for actual feature eligibility and crawl/indexing context. Schema.org-valid data alone does not guarantee a search feature.

JSON-LD structured-data inspector

Audit JSON-LD blocks, nodes, IDs, URLs, and field gaps

Paste raw JSON-LD or complete HTML. This browser-local workspace parses each JSON-LD block, summarizes the graph, and surfaces practical issues before you publish.

JSON-LD · HTML extraction · browser-local

Input modeOpen local JSON/JSON-LD/HTML fileMarkup

0JSON-LD blocks

0structured nodes

0unique types

0errors

0warnings

0duplicate @id

0relative URLs

Detected @type values: —

Issues

Copyable pre-publish audit

Structured-data node map

Ready.

Validation boundary. These are local JSON syntax, graph-structure, identifier, URL, and practical completeness checks. They do not fetch remote contexts, execute page JavaScript, validate the entire Schema.org vocabulary, or certify Google rich-result eligibility. After publishing, use the official Schema.org Markup Validator for generic Schema.org validation and Google Rich Results Test / Search Console for Google-specific eligibility and live-page behavior.

Search-engine boundaries

Local markup checks cannot know what a crawler fetched, rendered, indexed or selected as canonical. Search engines may rewrite title links/snippets, choose different canonicals, ignore invalid or ineligible structured data, and apply live HTTP/robots conditions that are not present in pasted text. Treat these tools as pre-publish QA, then verify live behavior with the relevant search-engine tools.

Schema.org validity is separate from Google feature eligibility

JSON-LD syntax, graph nodes, URLs, dates and practical type fields are checked locally. Search features can be retired or have stricter page/content rules.