Status, November 2026: Google stopped showing FAQ rich results in Search on May 7, 2026 and removed the FAQ documentation on June 15, 2026. FAQPage markup is still valid schema.org vocabulary, but it no longer earns the expandable questions under your result in Google.
Generate FAQPage JSON-LD
Answers may span several lines; everything until the next Q: belongs to the answer. Nothing leaves your browser.
FAQPage markup wraps each visible question and answer in a Question with an acceptedAnswer. It is easy to generate and harmless when it matches the page. Since May 2026 it no longer produces a rich result in Google, so the visible FAQ section, not the markup, is now where the value is.
What changed, and when
| Date | Change in Google Search | Source |
|---|---|---|
| August 8, 2023 | FAQ rich results limited to well-known, authoritative government and health sites | Google Search Central blog |
| May 8, 2026 | Deprecation notice added: FAQ rich results "will no longer appear in Google Search starting May 7, 2026" | Google structured data changelog |
| June 15, 2026 | FAQ documentation removed; the feature "is no longer shown in Google Search results" | Google structured data changelog |
This was the end of a long wind-down. On August 8, 2023, Google said FAQ rich results would "only be shown for well-known, authoritative government and health websites", so most sites had not seen them for almost three years. The 2026 change removed them for everyone.
Why a generator is still useful
- Other consumers read schema.org. FAQPage is part of the shared vocabulary, and parsers other than Google's rich result system can read it. No search or AI company has published that it rewards the markup, so treat any benefit as unproven.
- Clean replacement for broken markup. Many sites carry FAQ markup from old plugins with mismatched or empty answers. If you keep markup, it should at least be valid and match the page.
- Structured content discipline. Writing each answer so it stands alone, starting with the direct answer, is what makes a FAQ section quotable by people and by AI answers alike.
The structure, and what to avoid
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "How long does setup take?",
"acceptedAnswer": {
"@type": "Answer",
"text": "About ten minutes. You connect Search Console, then choose where pages are published."
}
}]
}
</script>
| Mistake | Why it matters |
|---|---|
| Questions in the markup that are not on the page | Google's general guidelines require markup to describe content visible to readers |
| Two FAQPage blocks on one page (theme plus plugin) | Parsers see duplicated, sometimes conflicting entities; keep one source |
| Marketing slogans as answers | An answer that does not answer is useless to readers and to any system quoting it |
| FAQ blocks pasted on every page | Repeated identical questions across a site add nothing and dilute each page |
Writing answers that get quoted
- Use the question a buyer would type, in their words, not your product's feature names.
- Answer in the first sentence. Add the detail after.
- Include the number, limit or condition that makes the answer specific: a time, a price range, a plan name.
- Keep each answer self-contained; an AI answer may quote one answer without the rest of the page.
Then check the page itself: the title and meta checker lists the schema types it finds, so you can confirm there is one FAQPage block, not two.
Questions people ask
Does FAQ schema still show in Google?
No. Google's structured data changelog says the FAQ rich result stopped appearing in Google Search starting May 7, 2026, and the FAQ documentation was removed on June 15, 2026.
Will FAQPage markup hurt my site now?
Google has not said it penalizes the markup. Valid markup that matches visible content is simply ignored for rich results. Markup that does not match what readers can see goes against Google's general structured data guidelines.
Should I remove existing FAQ schema?
There is no need to rush. If it is valid and matches the page, leaving it costs nothing. Spend new effort on the visible FAQ section itself: questions buyers ask, answered in the first sentence.
Is FAQ markup good for AI answers?
No AI search company has published that FAQPage markup affects citations. Microsoft's guidance for Copilot citations mentions FAQ sections, meaning the visible content, among the structures that make information easy to reference.
Related
Sources
- Google Search Central: FAQ (FAQPage) structured data, deprecation notice and changelog, accessed 2026-11-12.
- Google Search Central blog: Changes to HowTo and FAQ rich results (Aug 8, 2023), accessed 2026-11-12.
- schema.org: FAQPage, accessed 2026-11-12.
- Google Search Central: General structured data guidelines, accessed 2026-11-12.
- Bing Webmaster Blog: AI Performance in Bing Webmaster Tools (Feb 10, 2026), accessed 2026-11-12.