Rich Results

TL;DR — Rich results are the fancier search listings — the ones with star ratings, prices, images, or recipe times baked right into the result. You get them by adding structured data (a bit of code that labels what your content is) to your page. But adding the code only makes you eligible — Google still decides whether to actually show the enhanced look.

What a rich result is

When you search Google, most results are a plain blue link with a title and a line or two of text. A rich result is the same listing dressed up with extra detail pulled from the page: gold review stars, a price and “in stock” label, a recipe’s photo and cook time, an event’s date, a video thumbnail, or the little “breadcrumb” trail showing where the page sits on a site.

Those extras don’t appear by magic. You add code called structured data (usually in a format called JSON-LD) that labels your content — “this is a product, here’s its price, here’s its rating.” Google reads that code and may turn it into a richer display.

You might hear these called rich snippets. That’s just the old name. Google renamed them “rich results” years ago; both terms mean the same thing.

How to get them

1. Pick the right type for your page — Product, Recipe, Article, Video, and so on.
2. Add the structured data to your page’s HTML (most CMSs and SEO plugins can do this for you).
3. Test it with Google’s free Rich Results Test — paste your URL and it tells you what rich result the page is eligible for.

The two things people get wrong

• Eligible isn’t the same as guaranteed. Even with perfect markup, Google may choose not to show the rich result. That’s normal.
• Rich results don’t make you rank higher. They change how your listing looks, not where it sits. They can earn more clicks, but they’re not a ranking boost.

One more catch: the code has to describe what’s actually on the page. Marking up a five-star rating you don’t really show visitors can get you penalized.

Want the full type list, the deprecation history, and the CTR data? Switch to the Advanced tab.

TL;DR — Rich results are SERP listings enhanced from structured data markup (JSON-LD recommended; Microdata/RDFa also accepted). The core rule: markup makes a page eligible, not guaranteed — Google’s docs say so explicitly, and Google still decides whether to render the feature. Rich results are a display feature, not a ranking signal (Mueller, 2025: “Structured data won’t make your site rank better”). Only ~25 of schema.org’s 800+ types produce Google rich results, and the list is shrinking — How-To (desktop, 2023), Sitelinks Searchbox (Nov 2024), seven types (June 2025), FAQ (fully removed May 7, 2026). Stars can meaningfully lift CTR (industry estimates vary; no single verified figure) but stars below 3.0 are widely reported to hurt it; self-reviews don’t qualify; product stars require a single-product page. Markup must match visible content or risk a manual action.

Rich results vs. rich snippets vs. SERP features vs. structured data

These get used loosely, so let’s separate them:

• Structured data is the input — schema.org markup in your HTML that tells engines what your content means.
• Rich results are one possible output — the enhanced listing Google builds from that markup. “Rich snippets” is the legacy name (Google’s 2009 launch term); “rich results” has been the official term since ~2018.
• SERP features is the broader bucket — featured snippets, People Also Ask, the knowledge panel, AI Overviews, image packs. Some are powered by your structured data (rich results), many aren’t.

The key relationship: structured data helps Google understand a page; a rich result is one possible consequence of that understanding — never an automatic one.

Eligibility is not a guarantee

This is the line that saves the most wasted effort. Google’s documentation is explicit: “Using structured data enables a feature to be present, it does not guarantee that it will be present.” Valid markup plus all required properties makes you eligible. Whether the rich result actually displays depends on content quality, query intent, page authority, device, and Google’s own SERP-design decisions on that query. Bing says the same thing: “The presence of annotations alone does not guarantee Bing will use your annotated content to generate a visually rich snippet.”

So “I added the schema and it passed the test but I don’t see stars” is not a bug — it’s the system working as documented.

Why a rich result stops showing (or never did) — these are distinct causes, and mixing them up wastes debugging time. Working through the article’s own material:

1. The markup itself is invalid. Missing required properties or malformed JSON-LD — the Rich Results Test or Schema Markup Validator will flag this directly.
2. The type isn’t a supported Google feature. Valid schema.org markup for a type outside the Search Gallery (or a deprecated one) produces no SERP feature, even though nothing is technically wrong with it.
3. A policy violation or manual action. Markup that doesn’t match visible content, or self-serving reviews — covered in “The rules that disqualify you” below — can get a page disqualified even with syntactically valid markup.
4. Recrawl lag. Google hasn’t re-crawled/re-processed the page since the markup changed; Search Console’s Enhancements reports and URL Inspection reflect the last crawl, not the live page.
5. Ordinary display volatility. Eligible, policy-clean, freshly-crawled markup can still not show on a given query because Google’s SERP-design decision that day didn’t include it — this is the “eligible isn’t guaranteed” rule in practice, and it can change query to query with no error to chase.
6. Deprecation. The type used to be a Google feature and no longer is (see the deprecation wave above) — the markup is harmless but permanently produces nothing on Google, regardless of validity.

Supported formats

Google accepts three formats and recommends JSON-LD: “In general, Google recommends using JSON-LD for structured data if your site’s setup allows it, as it’s the easiest solution for website owners to implement and maintain at scale.” Microdata and RDFa still work; they’re just harder to maintain because the markup is interleaved with your visible HTML. Bing is format-neutral — it’ll take JSON-LD, Microdata, Microformats, RDFa, and Open Graph without preferring any.

The types that still produce rich results (~25)

Only types in Google’s Search Gallery are eligible. As of mid-2026 that’s roughly two dozen: Article, Breadcrumb, Carousel, Course Info (list), Dataset, Discussion Forum, Education Q&A, Employer Aggregate Rating, Event, Image Metadata, Job Posting, Local Business, Math Solver, Movie, Organization, Product, Profile Page, Q&A, Recipe, Review Snippet, Software App, Speakable, Subscription/Paywalled Content, Vacation Rental, and Video. (Full breakdown in the Cheat Sheets tab.) Schema.org defines 800+ types — implementing one that’s not in the gallery is harmless for Google but produces no SERP feature.

The deprecation wave is real and ongoing

This is the part most evergreen guides get wrong because they’re out of date. Since 2023 Google has steadily pruned the gallery:

• How-To — removed from desktop in August 2023 (it can still surface on mobile in limited cases).
• FAQ — first restricted in August 2023 to “well-known, authoritative government and health websites,” then fully deprecated on May 7, 2026. It is no longer shown in Google Search at all. Google has since removed the FAQPage documentation page as well — as of this update the old URL returns a 301 to the “removing FAQ rich result” entry in Google’s Search changelog, which records the documentation removal on June 15, 2026. Search Console rich-result reporting and Rich Results Test support for the type were dropped in June 2026, with API support ending in August 2026. This one stings because FAQ was one of the most widely implemented types.
• Sitelinks Searchbox — removed globally in November 2024, and dropped from Search Console and the Rich Results Test. Existing markup causes no errors.
• Seven types, June 2025 — Book Actions, Claim Review, Course Info (the old format), Estimated Salary, Learning Video, Special Announcement, and Vehicle Listing. Google’s stated reason: “we found that these specific displays are no longer providing significant additional value for users.” Search Console stopped reporting them September 9, 2025; API support ended December 2025.

What to do with deprecated markup: leaving it in place is harmless for Google and can be useful insurance — Bing may still display some types Google dropped (Claim Review, Course Info, Learning Video are candidates), and Google still parses the markup for content understanding. Remove it only if it’s cluttering your templates.

Rich results are a display feature, not a ranking factor

Worth stating bluntly because it’s still widely misunderstood. John Mueller, April 2025: “Structured data won’t make your site rank better” — and “you’re unlikely to see any visible change from it in Google Search” beyond eligibility for the feature itself. Structured data isn’t a generic ranking boost. Its value is (1) eligibility for rich results and (2) helping Google understand your content and entities, which can improve targeting for the right queries — not a position lift.

Do rich results improve CTR? (with the honest caveats)

Often yes, but conditionally — and I want to be precise about what’s verified here versus what’s industry folklore. This is a display-and-clicks question, separate from both eligibility (does the markup qualify) and ranking (rich results don’t move position — see above).

SEO-industry sources commonly cite CTR lifts for star ratings somewhere in the 10%–30%+ range versus a plain listing, but when I went looking for one current, rigorously documented primary study that pins an exact figure, I couldn’t find one — the study most often linked for this claim (a 2020 Milestone Research analysis of 4.5M queries, covered by Search Engine Journal) studies rich results broadly and doesn’t report a star-rating-specific number. Treat any single precise percentage, including ones you’ll see elsewhere, as a directional estimate rather than a number you can bank on for your own pages — measure your own before/after delta instead (see the Metrics tab).

Three caveats most guides skip regardless of the exact number:

1. Stars below 3.0 are widely reported to hurt CTR versus showing no stars at all — a visible bad rating being worse than no rating is a directionally logical and commonly repeated claim, though I couldn’t verify a specific study quantifying it either.
2. The zero-click context. SparkToro’s most recent published analysis (June 2026, using Similarweb panel data for January–April 2026) put roughly 68% of US Google searches ending without a click — up from about 58% in 2024, largely attributed to AI Overviews expanding. A CTR lift only matters on queries that still send clicks, and that share keeps shrinking.
3. Eligibility ≠ display, so any projected lift assumes the rich result actually shows.

The rules that disqualify you

A few enforcement details that quietly kill rich results:

• Markup must match visible content. Google’s policy: “don’t add structured data about information that is not visible to the user, even if the information is accurate.” Mismatched or fake markup (e.g., invented reviews) risks a structured-data manual action.
• Self-reviews don’t get stars. If the entity being reviewed controls the reviews about itself, “their pages that use LocalBusiness or any other type of Organization structured data are ineligible for star review feature.” Stars come from genuine third-party review content, not your own marketing of yourself.
• Product stars need a single product. “Product rich results only support pages that focus on a single product (or multiple variants of the same product).” Category pages and product-listing pages can’t earn product rich results.

Where this sits

Rich results are the most visible payoff of structured data, but they’re a subset of it. For the markup itself — formats, the schema.org vocabulary, validation, and entity understanding — see the Structured Data hub. For the AI-search angle (which is not the same as rich results — most AI crawlers don’t execute or parse JSON-LD the way Google does), see Schema markup for AI.

AI summary

A condensed take on the Advanced version:

• Rich results = enhanced SERP listings (stars, prices, images, breadcrumbs, video thumbnails) that Google/Bing build from structured data markup. “Rich snippets” is the legacy name for the same thing.
• Eligibility ≠ guarantee. Valid markup + required properties makes a page eligible; Google still decides whether to show the feature. This is documented, not a bug.
• Display feature, not a ranking factor. Mueller (2025): “Structured data won’t make your site rank better.” Value is eligibility + content/entity understanding, not a position boost.
• Format: JSON-LD recommended (Microdata/RDFa accepted); Bing is format-neutral.
• ~25 supported types of schema.org’s 800+; unsupported types are harmless but produce no SERP feature.
• Shrinking list: How-To (desktop, 2023), FAQ (restricted 2023 → fully removed May 7, 2026, notice added to the existing doc rather than removing it), Sitelinks Searchbox (Nov 2024), and 7 types in June 2025 (Book Actions, Claim Review, Course Info, Estimated Salary, Learning Video, Special Announcement, Vehicle Listing).
• CTR: stars can meaningfully lift CTR, but no single verified figure — industry estimates vary widely (~10–30%+); stars below 3.0 are widely reported to hurt CTR; ~68% of Google searches were zero-click as of early 2026 (up from ~58% in 2024), so any lift only applies to click-sending queries.
• Disqualifiers: markup must match visible content (or risk a manual action); self-reviews on LocalBusiness/Organization pages don’t get stars; product stars need a single-product page.
• Tools: Rich Results Test (eligibility), URL Inspection in GSC (real rendering), Schema Markup Validator (general schema.org correctness).

Official documentation

Primary-source documentation from the search engines.

Google

• Intro to structured data markup — what rich results are, supported formats, and the “enables, does not guarantee” framing.
• Search Gallery (supported types) — the authoritative list of types eligible for Google rich results.
• Structured data general guidelines (policies) — content-must-match-visible-content and anti-deception rules.
• Review snippet — eligible types and the self-serving review restriction.
• Product snippet — the single-product requirement and required properties.
• Rich Results Test — checks eligibility and previews the feature.
• Schema Markup Validator — validates general schema.org correctness (not Google-specific).
• How-To and FAQ changes (Aug 2023) — How-To desktop removal; FAQ restriction.
• Farewell, Sitelinks Search Box (announced Oct 2024, removed Nov 21, 2024).
• Simplifying search results (June 2025) — the seven deprecated types and Google’s reasoning.

Bing / Microsoft

• Marking up your site with structured data — Bing’s format-neutral stance and “no guarantee” statement; Bing Markup Validator.

Quotes from the source

On-the-record statements from Google and Bing. Each link is a deep link that jumps to the quoted passage on the source page.

Google — eligibility and format

• “Using structured data enables a feature to be present, it does not guarantee that it will be present.” — Google Search Central docs. Jump to quote
• “In general, Google recommends using JSON-LD for structured data if your site’s setup allows it, as it’s the easiest solution for website owners to implement and maintain at scale.” Jump to quote

Google — policies (markup must match visible content)

• “Don’t create blank or empty pages just to hold structured data, and don’t add structured data about information that is not visible to the user, even if the information is accurate.” Jump to quote
• “Don’t mark up irrelevant or misleading content, such as fake reviews or content unrelated to the focus of a page.” Jump to quote

Google — reviews and products

• “If the entity that’s being reviewed controls the reviews about itself, their pages that use LocalBusiness or any other type of Organization structured data are ineligible for star review feature.” Jump to quote
• “Currently, product rich results only support pages that focus on a single product (or multiple variants of the same product).” Jump to quote

Google — the June 2025 deprecations

• “We found that these specific displays are no longer providing significant additional value for users… Removing them will help streamline the results page and focus on other experiences that are more useful and widely used.” Jump to quote

John Mueller, Google — structured data and rankings

• “Structured data won’t make your site rank better.” (Bluesky, April 2025.) Relayed via Search Engine Journal’s coverage — Google Confirms Structured Data Won’t Make a Site Rank Better; confirm against the original Bluesky post before treating as final.

Bing / Microsoft

• “The presence of annotations alone does not guarantee Bing will use your annotated content to generate a visually rich snippet.” Jump to quote

Supported rich result types — cheat sheet

Status as of mid-2026. “Active” = currently produces a Google rich result; “Deprecated” = no longer shown by Google (markup is harmless and may still help Bing / content understanding).

Validation fast facts

• Rich Results Test (search.google.com/test/rich-results) → eligibility + preview.
• URL Inspection (Search Console) → how Google actually rendered/indexed a live URL.
• Schema Markup Validator (validator.schema.org) → general schema.org correctness, not Google-specific.
• Bing Markup Validator (Bing Webmaster Tools) → Bing’s view.

Each check confirms a different thing, and none of them confirm the others: the Rich Results Test confirms eligibility (syntax + required properties for a supported type), URL Inspection confirms what Google actually rendered/indexed, the Enhancements reports in Search Console confirm ongoing validity across the site, and none of those three confirm the feature actually displayed on a SERP or how it performed — for that, check Search Console’s Performance report filtered by Search Appearance.

Rules that disqualify you

• Markup must describe content visible on the page — no hidden/fake data.
• Self-reviews on LocalBusiness/Organization pages → no stars.
• Product stars require a single-product page (not category/PLP pages).

Mistakes that disqualify a rich result

These are the concrete ways sites lose rich result eligibility or trigger a manual action — pulled from the disqualifying rules covered above, not hypothetical edge cases.

• Marking up content that isn’t visible on the page. Google’s policy is explicit: don’t add structured data “about information that is not visible to the user, even if the information is accurate.” Why it’s wrong: it’s treated as deceptive markup regardless of intent, and can trigger a structured-data manual action. What to do instead: only mark up what a visitor actually sees rendered on the page — if the price, rating, or availability isn’t on the page, it doesn’t belong in the JSON-LD.

• Faking or inflating reviews. Google’s guidance also flags “fake reviews or content unrelated to the focus of a page.” Why it’s wrong: it’s the same visible-content violation applied to ratings specifically, and stars are the rich result readers scrutinize most. What to do instead: only mark up genuine third-party review content that’s actually collected and displayed.

• Adding review markup to your own Organization/LocalBusiness reviews. If the entity being reviewed controls the reviews about itself, those pages “are ineligible for star review feature.” Why it’s wrong: it’s a self-serving-reviews violation, not a technical error — the markup can validate perfectly and still never show stars. What to do instead: source ratings from genuine third-party reviewers, not testimonials you wrote or curated about yourself.

• Adding Product rich result markup to a category or listing page. Product rich results “only support pages that focus on a single product (or multiple variants of the same product).” Why it’s wrong: a PLP or category page describes many products, so the markup doesn’t match a single, focused entity. What to do instead: reserve Product markup for individual product detail pages; leave category pages unmarked or use ItemList instead.

• Assuming eligible means it will display. Treating a passing Rich Results Test as proof the feature will show in Google. Why it’s wrong: Google’s own docs say structured data “enables a feature to be present, it does not guarantee that it will be present” — display depends on content quality, query intent, and Google’s SERP-design decisions. What to do instead: use the Rich Results Test to confirm eligibility only, then check actual display with URL Inspection or Search Console’s Enhancements reports over time.

• Chasing rich results as a ranking tactic. Implementing structured data expecting a position boost. Why it’s wrong: Mueller was direct — “Structured data won’t make your site rank better” — it’s a display feature, not a ranking signal. What to do instead: implement structured data for eligibility and content/entity understanding; measure success by CTR and display rate, not rank movement.

• Leaving deprecated markup in place expecting it to still work on Google. Assuming FAQ, How-To, or the June 2025 deprecated types still produce a Google rich result. Why it’s wrong: those types are fully removed from Google Search (FAQ as of May 7, 2026); the markup itself is harmless but produces nothing there. What to do instead: keep the markup only if you want the Bing/content-understanding upside covered earlier — don’t budget for a Google rich result from a deprecated type.

Tracking rich result performance

The article’s own CTR data — the directional star-rating lift, the sub-3.0 CTR penalty, and the ~68% zero-click baseline — points to an ongoing measurement, not a one-time check. These are the metrics worth watching once markup is live.

CTR for pages with the rich result vs. without

What it tells you: whether the rich result is actually producing the click lift the article describes, on your own queries. How to pull it: Google Search Console’s Performance report, filtered by Search Appearance (e.g. “Review snippet”), compared against the same page’s CTR before the feature appeared or against similar pages without it. Benchmark / realistic range: industry sources cite lifts anywhere from roughly 10% to 30%+ for star ratings above a 3.0 threshold — I couldn’t verify one authoritative current study behind a single number, so there’s no figure here worth treating as a target. Track your own before/after delta as the real number that matters. Cadence: monthly, once the feature has had a few weeks to stabilize in Search Console’s data.

Displayed star rating

What it tells you: whether your rating is helping or actively hurting CTR. How to pull it: whatever surfaces the visible rating — Search Console’s URL Inspection rendered preview, or a manual SERP check for your key pages. Benchmark / realistic range: the article’s own line in the sand is 3.0 — ratings at or above that are the ones associated with a CTR lift; ratings below it can suppress clicks relative to no stars. There’s no defensible “good” number beyond that threshold from this article — if your rating is above 3.0, establish your own baseline CTR and watch it over time. Cadence: check whenever the underlying review data changes materially (new review batch, product changes).

Rich result eligibility / validity rate

What it tells you: whether your markup is staying valid as templates and CMS updates roll out, since the CTR gains only apply if the feature can display at all. How to pull it: Search Console’s Enhancements reports for the eligible types (Product, Review, etc.), which show valid vs. invalid item counts across the site. Benchmark / realistic range: no article-level benchmark applies here — this is a correctness check, not a comparative stat. Establish your own baseline (ideally 100% valid for templated pages) and watch for regressions. Cadence: monthly, or immediately after any template/CMS change that touches the marked-up pages.

Zero-click share for the queries you rank on

What it tells you: how much of any CTR lift is even reachable, since a rich result only helps on queries that still send a click. How to pull it: Search Console’s Performance report (impressions vs. clicks) for the query set your rich result pages target. Benchmark / realistic range: SparkToro’s most recent published analysis (June 2026, Similarweb panel data for Jan–Apr 2026) put roughly 68% of US Google searches ending without a click, up from about 58% in 2024 — that’s a general, fast-moving figure driven largely by AI Overviews, not specific to your queries, so use it as context rather than a target. Establish your own baseline zero-click rate for your query set from Search Console data. Cadence: quarterly — this has been shifting faster than “slowly” lately as AI Overviews expand; re-check sooner if you see a CTR drop with no ranking change.

Resources worth your time

My related writing

• The Beginner’s Guide to Technical SEO — where structured data and rich results fit in the bigger picture.
• Structured Data — the hub this article sits under: formats, the schema.org vocabulary, validation, and entity understanding.
• Schema markup for AI — why rich results and “schema for AI visibility” are not the same thing (most AI crawlers don’t execute or parse JSON-LD the way Google does).

From around the industry

• Search Gallery (Google) — the only authoritative, always-current list of supported types.
• Rich Snippets: How to Get Them for Your Website (Ahrefs, Chris Haines) — practical walkthrough of types and implementation.
• What Is Schema Markup & How to Add It (Ahrefs, Despina Gavoyannis) — the markup side of producing rich results.
• Google Confirms Structured Data Won’t Make a Site Rank Better (Search Engine Journal) — the 2025 Mueller statement in context.
• Google Retires 7 Structured Data Features (Search Engine Journal) — coverage of the June 2025 deprecations.
• Web Almanac 2024 — Structured Data (HTTP Archive) — adoption data across ~17M sites (JSON-LD at 41%, FAQPage growth before deprecation).
• Which Rich Results Get the Most Clicks (Search Engine Journal) — SERP CTR study across millions of queries.
• In 2026, Less than One Third of Google Searches Still Send a Click (SparkToro, June 2026, Similarweb panel data) — the current zero-click context (~68%) for any CTR claim; the article’s earlier 2024 figure (58.5%) has since moved.

Test yourself: Rich Results

Five quick questions on what rich results are, how they behave, and what’s changed. Pick an answer for each, then check.

Rich Results

Rich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show.

Related: Structured Data, Schema Markup

Rich Results

Rich results are enhanced search result displays that go beyond the standard blue link and meta description — star ratings, product prices, recipe images, event dates, breadcrumb trails, video thumbnails, and similar visual treatments shown directly in the SERP. Google and Bing generate them from structured data markup (typically JSON-LD using the schema.org vocabulary) embedded in a page’s HTML. “Rich results” is Google’s current official term; “rich snippets” is the older name still common in the industry.

The single most important nuance: structured data makes a page eligible for a rich result, it doesn’t guarantee one. Google’s structured-data guidelines explicitly make that distinction. Whether the enhanced display actually appears depends on content quality, query intent, page authority, and Google’s own SERP design decisions.

Two more distinctions trip people up:

• Rich results ≠ ranking factor. They change how a listing looks, not where it ranks. John Mueller reiterated in 2025 that structured data does not by itself improve ranking; Google uses it to enable supported search features.
• Schema.org ≠ Google’s supported gallery. Schema.org defines 800+ types; only ~25 are eligible to produce Google rich results, and that list shrinks — How-To, FAQ, Sitelinks Searchbox, and seven other types were removed between 2023 and 2026.

Markup must describe content that’s actually visible on the page; describing hidden or different content violates Google’s structured data policies and can trigger manual actions.

Related: Structured Data, Schema Markup

Changelog