Rich snippets: what they are and which still show
Rich snippets is the old name for rich results. The types Google still shows, the markup each needs and why your page may not get one.
·5 min read
Rich snippets is Google's old name for rich results: search listings that show extra information pulled from a page's structured data, such as review stars, a price, a recipe's cooking time or a breadcrumb trail. Google renamed the feature to "rich results" in 2017, so the two terms describe the same thing. What has changed since is which types Google still shows, and that list is shorter than most articles admit.
The naming history matters for one practical reason. A page can have valid schema and still get no rich result, because the type is no longer eligible or because the site does not meet the conditions.
Rich snippets, rich results and featured snippets
| Term | What it means | Comes from markup? |
|---|---|---|
| Rich snippet | The old name for a rich result | Yes |
| Rich result | A listing enhanced with structured data | Yes |
| Featured snippet | A quoted answer in a box above the results | No |
| Knowledge panel | An entity box about a person, brand or place | Partly |
A featured snippet is chosen by Google from page content. No markup earns one. A rich result needs markup, and the markup only makes the page eligible; Google still decides whether to show it.
For the full comparison, read rich snippets vs rich results and featured snippets.
Which rich results Google still shows
Google's search gallery lists the types it supports. The ones most sites can use:
| Type | Typical result | Required properties |
|---|---|---|
| Article | News or blog result with a larger image | headline, image, datePublished, author |
| Breadcrumb | Path shown under the URL | itemListElement |
| Product | Price, availability and rating | name, offers or review/aggregateRating |
| Review snippet | Stars for a book, recipe, movie, product or local business | itemReviewed, reviewRating |
| Recipe | Image, cook time and rating in a recipe carousel | name, image |
| Event | Date, place and ticket status | name, startDate, location |
| Video | Thumbnail and key moments | name, thumbnailUrl, uploadDate |
| Local business | Details in a knowledge panel | name, address |
| Organization | Logo and brand details | name, url, logo |
| Software app | Rating and price for an app | name, applicationCategory, offers |
| Job posting | Job details in the jobs experience | title, datePosted, hiringOrganization |
| Q&A | Question and answer page | mainEntity |
| Discussion forum | Threaded forum content | author, datePublished, text |
| Profile page | Person or organization profile | mainEntity |
| Dataset | Entry in Google Dataset Search | name, description |
| Course list | Course carousel | name, description, provider |
| Vacation rental | Rental details | name, address, image |
The gallery changes. Check it before you build markup for a new type.
FAQ and HowTo are mostly gone
Two types that dominated SEO advice for years no longer work the way the articles say.
- FAQ rich results are limited to well-known, authoritative government and health websites. A normal business adding
FAQPagemarkup will usually get no rich result, though the markup can still help other systems understand the page. - HowTo rich results were deprecated. The markup is still valid schema.org, but Google no longer shows the step-by-step treatment.
Adding either is not harmful. Expecting stars or an expandable FAQ from them is.
What each type needs in practice
The required properties are the minimum. These are the mistakes that show up in validation.
- Product: a price without a currency, or an
offersblock with nopriceorpriceCurrency, fails. Reviews must be real and visible on the page. - Article:
authorshould be aPersonwith aname, not a string.datePublishedmust be an ISO 8601 date. - Breadcrumb:
itemListElementneeds apositionon every item, starting at 1. - Event:
startDatemust include a timezone or be a full date-time. A past event is not shown. - Video:
thumbnailUrlmust resolve to an image, anduploadDatemust be real. - Local business:
addressneeds aPostalAddress, not a single string.
A validator catches missing fields. It does not catch markup that describes something the page does not show. That is a spam policy issue, not a schema issue.
How to check a page for rich snippets
- Run the Rich Results Test. It reports which Google features the URL is eligible for and which required fields are missing. Our rich results test guide walks through the report.
- Validate the JSON-LD itself. A syntax error stops every type on the page. Paste the block into a schema validator and read the parse error before the warnings.
- Check the rendered HTML. If the markup is added by JavaScript, confirm it appears in the rendered DOM and not only in the source.
- Open the Enhancements reports in Search Console. They show valid, invalid and warning items by type, with the URLs affected.
- Look at the live result. Search the exact page title. If a rich result appears for a competitor and not for you, compare their markup and their page.
Our schema checker fetches a URL, extracts every JSON-LD block and reports the types, required fields and parse errors in one pass.
Why a valid page still gets no rich result
Eligibility is not a guarantee. Google lists several reasons a valid page may show a plain result.
- The type is not eligible for the query. Review stars do not appear for every search.
- The page is new or not indexed. A rich result cannot appear before the page does.
- The markup is hidden. Content in the markup must be visible to users.
- The reviews are self-serving. A business marking up its own reviews about itself can lose the feature.
- The site lacks trust. Google may limit rich results for a site with quality or spam problems.
- The type was deprecated. See FAQ and HowTo above.
- The markup conflicts. Two blocks describing the same entity with different values can cancel each other.
None of these are fixed by adding more markup. Fix the page or the trust signal first.
Check the markup you already have
Our schema checker fetches any public URL, lists every JSON-LD type it finds and names the fields Google requires that are missing. Run it on your homepage, your money page and one article. If you are starting from nothing, add schema markup shows the blocks to write first, and FAQ schema explains what the markup still does when the rich result does not appear.





