If you came here to add FAQ schema so you can win the expandable question-and-answer boxes in Google, there is something you need to know first: those boxes are gone. Google deprecated FAQ rich results on 7 May 2026, so for ordinary sites the markup no longer produces anything visible in search. That does not mean FAQ content is worthless for AEO, far from it, but it does mean most FAQ-schema advice you will find is now out of date. This guide separates what the schema actually does from what the FAQ format does, and tells you what is still worth your time.
What actually changed
For years, FAQ schema had a clear payoff: mark up your questions and answers, and Google might show them as an expandable rich result under your listing, taking up more space and pulling more attention. That was the reason most sites added it.
On 7 May 2026, Google deprecated FAQ rich results. The rollout removed the rich result from search, then the FAQ report and Rich Results Test support through mid-2026. For the vast majority of sites, adding FAQPage markup now produces no visible rich result at all.
So the single biggest reason people added FAQ schema no longer exists. If a guide or an agency is still promising FAQ rich results, it is describing a feature Google has switched off.
The distinction that matters: schema versus content
Here is the mistake almost everyone makes. They treat "FAQ schema" and "FAQ content" as the same thing. They are not, and the difference is the whole point of this guide.
The schema is the invisible markup, the JSON-LD that labels a block of text as questions and answers for machines. That is what earned the rich result, and that is what is now switched off in Google.
The content is the visible FAQ section itself: real questions, with clear, direct answers, that a reader (or a machine) can lift out. That content is a series of self-contained question-and-answer passages, and self-contained passages are exactly what AI answers are built from. That value did not change on 7 May. It has nothing to do with the markup.
So the honest reframe is: you are not optimizing FAQ schema for AEO. You are writing FAQ content for AEO, and optionally keeping the schema around because it is harmless. This is the same pattern across all of answer engine optimization: the structure earns the citation, not the tag.
Does FAQ schema help AI citations?
On the evidence, not directly. A controlled test across seven AI platforms found that schema behaves as an SEO lever rather than an AI-citation one, and that six of the seven platforms could not even read schema markup when asked, because the pipelines that feed AI models often strip the script tags that hold JSON-LD before the model sees them. Google's own 2026 guidance says the same thing from the other side: you do not need special schema to appear in its AI features.
What does get cited is clear, extractable content, which a good FAQ section happens to be. The FAQ format wins on structure, not on markup. If you want the mechanism behind why extractable passages get chosen, see How LLMs Retrieve and Cite Sources.
The practical guide: FAQ content that actually gets cited
This is the part that still works. Build the FAQ section for extraction, and it will earn citations regardless of the schema.
Use the real questions buyers ask
Do not invent questions to stuff keywords. Use the actual questions your buyers type or ask an assistant before deciding, "best CRM for a small business," "does X integrate with QuickBooks," "how much does Y cost." These match the queries AI systems are answering, which is what gets you retrieved in the first place.
Answer in the first sentence
Lead each answer with the answer. "Yes, X integrates with QuickBooks via a native connector," not three sentences of preamble first. Answer engines lift the clean, direct statement; they skip the hedging.
Keep each answer self-contained
Each question-and-answer pair should make sense pulled out on its own, with no "as mentioned above." That is precisely how it will be used, quoted out of context, so write it that way.
Keep answers concise, then elaborate
A tight two-to-four-sentence answer is the most quotable unit. If there is more to say, say it after the direct answer, not before. One question, one clear answer, optional detail.
Put FAQs where they are genuinely relevant
Add FAQ sections to pages where real questions belong, product pages, service pages, guides, not as a bolt-on block of unrelated questions on every page. Relevance is part of what gets a passage selected.
Keep the schema, for the right reasons
You can still add FAQPage schema. It remains a valid Schema.org type, it does no harm, and other systems beyond Google Search may parse it. Google advises that any structured data should match your visible text, so keep them in sync. Just add it as harmless hygiene, not as your AEO strategy, and do not spend real effort optimizing the markup itself.
So should you still add FAQPage schema?
Short answer: you can, but for modest reasons. It will not get you a rich result in Google anymore, and it will not directly earn AI citations. It stays valid, it does not hurt, and it keeps your options open for systems that might use it. That is the honest case, no more and no less.
Where your effort should go is the FAQ content: real questions, direct answers, self-contained passages, on relevant pages. That is what earns the visibility, in AI answers and traditional search alike.
Frequently asked questions
Want to see whether AI systems are actually quoting your FAQ and other content? Get a free AI Visibility Audit.
Sources
- Search Engine Journal, "Google Drops FAQ Rich Results From Search" (deprecation, 7 May 2026) — https://www.searchenginejournal.com/google-drops-faq-rich-results-from-search/574429/
- Google Search Central, "Optimizing your website for generative AI features on Google Search" (no special schema needed) — https://developers.google.com/search/docs/fundamentals/ai-optimization-guide
- Otterly, "Does Schema Markup Really Impact AI Search?" (schema as SEO lever, not GEO; 6 of 7 platforms could not read markup) — https://otterly.ai/blog/schema-markup-real-impact-ai-search/