Short answer: no. Keep your FAQ schema — but not for the reason you added it.
On May 7, 2026, Google stopped showing FAQ rich results in Search. The expandable question-and-answer dropdowns that used to appear under organic listings are gone. For every site, in every niche, with no exceptions. If your pages lost those dropdowns overnight, nothing is broken on your end. Google turned the feature off.
That leaves a practical question: if the markup no longer earns extra space in search results, is it dead weight? It is not. FAQ schema stopped being a SERP feature and became an AEO asset. This article covers what exactly changed, what FAQPage markup still does in 2026, when removing it actually makes sense, and what to do with your FAQ content now.
What Exactly Google Removed
FAQ rich results were the two-to-four expandable Q&A rows Google displayed directly under a page’s title and description in search results. Sites earned them by adding FAQPage structured data to pages with question-and-answer content.
For years they were one of the easiest rich results to win. They made your listing taller, pushed competitors further down the screen, and answered pre-click questions. SEO teams added FAQ blocks to thousands of pages purely to get them.
This did not happen all at once. Google first cut FAQ rich results back in August 2023, limiting them to well-known health and government websites. May 7, 2026 finished the job: the feature is now retired for everyone, including those sites.
Two things did not change:
- Your FAQ content still appears on your page and still gets crawled and indexed
- FAQPage markup is still valid structured data — Google did not deprecate the schema type itself, it stopped rewarding it with a visual feature
Why Google Did It
Google has not published a detailed explanation, and it does not need to. The timeline speaks for itself: on May 19, 2026 — twelve days after removing FAQ rich results — Google made AI Mode the default search experience in the US.
AI Overviews and AI Mode answer questions directly on the results page. Keeping a second question-answering feature under individual listings would duplicate that job and compete with it for space. FAQ dropdowns answered questions for free next to your link. AI answers them inside Google’s own interface. From Google’s perspective, one of these had to go, and it was never going to be the AI.
The practical takeaway: Google is consolidating question-answering into AI surfaces. Which is exactly where your FAQ content still has a role.
What FAQ Schema Still Does in 2026
Here is the part most site owners miss. The SERP feature died. The machine-readability of your content did not.
AI crawlers still parse FAQPage markup. ChatGPT, Perplexity, Gemini, and Google’s own AI systems read structured data when they crawl your pages. A marked-up FAQ block hands them a clean, unambiguous package: this exact question, this exact answer, no guessing about where an answer starts and ends. That precision matters when an AI system decides which source to quote. We broke down how that selection works in our guide to Answer Engine Optimization — structure and extractability are core ranking factors for AI citations, and FAQ markup delivers both.
Q&A format matches how people use AI search. Queries in ChatGPT and AI Mode are conversational questions, not keyword fragments. Content already written as direct questions with concise, factual answers is the closest possible match to what these systems need to generate a response. You are not reformatting content for a machine — the machine’s input format happens to be your FAQ.
Structured answers get extracted, vague text gets skipped. Research on AI citation behavior, including SE Ranking’s studies of what ChatGPT and AI Overviews cite, points the same direction: AI systems favor pages with clearly structured, specific, extractable answers. A 3-sentence FAQ answer with a price, a timeframe, or a concrete step is extraction-ready. Ten paragraphs of narrative are not.
Google still reads the markup for understanding. Rich result or no rich result, structured data helps search engines understand what a page contains. FAQPage markup tells Google «this section answers these specific questions» — useful context for matching your page to question-shaped queries, in both classic results and AI surfaces.
So the value did not disappear. It moved. Before May 2026, FAQ schema bought you screen space. Now it buys you extractability — and in a search environment where AI answers sit above every organic result, extractability is the more valuable currency.
When Removing FAQ Schema Makes Sense
Keeping the markup is the default. But there are real cases where deleting it is the right call.
The FAQ was fake to begin with. If the questions were invented purely to trigger rich results — restating obvious points, keyword-stuffing, answering things no customer ever asked — the feature that justified them is gone. Content that exists only to game a retired SERP feature has no audience, human or AI. Delete the block, not just the schema.
The answers are thin or circular. «How much does it cost? Contact us for a quote.» That answer gives an AI system nothing to extract and a user nothing to act on. Either rewrite it with real information or remove it.
The markup does not match the visible content. If your schema lists questions that no longer appear on the page — a common leftover from old plugins and page rebuilds — you have a mismatch that violates Google’s structured data guidelines. Fix it or strip it.
You are marking up every page indiscriminately. Some plugins inject FAQPage markup sitewide, including on pages with no FAQ content. That was always sloppy. Clean it up.
The pattern: remove schema where the content behind it is worthless. Keep it where the content is real. The markup was never the problem — low-effort content chasing a SERP feature was.
What to Do Instead: 4 Practical Steps
1. Rewrite questions the way people actually ask them
Pull real questions from sales calls, support emails, and the People Also Ask boxes for your target queries. «What is your service area?» is a page filler. «Do you serve [city] and how much does travel cost?» is a query someone types into ChatGPT. The closer your question matches real phrasing, the better your odds of being the extracted answer.
2. Make every answer specific and self-contained
Two to four sentences. Include the number, the price range, the timeframe, the step. Each answer should make sense if quoted alone with no surrounding context, because that is exactly how an AI system will use it. If an answer cannot stand alone, it will not get picked up.
3. Validate what you have
Run your key pages through Google’s Rich Results Test and check the structured data report in Search Console. You are no longer chasing a rich result — you are checking that the markup parses cleanly and matches the visible content. Broken or mismatched schema helps nobody.
4. Put FAQ blocks on money pages, not just blog posts
Service pages, pricing pages, location pages. That is where high-intent questions live: how much, how long, what is included, what happens if. These are the pages you want AI systems quoting when someone asks «how much does [your service] cost in [your city]» — and they are usually the pages with the thinnest FAQ coverage. This is standard practice in our SEO work: every core service page gets a real FAQ section built from real client questions.
Not Sure What Your Schema Is Doing? Find Out
We run a free AEO audit: we check your structured data, review how extractable your key pages are for AI search, and tell you exactly what to keep, fix, or remove — no generic checklist, specific pages and specific changes.
Get Your Free AEO Audit — Contact Us
No commitment. You will know where you stand in a few days.
TwoX Digital is a digital marketing agency specializing in SEO, AEO, GEO, and PPC for businesses in the US and English-speaking markets.
