Why is my JSON-LD structured data not working?
Rubric check: structured data that can't be read (check id sd_parse_error)
Most likely a syntax error. A trailing comma, a stray or unescaped quote, or a line break inside a value makes the JSON invalid, and search engines then ignore the whole block. Rubric flags pages with a JSON-LD block that fails to parse.
Why it matters for SEO
Google Search Console reports these as "Unparsable structured data". Everything in the broken block is lost: the product, article or organisation details it held, and any rich result they'd support. Usually one character is the cause.
Does this matter for ChatGPT and AI Overviews?
Structured data doesn't on its own make AI tools cite a page, but it carries facts such as prices, dates and authors. A broken block drops all of them for every reader. Fixing it is quick.
How Rubric scores it
MinorMinor checks cost a quarter to a half of a standard check when they fail.
Why this tier: Markup that can't be read.
It is judged on every page Rubric scores.
Every Rubric score starts at 100. When this check fails, it takes up to 6 points off. Even one failing page costs at least 3 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.
All the minor checks share one limit: together they can take off at most 25 points, however many of them fail.
This check doesn't cap your score. It only takes off its own points.
From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).
How common it is
Found on 15 of 300 sites where Rubric could judge it (5.0%). That is 15 of 287 judged sites in Rubric's 313-site test set and 0 of 13 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.
How accurate the check is
Lab test: passed. On test pages built with this problem, it caught 3 of 3. On clean test pages, it stayed quiet 2 of 2 times. (Engine build bbcec7c.)
Real sites: people checked 11 of its findings by hand and 1 was wrong (9.1%). Last checked 14 Nov 2026. That's a small sample, so treat the rate as rough.
Holdout test 5 (sites the check had never seen): 0 of 12 findings judged wrong.
Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.
How to fix it
WordPress
- Run the page through Google's Rich Results Test, which points to the line that fails.
- Plugin markup rarely breaks. Look for JSON-LD you pasted into a Custom HTML block or a header-and-footer plugin.
- Fix the character, save, clear the cache and test again.
Shopify
- Test the page in the Rich Results Test.
- In Online Store > Themes > Edit code, search for
application/ld+json. - Product titles or descriptions with quotes break hand-built JSON. Output each value with the
| jsonfilter, for example"name": {{ product.title | json }}.
Webflow
- Test the page, then open Page settings > Custom code or the Embed that holds the JSON-LD.
- CMS fields inserted into JSON can carry quotes or line breaks. Use plain text fields and keep rich text out of the markup. Publish.
Custom code
Common breaks and fixes:
{"@type": "Product", "name": "Boots",} // trailing comma: remove it
{"@type": "Product", "name": "12" Boots"} // escape the quote: "12\" Boots"Generate JSON-LD with JSON.stringify or your language's JSON encoder rather than string templates.