A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://support.google.com/webmasters/answer/7552505 below:

Rich result report overview - Search Console Help

Rich result report overview

Rich result reports in Google Search Console show structured data (and its validity) found on your site. Valid structured data is eligible to appear as rich results in Google Search. Search Console provides a separate report for each type of rich result found on your property. 

The reports aren’t a comprehensive list of all detected items. They show a sample of detected items to help assess the quality of your structured data. Use the URL Inspection tool to see if URLs not listed in the report have detected the structured data.

Monitoring Rich Results in Search Console - Google Search Console Training

These reports allow you to:

Find and open the report

To access rich result reports:

  1. Open Search Console.
  2. Locate the reports under Enhancements in the navigation bar. For product snippets and merchant listings, reports can be found under Shopping.

A rich result report for a type will appear only if:

If a report is missing for a supported type, see how to debug missing structured data.

Supported rich result reports

Google Search Console supports reports for the following rich result types:

Navigating a rich result report

Each rich result report includes a landing page and an issue details page.

Landing page

The chart shows how many valid and invalid structured data items Google found on your site over time. 

A valid item is an item that doesn’t have any critical issues and can appear on Google as a rich result. An invalid item has at least one critical issue preventing it from appearing as a rich result.

The two tables include:

Valid items are listed when you click View data about valid items below the chart on the landing page.

To see all issues affecting a single structured data item, you can inspect the page that hosts the URL, or use the Rich Results Test.

Issue details page

Select an issue row in the landing page table to open a page showing details for the selected issue. An issue can affect structured data items on different pages, multiple structured data items on a single page.

The issue details page includes:

Issue title and help link Short description and link to documentation. State Validation status if validation was started. If all issues of this type are resolved, but a new instance of this issue appears within 90 days, the date will be the original first detected date, not the date of the new instance. First detected Initial detection date of the issue. Examples List of affected rich results with options to inspect errors in the code. Note that it's possible that the examples list might omit rows for various reasons, such as issue instances that happened after the last crawl of your site, or instances that affect more than 1,000 items (the table is limited to 1,000 rows). Last crawled  The most recent date Google crawled the page with the issue. Select the issue in the examples table for more details. Click the inspect icon    next to the URL to run the URL Inspection tool for error details, and indexed and live test results. Common Questions Why are structured data item totals lower than valid + invalid totals?

The total number of items shown in the report might be lower than the actual known number of items on your site, for various reasons. Therefore, the total of valid + invalid items might be lower than the number of items actually known to Google. 

To confirm if specific items are indexed, inspect the page in Search Console under Enhancements.

Why do issue totals exceed the valid + invalid totals?

One item may have multiple issues (critical and non-critical), causing it to appear multiple times in issue tables but only once in the invalid tab total.

Why can’t there be a "Fix this issue" button?

The structured data resides on your website, not Google’s servers. Fixes must be applied to your site’s source code to resolve issues permanently.


  Was this helpful?

How can we improve it?


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4