Is FAQ schema still worth adding now that Google dropped FAQ rich results?
Updated 10 Nov 2026 · by Venu Gopal Reddy Muvva, founder of BrandInAIAnswers · official sources checked 10 Nov 2026
Google's Search Central changelog says FAQ rich results stopped appearing in Google Search from 7 May 2026, so FAQPage markup no longer earns a special search display there. Writing real questions and answers on the page still helps AI answers, which quote clear Q&A text, and keeping valid FAQPage markup is harmless and machine-readable for other tools.
What changed
- 8 May 2026 entry: FAQ rich results will no longer appear in Google Search from 7 May 2026.
- 15 June 2026 entry: the feature is no longer shown and its documentation was removed.
- Google's AI features page says no special schema is needed for AI Overviews or AI Mode.
What still works
| Practice | Why |
|---|---|
| Questions as headings, answers in the first sentence | AI answers quote short, self-contained answers |
| Questions phrased the way buyers ask | Matches the questions people type into AI assistants |
| Answers with numbers and conditions | Specific facts are what get cited |
| Valid FAQPage JSON-LD that matches the visible text | Harmless, and other parsers can read it |
Example: one good FAQ item
<h3>How long does GST registration take?</h3>
<p>Usually 3 to 7 working days after you submit a complete application on the GST portal, longer if the officer asks for clarification.</p>
{ "@type": "Question", "name": "How long does GST registration take?",
"acceptedAnswer": { "@type": "Answer", "text": "Usually 3 to 7 working days after you submit a complete application..." } }The visible answer is self-contained: someone reading only that sentence has the answer. That is what makes it quotable.
Where to put FAQs so they get used
Put FAQs on the page that answers the topic, not on a single site-wide FAQ page. A pricing page should carry pricing questions; a product page should carry setup and compatibility questions. Engines quote the answer from the page that is about the question.
Write each answer so it stands alone: repeat the subject ('GST registration takes...') instead of starting with 'It' or 'Yes'. Keep answers between one and four sentences, and include the number, date or condition the reader needs. If the honest answer is 'it depends', say what it depends on.
Review FAQs when prices, policies or laws change. A wrong FAQ answer is quoted with the same confidence as a right one.
How to find the right questions
Start from real sources: questions in support tickets, sales call notes, chat transcripts and the 'People also ask' boxes for your topic. Then ask an AI assistant your main topic question and note the follow-up questions it suggests; those are the questions people ask next. Pick the ones your page can answer better than anyone, with a fact only you know, such as your exact price, limit or process.
Questions
Should I remove existing FAQPage markup?
No need, if it matches the visible text. It costs nothing to keep.
Do ChatGPT or Perplexity read JSON-LD?
Their crawler pages do not say how they use structured data. The visible Q&A text is what you can rely on.
How many FAQs per page?
Three to six real questions is plenty. Padding pages with generic FAQs adds nothing.
See which AI answers name you today
BrandInAIAnswers's free audit checks whether AI crawlers can read your site and asks an AI with web search the questions your buyers ask, then shows who gets named. The first 14 days of the full app are free.
Sources
- Google Search Central: FAQ rich result updates (checked 10 Nov 2026)
- Google Search Central: AI features and your website (checked 10 Nov 2026)
- schema.org: FAQPage (checked 10 Nov 2026)