Rich Snippet Fixes: From Eligible Markup to Results in Search
Rich snippets, which Google calls rich results, are the search listings that show extra detail such as star ratings, prices, cooking times or event dates. Getting one takes two things: markup that makes the page eligible, and Google choosing to show the enhanced listing for a particular search.
The Rich Snippets Suite finds which rich result types each page is eligible for, validates the markup, previews how the result could look and tracks which rich results actually appear over time. This page explains the gap between eligible and shown, and links the fix for each finding.
Valid, eligible, shown: three different states
Most confusion about rich snippets comes from treating three separate states as one. A page can pass one stage and stall at the next, and each stage has different causes and different fixes.
- Valid. The structured data parses and uses real schema.org types and properties. This is necessary but says nothing about Google features.
- Eligible. The markup meets the requirements of a specific Google rich result: the right type, every required property, values in the right format, and content that follows Google's policies for that feature. Google's Rich Results Test and the Suite both report this.
- Shown. Google actually displays the rich result for a real search. This depends on the query, the device, what else is on the results page, and Google's view of the page and the site. No tool can guarantee it.
The findings in the Suite follow the same split. Errors block eligibility and are fully in your control. Coverage and display findings are about what Google does with eligible pages, and the fixes there are about quality, relevance and policy rather than syntax.
Which rich results are still worth pursuing
Google has cut back several rich result types in recent years. Chasing a feature that no longer appears for your kind of site wastes effort, so check the current position before starting. As of this update:
| Rich result | Current position | Suits |
|---|---|---|
| Product snippets and merchant listings | Widely shown: price, availability, ratings, shipping and returns details | Any site selling products |
| Review snippets (stars) | Shown for eligible types; self-serving reviews of your own business are not eligible | Products, recipes, books, software, courses and similar items |
| Recipe | Shown, including in recipe carousels on mobile | Food sites and recipe pages |
| Event | Shown in Google's event listings for eligible events | Venues, promoters, ticket sellers |
| Job posting | Shown in Google's job search experience | Employers and job boards |
| Breadcrumb | Widely used in listings | Almost every site |
| FAQ | Limited since 2023 to well-known, authoritative government and health websites | Very few sites |
| HowTo | No longer shown by Google since 2023 | None in Google; the markup is still valid schema.org |
Google has also retired several less-used types, and it announces changes on its Search Central blog. If a finding refers to a feature you depend on, check Google's current documentation before investing more work in it.
The fix guides
Each guide covers one Suite finding, what causes it and what you can realistically do about it.
Getting and staying eligible
Fixing eligibility-blocking errors covers invalid markup and missing required properties that take a page out of the running entirely. Fixing rich result coverage drops covers what to check when Search Console shows fewer valid items or fewer impressions with a rich result than before, and how to tell a site change from a Google change.
Eligible but not appearing
Fixing eligible-but-not-displayed pages covers the quality, relevance and competition reasons Google may leave a listing plain, and what improves the odds.
Specific result types
Fixing review and rating snippets covers where reviews must appear, genuine rating counts and the rules on self-serving and third-party reviews. Fixing recipe carousel inclusion covers images, times, ingredients, instructions and ratings for recipe pages. Fixing HowTo step results explains what happened to HowTo results in Google and what still helps instructional pages. Fixing FAQ rich result eligibility explains the 2023 restriction and when to keep FAQ markup without expecting a rich result. Fixing event, job and product results covers the minimum properties for each of those three types.
By platform and site type
WordPress covers SEO plugin settings, schema block plugins and page builders. Shopify covers product results, review apps and offer and availability gaps. Content sites covers recipe, article and instructional pages on any platform.
Policy problems that remove rich results quietly
Some pages have flawless markup and still never get a rich result because they break a content policy. These problems do not show up as syntax errors, so they are easy to miss.
- Markup describing hidden content. Structured data must describe what visitors can see. Ratings, FAQs or prices that appear only in the markup are against Google's guidelines.
- Self-serving reviews. Reviews that a business collects about itself and marks up on its own site, as a LocalBusiness or Organization, are not eligible for review stars. Reviews of individual products can be.
- Aggregated ratings with no reviews behind them. An
aggregateRatingneeds real ratings from users that visitors can check. - Wrong page for the markup. Recipe or Product markup on a category page that lists many items, or Event markup for something that is not a scheduled event such as a voucher or an ongoing sale.
- Expired content. Job postings past their closing date and events that have ended should be removed or updated.
Measuring what actually appears
The Suite tracks rich result coverage over time. Google Search Console adds your own data from Google's side, and the two together show whether a change is yours or Google's.
- Enhancement reports in Search Console list valid items and items with issues for each rich result type Google found on your site. A fall in valid items usually means something changed in your markup.
- The Performance report can be filtered by search appearance to show clicks and impressions for listings that had a rich result. A fall in impressions with steady valid items points to a change in how often Google shows the feature rather than a markup problem.
- The URL Inspection tool shows what Google saw on its last crawl of a single page, including detected structured data.
Allow time after a fix. Google needs to recrawl the page before reports change, and for a large site it can take weeks for every page to be revisited. Requesting indexing for a few key URLs speeds up confirmation that the fix works, but it does not speed up the whole site.
Which findings to fix first
- Manual actions and policy problems. These can block rich results site-wide, so rule them out first.
- Blocking errors on revenue pages. Product, event and job pages with missing required properties lose eligibility completely.
- Sudden coverage drops. A large drop usually has one cause, often a theme, plugin or template change, and one fix restores many pages.
- Review markup. Stars are among the most visible enhancements, but only where the rules allow them.
- Eligible pages not shown. Work on content quality and specificity once the technical side is clean.
- Restricted features. Stop spending time on FAQ or HowTo results unless your site is in the narrow group still eligible.
A sensible order of work
- Run the Rich Snippets Suite on a sample of pages from each template to see which result types each is eligible for.
- Check Search Console's Manual actions report and the enhancement reports for your site.
- Fix blocking errors at the template or plugin level, starting with product, event and job pages.
- Review every rating and review in your markup against the policy rules above.
- Remove markup for features you cannot get, or keep it knowingly if it still describes the page accurately.
- For eligible pages with no rich result, improve the content and make the markup as specific and complete as the page allows.
- Re-run the Suite and watch Search Console over the following weeks as Google recrawls.
The Rich Snippets Guide covers the Suite in depth. For building or repairing the markup itself, see the Schema Builder Guide and the Schema Debugger Guide; for how a listing looks in search, see the SERP Preview Guide.
1. Why is my page eligible but showing no rich result?
Eligibility means Google could show a rich result, not that it will. Google decides per search, based on the query, the device, the other results and its assessment of the page and site. Pages that are new, thin or rarely clicked often stay plain for a while. Make sure the markup is complete and specific, that the content is genuinely useful, and that no policy problem is holding it back. Then give it time.
2. How long does it take for rich results to appear after adding markup?
There is no fixed time. Google has to recrawl the page, process the markup and then decide to show the result for relevant searches. For a page Google visits often, changes can show within days; for rarely crawled pages it can take weeks. Using the URL Inspection tool in Search Console to request indexing can speed up the first step for important pages, but it does not guarantee display. Keep an eye on the enhancement report for that type.
3. Can I get review stars for my business in Google results?
Not from your own website's markup about your own business. Google stopped showing review stars for LocalBusiness and Organization reviews that a business publishes about itself in 2019, because they are self-serving. Stars can still appear for reviews of specific items such as products, recipes or software. Stars for a business itself usually come from Google's own reviews in your Business Profile, which are handled separately from markup and cannot be added by editing your pages.
4. Why did my FAQ rich results disappear?
In August 2023 Google limited FAQ rich results to well-known, authoritative government and health websites. For almost every other site they stopped appearing, whatever the quality of the markup. That was a policy change rather than a fault on your site. You can leave FAQPage markup in place if it accurately describes questions shown on the page, but do not expect a rich result from it and do not spend time trying to restore one.
5. Do rich snippets improve rankings?
Google has said structured data is not a general ranking factor, so rich snippets do not move a page up the results by themselves. What they can do is make a listing more informative and more noticeable, which may affect how many people click it. The effect varies a lot by query and industry, so measure it in Search Console for your own pages rather than relying on figures quoted for other sites.
6. Why does the Rich Results Test pass but Search Console shows errors?
The two look at different things at different times. The Rich Results Test checks one URL as it is right now. Search Console reports on what Google found when it last crawled each page, which may be days or weeks old, and covers every page on the site. If you have just fixed a template, Search Console will show the old errors until those pages are recrawled. Use Validate fix in the report to prompt a recheck.
7. Is it worth adding markup for rich results Google no longer shows?
It depends on whether the markup describes the page accurately. HowTo and FAQPage are still valid schema.org types, and other search engines or tools may read them, so accurate markup does no harm. But do not add them expecting a Google rich result, and do not keep inaccurate or padded markup for a feature that no longer exists. Put effort first into types Google still shows for your kind of site, such as products or events.
The Rich Snippets Suite identifies every rich result type your page is eligible for, validates the schema, previews how the result could look and tracks the rich result coverage your pages actually get in Google over time.
Run the Rich Snippets Suite →