Google rich results: all 25 supported types

What a rich result actually is

A rich result is a search listing with something extra attached to it.

A plain listing is a title, a URL and a snippet. A rich result adds structure — a price, a rating, a set of opening hours, a thumbnail, a breadcrumb trail.

You do not choose a rich result. You become eligible for one by marking the page up with structured data, which is machine-readable code that labels what the page contains. If you are new to that layer, start with our guide to schema markup and come back here for the type list.

Two words get used loosely. "Rich snippet" is the older term and usually means the extras bolted onto a normal blue-link result. "Rich result" is Google's current word and covers that plus the bigger formats — carousels, host-level listings, job cards. We use Google's word throughout.

One honest caveat up front. Valid markup makes a page eligible. Google decides per query whether to show the enhancement, and often does not.

The 25 rich result types Google supports in 2026

Google maintains one authoritative list: the structured data gallery in Search Central documentation, last updated 16 October 2026. It carries 25 types. Anything not on it does not produce a rich result in Google Search, however valid the schema.org markup may be.

The "what it needs" column is deliberately broad. Each type has its own required and recommended properties, and getting one wrong is the usual reason a valid-looking page draws nothing. Our per-type posts carry those property tables; this page is the map, not the manual.

Need the markup itself? Our schema markup generator builds a clean block for the common types, and you paste it into AIOSEO > Custom Schema rather than into the post body.

The types Google withdrew — and when

Rich results get retired. Several guides still tell readers to add markup for formats that stopped appearing more than a year ago. Here is the documented record, taken from Google's own latest documentation updates page.

FAQ and HowTo are both gone. Neither produces a rich result in Google Search any more. HowTo went first; FAQ stopped appearing on 7 May 2026, and the documentation came down on 15 June 2026.

FAQPage markup is still valid schema.org. It is still machine-readable context about your page. It simply draws no rich result. That is the honest sentence, and it is the one to use when someone asks whether to keep it. We cover what that means for existing pages in our post on FAQ schema after the deprecation.

So keep the accordion on your page if users find it useful. Just stop expecting a stacked set of questions under your listing. If you want extra SERP real estate from question content now, the route is the ordinary featured snippet — earned by clear on-page answers, not by markup.

Three restrictions that catch people out

Three types on the list do not work the way the name suggests. Each one is a recurring reason a client's markup validates perfectly and still shows nothing.

• Carousel is a combination feature, not a standalone one. You cannot mark a page up as "a carousel". It must be paired with Recipe, Course list, Restaurant or Movie.
• Review snippet applies to a defined list of item types only: Book, Course list, Event, Local business, Movie, Product, Recipe and Software App, plus a set of creative-work and media types and Organization. Adding Review markup to an arbitrary page — a service page, a blog post, a homepage — earns no star rating. Google's 24 July 2026 guideline also rules out fake and undisclosed incentivised reviews, and self-serving reviews about your own business are ineligible. We do not put Review or AggregateRating markup on our own testimonials, and we advise clients the same way.
• Speakable is narrow. It covers news content read aloud on Assistant-enabled devices. It is not a general-purpose voice or audio tag.

Seven types come up in nearly every engagement we scope: breadcrumb, organization, product, local business, article, review snippet and event. All seven are currently supported. That matters, because a lot of advice in circulation still mixes them in with FAQ and HowTo as though the whole set were equally available.

What we see on Indian client sites

First-hand, from our own work: across the SEO accounts we run in India, the rich result types fall into two groups, and the gap between them is wider than most type lists admit.

The ones that move click-through for us, consistently:

• Local business — for anything with a physical catchment. Opening hours and a phone number in the result change who taps, especially on mobile.
• Product — price and in-stock status visible before the click. This is the single biggest CTR mover we see on e-commerce accounts.
• Review snippet on eligible item types, where genuine third-party ratings already exist.
• Video — a thumbnail next to a listing competes with everything around it.

The ones that are largely cosmetic, in our experience:

• Breadcrumb — it tidies the URL line and helps Google understand hierarchy. We have not seen it shift clicks on its own. Add it for the structure, not the uplift.
• Organization — valuable for entity clarity and knowledge panel accuracy, not for the click.
• Article — rarely changes the look of a listing for a mid-sized Indian site.

Both groups are worth marking up. Only the first group is worth budgeting against a traffic target. When a client asks us to "add schema to improve traffic", this is the distinction we walk them through first.

One more pattern worth naming: a rich result can win attention and still cost you the visit. Opening hours, a price, a rating — sometimes that is the whole answer the searcher wanted. That trade-off sits inside the broader shift we unpack in zero-click search.

Rich results are not an AI visibility tactic

This needs saying plainly, because a lot of 2026 advice gets it backwards.

Structured data governs rich-result eligibility. That is its job. Google's guide to performing well in its AI experiences, updated 10 July 2026, states that there are no additional technical requirements and no special structured data needed for AI Overviews or AI Mode.

So adding Product markup does not buy you a citation in an AI Overview. It buys you a chance at a price in a blue-link result. Those are different outcomes with different inputs. What actually governs the AI surfaces is covered in our post on how AI Overviews work.

Mark up your pages because the SERP formats are worth having. Not because someone sold you schema as an answer-engine lever.

Where to take this next

Work the list in priority order rather than all at once.

1. Match your page types to the 25. Most sites have three or four genuine matches, not fifteen. A services site is usually Organization plus Local business plus Breadcrumb.
2. Check what the type requires before you write anything. A missing required property means no rich result at all, not a partial one.
3. Remove the dead weight. If FAQ or HowTo markup is still on your pages, it is doing nothing for the SERP. Deciding to leave it is fine. Expecting it to draw a rich result is not.
4. Generate, then place it correctly. Build the block, put it in AIOSEO > Custom Schema or your theme, and keep it out of the post body where editors and plugins can strip it.
5. Re-check after any template change. Markup lives in templates. Template edits break it silently.

Expect timelines to behave like the rest of organic search. Markup is picked up on the next crawl, but the visible effect on clicks shows over three to six months as the pages it sits on earn rankings worth enhancing.