Teardown
Structured data that does not parse: work that nothing can read
Missing markup is a choice. Broken markup is effort spent for nothing.
On this page
Structured data is code on a page that describes it in a form machines can read: this is an article, this is its author, this is the product and its price. Of the 42 startup sites I audited, 5 had structured data that fails to parse. 24 had it on some pages and not others. Only 3 had none at all.
The 5 are the interesting ones. A site with no structured data made a choice. A site whose structured data does not parse did the work and got nothing for it.
What I found
42 startup sites, 14,023 pages, crawled 15 to 18 September 2026
- Fails to parse
- 5 of 42 sites (12%)
- On some pages but not all
- 24 of 42 sites (57%)
- None anywhere
- 3 of 42 sites (7%)
Why it breaks: one character in a template
Structured data is usually written in a strict format called JSON-LD. One wrong character, such as an unescaped quotation mark or a raw line break inside a piece of text, makes the whole block unreadable, not just that line.
The character almost always arrives through a template. The markup works on the page someone tested, then breaks on the page where an FAQ answer happens to contain a quotation mark. Google's own documentation anticipates exactly this:
Be sure to check your structured data using the Rich Results Test during development, and the Rich result status reports after deployment, to monitor the validity of your pages, which might break after deployment due to templating or serving issues.
Google Search Central, structured data
What Google needs from it
Google accepts several formats and says so, with one condition attached:
In general, we recommend using a format that's easiest for you to implement and maintain (in most cases, that's JSON-LD); all 3 formats are equally fine for Google, as long as the markup is valid and properly implemented per the feature's documentation.
Google Search Central, structured data
Markup that does not parse is not valid, so it does not meet the condition.
What fixing it will not do
Fixing it guarantees nothing. Structured data makes a page eligible for some search features; it does not earn them.
It is not a shortcut into AI answers either. When I measured which pages Perplexity cited across 603 citations, pages with FAQ markup were no more likely to be cited once their search position was taken into account. I would fix broken markup because it is wasted work, not because of what it is sometimes sold as.
Check your own site, no code needed
- Open Google's Rich Results Test in your browser.
- Paste the address of a page that should carry structured data, and run the test.
- If it reports that the markup could not be read, or lists errors, that page's markup is broken. Test one page of each type: an article, a product, an FAQ.
- Once Search Console is set up, its structured data reports keep watching after the fix.
What to ask your developer
- Is the structured data typed into the template by hand, or generated in a way that handles quotation marks and line breaks safely?
- Can the Rich Results Test run on one page of each type before every release?
What I could not tell from outside
I tested whether the markup parses, not whether it qualifies for any search feature. Valid markup can still be missing properties a feature needs.
These are counts on 42 startup sites I audited from the outside, mostly developer tools and SaaS. They are not an industry average, and nothing here measured whether any of these sites performed worse in search because of what I found.
Want to know which of these your site has?
Send a URL. Three to five verified findings come back within two working days, free, each with a way to check it yourself.