One or more JSON-LD blocks contain invalid JSON
If this finding appears in a report, at least one sampled application/ld+json block could not be parsed as JSON. Confirm the affected URL, block and parser error; this reference page does not inspect your markup. Syntax failure is different from valid JSON that uses an unsupported type or omits a feature-specific property.
Why this matters
A consumer cannot reliably process a block it cannot parse. Other valid blocks and the visible page content may still be usable. The observation alone does not prove lost AI citations, a ranking penalty or loss of every rich-result feature. Feature eligibility also depends on the supported type, required properties and content policies.
How to fix it
Locate the exact failing block in both the delivered HTML and rendered page. Check it with a JSON parser, repair the reported syntax issue and test all blocks again. Common causes include trailing commas, unescaped quotation marks and template placeholders inserted without JSON encoding. Generate JSON with a serializer instead of concatenating unescaped values. Then validate the relevant supported structured-data type and confirm that it describes the visible page accurately. Use Google's Rich Results Test for supported Google features and inspect the deployed URL. A block that parses successfully still needs semantic and eligibility checks; do not treat JSON parse success as a rich-result guarantee.
Turn website findings into an action plan
Create an account to start a Full Audit of your website, with supporting evidence and a prioritised action plan.
Start Full Audit