Dispatch
What Are Rich Results? How Structured Data Creates Enhanced Search Listings
Rich results are search listings that show more than a blue title, a URL, and a snippet of text. A recipe result with a star rating, cook time, and a...
On this page
Rich results are search listings that show more than a blue title, a URL, and a snippet of text. A recipe result with a star rating, cook time, and a thumbnail photo; a product listing with price and stock status; a breadcrumb trail replacing a long URL path; a third-party review listing with star ratings; all of these are rich results, and all of them exist because the page behind them carries structured data Google can parse with confidence.
What Structured Data Actually Does
Structured data is markup, usually written in JSON-LD, that describes the content on a page in a standardized vocabulary (schema.org) so that search engines don’t have to infer what a page is about from unstructured text alone. Google is explicit that structured data does not directly improve rankings. What it does is make a page eligible for enhanced display formats, which can improve click-through rate by making a listing more visually prominent and informative, even at the same ranking position (Google Search Central, “Intro to How Structured Data Markup Works”).
That distinction matters because it’s commonly misunderstood. Adding schema to a page that’s poorly optimized for relevance and quality will not push it up the rankings. Adding schema to a page that’s already well-optimized can make its existing position more clickable.
Common Rich Result Types
| Schema type | Typical rich result | Where it commonly appears |
|---|---|---|
| Product | Price, availability, review stars | E-commerce product pages |
| Recipe | Cook time, ratings, calories, photo | Food and cooking sites |
| Article / NewsArticle | Enhanced display in Top Stories and News surfaces | Publishers and news sites |
| LocalBusiness | Supports local pack and knowledge panel data | Business location pages |
| Organization | Knowledge panel logo and brand details | Company homepages |
| Review / AggregateRating | Star ratings in search snippets, limited to genuinely third-party reviews | Product pages and independent review/comparison sites |
| BreadcrumbList | Breadcrumb trail instead of full URL path | Most site types |
Eligibility for each type comes with its own required and recommended properties, documented individually by Google for each schema type. Missing a required property typically disqualifies the page from that rich result even if the optional fields are filled in correctly.
Two types deserve a separate callout because a lot of SEO content still recommends them as if the rich result still exists, and the actual display has been gone for years in one case and shut down entirely in 2026 in the other:
- HowTo: Google removed the HowTo rich result from mobile search in August 2023 and from desktop shortly after, in September 2023. The structured data type still exists in schema.org and Google’s documentation set, but it no longer produces any visible rich result on Search, on any device (Google Search Central Blog, “Changes to HowTo and FAQ rich results”).
- FAQPage: Google restricted FAQ rich results to a small set of well-known government and health sites in August 2023, then dropped the feature for everyone, including those sites, starting May 7, 2026. Google is also removing the FAQ search appearance filter, the FAQ rich result report, and Rich Results Test support for the type in June 2026, with Search Console API support for it following in August 2026 (Google Search Central, FAQPage structured data documentation).
Leaving existing FAQPage or HowTo markup on a page won’t cause harm, and Google has said it may still use the structured data to understand the content, but neither type is worth implementing today with the expectation of an enhanced SERP listing. Treat any current guide, including older content elsewhere, that still lists FAQ or HowTo as an active rich result opportunity as out of date.
Self-serving reviews are a related trap worth flagging separately. Since September 2019, Google has excluded “self-serving” reviews from the star-rating snippet: a review about an entity that appears on that same entity’s own site, whether marked up directly or pulled in through an embedded third-party widget, does not qualify, even with technically valid LocalBusiness or Organization review markup. The star snippet is reserved for reviews hosted on a genuinely independent third-party site reviewing someone else (Google Search Central Blog, “Making Review Rich Results more helpful”). A business marking up its own testimonials in the hope of stars next to its homepage in search results will not get them, regardless of how correctly the schema is written.
Implementation: JSON-LD Is the Recommended Format
Google supports three syntaxes for structured data (JSON-LD, Microdata, and RDFa) but explicitly recommends JSON-LD where possible, because it’s a separate script block that doesn’t need to be interwoven with visible HTML, which makes it easier to implement, validate, and maintain without breaking page markup. Most modern CMS plugins and ecommerce platforms generate JSON-LD by default for this reason.
A few implementation patterns to get right:
- Markup should describe content that’s actually visible to users on the page. Marking up information that doesn’t appear anywhere in the visible content is a guideline violation, not just a best-practice miss.
- Required properties vary by type; a Recipe needs ingredients and instructions, a Product benefits from price and availability, an Event needs a start date.
- Schema should be kept current. A Product page that no longer reflects current price or stock status, while its schema still shows the old data, creates a mismatch between what’s marked up and what’s displayed, which is exactly the kind of inconsistency Google’s guidelines flag.
Validation and Monitoring
Two tools matter here. The Rich Results Test checks a single URL or code snippet and reports which rich result types are eligible and what errors or warnings exist. The Page indexing report and the dedicated structured-data reports inside Google Search Console (formerly surfaced under separate “Enhancements” reports per schema type) show how markup is performing across the whole site over time, including any pages where Google detected but couldn’t validate structured data.
Neither tool guarantees a rich result will display. Eligibility is necessary but not sufficient: Google ultimately decides whether and when to show an enhanced format based on relevance to the query and overall page quality, and that decision can change without any change to the markup itself.
Structured Data Spam Policies
Google’s general structured data guidelines state plainly that markup must be a true representation of page content, and that violating quality guidelines can prevent structured data from generating a rich result or cause it to be treated as spam under Google’s structured data policies (Google Search Central, “General Structured Data Guidelines”; Google Search Central, “Spam Policies for Google Search”). Marking up fake reviews, inflated ratings, or content that doesn’t exist on the page is treated as manipulation, not a technical error, and can result in the structured-data type being suppressed sitewide rather than just on the offending page.
Why Rich Results Matter for Click-Through
Search listings with star ratings, prices, or recipe photos occupy more visual space and communicate more information before a click than a plain text snippet. Industry click-through-rate studies consistently associate rich results with higher engagement than equivalent plain listings at the same position, though the exact lift varies widely by query type, vertical, and competitive context, and no single universal percentage applies across all sites. Treat any specific CTR-lift number from a third party as a directional estimate rather than a guaranteed outcome for a particular page.
Build and Maintenance Checklist
- Identify which schema types are relevant to the page’s actual content type (don’t force Product schema onto a blog post).
- Implement in JSON-LD, matching every required property documented by Google for that type.
- Validate with the Rich Results Test before publishing.
- Keep schema data in sync with visible content whenever prices, ratings, availability, or other dynamic fields change.
- Monitor structured-data reports in Search Console for validation errors that appear after template changes or CMS updates.
- Avoid marking up content that isn’t visible to users; this is a guideline violation, not just wasted effort.
Frequently Asked Questions
Does adding structured data improve rankings directly?
No. Google states structured data does not directly affect ranking. It affects eligibility for enhanced display formats, which can indirectly improve click-through rate at an existing ranking position.
What happens if structured data doesn’t match the visible page content?
It risks being treated as a violation of Google’s structured data guidelines, which can disqualify the page from rich results or, in more serious cases, lead to a manual action for structured data spam.
Is JSON-LD required, or can Microdata still be used?
Both are supported, along with RDFa, but Google recommends JSON-LD because it’s easier to implement and maintain without entangling markup in the visible HTML.
How do I know if my rich results are actually showing in search?
The Rich Results Test confirms eligibility for a given URL. Whether a rich result actually displays for real searches, and how often, is best tracked through the structured-data performance reports in Search Console, which show impressions and clicks for pages with valid markup over time.