Unparsable Structured Data in Search Console: How to Find and Fix It

This guide shows you how to read the unparsable structured data report in Google Search Console, what each parsing error means in plain English, and how to fix the template that usually causes it. When I check schema for clients, one broken plugin setting or a stray quote in a custom field is behind most of these reports.

What does unparsable structured data mean?

It means Google found structured data on your site that it could not parse because of a serious syntax error, so the markup is ignored instead of being checked for rich result eligibility. That is how Google’s Unparsable structured data report help describes it.

This is different from the rich result reports such as Product or Breadcrumb, which flag missing or invalid properties in markup Google could read. Here the problem is earlier: the code is not valid JSON, Microdata or RDFa, so Google cannot even tell what type of item it is.

That also means these errors can hide other problems. Once the syntax is fixed, the markup may start appearing in the normal rich result reports with its own warnings, so check those reports again after the fix.

Google’s help also notes that when the same error appears on many pages, the cause is usually a template error. That matches what I see. You rarely fix these one page at a time.

How do I fix a parsing error missing comma in JSON-LD?

You fix “Parsing error: Missing ‘,’ or ‘}'” by finding the line where one property ends and the next begins without a comma, or where an object is not closed, and adding the missing character. Most JSON-LD errors are one character out of place.

This reference table lists the errors I see most often, with the usual real cause:

Unescaped quotes from user entered content are the classic trap. A product name such as a 12″ pizza, review text or FAQ answer containing a double quote breaks the whole JSON block if the plugin or theme does not escape it. The quote ends the string early, so Google then reports a missing comma or brace on that line even though the real fault is the quote.

How do I fix unparsable structured data step by step?

You fix it by finding which template produces the broken markup, correcting the syntax at the source, and testing the output before asking Google to recheck. Follow these steps.

1. Open the report. In Search Console, open the Unparsable structured data report. Click each error type to see example URLs and the line Google flags.
2. Group by template. Check whether the URLs share a page type, such as all products, all posts or all location pages.
3. Test one URL. Run it through the Rich Results Test, which reports the same syntax problems and shows the code Google rendered.
4. Find the source. Is the markup from an SEO plugin, the theme, a reviews plugin, a page builder widget or hand written code in the header? Disable or check them one at a time on a staging copy if needed.
5. Isolate the error. Google’s help suggests starting from an empty object and adding content back piece by piece until the error returns. That works well for long hand written blocks.
6. Fix the source, not the output. Edit the template, plugin setting or custom field that generates the broken line, so every page is repaired at once.
7. Remove duplicates. If two tools output the same type, such as two Organization blocks, keep one.
8. Clear caches and confirm the live HTML now contains the corrected markup.

If you write markup by hand, generating it with a tool reduces typing errors. My free FAQ schema generator, for example, outputs JSON-LD with quotes already escaped.

How do I test structured data before Google crawls it?

You test structured data before Google crawls it with the Rich Results Test, which accepts either a live URL or a pasted code snippet, and with the live test in URL Inspection. Google’s structured data general guidelines name both tools for checking compliance.

Pasting the code snippet is the fastest way to test a template change before it goes live. Once deployed, test the real URL too, because plugins, caching or minification can change the output.

Keep expectations realistic. Valid markup makes a page eligible for rich results, but Google states it does not guarantee that structured data will show up in search.

How do I validate the fix in Search Console?

You validate by confirming a clean result in the Rich Results Test for each template, then clicking Validate fix on each error type in the Unparsable structured data report. Each error type is validated separately.

1. Test one URL per affected template and confirm no parsing errors remain.
2. In the report, open an error type and click Validate fix.
3. Repeat for each error type you fixed. Do not click Validate fix again on the same issue while it is running.
4. Allow up to about two weeks. Google may first check a sample of pages, then the rest.
5. If validation fails, open See details, find the URL that caused the failure, fix it and start a new validation. URLs marked Passed or Other are not rechecked.

What does a fixed JSON-LD error look like?

Schema work is part of my content and media SEO service, and for other report types see the Search Console errors guide.

Frequently asked questions

Sources

Facts checked against these official pages. Read how I check facts in my editorial policy.

• Google Search Console Help: Unparsable structured data report
• Google Search Central: General structured data guidelines