Quick Reference: FAQ Schema Google Update
| Question | Answer |
| Are FAQ rich results gone? | Yes, as of May 7, 2026 |
| Is FAQPage schema banned? | No, it’s still valid structured data |
| Should I remove my FAQ schema? | Probably not, only if it’s thin or purely decorative |
| Who can still get FAQ rich results? | Government and authoritative health sites only |
| Does FAQ schema help with AI Overviews? | Yes, 3.2x more likely to appear in AI results |
| What’s the ideal FAQ answer length? | 40–60 words for optimal AI extraction |
| When does Search Console drop FAQ reporting? | June 2026 (Rich Results Test), August 2026 (API) |
| What schema should I use if users submit answers? | QAPage — not FAQPage |
| Can I use HTML inside Answer text? | Yes — <p>, <ul>, <li>, <a>, <strong>, <em> and more |
If you logged into Google Search Console recently and noticed your FAQ-related rich results have vanished, you’re not alone, and you’re not broken.
On May 7, 2026, Google officially removed FAQ rich results for good. Those expandable dropdown snippets that used to give your listing extra real estate on the results page? Gone. And with them, a strategy that many SEOs had come to rely on, almost like a cheat code.
But here’s the thing: panicking would be the wrong move. Because while Google no longer supports FAQ rich results, the underlying strategy, structuring your content around real questions and clear answers, has never been more valuable.
Let’s break down exactly what happened, why Google deprecated FAQ rich results, and what you should do right now.
FAQ Schema Deprecated: What Actually Changed and What Didn’t
Let’s be precise here, because there’s a lot of confusion floating around.
What’s gone:
- The expandable FAQ dropdown appearance in Google’s search results
- FAQ reporting in Google Search Console (being removed June 2026)
- FAQ rich result support in the Rich Results Test (June 2026)
- FAQ rich result data in the Search Console API (August 2026)
What’s NOT gone:
- FAQPage schema markup itself — it’s still valid structured data
- Your ability to publish helpful Q&A content on your pages
- The value of that structured data for AI-powered search
This is a critical distinction. Google hasn’t said “FAQ schema is spam, remove it immediately.” What they’ve done is retire a specific display feature — the visual treatment in the SERP. The underlying markup is still being read, still being processed, and in the age of AI search, it’s arguably more useful than ever.
Why Did Google Drops FAQ Rich Results From Search?
Google’s move didn’t come out of nowhere. They’d been scaling back FAQ rich results since 2023, when they restricted the feature to only high-authority government and health sites. The full deprecation in May 2026 was the final step in a process that had been unfolding for years.
The reason is straightforward: the feature was being abused. FAQ schema was originally meant to surface genuinely helpful question-and-answer content directly in search. Instead, it became a shortcut; marketers crammed keyword-stuffed questions into FAQ sections, duplicated content across pages, and used the markup purely to grab more SERP real estate rather than to serve actual users.
The result? Search results became cluttered with repetitive accordion-style answers that all looked the same. Google decided that wasn’t good for users, so they pulled it.
If your FAQ content was always genuine, real questions your customers ask, answered with actual expertise, this change affects your visibility but not your credibility. If you were gaming it, well, the game’s over anyway, as Google deprecated FAQ rich results.
Should You Remove Your FAQ Schema?
Short answer: NO
Google itself has said there’s no urgent need to remove FAQ structured data just because it no longer triggers a visual feature. A SearchPilot study from late 2024 found that removing FAQ schema didn’t produce a statistically significant change in organic traffic either way.
That said, use some common sense:
- Keep it if the questions and answers are real, visible on the page, and genuinely helpful to users
- Clean it up if it was implemented purely to manipulate rich results, thin, keyword-stuffed, or irrelevant Q&As
- Remove it if it adds maintenance complexity or confusion to your codebase without any benefit
| The key question is: Does this FAQ content actually help someone who lands on this page? If yes, keep the markup. If it was always a technical trick with no real substance behind it, this is a good time to clean house. |
Is FAQ Schema Still Relevant
If you walk away from this article with one insight, let it be this.
The same week Google retired FAQ rich results from its traditional search interface, AI-powered search was exploding. Google’s AI Overviews now appear on 50–60% of US searches. ChatGPT processes roughly two billion queries daily. Perplexity, Claude, Gemini, they’re all pulling answers from the web and citing sources.
And what format do these AI systems love most when extracting answers? Structured, question-and-answer content backed by FAQPage schema.
Pages with FAQ schema are 3.2x more likely to appear in Google AI Overviews compared to pages without it. Research from AirOps found that pages with clean structure paired with schema earn 2.8 times higher AI citation rates than poorly structured pages. AI-referred sessions jumped 527% between January and May 2025 — that growth is still accelerating.
Here’s why this makes intuitive sense: when ChatGPT or Gemini assembles an answer, it’s parsing the web for content it can extract, trust, and cite. Structured data removes the guesswork. Instead of forcing an AI to read a block of prose and infer what the question is, FAQPage schema tells it explicitly: “Here is the question. Here is the answer. This source said it.”
The SERP feature that made your listing bigger is gone. The backend value that gets your content cited in AI answers? Higher than ever.
What to Do Right Now
| Old Goal | New Goal |
| Win FAQ dropdown for more SERP space | Get cited in AI Overviews, ChatGPT, and Perplexity |
| Stuff keywords into FAQ questions | Write questions your audience genuinely asks |
| Maximize the number of FAQ entries per page | Focus on 3–7 high-quality, relevant FAQs per page |
| Write long, detailed answers | Create concise 40–60 word answers optimized for AI extraction |
| Add FAQ schema everywhere | Use FAQPage schema only where real Q&A content exists |
| Target traditional featured snippets only | Optimize for answer engines and conversational search |
| Repeat exact-match keywords excessively | Use natural language and semantic relevance |
| Treat FAQs as SEO filler content | Use FAQs to improve clarity, trust, and topical authority |
| Write generic questions | Address specific user pain points and intent |
| Focus only on Google rankings | Optimize for multi-platform AI visibility |
1. Audit your existing FAQ content
Before anything else, look at what you actually have. Go through pages with FAQ schema and ask honestly: are these questions real? Are the answers useful? Are they visible on the page (not hidden or injected purely via JSON-LD)?
If yes — great, you’re in a better position than most. If not, now is the time to fix it rather than delete it.
2. Monitor your CTR in Search Console
The FAQ dropdown was doing persuasion work on your behalf. Users could see your questions before clicking. Without that, some of your pages may see a CTR dip even if rankings haven’t moved.
Compare your click-through rate 28 days before and after May 7, 2026, at the page level. Don’t panic over query-level noise — the UI changed, that’s what you’re measuring. But if specific high-traffic pages took a hit, that’s worth addressing with better title tags and meta descriptions.
3. Optimize for AI citation, not SERP pixels
This is the strategic shift. Your FAQ content needs to be built for AI extraction now, not for visual real estate.
Concretely, that means:
- Keep answers between 40–60 words — this is the sweet spot for AI extraction. Long enough to be substantive, short enough to be quoted directly
- Lead with the answer — don’t bury the response after a paragraph of context. Give the direct answer in the first sentence, then add detail
- Use plain language — avoid jargon, hype, or vague phrasing that an AI can’t confidently extract
- Make sure Q&As are visible on the page — not hidden in tabs or injected only via code. If a human can’t see it, an AI is less likely to trust it
4. Don’t abandon structured data — expand it
FAQ schema is one piece. If you’re only using it, you’re leaving signals on the table.
In 2026, a well-optimized page typically carries a combination of schema types: Article for authorship and content type, Organization for brand identity, FAQPage where Q&A content genuinely exists, and BreadcrumbList for site structure. Together, these create what some SEOs call a “knowledge graph lite” for your brand — a machine-readable picture of who you are, what you cover, and why AI systems should cite you.
5. Shift how you measure success
FAQ impressions in Search Console will disappear by June 2026. If your reporting still relies on them, update your dashboards now before stakeholders start asking questions.
The new metrics that matter:
- AI Overview impression rate (trackable in Search Console’s AI Overviews filter and Semrush’s AI Toolkit)
- Organic CTR at the page level — the most reliable downstream signal
- AI citation frequency — how often tools like Perplexity or ChatGPT reference your pages for target queries
The Bigger Picture: From Ranking to Being Cited
The May 2026 FAQ deprecation is a symptom of a larger shift that’s been underway for a couple of years now.
Traditional SEO was about ranking, getting your blue link as high as possible on the results page so users would click it. That model is still relevant, but it’s no longer sufficient on its own.
In 2026, a growing proportion of users begin their information journey with an AI-generated answer. They ask a question, get a synthesized response from Google AI Overviews, ChatGPT, or Perplexity, and may never click through to any source at all. The websites that get cited in those answers get brand exposure, trust-building, and eventually traffic. The ones that don’t are increasingly invisible, even if they rank #3 on the traditional SERP.
An Ahrefs study from February 2026 found that only 38% of pages cited in Google AI Overviews rank in the top 10 of traditional search results. That figure was 76% in mid-2025. The gap between “ranking well” and “getting cited by AI” is widening fast.
FAQ schema, done right, is one of the simplest and cheapest signals you can give AI systems to say: “This content has clear answers to clear questions. It’s worth citing.”
The Bottom Line
Google killing FAQ rich results marks the end of an old SEO tactic, but not the end of FAQ strategy itself. In fact, the role of structured Q&A content is becoming even more important as AI-powered search platforms like ChatGPT, Google AI Overviews, Gemini, and Perplexity reshape how users discover information online.
The websites winning in 2026 are no longer the ones simply chasing SERP features. They’re the ones creating genuinely helpful, well-structured, machine-readable content that AI systems can confidently extract, understand, and cite.
That means the future of SEO is shifting from:
- ranking pages → becoming trusted sources
- optimizing for clicks → optimizing for citations
- writing for algorithms → writing for both humans and AI systems
At Orange MonkE, this is exactly how we approach modern SEO: combining technical optimization, AI-ready content structure, semantic search strategy, and authority-driven content that performs across both traditional search and emerging AI answer engines.
In the new search era, visibility won’t just come from being ranked; it will come from being referenced.

We build the digital growth engine for businesses that don't have the time, team or clarity to do it themselves
Let's Start Your Success Story