How do I check if my structured data is valid?
Rubric check: structured data that doesn't parse (check id schemavalidity)
Paste the page's URL into Google's Rich Results Test or the Schema Markup Validator. Rubric checks that every JSON-LD block on a page parses as valid JSON and names its @type. A block that fails to parse is ignored entirely.
Why it matters for SEO
Search engines can only use structured data they can read. One stray comma makes a whole JSON-LD block unreadable, so any rich result it would support can't show. A block with no @type says nothing about what the page is.
Does this matter for ChatGPT and AI Overviews?
Valid markup is a basic requirement, not a citation boost: studies of AI search haven't shown structured data on its own causing citations. Broken markup, though, means any facts you put there (prices, dates, authors) are lost to every reader.
How Rubric scores it
MinorMinor checks cost a quarter to a half of a standard check when they fail.
Why this tier: Markup that doesn't parse can't be read, so search and AI engines ignore it.
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 20 of 293 sites where Rubric could judge it (6.8%). That is 16 of 224 judged sites in Rubric's 313-site test set and 4 of 69 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Across those sites, about 530 of 10,238 pages were affected (5.2%). 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 1 of 1 times. (Engine build bbcec7c.)
Latest review round: 0 of 6 findings judged were still wrong after the last fix.
Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.
How to fix it
WordPress
- Run a flagged page through the Rich Results Test and note which block fails.
- Markup from Yoast SEO, Rank Math or WooCommerce is generated, so it rarely breaks. Hand-pasted JSON-LD in a custom HTML block or a header plugin is the usual cause.
- Fix or remove that block, clear the cache and test again.
Shopify
- Test a product page in the Rich Results Test.
- If a block fails, find its source: the theme (search Edit code for
application/ld+json) or an app. - Fix the Liquid that builds it, often a missing
| jsonfilter on a value with quotes in it, or turn off the app's markup.
Webflow
- Webflow adds little markup itself, so blocks usually come from Custom code or an Embed.
- Test the page and fix the block in Page settings > Custom code. On CMS templates, check that inserted fields don't break the JSON with quotes or line breaks.
- Publish.
Custom code
Build JSON-LD from data, not by joining strings, so it always parses:
const ld = { "@context": "https://schema.org", "@type": "Article", headline: post.title };
html += `<script type="application/ld+json">${JSON.stringify(ld)}</script>`;