Structured data that does not parse
1.1%
of the 3,044 free scans considered in the last 30 days raised this finding. That is 33 scans across 33 distinct sites. 95% interval 0.1% to 12.3%.
What it means
Malformed structured data is invisible to anything reading it: a syntax error is the same as having none.
How to fix it
Fix the JSON-LD so it parses: a trailing comma or an unescaped quote makes the whole block invisible. Paste it into Google's Rich Results Test to see it fail.
How to check it yourself
View source, copy the JSON-LD block, and paste it into the DevTools console with JSON.parse. An error means it does not parse.
What fixed looks like
The JSON-LD block parses cleanly in the DevTools console with no error from JSON.parse.
How we measured this
Go Voltic scans a site and records which findings it raises. The share above is over every free four-page scan in the last 30 days that loaded at least one page, which is 3,044 scans. Deep scans of paid reports and of the research sweep read a site at a different depth and are a separate population, never in this denominator. It is not a survey and it is not an estimate: it is a count of what our own scanner found. Sites are counted once each in the distinct-sites figure, so a site scanned twice does not weigh double there.
The interval is a 95% Wilson interval. A share printed without its sample size reads as certainty and is indistinguishable from a guess, so both are always shown. Figures on this page were computed on 2026-09-08.
The same share sits beside every other finding on the benchmarks page, which also carries the whole table as CSV and JSON and says how to cite it.
Check your own site
The free scan reads four pages and reports every finding it raises, including this one. It takes about ten seconds and asks for nothing but the address.