Main area
Agency
technisches-seo

Schema Types for Rich Results — what still triggers SERP features in 2026

Redaktion ·

Not every piece of schema.org markup you add produces a pretty search result with stars, images or prices. That’s the uncomfortable truth many structured-data strategies trip over: the schema.org vocabulary is huge, but the subset Google actually translates into a rich result is small — and shrinking. This article separates the types that still trigger SERP features in 2026 from the ones that only improve your page’s machine understanding. Both are valuable, but only the first visibly changes your snippet.

Rich result vs. machine understanding — the key distinction

Structured data has two effects you mustn’t confuse:

  • Rich results — visible SERP enhancements: star ratings, product prices, breadcrumb paths, recipe cards, event listings. Here the markup directly changes how your result looks.
  • Machine understanding — invisible structuring: Google (and AI answer systems) recognise via schema what an entity is, who the author is, which organisation a page belongs to. This triggers no SERP feature of its own, but helps with entity assignment and increasingly with AI Overviews.

Anyone who adds schema only for rich results and is disappointed when no stars appear has overlooked the second effect. Conversely, anyone expecting every markup to produce a snippet will also be disappointed. Both expectations are wrong.

The types that still reliably trigger rich results in 2026

These schema.org types continue to produce visible SERP features — provided the required properties are set and the content policies are followed:

  • Product / Offer — price, availability, rating stars right in the result. One of the strongest levers for shops. Required: name; recommended/triggering: offers (with price, priceCurrency, availability), aggregateRating, review.
  • Review / AggregateRating — star ratings embedded in other types (Product, LocalBusiness, Recipe). Required: itemReviewed, reviewRating or ratingValue. Must reflect real ratings visible on the page.
  • BreadcrumbList — the path navigation instead of a bare URL under the title. Low effort, almost always adopted. Required: itemListElement with position and name.
  • Recipe — recipe cards with image, time, rating, sometimes in a carousel. Required: name, image; triggering: recipeIngredient, recipeInstructions, aggregateRating, cookTime.
  • Event — date, location, ticket hint as an interactive listing. Required: name, startDate, location.
  • VideoObject — video preview with thumbnail, duration, key moments. Required: name, thumbnailUrl, uploadDate.
  • Article — larger title image and headline formatting, especially in Top Stories and Discover. Required mostly recommended: headline, image, datePublished, author.
  • Organization / LocalBusiness — knowledge-panel data, logo, opening hours, rating, directions. Required for LocalBusiness: name, address; strongly recommended: openingHours, telephone, geo.
  • JobPosting — interactive job-search results with logo and location. Required: title, datePosted, hiringOrganization, jobLocation.

The removed and heavily restricted types

This is where the most has changed — and exactly where outdated SEO guides lose their value.

FAQ — effectively sunset since May 2026

For a long time, FAQPage markup was the cheapest trick for more SERP real estate. That’s over. Back in 2023, Google already restricted FAQ rich results to well-established government and health sites. Then, on 7 May 2026, FAQ rich results were removed from Search entirely — the search appearance, the rich-results report and the test-tool support follow in June and August 2026 respectively (as of June 2026). For normal sites, FAQPage markup therefore triggers no rich result anymore. The content itself stays valuable for readers and AI answers — but no longer as a snippet lever.

HowTo — fully removed

HowTo rich results were switched off on desktop in 2023 and fully across all devices by 2024. HowTo markup no longer produces any SERP feature today. Maintaining it is wasted time if the rich result was the only goal.

The seven niche types retired in 2025

In June 2025, Google removed seven more, barely-used rich-result types: Book Actions, Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement and Vehicle Listing. The reasoning: too little usage, no measurable added value. Anyone maintaining one of these types should drop the effort.

Required vs. recommended properties — why markup often doesn’t take

Every rich-result type has required and recommended properties. The rule is hard: miss even one required field and there’s no rich result — no matter how clean the rest is. Recommended fields improve probability and presentation, but aren’t a deal-breaker.

Typical pitfalls:

  • Product without a valid offers.price — no price snippet, even though the markup is “there”.
  • Review without itemReviewed or with ratings not actually visible on the page — a policy violation; the markup is ignored or penalised.
  • Fields in the markup that don’t match visible page content — Google requires alignment between JSON-LD and what the user sees. Discrepancies lead to manual actions.

The Rich Results Test and the Search Console “Enhancements” report show you, per URL, which required fields are missing. That’s the mandatory diagnosis before any go-live.

Realistic expectation: markup ≠ guaranteed snippet

Even when all required fields are in place and the test is green, Google guarantees no rich result. Display additionally depends on page quality, query context, device and Google’s own judgement of whether the feature helps the user. Structured data is an entry ticket, not a push-button trigger. Internalise that and you stop treating missing stars as a bug and start maintaining schema as a long-term understanding and eligibility layer.

FAQ

FAQ

Does FAQPage markup still earn a rich result in 2026?
For normal sites, no. Google removed FAQ rich results from Search on 7 May 2026; since 2023 they were already limited to authoritative government and health sites. The content stays useful for readers and AI answers but no longer triggers a snippet (as of June 2026).
Is HowTo markup still worth it?
No, if the goal is a rich result. HowTo rich results were fully removed across 2023 to 2024 and no longer produce a SERP feature. Maintaining it is wasted time unless another purpose (machine understanding) is behind it.
Why does my markup not appear as a rich result even though the test is green?
A passed test only means eligibility, not a guarantee. Google additionally decides by page quality, query context and device whether it shows the feature. Markup is an entry ticket, not a switch.
What happens if a required property is missing?
Then there is no rich result for that type — no matter how complete the rest is. Recommended fields only improve probability and presentation; required fields are a hard deal-breaker. The Search Console report shows missing fields per URL.
Which schema types are the safest levers in 2026?
Product/Offer, Review/AggregateRating, BreadcrumbList, Recipe, Event, VideoObject, Article and Organization/LocalBusiness still reliably trigger SERP features — provided the required fields are set and the markup mirrors visible page content.

Conclusion

The schema landscape in 2026 is smaller and stricter than three years ago. FAQ and HowTo, once the easiest snippet wins, are dead for normal sites. What remains are the robust types — Product, Review, Breadcrumb, Recipe, Event, Video, Article, Organization/LocalBusiness — and the iron rule that missing required fields topple any rich result. Treat structured data as a two-layer tool: visible rich results on top, the growing machine understanding for entities and AI answers underneath. And always check the state against the official search gallery, not old tutorials.

How schema fits into the bigger picture of crawling, rendering and indexing is shown in the sister article on technical SEO.

Themenuebersicht

Technisches SEOStructured Data