"Unparsable structured data" email from Google Search Console: what it means
By Michael Broadbridge. Last checked 14 November 2026 on Google Search Console.
Short answer
The email means Google found structured data on some pages that it could not read, usually because of one stray comma or quote mark. It does not stop those pages being indexed, but none of the details in the broken block count. Find the pages in the report, fix the code, then click Validate fix.
Symptoms
You may see one of these messages:
Unparsable structured data
Invalid JSON document
Parsing error: Missing ',' or '}'
Parsing error: Missing '}' or object member name
Parsing error: Missing ',' or ']' in array declaration
Parsing error: Missing ':'
Bad escape sequence in string
- You had an email from Search Console about new Unparsable structured data issues on your site.
- The Unparsable structured data report has appeared in Search Console, with one or more errors listed.
- Star ratings, prices or other extra details have dropped out of your Google results.
- The Rich Results Test shows a parsing error for a page instead of a list of detected items.
Causes, most likely first
Text pasted into a theme or plugin field
Some themes and plugins copy what you type in a setting straight into the structured data. A quote mark, a line break or an extra comma in that text can break the code around it.
A trailing comma
JSON-LD does not allow a comma after the last item in a list. One left at the end, often after someone removed a line, is enough to stop the whole block being read.
A broken app or plugin snippet
An app, plugin or tracking tool that adds its own structured data can output broken code, especially after an update or after it has been uninstalled and left code behind.
Two scripts merged together
When two blocks of structured data are pasted into one, or a closing bracket goes missing during an edit, the result is no longer valid JSON.
How to fix it
What the email means
Structured data is code in the page, usually a block of JSON-LD, that describes the page to Google in a fixed format: a product and its price, a business and its address, an article and its author. It is what makes star ratings and other extra details possible in search results.
Unparsable means Google could not read the code at all, because of a syntax error. When one character breaks JSON-LD, the whole block fails, so Google cannot tell what type of structured data it was meant to be or use any of the details in it.
Search Console only reports on pages Google has indexed, so the pages in the report are already in Google. The error affects the structured data on those pages, not whether they are indexed.
Find the affected pages and the error
- Sign in to Search Console and open the Unparsable structured data report. It only appears when Google has found unparsable structured data on the site.
- Click an error row to see its name and a list of example pages. Note the error name, such as Parsing error: Missing ',' or '}'.
- Copy one of the example pages and test it in Google’s Rich Results Test at search.google.com/test/rich-results. It shows whether the page has a parsing error and which error it is.
- Inspect the same page with the URL Inspection tool in Search Console and use Test live URL to see what Google finds on the page as it is now.
- Open the page in your browser, view the page source and search for application/ld+json. Each match is the start of a block of structured data. Read through each block for the problem.
If every page of one type is listed, such as every product page or every page on the site, the broken code is almost always in the theme, template or a plugin setting, not in each page.
Fix the code
- Work out where the broken block comes from. Check theme settings, SEO plugin settings and app settings for the text that appears near the error, such as a business name, address, opening hours or map position.
- If the error is in text you entered, retype it in the setting. Remove line breaks, and remove quote marks or replace them with a different character such as an apostrophe.
- If the error is a trailing comma, remove the comma after the last item before the closing bracket.
- If the block comes from an app or plugin, update it, then check its settings. If it still outputs broken code, contact its support team or switch off its structured data option.
- Test the page again in the Rich Results Test. Repeat until the parsing error has gone and the test lists the items it found.
Google’s advice for an error that is hard to find is to start from an empty block and add the content back piece by piece, testing as you go. Fixing a parsing error can also reveal other warnings or errors that were hidden before, so check the full test result.
Tell Google it is fixed
- Go back to the error in the Unparsable structured data report.
- Click Validate fix on the error details page.
- Wait. Google rechecks a sample of pages, and validation can take two weeks or more. Do not click Validate fix again until it has passed or failed.
- Search Console emails you when validation passes or if the problem is still there.
If that didn’t work
There is more than one broken block
A page can have several blocks of structured data from the theme, plugins and apps. Search the page source for every application/ld+json and test the page again after each fix.
The page is cached
A caching plugin, host or content delivery network may still be serving the old page. Clear the cache, then test the live page again.
The error is in microdata or RDFa, not JSON-LD
Some older themes add structured data as attributes in the HTML instead of a script block. Google’s list of errors includes ones for this, such as a reference to an item that does not exist.
An example we fixed
A business pasted a map position into a theme setting so its address would show on a map. The theme copied that setting into the structured data, and the pasted text included a character JSON-LD does not allow in that place. The whole block failed to parse on every page, and Search Console sent the Unparsable structured data email. Correcting the value in the theme setting fixed every page at once.
When to get help
Stop if the broken code is in a theme file or a plugin you cannot change through its settings, or if fixing one error keeps revealing others. Editing theme code by hand can break the page layout, and a mistake in a template can break the structured data on every page at once.
What a developer would check
- Which theme file, plugin or app outputs each block of structured data on the affected pages.
- How theme and plugin settings are inserted into the JSON-LD, and whether the text is escaped.
- Whether two tools are adding the same structured data, such as a theme and an SEO plugin both describing the business.
Describe the problem in your own words and WebFixed gives you an instant fixed quote. Nothing is charged until you accept it.
Related questions
- Will unparsable structured data stop my pages showing in Google?
- No. Search Console only reports on pages Google has indexed, so the pages in the report are already in Google. What you lose is the chance of star ratings, prices and other extra details showing for those pages until the code is fixed.
- How long does Validate fix take?
- Google says validation can take two weeks or more, depending on how often it crawls your site. You can check the status on the error details page in the report.
- Do I need to fix every page in the list one by one?
- Usually not. Most of these errors come from a theme, template or plugin setting, so one fix corrects every page that uses it. Test a few of the listed pages afterwards to be sure.
Written by Michael Broadbridge, Founder of Webgro. First published 14 November 2026. Last checked 14 November 2026 on Google Search Console.