Stars under a product, a price next to an In stock label, a breadcrumb path in place of a plain web address, a date and venue under an event: these extras are rich results, and many people still call them rich snippets. Rich snippets is the older name; rich results is the term in Google's current documentation. Both describe an enhanced Google Search listing.
Four appearances from Google's structured-data gallery are easy to recognize. A product result can show a price and availability. A review snippet can show a star rating or an excerpt. A breadcrumb result can show a path such as Home › Guides › Article. An event result can show a date and a place.
As a demonstration, imagine a made-up listing for a fictional Example Solar Notebook that shows 4.6 stars, 18 reviews, $24.00 and In stock. Those details are invented for illustration. On a real page, they would come from a product price and ratings that visitors can see, described in structured data that Google can read.
To get one on your own page, pick the Google feature that matches the page, add markup for it, match every value to the visible content, then test the page and watch it in Search Console. Google says correct markup makes a page eligible but does not guarantee a display.
Snippets, rich results, rich snippets and featured snippets
A snippet is the ordinary listing Google builds from a page's title, web address and a line or two of descriptive text. Every indexed page can have one. A rich result is a more detailed or interactive listing that Google supports through structured data or through another Google system. "Rich snippet" is the older industry name for the same idea, and Google's current documentation says "rich result."
A featured snippet is a different thing. It is an answer box that Google selects from page content, and it sits outside the rich-result gallery. Markup is not a route to a featured snippet, and Google does not list one as a structured-data feature. If your goal is a star rating or a price line, you are working with rich results. If your goal is an answer box, you are working on the page text.
Three layers are worth keeping apart. Schema.org is the shared vocabulary of types and properties. JSON-LD, Microdata and RDFa are the formats that carry that vocabulary; the JSON-LD, Microdata and RDFa comparison covers the choice. Google rich results are search features that Google controls. The guide to schema markup and structured data explains why people use the two terms for the same thing.
Examples of each rich result type Google lists
Google's gallery groups its supported features by purpose. Each feature has its own documentation, its own required properties and its own quality rules. The groups below describe what each one can show; whether it shows for a given query, device or location is Google's decision.
Four features describe the page or the site itself. Article can show the title, publication details and a larger image. Breadcrumb can show the site hierarchy, for example Home › Guides › Article. Organization can support the name, logo and identifiers that feed knowledge-panel information. Profile page connects a person or organization profile with a site. The Article schema guide and the breadcrumb schema guide cover those two in detail, and the Organization schema guide covers the third.
Commerce has two features. Product can show an image, a price, availability and eligible review information. Review snippet can show a rating or a review excerpt for eligible entities such as books, local businesses, movies, products, recipes and software apps. The Product schema guide and the Review schema guide show the properties each one needs.
Local and time-based features include Local business, Event and Vacation rental. Local business can show business details, hours, ratings, directions or actions. Event can show the name, date, location and event actions. Vacation rental can show a property name, images, location, ratings and reviews. See the Local Business schema guide and the Event schema guide.
Content and media is the largest group. Recipe can show an image, ratings and preparation details. Video can show a thumbnail, duration, playback information, segments or live-stream details. Discussion forum covers user-generated threads, and Q&A covers a question page with answers. Software app can show a name, description, link and rating. Image metadata can show creator, usage or credit details in Google Images. Subscription and paywalled content identifies content behind a paywall. The Recipe schema guide and the Video schema guide go deeper on two of them.
Employment and education features include Job posting, Employer aggregate rating, Course list and Education Q&A. Job posting can show a title, employer, location, salary and logo. Course list can show courses from one provider with a title and description. Education Q&A covers education questions and answers, including flashcard-style experiences.
A few specialized features complete the gallery: Math solver for structured math problems and solution walkthroughs, Speakable for news content marked for text-to-speech, and Carousel, a sequential list that combines eligible types such as Recipe, Course list, Restaurant or Movie. Some entries in the gallery are specialized surfaces rather than ordinary blue-link enhancements, so read each feature page before you plan around it.

Features Google has retired
Several features that older tutorials still recommend no longer show in Google Search. These dates come from Google's own announcements and its documentation updates page.
- HowTo: Google stopped showing How-to rich results on desktop on September 13, 2023, after earlier restrictions on mobile, according to Google's HowTo and FAQ changes post.
- Sitelinks search box: Google announced its removal on October 21, 2024, and the box was removed globally beginning November 21, 2024, as described in Google's sitelinks search box announcement.
- Practice Problem: Google deprecated it on November 5, 2025, in its November 2025 update on simplifying results, and planned to remove it from Search Console reporting, the Rich Results Test and Search appearance filters beginning January 2026.
- FAQ: Google announced on May 8, 2026 that FAQ rich results would stop appearing beginning May 7, 2026, and removed the FAQ feature documentation in June 2026.
- Course Info, Estimated Salary, Learning Video, Special Announcement and Vehicle Listing were phased out in 2025, following Google's June 2025 announcement about simplifying search results.
A retired display does not make the vocabulary invalid. FAQPage stays a valid schema.org type, and the same goes for the other types above. What changes is the reason to add it: do not add FAQ or HowTo markup as a way to get a Google display, because Google no longer shows one. The FAQ schema guide explains what the markup still describes.
Existing markup of a retired type can stay if it is accurate and matches the visible page, because other systems may still read it. Removing valid markup solely because one provider stopped displaying it is not a reliable reason. Keep it accurate if it stays, and stop adding it to new pages as a Google display tactic.
What a page needs to qualify
Google's general structured-data guidelines set the baseline. A page qualifies for a rich result when it meets all five of these conditions.
- The structured data is accurate and describes content visitors can see on the page.
- The content matches a Google feature that is currently supported.
- The markup includes every required property for that feature.
- Googlebot can crawl and index the page, with no robots.txt block,
noindextag or login wall in the way. - The page follows Google Search Essentials, the spam policies and any quality rules specific to the feature.
Those conditions fall into three layers. The technical layer covers the format and access: Google supports JSON-LD, Microdata and RDFa and recommends JSON-LD, the markup belongs on the page it describes, and image URLs need to be crawlable and indexable. The content layer covers honesty: mark up only what visitors see, keep it current, and never invent reviews, prices, availability, ratings or affiliations.
The display layer is the one people forget. Google may show a normal text result even when every technical requirement is met, and results can vary by query, device, location and language. The Rich Results Test checks many technical requirements but cannot promise an appearance, and a valid status in Search Console means the page is eligible, not that a rich result will show.
That is why "correct" has four separate meanings. The JSON syntax can be valid. The schema.org vocabulary can be valid. The requirements of a specific Google feature that still exists can be met. And the result can be indexed and actually shown. Passing one level says nothing about the next, so test and read them one at a time.
Required and recommended properties by feature
Pick the feature first, then look at its properties. Google's feature guides separate the properties a feature requires from the ones that make a result more complete. Property requirements change, so open the current feature page before you publish.
Article is the loosest. Google's Article guide currently documents no required properties, and recommends author, datePublished, dateModified, headline and image when they apply. Breadcrumb is stricter: itemListElement is required, and each ListItem needs position and name, with item recommended where the crumb points to a URL. Product needs a name plus a qualifying path through offers, a review or an aggregate rating, and Google recommends image, description, brand, sku and availability.
Recipe and Event also have feature-specific required fields. Follow the current Google guide for each one rather than copying a property list from an older tutorial. In every case, a property that is valid schema.org vocabulary is not automatically a property a Google feature uses, and the reverse also holds. Label them separately when you plan your markup, as in "required for this Google feature." The types of schema markup guide helps you choose the right type, and the guide on whether schema markup helps SEO covers the wider question.
Three examples to adapt
Each example below uses a reserved example domain and fictional names. Replace every value with facts that appear on your own page, and delete any property you cannot fill with a true, visible value. Keep the markup in a script element with the type application/ld+json on the page it describes, as covered in how to add schema markup. More copyable patterns live in the JSON-LD schema examples guide.
Article
An article page needs no required properties for Google's Article feature, but the recommended ones are worth adding when they are true. Change the headline, datePublished, dateModified, author and image values to match the visible page; publisher, description and articleSection are optional extras. Use a real date and a real author name, and keep the dates in step with what the page displays.
{
"@context": "https://schema.org",
"@type": "Article",
"@id": "https://example.com/guides/rich-results#article",
"url": "https://example.com/guides/rich-results",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://example.com/guides/rich-results"
},
"headline": "Rich Results Explained for Site Owners",
"description": "A plain-language introduction to rich results and search eligibility.",
"image": [
"https://example.com/images/rich-results-1x1.jpg",
"https://example.com/images/rich-results-4x3.jpg",
"https://example.com/images/rich-results-16x9.jpg"
],
"datePublished": "2026-06-30T09:00:00-06:00",
"dateModified": "2026-06-30T09:00:00-06:00",
"author": {
"@type": "Organization",
"name": "Example Publishing",
"url": "https://example.com/about"
},
"publisher": {
"@type": "Organization",
"name": "Example Publishing",
"url": "https://example.com/about",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/images/logo.png"
}
},
"articleSection": "Guides"
}Breadcrumb
A breadcrumb trail mirrors the real hierarchy of the site. List each level in order with position, name and, for every level except the current page, the item URL. The last crumb can leave out item because it stands for the page itself. If the visible trail on your page reads Home, Guides, then the title, the markup should say the same.
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://example.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Guides",
"item": "https://example.com/guides"
},
{
"@type": "ListItem",
"position": 3,
"name": "Rich Results Explained"
}
]
}Product
Use Product only on a genuine product page where the price and availability are visible to visitors. Replace the name, sku, price, priceCurrency and availability with the real values. The aggregateRating block holds fictional teaching numbers; keep it only when genuine ratings are shown on the page, and delete it otherwise. Do not use this pattern for a service, an article or an organization.
{
"@context": "https://schema.org",
"@type": "Product",
"@id": "https://example.com/products/solar-notebook#product",
"name": "Example Solar Notebook",
"image": [
"https://example.com/images/solar-notebook-front.jpg"
],
"description": "A fictional reusable notebook with solar-powered page lighting.",
"sku": "EX-SN-001",
"brand": {
"@type": "Brand",
"name": "Example Brand"
},
"offers": {
"@type": "Offer",
"url": "https://example.com/products/solar-notebook",
"priceCurrency": "USD",
"price": "24.00",
"availability": "https://schema.org/InStock"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.6",
"reviewCount": "18",
"bestRating": "5",
"worstRating": "1"
}
}A broken example for practice
The next block is intentionally invalid. It carries a trailing comma after the priceCurrency value, which is a JSON syntax error that a parser rejects. Use it only to learn what a syntax error looks like, and never publish it.
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Example Notebook",
"offers": {
"@type": "Offer",
"price": "24.00",
"priceCurrency": "USD",
}
}Test the markup and watch it in Search Console
Validation answers different questions at different steps, so run each one. Start with the JSON itself, since a stray or missing comma makes the block invalid. Then check the vocabulary with the generic Schema Nova validator, which tests schema.org structure rather than a single search engine's rules. Google also describes its own testing options in its structured-data testing documentation, including the Rich Results Test and the Schema Markup Validator.
The Rich Results Test is the Google-specific check. It reports whether the page's markup meets the requirements of the Google features it detects. A clean result there tells you the markup is eligible for those features. It does not tell you whether Google has indexed the page or whether a rich result will show for any query.

After the page is live, inspect its URL in Search Console. The URL Inspection tool shows how Google sees the live page and whether crawling or indexing is blocked. If the markup passes the tests but nothing appears, look at crawl and index status first, then at quality rules for the feature, and then give Google time to recrawl the page. For a longer look at tool choices, the guide to structured data testing tools compares the options.
When you edit visible content, edit the markup in the same change. A price that changes on the page but not in the JSON-LD is the most common mismatch, and Google's guidelines tell site owners to mark up only what visitors can see. Update both together whenever the visible value changes.
Make the same markup readable for Bing and AI search
Bing reads Schema.org in JSON-LD, Microdata, Microformats, RDFa and Open Graph, and its documented scenarios include breadcrumbs, businesses, events, people, products and offers, recipes, reviews, aggregate reviews and ClaimReview (Bing's structured data documentation). Bing URL Inspection shows the detected markup and reports issues. Yandex supports only some schema.org types, so use its structured data validator and see its semantic markup FAQ.
To make a page eligible for ChatGPT search, allow OAI-SearchBot in robots.txt (crawler documentation). Put important claims in the page text, not only in JSON-LD. See the guide to schema markup for AI search and whether AI systems use schema markup.
Questions people ask
Does structured data guarantee a rich result?
No. Google says correct markup makes a page eligible, and it may still show a normal text result. Results can differ by query, device, location and language, and a valid status in Search Console means eligibility, not a promise of display.
How do I get stars and prices to show for a product?
Use Product markup on a real product page, with offers.price, offers.priceCurrency and offers.availability matching what visitors see. Add aggregateRating or review only when genuine ratings or reviews appear on the page. Google decides whether to show them.
Should I use JSON-LD, Microdata or RDFa?
Google supports all three and recommends JSON-LD, which sits in one script element instead of being woven through the page's HTML. Bing says it reads JSON-LD, Microdata, RDFa, Microformats and Open Graph, so JSON-LD works for both.
Can I use schema.org types that Google no longer displays?
Yes. A schema.org type stays valid when Google retires its display, and other systems can still read it. Just do not expect a Google rich result from it, and keep every value accurate and visible on the page.
