What Is Rich Result?

How a Rich Result Works

A rich result begins with structured data. When Google crawls a page, it reads any schema.org markup it finds and uses it to classify the content — this is a product with a price and a rating, that is a recipe with a cook time and a calorie count. Google’s own documentation ties the two together directly: “Google uses structured data to understand the content on the page and show that content in a richer appearance in search results, which is called a rich result.”

That richer appearance replaces the plain title-and-snippet listing with something more visual and informative: star ratings under a product, a thumbnail beside a recipe, a price and availability on a merchant listing, a set of expandable questions, or a breadcrumb trail showing where the page sits in a site. Each of these is a feature, and each has its own contract of required and recommended properties the markup must supply.

Crucially, eligibility is not the same as display. Valid structured data makes a page eligible for a rich result, but Google decides at query time whether to show one, weighing quality, relevance, and its guidelines. A page can have flawless markup and still appear as a plain link — the markup is a prerequisite, not a trigger.

The Range of Rich Results

Google maintains a search gallery documenting the specific features structured data can unlock. As of 2026 that gallery documents 31 structured data features, spanning categories from ecommerce to publishing to events. A representative sample:

• Product and Review snippet — price, availability, and star ratings on product listings.
• Breadcrumb — the site hierarchy shown in place of a raw URL.
• Recipe — cook time, ratings, and a thumbnail, often within a carousel.
• Event — dates and locations for concerts, classes, and performances.
• Video — key moments and thumbnails for video content.
• Job posting, Local business, FAQ-style Q&A, and Article — each with its own eligibility rules.

Every feature is separately documented with the properties it needs, which is why “getting a rich result” is always specific: you’re qualifying for one named feature, not flipping a general switch.

Example of a Rich Result

The clearest sourced example is Google’s documented Product markup pathway. In Google’s structured data documentation, a page marked up with a valid Product type — including an offers block with a price and an aggregateRating — becomes eligible for a merchant listing rich result that can display the price and star rating directly in the search results. The documentation is explicit that eligibility carries conditions: the required properties must be present and valid, and the marked-up information must be “visible to the user” on the page. A rating the reader can’t see doesn’t earn a rich result; it can cost the page its eligibility under Google’s structured data guidelines.

This is a genuine, testable example rather than a claim, because the whole contract is documented and verifiable. You can take any product page, run it through Google’s Rich Results Test, and get back exactly which features it qualifies for and which required properties are missing — a deterministic check against Google’s published requirements. The lesson generalizes across all 31 features: a rich result is a conditional grant. Supply valid, visible, correctly-typed structured data for a supported feature, and the page becomes eligible for that feature’s richer appearance. What you don’t get is a promise it will show, or that showing it will always win the click — which is why the real work is choosing the pages where a richer listing genuinely helps a user pick you.

Frequently Asked Questions

The Bottom Line

A rich result is what structured data buys you when it works: a listing that shows more than a link — a price, a rating, a set of questions — and pulls the eye in a crowded results page. Google grants it based on valid, visible markup for one of its supported features, but grants it at its own discretion. Earn eligibility on the pages where a richer listing genuinely helps users choose you, then judge it by clicks, not by whether the markup validated.