What Is a Rich Result? β Definition and How It Works
Learn what rich results are, which types exist, how structured data enables them, and why eligibility is not a guarantee.
A rich result is a search listing enhanced beyond a title, URL, and snippet β showing ratings, prices, images, dates, or other attributes drawn from a page's structured data.
1. Common Types
| Type | Displays |
|---|---|
| Product | Price, availability, rating |
| Review snippet | Star rating and review count |
| Recipe | Image, time, rating, calories |
| Event | Dates, location, availability |
| FAQ | Expandable questions and answers |
| Breadcrumb | Site hierarchy instead of a raw URL |
| Video | Thumbnail, duration, key moments |
| Job posting | Salary, location, posting date |
Which types are supported changes over time, and support has been withdrawn from some in the past.
2. Structured Data Is the Mechanism
Rich results are generated from schema.org markup on the page, usually as JSON-LD. The engine reads the declared type and properties and renders the matching presentation.
Without valid markup for a supported type, the enhanced presentation is not available β the engine has nothing to render from.
3. Eligibility Is Not a Guarantee
Valid markup makes a page eligible. Whether the rich result appears depends on the query, the engine's judgement, the device, and whether the enhancement helps in that context.
This is the most common source of frustration: markup validates, and the enhanced listing still does not appear. Eligibility is a precondition, not an entitlement.
4. Markup Must Match the Page
Structured data describing content that is not visible on the page is a policy violation, and it can cost eligibility across a site rather than for a single page.
The rule is simple: declare what is genuinely there, keep it synchronised, and do not use markup to claim ratings, prices, or availability the page does not show.
5. Why They Are Worth Having
Enhanced listings occupy more space and communicate more before a click β a price and rating shown in the results answers part of the question immediately.
They are also a reason publishers maintain structured data accurately, which is precisely what makes that data a reliable extraction target for everyone else.
6. Validating
Structured-data testing tools report parsing errors, missing required properties, and eligibility for specific types. Search Console-style reporting shows which enhancements a site is actually receiving.
Validate after any template change, since a single malformed block can remove eligibility silently.
7. The Extraction Angle
For anyone collecting data, rich results are a signal that a page carries good structured data. The same JSON-LD driving the enhanced listing is available in the page's source and typically cleaner than parsing rendered markup.
Finding it is usually faster than writing selectors, and it survives redesigns that break them.
8. Summary
Rich results are enhanced search listings rendered from a page's structured data, covering products, reviews, recipes, events, FAQs, and more.
Valid markup for a supported type makes a page eligible rather than guaranteed, markup must match the visible page, and the same data that earns the enhancement is the most stable thing to extract from that page.