Invalid JSON-LD
JSON-LD blocks that are not valid JSON. A block that does not parse is thrown away whole. The page loses everything it tried to say, and nothing on screen shows it.
CriticalSTRUCT-002 · Structured data · checked on every page
Where it usually comes from
Hand-edited blocks with a missing comma or quote, product descriptions with quotes pasted into the JSON without escaping, or two plugins writing into one block.
How to fix it
- Paste the block into a JSON validator to find the broken character — usually a stray comma or an unescaped quote.
- Fix it in the template or plugin that writes it, then test the page in Google’s Rich Results Test.
How to check it yourself
Paste the page address into the Schema.org validator; it points at the line where the JSON breaks.
What it looks like in a report
Critical Invalid JSON-LD. · evidence: Unexpected token } at position 412
One broken character throws away the whole block, usually a trailing comma. (An example shop; the numbers are illustrative.)
How the audit counts it
STRUCT-002 is a critical in the structured data category, and weighs heavily in that category’s score. When it appears on many pages built from the same template, the report shows it once, with the number of pages it covers — because one change in the template fixes all of them.
If the finding is deliberate on your site, it can be accepted as intentional in the report. It then leaves the list and the score, and comes back on its own if what it shows changes.
Other structured data checks
- The page has no structured data · STRUCT-001
- JSON-LD without @context or @type · STRUCT-003
- Product without price or availability · STRUCT-004
- Article without headline or date · STRUCT-005
- Home page without Organization · STRUCT-006
- Deep page without a breadcrumb · STRUCT-007
Find it on your site
A Trakis audit runs this check and the other 65 on your site, and tells you on how many pages each one sits. Or go back to all the rules.