Enhancements Reports

What Enhancements Reports Are

Enhancements reports are the Google Search Console section that validates your structured data at scale — one report per feature type (Breadcrumbs, Products, Videos, Merchant listings, and more), each flagging pages as Valid, Valid with warnings, or Error. They're how you find out your Product schema broke on 300 URLs before you lose the rich results those pages were earning.

The stakes are simple: no valid structured data, no enhanced search appearance. A single missing required property can knock a whole template out of rich-result eligibility, and Enhancements is the only place that tells you which property, on which pages, at what scale.

A real example

A dev pushes a template change that drops the price field from your product markup. Nothing looks broken on the page. A few days later the Products enhancement report lights up: 300 URLs flipped to Error with "Missing field 'offers'." Your merchant rich results start vanishing from the SERP. Because GSC grouped the failures by error type, you fix one template, hit Validate Fix, and recover all 300 in a single pass.

Enhancement report types and what they check

You'll only see reports for feature types Google has detected on your site. No Videos report means Google found no video markup to validate — not that your videos passed. The status severity matters too: Errors disqualify a page from the rich result; Warnings don't block eligibility but cost you optional enhancements (like a missing image on an otherwise-valid product).

How to check it on your own site

1. Open Google Search Console and look in the left nav under the Enhancements heading. Each detected feature type is its own line item.
2. Click a report, e.g. Products. Read the trend chart — a sudden spike in Errors almost always maps to a deploy date.
3. Scroll to the Details table. It groups pages by exact error message, so you see the shared root cause instead of 300 individual problems.
4. Click an error row to get the list of affected URLs, then use Inspect URL or Google's Rich Results Test to see the failure on a live page.
5. Fix the underlying template or markup, redeploy, then return to the error row and click Validate Fix. Google recrawls the sample and re-checks the whole set.
6. Confirm recovery by watching Errors fall and cross-referencing the Search Appearance report for the corresponding rich results returning.

Common mistakes and how to fix them

• Treating warnings like errors. Warnings don't block the rich result — they're optional fields. Fix: triage Errors first; they're the ones actually costing you appearances.
• Fixing one URL and calling it done. These errors are almost always template-wide. Fix: patch the template once, then Validate Fix to sweep the whole batch.
• Skipping Validate Fix. Without it, Google recrawls on its own slow schedule and your report stays red for weeks. Fix: click Validate Fix to trigger a prioritized recheck.
• Assuming no report means you're clean. A missing feature report usually means Google found no markup of that type — a bigger problem than errors. Fix: verify the markup actually exists with the Rich Results Test.
• Validating before the fix is live. If the corrected markup isn't deployed and crawlable, validation fails and you burn the attempt. Fix: confirm the fix is live on production first, then validate.

FAQ

Where do I find the Enhancements reports?

In Google Search Console's left navigation, under the Enhancements heading. You'll see a separate report for each structured-data feature Google detected — Breadcrumbs, Products, Videos, and so on. Sites with no eligible markup see no reports there.

What's the difference between an Error and a Warning?

An Error disqualifies the page from that rich result — fix these first. A Warning flags a missing optional field; the rich result can still show, just without the extra enhancement. Both are worth cleaning up, but Errors are the ones bleeding appearances.

How is this different from the Search Appearance report?

Enhancements validate whether your structured data is correct; Search Appearance shows whether that valid markup is actually rendering in the SERP. Use Enhancements to fix, then Search Appearance to confirm the payoff.

What does "Validate Fix" actually do?

It tells Google to recrawl a sample of the affected URLs on a prioritized schedule and re-run validation against your corrected markup. If the sample passes, Google rolls the fix out across the full set. Skip it and you wait on the default crawl cadence.

Why did errors appear right after a site update?

A template or plugin change most likely dropped or malformed a required property across every page using that template. That's why errors arrive in bulk on a deploy date. Diff the markup before and after the release, fix the template, and revalidate. For deeper schema work, see our schema markup reference.