What Is a Rich Snippet? Stars, Prices, and Eligibility

Aug 10, 2026 · SEO Glossary

Compare two listings on a product SERP: one shows a title and two lines of grey text; its neighbor shows the same, plus 4.7 stars, 1,214 reviews, "$49," and "In stock." Eye-tracking and CTR studies have shown for years what common sense suggests — the enhanced listing pulls a disproportionate share of clicks for its position. That enhanced listing is a rich snippet, and the difference between the two results is usually about thirty lines of JSON in the page source.

What is a rich snippet, precisely? It's a standard organic result augmented with additional data — ratings, prices, availability, images, dates — that Google extracts from structured data markup on the page. (Google's own docs now say "rich result," an umbrella that also covers bigger units like carousels; "rich snippet" survives as the everyday term for the enhanced listing.)

How a Page Earns One

The pipeline has three gates, and you control only the first two:

1. Valid markup. You add structured data — almost always JSON-LD using schema.org vocabulary — describing the page's entity: a product, a recipe, an event, a job posting. It must include the properties Google requires for that result type.
2. Content parity and guideline compliance. The marked-up data must match what's visibly on the page. Marking up reviews the page doesn't display, or self-serving reviews on your own homepage, violates the guidelines and gets the enhancement dropped — sometimes with a manual action for structured data spam.
3. Google's discretion. Even valid, compliant markup only makes you eligible. Google decides per query whether to show the enhancement, based on the query, your site's trustworthiness, and what it decides serves the searcher. This is the gate people forget: "Search Console says valid, where are my stars?" is expected behavior, not a bug.

What Is a Rich Snippet Still Available in 2026?

The honest version of this list matters more than the optimistic one, because Google has been pruning.

• Alive and valuable: Product (price, availability, ratings), Review stars, Recipe, Event, Job posting, Video, Breadcrumb. For stores and content sites these carry real CTR weight.
• Effectively dead — FAQ: in August 2023, Google restricted FAQ rich results to "well-known, authoritative government and health websites." For everyone else, FAQPage markup no longer produces the expandable Q&A dropdowns in results. The markup isn't harmful, and the on-page FAQ content itself remains useful, but if a guide promises you FAQ dropdowns in the SERP, it's pre-2023 advice.
• Dead — HowTo: deprecated entirely in late 2023. HowTo markup earns nothing now.
• Shrinking: Google reduced sitelinks-style and other enhancements at various points, and AI Overviews at the top of many SERPs have squeezed how often some enhancements appear. Rich results remain worth having — but audit any list of "23 rich snippet types!" against Google's current search gallery before building anything.

Do Rich Snippets Improve Rankings?

No — structured data is not a ranking signal, and Google has said so repeatedly. The win is click-through: for the same position, an enhanced result draws more clicks, and the added detail pre-qualifies them (someone who clicks after seeing "$49" won't bounce at the price). There's a second-order benefit too: the same markup feeds Google's understanding of your entities, which supports things like product listings in the Shopping tab and better matching of your page to relevant queries.

One eligibility rule catches many businesses off guard: review stars don't show for LocalBusiness or Organization markup on your own site — Google classifies self-collected ratings about your own company as self-serving and dropped support for them back in 2019. Stars remain fully available for things you sell or review: products, recipes, books, software. If a competitor's homepage shows stars in the SERP, they're usually coming from a third-party platform's page ranking for the brand, not from markup on the competitor's own site.

Implementation Without the Foot-Guns

Use JSON-LD in a <script type="application/ld+json"> block — Google's recommended format. A minimal product example:

{"@context": "https://schema.org", "@type": "Product", "name": "Site Audit Pro", "offers": {"@type": "Offer", "price": "49.00", "priceCurrency": "USD", "availability": "https://schema.org/InStock"}, "aggregateRating": {"@type": "AggregateRating", "ratingValue": "4.7", "reviewCount": "1214"}}

The recurring mistakes: required properties missing (rating without a count), markup describing a different page than the one it's on, ratings hardcoded years ago and never updated when the review widget was removed, and markup injected by JavaScript that occasionally fails to render. That last one is sneaky — the enhancement quietly disappears and nobody notices for months. Our schema markup guide covers the vocabulary end in depth.

Testing and Monitoring

Google's Rich Results Test validates a URL or a code snippet against the currently supported result types — that's your pre-launch check. After launch, Search Console grows an "Enhancements" section per detected type, reporting valid items, warnings, and errors across the site; a spike in errors after a template deploy is the signal to look at what changed. And because structured data breaks silently — a theme update drops the JSON block, prices stop matching, an entire template loses its markup — it belongs in your routine site audits alongside titles and metas, not in a set-and-forget checklist. The stars you earned last year are only as durable as the markup that's rendering today.