Rich results are enhanced search engine listings that display additional information beyond the standard title, URL, and meta description — such as star ratings, review counts, prices, FAQ accordions, how-to steps, event dates, or recipe details. They are powered by structured data (typically JSON-LD using Schema.org vocabulary) that tells Google how to present page content in search results, increasing visual prominence and click-through rates.
A plain blue link in Google competes for attention with every other result on the page. A rich result — with star ratings, a price range, and expandable FAQ questions — stands out visually and signals more information before the click. That visual differentiation is why structured data investment consistently delivers measurable CTR improvements across content types.
What are rich results?
Rich results are Google's way of presenting structured page content directly in search results with visual enhancements. They go beyond the standard title-URL-description snippet to include visual elements that make a listing more informative and eye-catching.
The term "rich results" is Google's current official terminology. You may also encounter:
- Rich snippets — the older (pre-2017) term, still widely used colloquially
- Enhanced listings — used by Bing and other search engines
- SERP features — broader term including features like featured snippets, local pack, and image carousels (not all are structured-data-powered)
Rich results are enabled by adding structured data to your web pages — machine-readable code that describes the content type and key attributes to search engines. Google's primary supported format is JSON-LD using Schema.org vocabulary.
Types of rich results
Google supports dozens of rich result types. The most commonly used and highest-impact ones are:
| Rich Result Type | What it shows | Schema type | Best for |
|---|---|---|---|
| Review / Ratings | Star rating + review count | Product, LocalBusiness, Recipe, Article | E-commerce, local businesses, SaaS review pages |
| FAQ | Expandable Q&A in the SERP | FAQPage | Informational content, landing pages |
| Product | Price, availability, ratings | Product | E-commerce product pages |
| Recipe | Cook time, calories, ratings, image | Recipe | Food and cooking content |
| HowTo | Step-by-step instructions | HowTo | Tutorial and guide content |
| Event | Date, time, location, ticket status | Event | Events pages, ticketing sites |
| Article | Author, date, image in News/Discover | NewsArticle, BlogPosting | News publishers, blogs |
| Breadcrumb | Path trail instead of plain URL | BreadcrumbList | All sites with hierarchical structure |
| Sitelinks Searchbox | Search box inside the SERP listing | WebSite | Large sites with internal search |
How to implement structured data with JSON-LD
JSON-LD (JavaScript Object Notation for Linked Data) is Google's recommended structured data format. It sits inside a script tag in the page head and does not interfere with page rendering.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "What is a rich result?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A rich result is an enhanced search listing..."
}
}]
}
</script>
Implementation steps
- Choose the right schema type — match the Schema.org type to your content (Article, Product, FAQPage, Recipe, etc.)
- Write accurate, complete JSON-LD — include all required properties. Google's developer docs list required vs recommended properties for each type.
- Validate with the Rich Results Test — Google's free tool at search.google.com/test/rich-results checks for errors and shows a preview
- Deploy and monitor — after deployment, check Google Search Console's Enhancements reports within a few weeks to see if Google has detected and processed the schema
Eligibility vs display
A critical distinction: valid structured data makes a page eligible for rich results, but does not guarantee Google will show them. Google's decision to display rich results depends on:
- Content quality — the structured data must accurately reflect the actual page content. Schema that misrepresents the page is treated as spam.
- Query context — Google shows rich results when they add value for the specific query. A product schema on a blog post won't trigger product rich results.
- Page authority — lower-authority pages may have valid schema but not receive rich results if Google has insufficient trust in the page.
- Mobile vs desktop — some rich result types display differently on mobile vs desktop. Google's Search Console reports are device-segmented.
CTR impact of rich results
Rich results' primary value is improving click-through rate from existing ranking positions — getting more clicks at position 5 than you would with a plain listing. Research on CTR impact:
High CTR lift
- Review stars: +15-30% CTR for positions 1-5
- FAQ schema: larger listing height captures more visual attention
- Recipe rich results: strong image + metadata draws food-intent clicks
- Product schema with price: pre-qualifies buyer intent before click
Variable or lower CTR lift
- Breadcrumbs: helps CTR slightly, mainly improves perceived trustworthiness
- HowTo: large but varies significantly by query type
- Article: primarily matters for News and Discover, not regular SERPs
- Sitelinks Searchbox: convenient but mainly for branded queries
Testing and monitoring tools
- Google Rich Results Test (search.google.com/test/rich-results) — validates schema, shows preview of potential rich results, flags errors
- Google Search Console Enhancements — reports which rich result types Google has detected, error counts, and whether pages are valid or have issues
- Schema Markup Validator (validator.schema.org) — tests generic Schema.org validity beyond Google's specific requirements
- Structured Data Linter — alternative validation tool for microdata and RDFa as well as JSON-LD
Rich results best practices
- Use JSON-LD, not microdata. Google recommends JSON-LD as the cleanest implementation method. Microdata requires embedding attributes throughout HTML, which is harder to maintain.
- Match schema to content exactly. If your Product schema shows a price of $29, the page must show $29. Google's quality guidelines prohibit misleading structured data.
- Include all recommended properties. Required properties prevent errors; recommended properties increase eligibility and richness of the displayed result.
- Add BreadcrumbList to every page. Breadcrumb schema replaces the plain URL in the SERP listing with a readable path — this is a quick, low-effort win available to every site.
- Test before deploying. Use the Rich Results Test on staging before pushing to production. Errors in deployed schema can negatively impact your Search Console Enhancements reports.
- Monitor for errors monthly. Google Search Console's Enhancements section reports schema errors that prevent rich result eligibility. Set a monthly review calendar item.
- Don't duplicate schema across multiple page types. If you add Product schema to a blog post about a product (rather than the product page itself), Google may ignore it or flag it as misleading.
Common rich results mistakes
- Schema that doesn't match page content — using Product schema when the page is a blog post, not a product listing
- Review stars from first-party reviews only — Google requires aggregate rating data to come from third-party review platforms or credible aggregation, not self-written reviews
- Assuming schema = ranking boost — structured data improves CTR, not ranking position directly
- Not validating before deployment — shipping broken schema that causes Search Console errors
- Ignoring Search Console Enhancements — valid schema is deployed but errors accumulate unnoticed for months
- Using FAQ schema on low-quality thin pages — Google reserves rich result display for pages with genuine useful content, not thin pages with bolted-on schema
Frequently asked questions
Rich snippets is an older term (pre-2017) for the same concept — enhanced SERP listings beyond the standard title/description. Google now uses the term "rich results" officially. Both terms refer to structured-data-powered enhancements in search results.
No. Valid structured data makes a page eligible for rich results, but Google decides whether and how to display them based on content quality, page authority, query context, and whether the schema accurately reflects the page content. A page can have perfect schema and still not receive rich results in practice.
The recommended approach is JSON-LD embedded in the page's head section. Write a JSON-LD script using Schema.org vocabulary matching the content type. Validate using Google's Rich Results Test. Deploy and monitor with Google Search Console's Enhancements reports.
Structured data is not a confirmed direct ranking factor. However, rich results significantly improve CTR from search results, and CTR improvement can indirectly influence rankings. Star ratings, review counts, and FAQ accordions attract more clicks than plain blue links for comparable positions.
Review/rating stars consistently show the largest CTR lift — studies show 15-30% CTR improvement for positions 1-5 when star ratings are displayed. FAQ schema can increase listing height dramatically. Product schema with price and availability is essential for e-commerce.
Related glossary terms
Sources
