Reference guide · search-console · Published 2026-08-16 · 4 min read
Using the Search Console enhancements reports
Search Console enhancement reports: supported rich result types, what item-level feedback means, and how to fix issues.
- ·What the report shows
- ·Active report types
- ·Fix the issues
What the enhancements report shows
The Enhancements section of Google Search Console reports, for each structured data type Google supports, whether your pages can earn rich results. For every item, it reports the state the last time Google crawled it: Valid, Items with issues, or No items. Below the summary, the report links to the page URL that holds the item.
The word "enhancements" is deliberate: rich result support changes over time, and the report tracks only the types Google currently renders in search. It is the structured-data half of the Search appearance reporting. You do not need a report for every feature you mark up; it is most useful exactly where a type earns a rich result, or you are trying to make it one.
Which types are reported
The active types in 2026, with their report names, are the ones Google still displays in search results (the list has shrunk as types deprecate):
| Report | What it checks |
|---|---|
| Breadcrumbs | BreadcrumbList on a page with a visible trail |
| Product snippets | Product + offers, price, and rating where eligible |
| Merchant listings | Merchant and store content |
| Review snippets | Review with an item and aggregate rating |
| Video | Video objects, thumbnails, and VideoObject on pages |
| AMP | AMP pages for non-AMP verticals |
Types that left: HowTo (2023), the June 2025 six-type batch (Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement, Vehicle Listing) from September 2025, FAQ rich results (mid-2026), and Practice Problems (early 2026). The lesson for markup: validate against what is rendered, not against the schema library of two years ago.
Reading the item list
Open an enhancement type and you get a table of items. Each row is a page plus a reported state. The useful reading order:
- Look for Item state (an issue) versus Valid.
- Compare the page URL to the structured data reference for that type, because many "issues" are a missing required property that is easy to spot in the structured data guide.
- Click "Inspect live" to see the page's current markup with the renderer's feedback, not the stale crawl's.
A single page often has one or two item-level issues and the fix is small (a missing content or a price not matching the visible page). The report's job is to isolate those.
Fixing an enhancement issue
- Open the enhancement report and filter to the affected type.
- Inspect live one page to get the exact property names rather than the generic list.
- Fix the source markup (the template or the plugin generating the schema), not just the page.
- Use the URL Inspection tool to request re-crawling after the change and re-validate the item.
The URL inspection request re-crawls and shows the validation status, which closes the loop when the enhancements item flips from "Issues" to "Valid".
When not to chase the report
An enhancement report is a diagnostic, not a ranking lever. Google does not rank you for having valid markup; it renders it. So the effort returns: only fix reports with a type you want the rich result for, keep the ones you do not want off the page, and ignore stale types. The basics and the structured data guides cover the foundations, and the report is the place they are proven.
In short
The enhancements report is the one place Search Console tells you your structured data is understood as a richer object. Read it monthly, fix the few issues, and remember the types on it are a moving target: the current list is the only list that matters.