# Pages with unparseable JSON-LD

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

## What this report returns

An ld+json block that isn't valid JSON (a trailing comma is enough) is dropped whole by every consumer: search engines and agents see nothing of what it declared, making this the highest-severity structured-data defect.

A row appears here when this is wrong:

-   **JSON-LD Invalid JSON**An ld+json block doesn't parse as JSON (a trailing comma is enough; an empty block also counts), so every consumer drops the entire block.**Fix** Make the block valid JSON; validate with a JSON linter or Google's Rich Results Test.

## 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 Invalid JSON`jsonLdInvalidJson`
-   JSON-LD Parse Error Samples`jsonLdParseErrorSamples`
-   JSON-LD Findings`jsonLdFindings`

## About JSON-LD

Structured data describing what this page is about.

[Read how JSON-LD is checked](https://agentic-readiness.lumar.io/docs/content/json-ld), including the specification it is validated against and a worked correct and broken example.

## Running it

This report comes with Agentic Readiness in Lumar and appears on every crawl of any project that has it turned on. [See the whole set](https://agentic-readiness.lumar.io/scan-at-scale), or check a single URL with the [scanner on this site](https://agentic-readiness.lumar.io/), which runs the same code with no account.

[Get Lumar pricing →](https://www.lumar.io/pricing/)