Search Engines & SEO

Rich Result

Definition

Rich results are generated from structured data on the page, almost always schema markup written as JSON-LD. Google publishes a finite catalogue of supported types, each with its own required and recommended properties: Product with price and availability, Review with a rating, Event with dates and a location, Recipe with cook time and calories, Breadcrumb, Video, Job Posting, Dataset and others. Eligibility is not entitlement — valid markup makes a page a candidate, and Google decides at query time whether the enhanced form is useful for that search. The catalogue also shrinks: in August 2023 Google cut HowTo results entirely and limited FAQ results to well-known government and health sites, which removed a lot of markup from view overnight.

Why It Matters

The visible effect is space and attention. A result with review stars and a price occupies noticeably more of the screen than a plain listing, and on a phone it can push a competitor below the fold. Google is careful never to promise a click-through improvement, and honest measurement is hard because rich results are not evenly distributed across queries, but the enhanced listing has one certain advantage: it answers part of the question before the click. The reverse risk is real too. Markup that does not match what a visitor actually sees on the page is a policy breach, and the penalty for that is a manual action that removes your rich results across the board.

How It Works

During indexing, the renderer extracts structured data from the page and validates it against the type's schema. Missing required properties disqualify the item; missing recommended ones make it less likely to be chosen. The Rich Results Test checks a live URL or a pasted snippet and reports which enhancements it is eligible for, while the enhancement reports in Search Console show errors and valid items across the whole site over time. Displayed values must be present on the rendered page — a price in the markup that does not appear in the visible text is a mismatch. A featured snippet is a different thing entirely: that is an extract Google chooses from ordinary page text, with no markup involved and nothing you can add to request it.

Real-World Example

A baker publishes a single recipe page as static HTML at wren-sourdough.99helpers.site, with a JSON-LD Recipe block giving prep time, cook time, yield and an image URL. Before the markup, the listing is a title and two lines of text. After the next crawl, it carries a thumbnail, a cook time and a rating, and 99helpers' edge analytics shows views from search roughly doubling while impressions barely move — the same people, choosing that result more often.

Common Mistakes

  • Marking up data that is not visible on the page — the mismatch breaches Google's structured data policies and can cost every rich result on the site
  • Treating valid markup as a guarantee — it makes the page eligible, and Google still decides per query whether to use the enhanced form
  • Adding review stars to a page that reviews the business rather than an item — self-serving reviews of your own organisation have been ineligible since 2019
  • Confusing a rich result with a featured snippet — the snippet comes from ordinary page text and no amount of structured data produces one

Related Terms

Put a file online in seconds

Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.

Host a file free →