"Unparsable structured data" in Search Console: the Shopify causes, and the fix

Short answer. Google could not read a markup block on your page because of a syntax error, so it discarded the block entirely — price, availability, rating, everything it contained. The page keeps ranking on its text; only the enriched part disappears. On Shopify the cause is almost always a theme snippet or an app writing invalid JSON, and the fastest route to it is validator.schema.org, which names the exact character at fault.

This is the most literal failure in the whole Search Console reporting surface, and also one of the least visible. Nothing breaks on the page. Nothing looks wrong to a shopper. The store owner finds out because rich results quietly stopped appearing, or because a report line appeared that nobody can decode.

Google's reference is unusually direct about what it means. The report "lists structured data found on your site that could not be parsed because of a serious syntax error", and "the intended type of structured data (Job, Event, and so on) could not be determined because of the parsing error." Google did not disagree with your markup. It could not tell what your markup was.

The same page adds a detail worth taking seriously: "All items in this report are critical structured data errors; there are no warnings or valid items." There is no severity to weigh here. Everything listed is broken.

What you actually lose

The page stays indexed and keeps ranking on its text. What disappears is everything the block declared. If the failing block was your Product markup, then the price, the availability and the rating it carried are simply not there as far as Google is concerned, and the page becomes ineligible for the enriched result it used to earn.

That is why this failure is so often discovered through a symptom that looks unrelated. Review stars vanishing from a listing is the classic one, and broken markup is one of its recurring causes — we cover that path from the other end in the review stars article. Here we are starting from the report line rather than from the missing stars.

Across our own full-catalog scans of more than 90,000 Shopify product pages, a product schema block that fails to parse is one of the critical failures we encounter regularly. It is not the most common one, but it is close to the most damaging per store affected, because a single broken snippet in a theme applies to every product page at once.

Not sure whether your product markup still parses? We validate the structured data on your live product pages and flag the blocks Google would discard — read-only, no app to install, about 2 minutes. → free scan

The three syntax errors that cause it on Shopify

Two JSON documents concatenated. The theme writes one Product object and an app appends a second one into the same script tag, with nothing separating them. Two valid objects placed back to back are not valid JSON. Both are lost.

A trailing comma. The last property in an object or the last item in an array is followed by a comma with nothing after it. This is the single most common hand-edit mistake in a Liquid snippet, and it invalidates the entire document rather than the one line.

Unescaped characters inside a value. A product title or description containing a straight double quote, a line break, or a stray control character, injected into the JSON without escaping. This one is treacherous because it breaks on some products only — the ones whose text happens to contain the offending character — which makes it look intermittent and random until you notice the pattern.

Finding the source: theme or app

This is the step most guides skip, and it is the one that saves the time. Once the validator has shown you the failing block, copy a distinctive fragment of text from it and search for that fragment in Online Store → Themes → Edit code.

If the fragment is in the theme files, the theme is generating the block and you can fix it directly. If the fragment appears on the rendered page but nowhere in the theme, an app is injecting it at runtime, and editing theme code will achieve nothing. In that case the fix is in the app's own settings — most reviews, SEO and social apps have a toggle for their structured data output — or with its support team.

The distinction matters because the two cases have different failure modes over time. A theme fix stays fixed until someone edits the theme. An app fix can be silently undone by the app's next update, which is why this is a check worth repeating rather than performing once.

How to check and fix your own store

1. Paste a product URL into validator.schema.org and read the exact parsing error it returns, along with the block it belongs to.
2. Copy a unique text fragment from that block and search for it in Online Store → Themes → Edit code to establish whether the theme or an app produced it.
3. If it is the theme: remove the trailing comma, escape quotes and newlines inside values, and wrap multiple objects in an array rather than concatenating them.
4. If it is an app: disable its structured data injection, or contact its support with the validator output.
5. Revalidate on validator.schema.org, confirm with the Rich Results Test, then open the error in Search Console and click Validate Fix. Google notes that "validation typically takes up to about two weeks, but in some cases can take much longer" — the fix itself is live immediately, only the report lags.

One habit is worth building out of this. Because the symptom is invisible on the page, the natural moment to check is not when something looks wrong, but after any change that touches the theme or the app list. A theme update, a new reviews app, a bulk product import: each of those can introduce a stray character into a block that has parsed correctly for a year.