Google Retired FAQ Rich Results — Don’t Delete Your FAQPage Schema

News, May 27, 2026. Google has retired the FAQ rich result. As of May 7, 2026, the expandable question-and-answer dropdowns that used to appear under your search listings are gone. The reporting follows: the FAQ enhancement report and Rich Results Test support leave Search Console in June, and FAQ support exits the Search Console API in August. The first reflex across SEO teams this week was predictable — rip the FAQPage schema out of every template. Don't.

The critical detail almost every hot take missed: the schema.org FAQPage type is still valid. Google retired the display and the reporting, not the markup. And that markup is still doing real work — it helps the 5 AI engines (ChatGPT, Perplexity, Gemini, Claude, Grok) parse your Q/A pairs and cite them directly. Deleting it trades a real AI-extraction asset for nothing.

What Just Changed

On May 7, 2026, Google removed the FAQ rich result from the search results page. Pages that previously earned expandable Q/A accordions under their listing now appear as standard blue links. The visual real estate is gone, and with it the modest click-through lift that FAQ rich results provided in certain query classes.

This is a continuation, not a surprise. Google has been pruning rich result types for two years, and FAQ — easily abused, often keyword-stuffed — was a long-standing candidate. What makes the 2026 retirement notable is the timing: it lands inside Google's broader push toward AI surfaces. AI Overviews now reach roughly 2.5 billion users and AI Mode crossed 1 billion. The classic SERP is being simplified precisely as the answer layer above it expands.

The Deprecation Timeline

The rollout is staged across three dates. Knowing them prevents the silent-failure trap in August.

The August change is the one to flag now. Any dashboard or automated report that pulls searchAppearance = FAQ or RICHCARDS from the Search Console API will quietly return zeros instead of throwing an error. If you don't retire those queries before August, you will be looking at a flatline and mistaking it for a traffic collapse.

Why You Should Keep Your FAQPage Schema

Google retired the rich result and the reporting. It did not deprecate the schema.org FAQPage type. The markup remains valid, error-free, and machine-readable — and that last property is exactly why it still earns its place on the page.

FAQPage JSON-LD describes your content as a clean, structured set of question-and-answer pairs. That structure is a gift to AI crawlers. When ChatGPT, Perplexity, Gemini, Claude, or Grok retrieves your page, well-formed Q/A markup lets the engine lift an answer to a specific question without re-parsing your prose. It is one of the cleanest extraction signals you can ship — the same kind of structural clarity our Schema-Stitch approach is built around. The visual reward in Google is gone; the extraction value across the 5 AI engines is not.

This fits a pattern Google itself stated on May 15, 2026: AI-specific schema is not required for its AI features, because its systems read standard structured data and page content directly. Standard schema like FAQPage is the kind that keeps mattering — Google reads it, and so do the answer engines. We unpack that full guidance in our breakdown of Google's AI guidance.

What To Do This Week

Three moves. They take an hour and prevent both the panic-delete mistake and the August silent-failure trap.

Move 1 — Keep the FAQPage JSON-LD

Leave your FAQPage markup in place. It will not error, it will not hurt rankings, and it continues to feed structured Q/A pairs to the AI engines. The only thing that changed is that Google stopped rendering and reporting on it. Removing it is pure downside.

Move 2 — Stop measuring it through the GSC FAQ report

Pull any FAQ enhancement report from your monthly SEO review now, and audit your Search Console API calls for searchAppearance = FAQ or RICHCARDS filters before August. Replace those metrics rather than waiting for them to flatline. The report was never the real value of the markup — it was just the part Google chose to surface.

Move 3 — Measure it through AI citation instead

Reframe the ROI question. The right metric is no longer "how many FAQ rich result impressions did Google give me" — it is "do the AI engines cite my answers when my audience asks these questions." Track citation share for your FAQ topics across the 5 engines. That is the channel where FAQPage markup now compounds, and it is the channel Google's own roadmap is steering everyone toward.

The Bigger Picture

The FAQ rich result retirement is a small move that signals a large one. Google is thinning out the classic SERP's visual rewards — the dropdowns, the cards, the enhancements — at the exact moment it pushes search behavior into AI Overviews and AI Mode. The reward for structured content is migrating from a visual rich result you could see in a report to a citation you have to actively track across engines.

Brands that read this as "FAQPage is dead, delete it" will quietly strip extraction signal off their pages right as the answer layer becomes the dominant surface. Brands that keep the markup and switch their measurement to AI citation will hold the asset and start seeing the channel that actually pays it off. The markup didn't lose its value — Google just stopped being the one that reports it.

FAQ