Google Killed FAQ Rich Results. Why Smart SEO Teams Are Still Keeping FAQs for AEO and GEO
Author: Kevin C. Roy · GreenBanana SEO · Published: 2026-05-19
What Changed?
Google’s FAQ structured data documentation now says that as of May 7, 2026, FAQ rich results are no longer appearing in Google Search. Google also says it will drop the FAQ search appearance, FAQ rich result report, and Rich Results Test support in June 2026, with Search Console API support for FAQ rich result data scheduled to be removed in August 2026.
Google’s Search Central update log also confirms that a deprecation notice was added because the FAQ rich result feature will no longer appear in Google Search starting May 7, 2026.
Google removed the visual FAQ reward, not the value of clear answers.
Description: A clean diagram showing the split between outdated FAQ rich-result tactics and useful FAQ content for AEO and GEO.
That is a real change.
But it is a narrow change.
Google did not say:
- Remove all FAQ sections.
- Stop answering customer questions.
- Never use FAQ content.
- FAQs are bad for users.
- Questions and answers no longer matter.
Google changed the visible Search result treatment.
The old SEO promise was:
“Add FAQ schema and maybe earn expandable FAQ dropdowns under your listing.”
That promise is now obsolete.
The new strategy is:
“Use FAQ content to make your page clearer, more complete, more answerable, and easier for AI systems to interpret.”
FAQ Schema vs. FAQ Content
This is where teams get confused.
FAQ schema and FAQ content are not the same thing.
| Item | What It Is | 2026 Strategic Role |
|---|---|---|
| FAQ schema | Structured data that tells machines a page contains question-and-answer content | No longer a Google FAQ rich-result tactic |
| FAQ content | The visible questions and answers users can read on the page | Still valuable for users, SEO context, AEO, GEO, and answer extraction |
| FAQ rich result | The old enhanced Google Search result with expandable FAQ dropdowns | No longer appearing in Google Search as of May 7, 2026 |
| AI-readable FAQ | Clear, visible, concise Q&A content that answers real questions | Still useful as answer infrastructure |
The mistake is deleting useful FAQ content just because Google removed the visible rich-result benefit.
That is like throwing away the playbook because the scoreboard changed.
Why FAQs Still Matter for AEO and GEO
AEO, or Answer Engine Optimization, is about structuring content so answer engines can understand and use it.
GEO, or Generative Engine Optimization, is about improving the odds that generative AI systems can select, summarize, cite, or reference your content.
Neither one is guaranteed.
No serious SEO should promise that a specific FAQ will get cited by ChatGPT, Gemini, Perplexity, Google AI Overviews, or AI Mode.
But clear FAQ content can make a page easier to process.
That matters because modern AI search systems increasingly show sources, citations, links, or source panels. OpenAI says ChatGPT Search responses may include inline citations, and users can open sources to inspect where information came from. OpenAI’s deep research documentation also says outputs include citations or source links so users can verify information.
Google is also making source visibility a bigger part of AI search experiences. In May 2026, Google announced updates to AI Mode and AI Overviews designed to help users find relevant websites, original content, and useful sources across the web. Google’s AI Mode page says AI Mode provides helpful links so users can evaluate sources and explore further.
So the new question is not only:
“Can this page rank?”
The better question is:
“Can this page provide a clean, credible, extractable answer that an AI system can understand and a human can verify?”
That is where FAQs still work.
What Most Teams Are Missing
Most teams are going to treat this as a schema issue.
It is not only a schema issue.
It is a content architecture issue.
A weak FAQ section looks like this:
- Generic questions.
- Keyword-stuffed wording.
- Duplicate answers across many pages.
- Thin answers that do not solve anything.
- Hidden markup that does not match the page.
- Questions no real customer would ask.
A strong FAQ section looks like this:
- Real buyer questions.
- Direct first-sentence answers.
- Entity-specific language.
- Clear definitions.
- Conditions and exceptions.
- Helpful next steps.
- Visible content that matches any structured data used.
- Answers that can stand alone when quoted or summarized.
The modern FAQ strategy is not “add more schema.”
The modern FAQ strategy is “write better answers.”
Should You Still Use FAQPage Schema?
Yes, but selectively.
Google’s FAQ structured data guidelines still say FAQ content should be visible to users on the source page, that FAQPage should be used only where there is a single answer to each question, and that each Question and Answer should include the full text of the question and answer.
That means the safe rule is:
Use FAQPage schema only when the visible FAQ exists, each question has one clear answer, and the structured data matches the visible content.
Do not use FAQPage schema when:
- The questions do not appear on the page.
- The answer is hidden from users in a way they cannot access.
- The markup contains inflated or promotional content.
- The same FAQ is copied across many pages without a reason.
- The page allows users to submit multiple answers to one question.
- The schema exists only because a plugin auto-generated it.
The markup should describe the page.
It should not pretend the page is better than it is.
What Not to Promise in 2026
This belongs in every SEO audit, content brief, and client-facing recommendation.
Do not promise:
| Do Not Promise | Why |
|---|---|
| FAQ rich results in Google Search | Google says FAQ rich results are no longer appearing in Search |
| Expandable FAQ dropdowns under organic listings | That visible feature has been deprecated |
| CTR gains from FAQ rich-result visibility | The Search feature is no longer available |
| FAQ enhancement reporting in Search Console long-term | Google is removing related reporting and support |
| Guaranteed AI citations from FAQ schema | AI citation behavior is not guaranteed by schema alone |
The defensible promise is different:
“We are structuring FAQ content to improve clarity, topical completeness, user experience, and AI-readability.”
That is a stronger, cleaner, more accurate statement.
What Actually Works Now?
FAQ content still works when it answers real questions in a clean format.
The Strong FAQ Answer Formula
Use this structure:
- Answer the question in the first sentence.
- Name the topic or entity clearly.
- Add the condition or caveat.
- Explain why it matters.
- Give the next step when useful.
Weak Example
Question: Does FAQ schema still help SEO?
Answer: Yes, it can still help, but it depends on the site and the situation.
Stronger Example
Question: Does FAQ schema still help SEO in 2026?
Answer: FAQ schema no longer helps a site earn Google FAQ rich results, but visible FAQ content can still support SEO, AEO, and GEO when it answers real user questions in a clear, extractable format. Use FAQPage schema only when the visible FAQ exists and the markup matches the page.
The second answer is better because it is specific.
It tells the reader what changed.
It explains what still works.
It includes the caveat.
It can stand alone.
The 2026 FAQ Reset Framework
The 5-part FAQ reset turns outdated FAQ sections into answer infrastructure.
Use this framework for existing pages and new content briefs.
Step 1: Audit Existing FAQ Schema
Check every page using FAQPage schema.
Ask:
- Is the FAQ visible on the page?
- Does the markup match the visible copy?
- Is each question paired with one accepted answer?
- Is the answer still accurate?
- Is the FAQ useful to a real reader?
- Is the team still reporting FAQ rich-result benefits?
If the answer is no, update it or remove the markup.
Step 2: Keep High-Value FAQ Content
Keep FAQ sections on pages where buyers need fast answers.
Good candidates include:
- Service pages.
- Product pages.
- Pricing pages.
- Local landing pages.
- Comparison pages.
- SaaS feature pages.
- Healthcare, legal, finance, and B2B decision pages.
- Educational blog posts.
- AEO and GEO content hubs.
These are exactly the kinds of pages where users and AI systems need clear clarification.
Step 3: Delete or Rewrite Thin FAQ Filler
Remove FAQs that exist only for old-school SEO.
Bad FAQ sections usually include:
- Repetitive questions.
- Keyword stuffing.
- Generic answers.
- Duplicate copy across many pages.
- Answers that say nothing.
- Questions no customer would actually ask.
If the FAQ does not help a human, it probably will not help AI visibility much either.
Step 4: Rewrite for Extraction
Each FAQ answer should be useful even if pulled out of the page.
Bad answer:
“FAQs help because they give more detail.”
Better answer:
“FAQ content helps AEO and GEO because it organizes common questions into clear question-and-answer pairs that are easier for AI search systems to understand, summarize, and potentially cite.”
Specificity wins.
Step 5: Update Internal SEO Documentation
Add this warning to your content briefs:
FAQ Schema Warning — 2026:
Google says FAQ rich results are no longer appearing in Google Search as of May 7, 2026. Do not promise FAQ rich-result benefits. FAQ content may still support readers, long-tail intent, AEO, GEO, and AI answer extraction. Only use FAQPage schema when the visible FAQ exists on the page and the structured data matches it exactly.
That protects the strategy.
It also keeps the team from selling an outdated benefit.
Key Takeaway
Google removed the visual reward for FAQ schema in traditional Search.
That does not make FAQs useless.
It makes lazy FAQs useless.
The 2026 rule is simple:
Stop promising FAQ rich results. Keep useful FAQs. Rewrite them as clear, visible, answer-first content. Use FAQPage schema only when the page actually contains matching FAQ content.
FAQ schema is no longer the growth lever.
FAQ content still is.
Frequently Asked Questions About AEO
Should you remove FAQPage schema from old service pages?
No, you should audit it first and only remove or rewrite FAQPage schema if it is outdated, thin, inaccurate, duplicated, or not supported by visible page content.
How do you rewrite FAQs for ChatGPT, Gemini, Perplexity, and AI Overviews?
Rewrite each FAQ so the answer is clear in the first sentence, supported by proof, and easy for an AI system to extract, summarize, and cite.
What is the difference between FAQPage schema, QAPage schema, and visible FAQ content?
FAQPage schema marks up site-owned questions and answers, QAPage schema is for user-generated answers to a single question, and visible FAQ content is the actual text users can read on the page.
How should agencies update SEO reports after Google removes FAQ rich-result reporting?
Agencies should shift reporting from FAQ rich-result visibility to page performance, AI citations, cited URLs, query visibility, content improvements, and conversion impact.
What does an AI-readable service page look like in 2026?
An AI-readable service page uses answer-first sections, clear headings, proof blocks, visible FAQs, structured data, internal links, and a strong next-step conversion path.
Ready to talk AEO?
Contact GreenBanana SEO to discuss your AEO and GEO content needs.


