When does Search Console show an Unparsable structured data report?

Definition: The Unparsable structured data report in Search Console lists structured data that Google found on a site but could not parse because of a serious syntax error. Google says the parsing error prevents it from determining the intended structured data type, such as Job or Event.

Key facts

• The report appears in a property only when Google finds unparseable structured data on the site, according to Search Console Help.
• Every item in the report is a critical structured data error. The report contains no warnings or valid items.
• Google sorts errors automatically by severity, using the number of affected pages and other factors.
• A single error affecting several pages commonly comes from an underlying template error.
• Google Search supports JSON-LD, Microdata, and RDFa when the markup is valid and properly implemented, as documented by Google Search Central.

What triggers the report?

The trigger is a parsing failure at the syntax level. Google's report description says that structured data was found, but a serious syntax error stopped Google from parsing it and determining its intended type. The report also describes an incorrect value type as a field receiving the wrong kind of value and points to type-specific documentation for the required value type.

The report is conditional. It is available only when Google has found unparseable structured data in the property. If the markup parses successfully, the report has no valid-item section waiting to be filled: Google states that all items in this report are critical errors and that there are no warnings or valid items.

Which syntax failures does Google list?

Google lists Invalid JSON document for a top-level JSON syntax error. Other labels identify a missing colon, a missing comma or closing brace, a missing closing brace or object member name, and a missing comma or closing bracket in an array declaration. The table also includes invalid numbers, invalid escape sequences, invalid Unicode escape sequences, duplicate unique properties, invalid top-level elements, and references to nonexistent items.

One documented bad escape sequence is:

"description" : "Some \q unknown sequence"

The same report also labels an incorrect value type when a field receives the wrong kind of value, such as a string where a number or array is expected. Google directs readers to the structured data documentation for the required value type for that field.

How should a site owner investigate it?

Google's Unparsable structured data report instructions say that selecting an error row opens the affected pages, error details, and links to debugging tools. The documented repair flow uses the Rich Results Test to fix and test the syntax. Google suggests starting with an empty object and adding content back piece by piece when the error is difficult to locate. After an issue is fixed, the report provides a Validate Fix action in the error details page.

Fixing the parsing error can expose additional warnings or errors that were hidden while the item could not be parsed. Google also says that a site can fix issues without explicitly requesting validation, because the instance count updates when Google crawls a page with known issues.

Which markup formats are relevant?

Google Search supports JSON-LD, Microdata, and RDFa. Google describes JSON-LD as a JavaScript notation embedded in a script tag in the head or body of an HTML page, and says it can read JSON-LD that JavaScript injects into page contents. Google recommends JSON-LD when a site's setup allows it because the format is easier to implement and maintain at scale.

The W3C JSON-LD 1.1 Recommendation describes JSON-LD as a lightweight syntax for serializing Linked Data in JSON and states that it is compatible with JSON. A syntax failure in a JSON-LD block can therefore appear as a report item before Google can use the block's intended type.

Related terms

• Structured data
• JSON-LD
• Schema.org @id

FAQ

Does the report mean that a property is merely missing?

No. It indicates that Google could not parse the structured data because of a serious syntax error. A property requirement belongs to the type-specific structured data documentation after the data can be parsed.

Why can one report error affect many URLs?

Google says the most common cause of a single error affecting multiple pages is an underlying template error. A shared template can therefore place the same malformed structured data on several affected pages.

How do I confirm that a syntax fix works?

Use the Rich Results Test to test the corrected syntax, then select Validate Fix in the error details page. Google notes that fixing the parsing error can reveal warnings or errors that were previously hidden.

Sources

1. Google Search Console Help, "Unparsable structured data report", undated
2. Google Search Central, "Intro to How Structured Data Markup Works", 10 December 2025
3. W3C, "JSON-LD 1.1", 16 July 2020

---

Check how a page reads to answer engines. Open the GEO score analyzer