schemas

Rich Results: Schema Types That Win SERP Features

Which schema types still earn Google rich results in 2026, what was deprecated, measured CTR impact, and exactly how to qualify and keep your features.

Pages with rich results earn 58% of available clicks while standard listings capture just 41% — and that gap is widening as Google removes the SERP features that used to be easy wins (Milestone Research via Tonic Worldwide). Between September 2023 and May 2026, Google retired at least 10 rich result types — the largest contraction of structured data features in search history — while simultaneously making schema more valuable than ever as AI infrastructure (Digital Applied).

The 2026 reality: fewer schema types produce visible SERP features, but the 31 that remain generate measurable CTR lifts, and accurate structured data now influences whether your pages appear inside Google AI Overviews, ChatGPT, Perplexity, and Copilot results.

Quick answer:

31 schema types actively produce rich results in Google Search as of mid-2026. The highest-value active types are Product, Recipe, Video, Review snippet, Event, Article, LocalBusiness, and BreadcrumbList. FAQ and HowTo rich results are fully deprecated. Valid schema makes a page eligible — not guaranteed — to receive a feature. Implement JSON-LD in <head>, match schema to primary page content, and validate with Google's Rich Results Test.


What rich results actually are

A rich result is any Google Search listing that includes visual enhancements beyond the standard blue link, meta title, and description. These include star ratings, price ranges, recipe cook times, event dates, video thumbnails, product images, and breadcrumb trails.

Rich results require structured data — most commonly Schema.org vocabulary expressed in JSON-LD format — that Google can parse, validate, and choose to display. "Choose to display" is the key phrase: valid schema creates eligibility, not a display guarantee (Google Search Central — Structured Data Policies).

Schema is now doing double duty. Google, Microsoft, ChatGPT, Perplexity, Gemini, and Copilot all parse structured data for AI-generated answers. Google's Knowledge Graph holds over 500 billion facts about 5 billion entities, and accurate entity schema is a direct input to that graph (Tonic Worldwide).


The deprecation wave: what Google removed (2023–2026)

Understanding what no longer works is as important as knowing what does.

FAQ rich results — fully deprecated May 7, 2026

FAQ rich results had the highest CTR of any SERP feature ever studied at 87% (Milestone Research via Search Engine Journal) — which makes their removal the most commercially significant schema change in years.

The timeline:

  • May 2019: Google launched FAQ rich results
  • August 8, 2023: Restricted to "well-known, authoritative government and health websites" only. Commercial sites lost eligibility overnight (Google Search Central blog)
  • By August 2023: SISTRIX reported almost half of all FAQ snippets had already disappeared (Passionfruit)
  • May 7, 2026: FAQ rich results stopped appearing for ALL sites, including government and health domains (Search Engine Land)
  • June 2026: FAQ filter, report in Search Console, and Rich Results Test support removed
  • August 2026: FAQ API support in Search Console API removed

What this means for your existing FAQ schema: FAQPage remains a valid Schema.org type. Google explicitly states that structured data not used for display "does not cause problems for Search" (Google Search Central). Your existing FAQ markup likely still helps AI systems parse your content. You do not need to rush removal — but adding new FAQ schema purely for SERP display is now pointless.

Approximately 168,000 articles with templated FAQ markup had accumulated on the web before deprecation, largely due to advice that FAQ schema boosted AI visibility. This scale of low-quality markup is partly why Google removed the feature (Lily Ray / Amsive, via Passionfruit).

HowTo rich results — deprecated September 2023

  • August 2023: HowTo removed from mobile; limited to desktop "primary content" pages
  • September 2023: HowTo fully deprecated from desktop as well (Digital Applied)

HowTo schema remains valid Schema.org markup and is not penalised by Google.

Seven types retired June 2025

Google removed structured data support for these types simultaneously, citing low usage and low user value (Passionfruit):

  • Book Actions
  • Course Info
  • Claim Review
  • Estimated Salary
  • Learning Video
  • Special Announcement
  • Vehicle Listing

Practice Problem — January 2026

Google removed documentation for the Practice Problem structured data type, which had previously served educational/math content.


Active rich result types: the full 2026 list

Google's structured data gallery (Google Search Central search gallery) lists 31+ actively supported types as of mid-2026. Below is the complete reference table.

Rich result types at a glance

Schema Type Key Required Properties Status CTR Uplift
Article / NewsArticle / BlogPosting headline, image, datePublished, author Active Moderate
BreadcrumbList itemListElement Active Navigation clarity
Course list Course with name, provider Active Moderate
Dataset name, description Active Niche
Discussion Forum name, url Active Community
Education Q&A name, acceptedAnswer Active Edu queries
Employer Aggregate Rating name, aggregateRating Active Job searches
Event name, startDate, location Active High for events
FAQPage mainEntity, Question, Answer Deprecated (display) 0% (display gone)
HowTo step, supply, tool Deprecated 0%
Image metadata license, creditText Active Image search
Job Posting title, hiringOrganization, jobLocation Active Job searches
Local Business name, address, geo Active Local pack
Math Solver mathExpression Active Edu/math
Movie name, image, director Active Entertainment
Organization name, url, logo Active Knowledge Panel
Product / Merchant listing name, image, offers (price + currency) Active High for commerce
Profile Page name, url Active Entity
Q&A Page name, acceptedAnswer Active (NOT deprecated) Community
Recipe cookTime, recipeIngredient, recipeInstructions Active High — 62% CTR
Review snippet aggregateRating (third-party only) Active (restricted) +10–31%
Software App name, operatingSystem, offers Active App queries
Speakable cssSelector Active (AI signal only) AI citations
Subscription / Paywalled content isAccessibleForFree, hasPart Active Publisher
Vacation Rental name, address, offers Active Travel
Video name, thumbnailUrl, uploadDate Active 62% CTR

Important distinction: QAPage (for community Q&A with multiple user-submitted answers, like forums) is NOT affected by the FAQ deprecation. Only FAQPage (single authoritative answer per question) lost its display feature (Google Search Central).


CTR impact by schema type

Raw CTR data from multiple research sources:

Rich results vs standard listings:

By feature type:

Review star ratings specifically:

  • Mobile CTR uplift: +31% (3.4% without stars → 4.9% with stars)
  • Desktop CTR uplift: +10% (4.04% without → 4.49% with) (Elfsight internal research)

AI Overviews — the new rich result:

  • When AI Overviews appear, organic CTR drops 50–61% (Seer Interactive, Ahrefs via Almcorp)
  • Pages cited inside AI Overviews earn 120% more organic clicks per impression than uncited pages on the same queries (Seer Interactive, April 2026)
  • AI-referred visitors convert at 22.79% vs 2.45% for standard Google organic — a 9.3x conversion rate advantage (The HOTH)

Eligibility vs guarantee: the rules Google enforces

Valid, error-free schema makes a page eligible for a rich result. It does not guarantee display. Google's algorithmic and manual filtering layers are distinct from schema validation.

What triggers loss of eligibility

Content mismatch: Schema must match primary page content. FAQ schema on a page where FAQ is a minor sidebar section is now ineligible. Product schema on a non-purchasable landing page is classified as misleading markup (itlover.tech).

Self-serving reviews: Reviews of a business on that business's own site are not eligible for star ratings in search results — a policy Google has enforced since 2019 and confirmed in its updated review snippet documentation (last updated 2025-12-10) (Google Search Central — Review Snippet). Third-party review platforms (eKomi, Yelp, HomeAdvisor) publishing reviews on their own domains are unaffected (Birdeye).

Review eligibility is schema-type restricted: Star ratings only display for these 17 schema types: Book, Course, CreativeWorkSeason, CreativeWorkSeries, Episode, Event, Game, HowTo, LocalBusiness, MediaObject, Movie, MusicPlaylist, MusicRecording, Organization, Product, Recipe, SoftwareApplication (Search Engine Land).

Inflated aggregate ratings: A minimum of 5 genuine, verifiable reviews is the practical safe threshold. Unverifiable review counts face enhanced scrutiny (itlover.tech).

March 2026 core update — "Information Gain" filter: 24.1% of top-10 pages dropped out due to a new Information Gain algorithm component. Schema on low-information-gain pages lost eligibility even when technically valid (itlover.tech).

Manual actions: Google can remove rich result eligibility via a manual action without affecting standard web search rankings (Google Search Central — Structured Data Policies).


High-priority schema types: implementation details

Product schema (highest ROI for e-commerce)

Required properties for merchant listings: name, image, offers with price/priceSpecification.price + priceCurrency (Google Search Central — Product).

Product schema is the gateway to Google's Shopping Graph (60 billion product listings) and the newly launched Universal Cart (UCP), which went live May 19, 2026 across the US, Canada, and Australia with partners including Nike, Sephora, Target, Walmart, and Shopify merchants (Digital Applied). UCP eligibility requires a separate Merchant Center integration — Product schema alone is not sufficient.

Recipe schema

Recipe rich results appear for: prep time, cook time, aggregate rating, calories, and ingredient count. Video schema nested inside Recipe markup enables Key Moments in video results. Recipe pages with rich results see a 62% CTR in video-optimised results (Milestone Research).

Video schema

Required: name, thumbnailUrl, uploadDate. Strongly recommended: contentUrl, description, duration, and hasPart (Clip schema for Key Moments) (Digital Applied). Video is one of the highest-CTR rich result types at 62% and has not been subject to any deprecation.

Event schema

Required: name, startDate, location. Schema.org v29.4 (released December 8, 2025) added ConferenceEvent, PerformingArtsEvent, and InstantaneousEvent subtypes for more precise event markup (Digital Applied).

LocalBusiness schema

Required for local rich results: name, address. Strongly recommended: geo coordinates, openingHours, telephone, aggregateRating (third-party reviews only), priceRange (Hill Web Creations). Local Pack position 1 achieves 17.6% CTR — higher than organic position 1 on many query types.

Organization / Entity schema (AI infrastructure)

Organization with SameAs pointing to Wikidata, LinkedIn, and Crunchbase is the highest-leverage schema investment for AI citation in 2026. The SameAs property connects your website to the Knowledge Graph. knowsAbout on Organization and Person entities creates topical authority signals used by AI Mode for source selection (Digital Applied).

Google's Knowledge Graph now holds over 500 billion facts and is the primary lookup table for Google AI Mode, Google Gemini, and AI Overviews (Tonic Worldwide). Microsoft's Fabrice Canel confirmed in March 2025 that schema markup helps Microsoft's LLMs understand content for Copilot answers (Passionfruit).

Speakable schema (AI-only, no visual SERP feature)

Speakable schema produces no visible SERP enhancement but flags your most citable passage for AI synthesis tools. Recommended for your top-10 highest-traffic informational pages (Digital Applied).


Technical implementation requirements

  • Format: JSON-LD in <head> — Google's preferred format; microdata and RDFa have not increased in efficacy (Digital Applied)
  • Nesting: Use @graph array to nest related entities in a single block
  • Mobile parity: Mobile version must carry the same structured data as desktop — mobile-first indexing applies (Google Search Central)
  • File size: Googlebot reads HTML up to a strict 2MB limit (itlover.tech)
  • Core Web Vitals still matter: INP < 200ms (effectively < 150ms under competition), LCP < 2.5s, CLS < 0.1 (itlover.tech)

Validation tools:

For a complete implementation walkthrough covering JSON-LD syntax, validation errors, and deployment, see Structured Data & Schema Markup: The 2026 Guide.


Priority ranking: where to invest schema effort in 2026

Based on display eligibility, CTR data, and AI infrastructure value:

  1. Entity schema — Organization + SameAs, Person + knowsAbout (AI citation infrastructure)
  2. Product + Offer — Commerce sites; required for Shopping Graph and UCP eligibility
  3. Article + author — Content sites; feeds AI Overview citations
  4. LocalBusiness + geo — Local search; Local Pack is highest-CTR SERP position per impression
  5. Review schema (third-party aggregated) — Star ratings uplift CTR +10–31%
  6. Recipe + Video — Highest visible rich result CTR at 62%
  7. Event — Transactional intent, high engagement rate
  8. Speakable — Top informational pages only; AI signal, no visual feature
  9. BreadcrumbList — Every site; navigation clarity, minor CTR uplift
  10. Retire investment in: FAQ (display gone), HowTo, and the seven June 2025 deprecated types

Only 12.4% of registered domains (45 million of 362.3 million) currently use any structured data (Tonic Worldwide). That gap is your competitive advantage — if your schema is accurate and matched to primary content.


The AI era shift: schema as infrastructure, not decoration

The strategic framing for schema has changed fundamentally. Structured data is no longer primarily about winning SERP visual features — it is about being machine-readable for an AI-first index.

The numbers:

Google's May 2026 guide on optimising for generative AI states the priority is "non-commodity content" with unique perspective, original research, and authoritative experience — not special format requirements like llms.txt (itlover.tech). Schema is the structural layer that makes authoritative content machine-legible.

For a broader look at how entity schema feeds into topical authority signals, see Technical SEO.


Frequently asked questions

Does removing FAQ schema hurt my site?

No. Google confirmed that structured data not used for display "does not cause problems for Search." FAQPage schema may still help AI systems (ChatGPT, Perplexity, Gemini) parse your content. Only remove FAQ markup if it was purely decorative and adds maintenance overhead. If your FAQ content genuinely answers user questions, keep both the content and the schema (Google Search Central).

How many reviews do I need before adding Review schema?

A minimum of 5 genuine, verifiable reviews is the practical safe threshold for aggregate ratings. Below that, Google's systems flag the data as potentially inflated. The reviews must come from third parties — your own business cannot add a review about itself and display star ratings in search results (Elfsight, Google Search Central Review Snippet docs).

My schema is valid — why am I not getting rich results?

Five common reasons: (1) Schema type is deprecated (FAQ, HowTo, one of the seven June 2025 types). (2) Schema describes supplementary content, not the page's primary purpose. (3) Page has a manual action from Google. (4) Page quality is too low — Information Gain filter since March 2026 removes eligibility from thin content. (5) Feature is not available in your country/device combination (some beta features are geo-restricted). Check Google Search Console Enhancements reports for specific error messages (Google Search Central — Structured Data Policies).

Is QAPage schema the same as FAQPage schema?

No — and this distinction matters. QAPage is for pages where multiple users submit different answers to a question (forums, community Q&A). FAQPage is for pages where a single authoritative answer exists per question. Only FAQPage rich results were deprecated. QAPage remains fully active and unaffected (Google Search Central).

What schema should I add for AI Overview citations?

Entity schema is the primary lever. Implement Organization with SameAs pointing to Wikidata and LinkedIn (the most powerful Knowledge Graph connectors), add knowsAbout for topical signals, and use Speakable to flag your most citable passages. For commerce, accurate Product markup feeds the Shopping Graph. Note that a December 2024 Search/Atlas study found no direct correlation between schema coverage and AI citation rates — content quality and entity accuracy matter more than schema volume (Passionfruit, Digital Applied).

Originally published in the EcomExperts SEO library.

Ready to Become One of Our Success Stories?

Book a free 30-minute consultation and get a custom SEO strategy that will increase your revenue, not just your traffic. We'll show you exactly how to outrank your competitors and capture more customers.

Book your Free 30-minute Consultation Now