AI search glossary
FAQ schema in 2026: Google dropped the rich result. Is it still worth it?
FAQ schema is structured data using the schema.org FAQPage type to mark a page as a list of questions with answers, each question as a Question with an acceptedAnswer. Google used it for an FAQ rich result, which it stopped showing in May 2026.
Also called: FAQPage schema, FAQ structured data, FAQ markup
Why it matters for AI search
The visual reward in Google is gone, but the habit FAQ markup encouraged still matters for AI answers: short, direct answers to the exact questions buyers ask, written on the page in plain text. AI engines lift answers from visible content, and Google says no special schema is needed for its AI features. Keep the questions and answers on the page; treat the markup as optional.
What FAQ schema looks like
Schema.org defines FAQPage as a type of WebPage presenting one or more frequently asked questions. The markup lists each question and its accepted answer:
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "Do you ship to Canada?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Orders to Canada ship in 3 to 5 business days."
}
}]
}
It was usually written as JSON-LD and placed on support pages, product pages and blog posts with a questions section.
What happened to the rich result
For several years FAQ markup could add expandable questions under a page's blue link, which made the result taller and pushed competitors down. That made it one of the most used (and overused) types of schema markup. Google's documentation changelog records the decline:
- September 14, 2023: the FAQ documentation was updated to say the rich result is only shown for well-known, authoritative government and health websites. HowTo rich results were removed the same day.
- May 8, 2026: Google announced the FAQ rich result would no longer appear in Google Search starting May 7, 2026.
- June 15, 2026: Google removed the FAQ rich result documentation, noting the feature is no longer shown.
What to do now
- Keep good FAQ content on the page. Questions that buyers really ask (price, shipping, compatibility, who it is for) with short, factual answers are still useful to people and quotable by AI engines.
- Leave existing markup or remove it, based on effort. It no longer earns a Google feature. If you keep it, it must match the visible text, per Google's general guidelines.
- Do not add FAQ markup to chase a feature. Spend that time on Product and Organization markup, which still feed visible features and entity understanding.
- Write answers in the first sentence. Google's People Also Ask box and AI answers both favor a direct reply followed by detail.
FAQ content and AI answers
Google states that no special schema.org structured data is needed to appear in AI Overviews or AI Mode. What those features need is an indexed, snippet-eligible page with a clear answer. A well-written FAQ section is one of the simplest ways to put many such answers on one page, which is why it remains a staple of answer engine optimization even without the rich result.
Questions
- Does Google still show FAQ rich results?
- No. Google's documentation changelog says the FAQ rich result would no longer appear in Google Search starting May 7, 2026, and the FAQ structured data documentation was removed on June 15, 2026.
- Who could get FAQ rich results before that?
- From September 2023, Google limited the feature to well-known, authoritative government and health websites. Most commercial sites had already lost it then.
- Should I remove FAQPage markup from my site?
- There is no rush. FAQPage is still a valid schema.org type and other consumers may read it. If you keep it, Google's general rules still apply: the questions and answers must be visible on the page and must not be misleading.
- Do FAQ sections still help with AI search?
- The visible questions and answers can. AI engines quote pages that answer a specific question directly, and an FAQ section is a compact way to do that. The benefit comes from the text, not the markup.