Guide

Structured Data Errors and Lost Rich Results

Structured data errors stop Google from reading your markup, and rich results vanish when it cannot trust what it finds. The fix starts with the Enhancements reports and the Rich Results Test.

Structured data errors are problems in the markup that describes your page to Google, such as missing required fields, wrong types or content that does not match what visitors see. When Google cannot use the markup, the page loses eligibility for rich results like review stars, product details and breadcrumbs. You find the errors in Search Console, confirm them with the Rich Results Test, and fix them at the source.

How to tell structured data is the problem

Rich results disappear for several reasons, and errors are only one. Open Search Console and look in the left menu for the Enhancements section. Each type of markup Google detects on your site, such as Breadcrumbs, Products, Review snippets or Videos, gets its own report. Each report lists valid items, items with warnings and items with errors, with a trend over time.

A sudden jump in errors, or a drop in valid items, close to the date your rich results vanished is strong evidence. A site wide change in template, plugin or theme is the usual trigger.

Common structured data errors

Error typeWhat it meansTypical cause
Missing required fieldA property Google needs for that rich result is absentPlugin outputs partial markup, or a field is blank in the template
Invalid value typeA field holds the wrong kind of value, such as text where a number is expectedPrice with currency symbols, dates in the wrong format
Parsing errorThe markup is broken and cannot be read at allStray commas or quotes in JSON-LD, often from copy and paste
Content mismatchThe markup describes something not visible on the pageHidden reviews, ratings added by hand, or stale prices
Duplicate or conflicting markupTwo sources describe the same item differentlyTheme and plugin both add schema
Policy violationMarkup breaks Google's structured data guidelinesSelf serving reviews, markup for content users cannot see
The most common structured data errors and where they come from.

Errors stop a page qualifying for a rich result. Warnings flag optional fields and usually do not block eligibility, though filling them can help.

Step by step: finding and fixing the errors

1. Read the Enhancements report

Open the report that matches the lost feature. Click an error row to see the affected URLs and the exact issue. Note how many pages share the same error. One template fault often explains hundreds of pages.

2. Test a live page

Paste an affected URL into the Rich Results Test. It shows which rich results the page is eligible for and flags each error. The Schema Markup Validator checks syntax for all schema types, including those Google does not use for rich results.

3. Compare markup to the visible page

Google's guidelines say markup must reflect content users can see. Check that the price, rating, author and dates in the markup match the page. Remove markup for anything that is not on the page.

4. Fix the source, not each page

If a plugin or theme template generates the markup, fix it there. Edit the template, update the plugin, or turn off a second plugin that duplicates the output. Fixing pages one by one when the cause is a template wastes days.

5. Validate the fix in Search Console

After fixing, open the error in the Enhancements report and use Validate fix. Google then rechecks the affected URLs. This can take days or weeks depending on how many pages there are and how often they are crawled.

6. Make sure the pages are crawled

Rich results cannot return until Google recrawls the page. Confirm the pages are indexed with the URL Inspection tool, keep your sitemap current and make sure the fixed pages are not blocked or set to noindex. Our guide on noindex and robots mistakes covers the common blockers.

Why rich results can disappear without any error

Not every loss is a fault. Google changes which rich results it shows. It has limited some types, such as FAQ and HowTo, to narrower sets of sites or removed their display on most results. If your reports show valid markup and the rich result is still gone, the cause may be a Google policy change or a change in what it chooses to show for that query.

Our page on lost featured snippets and rich results separates snippet losses caused by competitors from those caused by your own markup. If your pages are also losing visibility to near copies, check duplicate content fixes too, since conflicting versions of a page can confuse which one carries the markup.

Keep it from breaking again

Test markup in a staging copy before a theme or plugin update goes live. Re-check the Enhancements reports after every template change. Assign one owner for schema on the site, so two plugins are never fighting over the same output. This is part of the regular checks inside our technical SEO fixes work.

When to call for help

Get help when errors reappear after you fix them, when markup is generated by custom code you cannot read, or when rich results vanished with no clear error and no clear policy reason. Those cases need the rendered page, the source and the crawl data compared side by side.

Send us the affected URLs and the report screenshots. A free SEO triage will tell you whether the markup is the cause and what the repair involves.

FAQ

Questions owners ask us

Does fixing structured data guarantee rich results come back?

No. Valid markup makes a page eligible. Google decides whether to show a rich result, and it can choose not to. Fix the errors, then give Google time to recrawl and reassess.

Do structured data errors lower my rankings?

Not directly. Markup helps Google understand a page and can earn rich results, but errors alone do not demote a page. What you lose is eligibility for the enhanced display, which can cut clicks.

Why did my FAQ rich results disappear?

Google limited FAQ rich results to a small set of well known authoritative sites, so most sites no longer get them even with valid markup. Check the Search Console Enhancements reports to see whether the cause is an error or a policy change.

Get started

Tell us where it hurts.

Your site, what changed and when. We reply with a first read on the cause.