Google Search Console Drop Rich Result Performance Report
Why Google decided to sunset the rich result search appearance?
Google announced that they are removing the generic rich result filter from the Google Search Console performance report search appearance section. It means that users will no longer to see that how well rich results are performing on the website. Instead, you will drill into each individual rich result that your site supports to see how they are doing.
What is Rich Result?
Rich Results (also known as “Rich Snippets ”) are normal Google search results with additional data displayed. This extra data is usually pulled from Structured Data found in a page’s HTML. Common Rich Snippet types include reviews, recipes and events.
Google said this generic one is no longer required since they have “breakouts for most rich result types.” Google added “in addition, we realize that grouping data for rich results is not ideal, as each type may have a significantly different behavior. Therefore we decided to sunset the Rich result search appearance in Google Search Console.”
So instead of filtering on “rich results” you will filter using the search appearance filter in the performance report on specific types. There are currently 19 supported search appearance types including a few AMP versions, Android app, event, FAQs, how-to, job details, job listings, practice problems, product results, Q&A, recipe rich rich results, recipe gallery, review snippets, special announcements, videos, web light, web story and more to come. The generic Rich Results would show “any type of rich result defined in structured data listed in the search gallery. This includes all rich-result subtypes such as job listing and AMP article rich results showing in the Google Search Console.
Here is the screenshot:
The rich result performance report in Google Search Console is going away on August 1, 2021 from both the interface including the API and this will not impact your website traffic from Google, it is just a reporting change.
Forum discussion at Twitter.