FAQ Schema and AI Answers After the Deprecation

Google removed FAQ rich results from Search in 2026. The timeline, as of October 2026:

• 7 May 2026: the deprecation took effect (Google's changelog entry is dated 8 May).
• 15 June 2026: Google removed the FAQPage structured data documentation. The old documentation URL now redirects to the changelog.
• August 2026: Search Console API support for FAQ rich results was removed.

So the visible reward for FAQPage schema, the expandable question list under a search result, no longer exists on Google. The markup can still sit in your page source. It just no longer produces a Google rich result.

The scope matters. The deprecation kills FAQ markup as a Google display feature. It says nothing against Q&A content on your pages. A well-written answer to a question buyers actually ask is as useful to a reader as it was last year. If you need a refresher on what rich results were and how they differ from AI answers, start there.

Many GEO guides still say FAQ schema gets you cited by AI. The primary sources say otherwise.

Google's own position

Google states that structured data isn't required for generative AI search. Its AI features documentation says a page must be indexed and eligible to show with a snippet to appear as a supporting link in AI Overviews or AI Mode, and that "there are no additional technical requirements." Its guide to generative AI features adds that you don't need new machine-readable files, AI text files, markup or Markdown to appear.

The only matched test

Ahrefs tracked 1,885 pages that added schema, each compared against three matched control pages. It found no major uplift in citations on any platform. AI Overview citations fell 4.6%, a statistically significant drop. AI Mode rose 2.4% and ChatGPT rose 2.2%, neither a meaningful lift. The test covered schema generally, not FAQ markup alone, but nothing suggests FAQ markup would behave better.

The honest boundary

Every page in the Ahrefs dataset already had 100 or more AI Overview citations before schema was added. Whether markup helps a page enter the set of pages an engine considers is untested, not disproven. That is a gap in the research, not evidence of a benefit. Our longer review of whether schema markup helps AI citations covers the study design in detail.

It helps to separate the stages an answer passes through.

1. Parametric. What the model already knows from training, frozen at a cutoff. Nothing you publish this quarter changes it.
2. Access. Whether an AI crawler can fetch your page at all. robots.txt, your firewall or CDN, rendering and indexing decide this.
3. Retrieval. Whether your page enters the model's context for a given question. The engine rewrites the user's question into its own search queries, and you cannot see those queries.
4. Generation. Which retrieved pages the model uses and cites.

FAQ markup does not open any of these gates. It does not make a blocked crawler welcome, and it does not make JavaScript-only content readable. Research on content tweaks at the generation stage is not encouraging either. C-SEO Bench found most rewriting methods ineffective and often harmful, and a 252,000-trial study found formatting-only edits had little impact.

What the same 252,000-trial study did find helpful was content, not structure: explicit price information and a recent timestamp helped consistently. That fits the one positive signal for on-page work. Stating a specific fact on a fetchable page gives the engine a sentence it can quote.

The two get bundled together in most advice. They are different things with different evidence.

The practical reading: keep writing Q&A where buyers have real questions, and stop treating the markup as the part that does the work. A plain sentence such as "Our Starter plan costs $49 a month" in server-rendered HTML does more for an engine than the same fact wrapped only in JSON-LD. The comparison of structured data and plain-text facts goes further into why.

In your control

• Whether AI crawlers are allowed per bot in robots.txt. OAI-SearchBot controls ChatGPT search; GPTBot controls training only. Each setting is independent.
• Whether your firewall or CDN lets those crawlers through. A firewall can block a crawler that robots.txt allows.
• Whether your answers exist in the HTML before JavaScript runs. Vercel found ChatGPT and Claude crawlers fetch JavaScript files but don't execute them.
• Whether noindex, nosnippet, max-snippet:0 or data-nosnippet is suppressing your Q&A block.
• Whether each answer states a specific, correct fact that matches the rest of your site.

Not in your control

• Whether an engine searches the web for a given question at all. Retrieval is discretionary on every platform.
• The queries the engine actually runs after rewriting the user's question.
• Where your page lands in the model's context, and whether it gets cited.
• What the model learned before its knowledge cutoff.

No markup, FAQ or otherwise, moves anything on the second list. Nobody can promise you a citation. You can remove the things that block one.

Work from the gates that block you entirely toward the content itself.

1. Check crawler access. Confirm robots.txt allows OAI-SearchBot, PerplexityBot and Claude-SearchBot. Then confirm your CDN or firewall returns a 200 to them, not a 403 or a challenge page. Since 15 September 2026, Cloudflare blocks Training and Agent crawler categories by default on ad-displaying pages for new domains and free-tier customers, while Search stays allowed. The AI Crawler Checker requests a page as each AI crawler and shows which ones get turned away.
2. Check rendering. Many FAQ sections are accordions that load answers through JavaScript. Compare the raw HTML with the rendered page and confirm every answer appears in both. This playbook shows how to find facts hidden behind JavaScript.
3. Check suppression. Search your templates for data-nosnippet and robots meta snippet directives. A tag added to hide a cookie banner can sit over your Q&A block too.
4. Rewrite answers around facts. Lead each answer with the specific thing: the price, the limit, the date, the one-line definition. Make it match your pricing and about pages exactly.
5. Leave existing markup alone. Don't add FAQPage markup for AI and don't strip what you have. See whether removing schema markup hurts AI visibility.
6. Check what engines say. The free checker on this site shows whether AI engines name you for up to three buyer questions, as a snapshot.

• Adding FAQ markup to get cited. Google says structured data isn't required for generative AI search, and the only matched test found no major uplift. The effort goes nowhere useful.
• Ripping out existing markup. The overcorrection is just as unsupported. Google says existing markup does no harm. It is simply not a lever for AI answers.
• Building an FAQ page only for AI. You don't need one. A question answered well on your pricing or product page serves the same purpose. More on whether you need an FAQ page for AI.
• Padding with question variants. Google says you don't need to cover every long-tail variation of how someone might ask. Twenty rephrasings of one question add length, not facts.
• Writing in an "AI-friendly" style. Google rejects both special AI phrasing and chunking content for AI, and says there is no ideal page length.
• Hiding answers in client-side accordions. If the answer only appears after a click triggers a fetch, most AI crawlers never see it.
• Letting FAQ answers contradict other pages. An answer that quotes last year's price gives engines a wrong sentence to repeat. Update the FAQ whenever pricing or product names change.