Pages with invalid JSON-LD

A per-URL report: one row per page that matches, over the pages a crawl reached.

What this report returns

JSON-LD script blocks are how a page describes itself to search engines and AI agents in machine-readable form.

These pages have JSON-LD that loses that meaning: unparseable JSON, an entity with no @context or @type, a non-schema.org vocabulary, a missing Google-required property, or a badly formatted value, so consumers drop the block or the entity.

The Conformance Issue Detected column is true only for unparseable JSON, which JSON-LD 1.1 requires (a JSON-LD document must be valid JSON); a missing @context, @type or vocabulary is Lumar's readiness profile, and required properties and value formats follow Google Search and Schema.org guidance rather than a specification rule, so those rows read as usable-by-agents problems and not as spec violations.

How to fix it. Make each block valid JSON, give every top-level entity "@context": "https://schema.org" and an "@type", and check type requirements with Google's Rich Results Test; the flagged columns show which rule each page breaks.

The columns it shows

Every defect this technology can carry is a column in the grid, worst first, so nothing is hidden behind a filter you have to know to apply.

JSON-LD ValidjsonLdValid
JSON-LD Conformance Issue DetectedjsonLdConformanceIssueDetected
JSON-LD FindingsjsonLdFindings
JSON-LD Block CountjsonLdBlockCount
JSON-LD Entity TypesjsonLdEntityTypes
JSON-LD Parse Error SamplesjsonLdParseErrorSamples
JSON-LD Missing Required Prop SamplesjsonLdMissingRequiredPropSamples
JSON-LD Invalid Value SamplesjsonLdInvalidValueSamples
JSON-LD Invalid JSONjsonLdInvalidJson
JSON-LD Missing ContextjsonLdMissingContext
JSON-LD Missing TypejsonLdMissingType
JSON-LD Missing Required PropertyjsonLdMissingRequiredProp
JSON-LD Invalid Value FormatjsonLdInvalidValueFormat
JSON-LD Non-Schema ContextjsonLdNonSchemaContext

About JSON-LD

Structured data describing what this page is about.

Read how JSON-LD is checked, including the specification it is validated against and a worked correct and broken example.

Running it

This report ships in the Lumar agent-readiness container and appears on any project it is linked to, on every crawl. See the whole set, or check a single URL with the scanner on this site, which runs the same code with no account.

Get Lumar pricing