Scan at scalePages with unparseable JSON-LD
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.
How to fix it. Repair the JSON (remove trailing commas, quote keys, escape embedded quotes) and re-validate the block 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, 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.