What changed, and why the schema still earns its place
Two things get confused constantly, so let's separate them.
FAQ rich results were a display feature: the visible accordion of questions under your blue link.
FAQPage schema is the markup underneath: JSON-LD that labels a block of content as structured question-answer pairs.
On 7 May 2026, Google stopped showing FAQ rich results in Search and added a deprecation notice to its FAQPage documentation. Search Console reporting and Rich Results Test support for FAQ were removed in stages through mid-2026 (Search Engine Journal, Google Search Central).
What did not change: FAQPage remains a valid Schema.org type, and Google has confirmed unused structured data does not harm Search, so the markup can safely stay on your pages (The HOTH).
The reason to keep it is AEO. Answer engines parse structured data to understand which spans of your page are self-contained answers to specific questions. A well-formed Question/acceptedAnswer pair is the cleanest possible signal that "this text answers this question," which is exactly the unit an LLM wants to lift into a cited response.
The citation benefit, concretely
Answer engines reward extractable, self-contained answers backed by sources (DataImpulse). FAQPage schema helps in three ways:
Explicit question-answer boundaries. The model does not have to guess where an answer starts and stops. Your acceptedAnswer.text is the boundary.
Query-to-answer matching. Real user prompts are phrased as questions. When your Question.name mirrors the phrasing people actually use, the semantic match is tighter.
Entity and fact grounding. Short, factual answers with numbers, dates, and named entities are the kind of "verifiable data points" AI models prefer over narrative fluff (SEOProfy).
Schema is not a magic citation switch. Crawler access, page authority, and answer quality still dominate. But among on-page levers, structured Q&A is one of the highest-leverage and lowest-effort.
Copy-paste FAQPage JSON-LD
Drop this in the <head> or at the end of <body>. Replace the questions and answers with content that actually appears in the visible page (Google and most parsers require parity between markup and on-page content).
```html
Field reference
| Field | Required | Notes |
|---|---|---|
| @type: FAQPage | Yes | One FAQPage block per page. |
| mainEntity | Yes | Array of Question objects. |
| Question.name | Yes | The full question text. Phrase it the way users ask. |
| acceptedAnswer | Yes | Exactly one per question. |
| acceptedAnswer.text | Yes | The answer. Limited HTML allowed (a, br, p, ul, ol, li, b, em). |
Implementation rules that keep you clean
Parity. Every question and answer in the JSON-LD must be visible on the rendered page. Hidden-only FAQ markup is against Google's guidelines and gives AI parsers nothing to reconcile.
One canonical answer. Use a single acceptedAnswer, not suggestedAnswer. Answer engines want a definitive response.
Self-contained answers. Write each answer so it makes sense lifted out of context. Lead with the direct answer, then add one or two sentences of detail.
Facts over fluff. Include the number, the date, the version, the price. Verifiable specifics get cited; vague copy does not.
Don't duplicate across pages. The same Q&A repeated site-wide dilutes signal. Map each FAQ to the page that best owns that question.
Validate. Use the Schema.org validator or Google's Rich Results Test for syntax (note: the FAQ-specific report was removed, but generic JSON-LD validation still works).
Where FAQPage fits in an AEO stack
FAQPage is one layer. To actually get cited, pair it with:
Crawler access. Keep OAI-SearchBot, PerplexityBot, Google-Extended, and ClaudeBot unblocked in robots.txt if you want to appear in those answers (DataImpulse).
Entity clarity. Consistent Organization and Article schema so the model knows who is answering.
Authority. Citations from sources the models already trust do more than any single markup type.
FAQ
Is FAQPage schema deprecated?
No. Google deprecated the visible FAQ rich result on 7 May 2026, not the FAQPage schema type. The markup remains valid on Schema.org and is safe to keep on your pages (Google Search Central).
Will FAQPage schema get me a rich snippet in Google again?
Not currently. Google removed the FAQ display feature in Search. The schema's value today is machine-readability for AI answer engines and AI Overviews, not a blue-link accordion.
Does FAQPage schema directly increase AI citations?
It helps but does not guarantee. Schema makes your Q&A pairs extractable, which is a prerequisite for citation. Crawler access, answer quality, and site authority still decide whether you get picked.
Can I keep old FAQPage markup that's already on my site?
Yes. Google states unused structured data does not cause problems for Search, so there is no need to remove it. If anything, it now works for AEO.
How is FAQPage different from QAPage schema?
FAQPage is for pages where the site provides both question and canonical answer. QAPage is for user-generated Q&A (like a forum thread) with one question and possibly many user answers. Use FAQPage for editorial FAQs.
Do I need FAQ answers to be short?
Aim for 2 to 4 sentences. Long enough to fully answer, short enough to lift cleanly. Lead with the direct answer in the first sentence.
Run the check
SEO AEO Specialist audits your FAQPage markup for validity, on-page parity, crawler access, and answer extractability, then scores how citable each page is by AI engines.
Free: €0, check up to 50 pages per project.
One-time report: €9 for a full AEO audit you can act on today.
Ongoing: €19/mo per domain for continuous monitoring as answer engines change.
Run a free scan and see which of your FAQ answers are actually extractable.
How to Optimize Product Pages for ChatGPT Shopping
See where you stand
SEO AEO Specialist runs a free AI-visibility audit and hands you the exact fixes. One-off report €9, unlimited €19/mo.
Run your free audit →