What Are Rich Snippets? A Plain-English Guide
What are rich snippets? Learn how they work and why they make Google results easier to trust.
Rich snippets are enhanced Google result listings that show extra details like ratings, prices, dates, or images instead of only a plain blue link. They are usually powered by structured data on the page, but valid markup only makes a page eligible; it does not guarantee the richer display will appear.
What are rich snippets, exactly?
Think of a normal result as a short label and a rich snippet as the same label with a few useful details attached. Google says structured data helps it understand a page and can make that page eligible for a richer appearance in results.
That extra detail might be a product price, a recipe time, a review rating, or a date. It is not a separate kind of website content; it is a different way of presenting information that Google already understands from the page.
“Valid markup makes a page eligible; it does not promise a richer display.”
“Google may show a richer result when the page content, markup, and user need all line up.”
How rich snippets actually appear
Google’s own tools describe rich results as experiences that go beyond the standard blue link. They can include carousels, images, and other non-textual elements, which is why they often feel more noticeable than a plain result.
The important part is that the page has to earn that treatment. Google’s guidelines say the markup should match the main content of the page, the content must be visible to users, and the page must be accessible to Googlebot.
A simple analogy helps here: structured data is like placing neat labels on boxes in a storeroom. The labels do not create the objects inside the boxes, but they make it much easier to identify what is there.
What rich snippets can show
Different page types can surface different kinds of extra details. Product pages may show price, availability, shipping, and return information; article pages may surface better title text, images, and dates; local business pages may show hours, directions, and actions such as booking or ordering.
For question-and-answer content, Google supports Q&A structured data for pages that present a single question with answers beneath it. For data-heavy pages, dataset markup can help Google understand the dataset and show more useful metadata.
This is why rich snippets are so useful for practical pages. A shopper wants price and stock status. A reader wants publication date and headline clarity. A visitor to a local business wants hours, location, and a fast next step.
What rich snippets cannot do
They cannot force a page into a richer display just because the code is correct. Google explicitly says structured data enables a feature to be present, but it does not guarantee that the feature will be shown.
They also cannot rescue thin or misleading pages. If markup is incorrect, hidden from users, or unrelated to the visible content, Google may ignore it or treat it as spammy.
“Rich snippets are a presentation layer, not a promise.”
Another common mistake is assuming every old schema pattern still works the same way. Google removed How-to rich results and sharply reduced FAQ rich results visibility in 2023, and later documentation updates continued to note the simplification of result-page features.
That matters because outdated advice is still everywhere. A page can have valid FAQPage markup on schema.org, but Google now shows FAQ rich results regularly only for well-known, authoritative government and health websites.
How to get rich snippets onto a page
Start by choosing the correct structured data type for the page. Google says most structured data uses schema.org vocabulary, and JSON-LD is the recommended format. Microdata and RDFa are also supported.
Then make sure the markup matches what the page actually shows. If your page says a product costs one amount but the markup says another, or if the key details are hidden from users, the page may fail eligibility or be treated as misleading.
Next, test the page before you assume it is ready. Google’s Rich Results Test is the official tool for checking what rich results a page can generate, and the URL Inspection tool helps you see how Google reads the live page.
After that, monitor real pages over time. Google recommends deploying a few pages first, then using URL Inspection and allowing time for recrawling and reindexing; markup can break later when templates change or product data changes.
“Correct code is only the starting line.”
Rich snippets vs featured snippets vs regular snippets
These terms get mixed up all the time, but they are not the same thing. Google’s featured snippets are special boxes where the descriptive snippet is shown first, often because the page answers the question well; rich snippets, by contrast, are enhanced result appearances driven by structured data.
Here is the cleanest way to think about them.
| Type | What it is | How it usually appears | What drives it |
| Regular snippet | A standard result with title, URL, and summary | Plain listing | Page content and Google’s snippet generation |
| Rich snippet / rich result | A result with extra details such as prices, ratings, dates, or images | Enhanced listing or visual result | Structured data on the page plus Google’s eligibility rules |
| Featured snippet | A highlighted answer box taken from a page | Box above or among results | How well the page answers the query |
The practical difference is simple. Rich snippets help explain a page; featured snippets try to answer a question directly.
Common mistakes people make
One mistake is adding markup because a plugin suggests it, then forgetting to check whether the page content actually supports it. Google’s guidelines are strict about matching structured data to visible content, so “close enough” is usually not good enough.
Another mistake is chasing every schema type under the sun. A better approach is to mark up the page type that truly fits the page, such as Product, Article, LocalBusiness, QAPage, or Dataset, and then keep that data accurate over time.
A third mistake is assuming that rich snippets are permanent. Google’s documentation shows that it regularly simplifies result-page features and retires support for some types, so a page that earns a richer display today may not display the same way forever.
FAQ
Do rich snippets improve click appeal?
Yes, often they do, because they give people more context before they click. Google’s rich-result and snippet docs are built around the idea that extra detail can make a result more informative and useful.
Is structured data required for rich snippets?
Structured data is the usual path to eligibility, and Google’s documentation says to use it for richer result appearances. Without it, a page is far less likely to qualify for those enhanced formats.
Which format should I use?
JSON-LD is Google’s recommended format. Google also supports Microdata and RDFa, but JSON-LD is the default choice for most pages because it is easier to manage.
Why is my rich snippet not showing?
The most common reasons are invalid markup, markup that does not match visible content, pages blocked from crawling, or a feature type that is no longer broadly shown. Google’s guidelines and deprecation notices cover all of these possibilities.
Are FAQ rich snippets still common?
Not for most sites. Google now shows FAQ rich results regularly only for authoritative government and health websites, and it has reduced or removed support for several other legacy rich-result types.
Key Takeaways
- What are rich snippets? They are enhanced Google result listings that show extra details beyond a plain blue link.
- Structured data is the main way to make a page eligible, and JSON-LD is Google’s recommended format.
- Eligibility does not guarantee display; Google still decides whether the richer format fits the page and the query.
- Rich snippets can show useful details such as prices, availability, dates, ratings, and business information.
- How-to rich results are deprecated, and FAQ rich results are now heavily limited.
- The safest markup is the markup that matches what people can actually see on the page.
- Use the Rich Results Test and URL Inspection tool to check what Google can read before and after publishing.
