Skip to content
MrKeyword
Technical SEO

Unparsable structured data in Google Search Console: what it means and how to fix it

Google found structured data on the page but could not parse it, so the item is ignored and the page cannot get rich results from it. The fix is almost always a small syntax error in a template or plugin.

A checklist-style dashboard of page and structured data checks
The short version
  • Unparsable structured data means Google found markup it could not read, so the item is ignored and the page cannot get rich results from it.
  • The report names the exact error. Match that name to the cause and fix in the table below instead of guessing.
  • Most errors are one character. A missing comma or bracket, a curly quote, a trailing comma or an unescaped quote in a product name breaks the block.
  • Find the broken line with a validator. The Rich Results Test and validator.schema.org point at the failing line; a JSON linter shows the exact position.
  • Fix the template or plugin, not just the page. A syntax error in a template repeats on every page that uses it.

What does Unparsable structured data mean?

The 'Unparsable structured data' report lists pages where Google found JSON-LD, Microdata or RDFa it could not read because of a syntax error. Because the markup cannot be read, Google ignores the item, so the page cannot get rich results from that item.

The report is not saying the page is broken or that the content is wrong. It is saying the structured data block failed to parse, which is a code error in the markup itself. That is good news: a syntax error is usually a one-line fix, and you do not need to rewrite the page.

You find the report under Enhancements in Search Console, or in the list of structured data reports. Open the report to see the affected items, the error name Google recorded and sample URLs. Google's structured data general guidelines explain which formats Google supports and how it reads them (checked November 2026).

Unparsable is different from a valid block that is missing a required field, such as the offers, review or aggregateRating error on Product snippets. A missing field leaves a readable item; a parse error leaves no item at all.

What are the common errors?

The report uses specific error names, and each one points at a different kind of syntax mistake. The table gives the typical cause and the fix for each error.

Unparsable structured data errors, causes and fixes

ErrorCauseFix
Missing ',' or '}'A JSON object is missing a comma between properties or the closing brace, often after an edit to a template.Add the missing comma or brace. Count the opening and closing braces, then lint the block.
Bad escape sequence in stringA backslash in a string does not start a valid escape, such as a Windows path or a stray backslash before a quote.Escape it as \\ or remove it. In JSON, a literal backslash must be written as two backslashes.
Parsing error: Missing ',' or ']' in array declarationAn array such as a list of authors, images or offers is missing a comma between items or the closing bracket.Add the missing comma or bracket and check that every array item is separated.
Incorrect value typeA property expects a nested object but gets a plain string, for example "offers": "29.99" instead of an Offer object.Use the type the property expects: wrap the value in an object with its own @type, such as an Offer with price and priceCurrency.
Duplicate unique propertyThe same unique property appears twice in one item, often because a theme and a plugin both write it.Keep one value and remove the duplicate property or the second block writing it.
Invalid top level elementThe JSON root is not a valid schema.org object, such as a bare string or a custom key instead of @context and @type.Wrap the item in an object with a valid @context and @type, and use one object per top-level item.
Error names follow Google's structured data report help, checked November 2026.

Read the error name literally. 'Missing' means a character is absent, 'Bad escape' means a backslash is wrong, and 'Incorrect value type' means the value is the wrong kind, not that it is missing.

How do I find the broken line?

Paste the page URL or the raw markup into a validator and let it point at the failing line. Three checks find the exact position quickly.

  1. Google's Rich Results Test

    The Rich Results Test fetches the live URL or reads pasted code. When a block cannot be parsed it shows the error and the code that failed, so you can see which script block is broken.

  2. Schema Markup Validator

    validator.schema.org checks every JSON-LD, Microdata and RDFa block on the page against the schema.org vocabulary and reports syntax problems with the line number. Use it when the Rich Results Test says the page has no items at all.

  3. JSON linting

    Copy the contents of the script block, without the <script> tags, and paste it into a JSON linter. A linter reports the exact character position of a missing comma, an unclosed brace or a bad escape, which is faster than reading a long block by eye.

Start with the live URL so you test what Google actually receives. If the live page parses but Search Console still shows the error, the report is showing the last crawl; test the URL in URL Inspection and use Test live URL to confirm the current version.

Why do CMS plugins cause it?

Most unparsable blocks come from a plugin or theme generating JSON from user content without escaping it. The code is usually valid until a real product name, a migration or a second plugin is added.

  • Unescaped quotes in product names. A product called 12" Pizza Pan or a title with a double quote is inserted into a JSON string without escaping, which closes the string early and breaks the block. Escape " as \" in the generator, or use a plugin that encodes values correctly.
  • Trailing commas. Some page builders and hand-edited snippets leave a comma after the last property, which is valid JavaScript but invalid JSON. Remove the trailing comma or lint the output.
  • Two plugins writing the same block. An SEO plugin, a theme and a page builder can each output an Organization, Product or BreadcrumbList block with different values. Duplicate unique properties or two competing blocks produce errors, so keep one source for each type.
  • Raw HTML in a field. A description that contains a line break or an unescaped special character can break a JSON string. Strip or escape newlines and control characters.

The same rules that make a schema markup block valid make it parsable: valid JSON, straight quotes and one source per item. A broken block does not earn rich results, and it also stops the whole item being read, so fix it before you tune the fields.

Before and after JSON-LD

The before block fails because the product name contains an unescaped quote and the object has a trailing comma. The after block is valid JSON.

// Before: invalid JSON
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "12" Pizza Pan",
  "brand": { "@type": "Brand", "name": "Example" },
}

// After: valid JSON
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "12\" Pizza Pan",
  "brand": { "@type": "Brand", "name": "Example" }
}

Wrap either object in <script type="application/ld+json"> and </script>. The second block parses and the Product item can be read.

How do I validate the fix in Search Console?

Confirm the live page parses, then press Validate fix in the report. Validation asks Google to recheck the affected items; it does not guarantee a rich result.

  1. Re-test the live URL

    Run the page through the Rich Results Test and validator.schema.org again. Both should show parsed items and no syntax error before you ask Google to recheck.

  2. Press Validate fix

    Open the Unparsable structured data report, select the affected item and choose Validate fix. Google rechecks the URLs and tracks progress in the report.

  3. Wait and recheck

    Validation can take days to weeks. If the error returns, some pages still serve the old template or a cached copy, so fix the remaining source and validate again. The Page indexing report covers the indexing side if the page is also not being indexed.

Once the block parses, check that the rich result actually appears. Our schema markup guide covers the fields a valid item still needs before it can earn an enhancement.

Questions and answers

Unparsable structured data questions

Does unparsable structured data affect rankings?

Not directly. Structured data is not a ranking factor, and a parse error does not remove the page from search. It does mean Google ignores the item, so the page cannot get rich results from it, which can reduce clicks.

What is the difference between unparsable and invalid structured data?

Unparsable means the syntax is broken, so Google cannot read the item at all. Invalid usually means the item is readable but a required property is missing or the value is wrong. A parse error must be fixed first, because nothing in the block is read until it parses.

How long does it take to clear the error after a fix?

There is no fixed time. After the live page parses, press Validate fix in the report. Google says validation can take days to weeks, and the error clears only after Google recrawls the affected URLs.

Can I fix unparsable structured data in Google Tag Manager?

Yes, if the markup is injected by a tag. Fix the tag's JSON, then publish the container and test the live URL with the Rich Results Test. If a plugin also writes the same block, remove one source so the duplicate does not come back.

About this article

Written by the MrKeyword team, who build an SEO workspace on first-party Search Console and Bing data. Outside facts link to their original source below. We update this page when the product or the sources change.

Sources

  1. Structured data general guidelines — Google Search Central on supported formats, valid markup and how Google reads structured data
  2. Structured data reports — Search Console Help on enhancement reports and unparsable structured data errors
Keep reading

More on technical SEO, plus the feature and free tool for the same job. All technical SEO guides →

Fix the syntax error at the source.

Check any URL for valid JSON-LD and every structured data block with the free schema markup validator. Free plan for one website, no card; paid plans from $10 a month.