# Rich results Rich results are Google search results that show more than the title, URL and snippet, like stars, prices, availability, images or breadcrumbs. For a small site, they can lift visibility and click-through on core pages without more links or content. You need the right structured data and a clean page to be eligible. Updated 2026-09-14 · Source: https://porteur.ai/glossary/rich-results ## What shows as a rich result Rich results cover many formats: product prices and stock, star ratings, FAQ answers, breadcrumbs, recipe cards, event dates, job listings, sitelinks and some images. Most rely on structured data that Google validates for that type. Some, like sitelinks and some images, are chosen by Google without markup. Eligibility is not a guarantee. You can pass all tests and still see only a plain result. Treat rich results as a bonus that comes and goes per query. ## Structured data that makes you eligible Use JSON-LD. Google also reads Microdata and RDFa. JSON-LD can sit in the head or body, and Google renders pages, so injected scripts are read. Most answering AI crawlers do not run scripts, so prefer server-rendered JSON-LD when you can. - Article: headline, image in 16:9, 4:3 and 1:1, datePublished, dateModified, author with name and url. Long headlines may be truncated. AMP is not required for Top Stories. - Product: name, and at least one of review, aggregateRating or offers. For offers add price, priceCurrency, availability value like InStock, url. image, brand, sku, gtin are recommended. Merchant listing results also read shipping and returns. - SoftwareApplication: name, offers.price and offers.priceCurrency, and a rating via aggregateRating or a review. applicationCategory and operatingSystem are recommended. - Organization: name, url, logo at least 112x112 and crawlable, sameAs profiles. contactPoint, address, founder, foundingDate help knowledge panels. Merchant return and shipping fields can also live here. - BreadcrumbList: itemListElement of ListItem with position from 1, name, and item URLs. The last item may omit the URL. - Review snippet: itemReviewed must be a supported type like Product or SoftwareApplication. Provide reviewRating with ratingValue and bestRating, author name. Or aggregateRating with ratingValue and ratingCount. Self-serving reviews for your own LocalBusiness or Organization are not shown. - FAQPage: mainEntity list of Question with acceptedAnswer text. Since 2023, Google shows FAQ rich results only for well-known government and health sites. - HowTo: markup is harmless, but Google removed HowTo rich results in 2023. - WebSite with SearchAction: the sitelinks search box was removed in 2024, so this markup earns nothing now. ## Test, validate and fix Use the Rich Results Test at search.google.com/test/rich-results. It tells you which Google rich results a page is eligible for and what fields are missing or invalid. The tool reads the rendered page, so it finds markup added by scripts after load. Use the Schema Markup Validator at validator.schema.org to check schema.org syntax. It does not apply Google’s rules. The old Structured Data Testing Tool was retired in 2020. - Common blockers: a required field missing, a relative URL where an absolute URL is needed, dates not in ISO 8601, a price as text with a currency sign, a rating out of range. - Policy violations: marking up content not visible on the page, or nesting types in a way that breaks the graph. - You can include several things in one @graph, for example Organization, WebSite and BreadcrumbList. > Mark up only what a visitor can read or see on the page. Hidden or misleading markup can lose eligibility sitewide. ## Track performance in Search Console Open Enhancements to see which types Google found and any errors and warnings. Fix errors first, then warnings that would improve completeness. Re-run the test and request validation when ready. 1. **See clicks by appearance** In Performance, add the Search appearance dimension. Compare clicks and CTR for, say, Product results versus Web results over 28 days. 2. **Check by page** Filter to a URL like /pricing or /guides/getting-started. Look for queries where the rich form shows. Compare CTR to the plain Web form. 3. **Decide what to scale** If Product results lift CTR on /store/widget, roll out Product and Review markup to more product pages. If CTR is flat, fix title and snippet first. Structured data is not a ranking factor by itself. It helps machines read the page and makes you eligible for rich results. Focus first on pages that can win the click and lead to a signup or sale. ## Questions ### What is the Rich Results Test? It is Google’s tool that checks a page against the rich result types Google supports. It shows eligibility, missing or invalid fields, and a preview when possible. It reads the rendered page, so it sees markup injected by JavaScript. ### What do rich results display on SERPs? They can show star ratings, prices, availability, breadcrumbs, event dates, recipe details, job listings, and sometimes images or sitelinks. The exact form depends on the query and the page type. ### What is the difference between rich snippets and rich results? Rich snippet is an older term for results with extra data in the snippet, like ratings. Rich results is Google’s broader term covering many result formats beyond snippets. Use Google’s term when testing and reporting. ### How do I track clicks from rich results? In Search Console, use the Search appearance dimension in the Performance report. Compare clicks and CTR for the rich appearance against Web results for the same page and queries over 28 days. ### Does JSON-LD have to be in the head, and can I use JavaScript? JSON-LD can be in the head or body. Google renders pages, so JSON-LD injected by JavaScript can be read. Many AI crawlers do not run scripts, so server-rendered markup is safer for them. ### Which rich result types matter most for a product or SaaS site? Start with Product or SoftwareApplication on sales pages, Review snippets where you have third-party reviews, Organization for your logo, and BreadcrumbList for navigation. Add Article to blog posts that can reach Top Stories if newsy. ## Read next - [The Rich Results Test: what it checks and what it does not](https://porteur.ai/guides/rich-results-test): Run Google’s Rich Results Test, read eligibility, warnings and errors, know its limits, and when to use schema.org’s validator and Search Console. - [Structured data](https://porteur.ai/glossary/structured-data): Structured data is schema markup that names your page type. See why it changes results, how to add JSON-LD, and how to validate it. - [Rich snippet](https://porteur.ai/glossary/rich-snippet): A rich snippet shows extras like price, rating or FAQ. See which schema can earn which result, how to add it, test it, and measure impact. - [Product schema: the fields Google reads and the ones it requires](https://porteur.ai/guides/product-schema): Set up Product schema that earns snippets and merchant listings. See the required fields, the recommended ones and a full JSON-LD example. - [SoftwareApplication schema for a SaaS: an example that validates](https://porteur.ai/guides/softwareapplication-schema): Add SoftwareApplication schema that passes Google’s Rich Results Test. See the required fields, a clean SaaS example, and how to test and ship it. - [Breadcrumbs: the navigation, the markup, and what Google shows](https://porteur.ai/guides/breadcrumbs): Add breadcrumb navigation that helps visitors, improves internal linking and gives Google a clean trail to show in results, with JSON-LD examples. - [SERP features](https://porteur.ai/glossary/serp-features): Learn the main SERP features, what they signal about intent, which a small site can win, and how to check them and act. Check if your key pages are eligible for rich results, and which rivals already win them, with a free 30‑second read of your URL that shows three findings. Free check: https://porteur.ai/