FAQ schema no longer produces a rich result in Google. Google's documentation says the feature stopped appearing in Search on May 7, 2026, and the guide was removed on June 15, 2026. Keep a visible FAQ section because readers use it. Treat any markup as optional, and keep it matching the page text.
What happened to FAQ rich results?
Google's FAQPage documentation records the timeline. In September 2023 the feature was limited to well-known, authoritative government and health sites. On May 8, 2026 a deprecation notice said it would no longer appear in Search starting May 7, 2026. On June 15, 2026 the documentation was removed, with a note that the feature is no longer shown in Google Search results.
That means the expandable question-and-answer boxes under a search result are gone for everyone, not just small sites. If your reason for adding FAQ schema was to earn that extra space on the results page, the reason no longer exists.
Does FAQ schema help with AI answers?
There is no support for that in Google's own guidance. Its page on AI features in Search says there is no special schema.org structured data you need to add to appear in AI Overviews or AI Mode, and no additional requirements beyond being indexed and eligible to show with a snippet.
Some SEO vendors claim FAQ markup increases AI citations. We found no primary source behind those claims, and we are not repeating them. If you have seen a number, check where it comes from before relying on it.
Should you remove existing FAQ schema?
You do not have to. Google's AI features page says structured data should stay consistent with the visible text on the page. As long as your markup mirrors a real FAQ section that readers can see, it is accurate and harmless. The cleanup case is markup that no longer matches the page: questions you deleted, answers you rewrote, or schema copied across pages where the questions do not appear.
If your CMS or plugin adds it automatically, leave it. Do not spend a sprint ripping it out.
Is a visible FAQ section still worth writing?
Yes, for different reasons than before. A good FAQ does three jobs that need no markup.
- It matches how people search. A question as a heading, with a short answer under it, is the shape of a snippet and of a quoted AI answer.
- It catches the follow-up questions. Google says its AI features run many related searches across subtopics. A page that answers the neighbors of your main question gives those searches more to pick from.
- It cuts support load. Buyers who find an honest answer to a price or fit question do not have to email you.
How to write FAQ answers that earn their place
- Use real questions. Pull them from sales calls, support email and search suggestions, not from a brainstorm of what sounds good.
- Answer in one to three sentences. Lead with the answer, then add one qualifier.
- Do not repeat the body. If the answer is a copy of a paragraph above, cut the question.
- Keep four to six. Past that, the later ones are filler.
- Update when facts change. A stale FAQ with dated claims is worse than none.
A quick decision guide
| Your situation | What to do |
|---|---|
| Plugin already adds FAQ schema | Leave it, check it still matches the page |
| Planning to add it for rich results | Skip it, the feature is gone |
| Page has no FAQ section | Write a visible one first, then decide on markup |
| Schema lists questions not on the page | Fix or remove it |
Nightcrop pages include a real FAQ with FAQ markup, and the reasoning above is why the visible section is the part that matters.
Where to spend the time instead
Answer-first openings, crawl access and clear text matter more than markup. Start with allowing the right AI bots in robots.txt and read whether you need an llms.txt file before adding any extra files.
An example of a useful FAQ
Suppose you sell bookkeeping software and your pricing page gets the same question by email every week: can I cancel mid-month? A good FAQ entry states the answer in a sentence, names the one exception, and links to the policy. It does not repeat the pricing table above it.
That one entry helps a buyer who is deciding, can be lifted as a snippet by a search engine or AI answer, and saves a support reply. None of that depends on whether Google shows a rich result.
One last check: read the answers aloud as if a customer asked them. If an answer sounds like marketing copy rather than a direct reply, rewrite it until it would satisfy the person asking.
Frequently Asked Questions
Does Google still show FAQ rich results?
No. Google's documentation says the feature stopped appearing in Search on May 7, 2026.
Will FAQ schema hurt my site?
Not if it matches the visible content. Mismatched markup is the thing to fix.
Do I need schema to appear in AI Overviews?
No. Google says there is no special schema you need to add for AI Overviews or AI Mode.
Should I delete my FAQ section?
No. The visible questions still help readers and give search and AI systems clear passages to quote.
How many FAQ questions should a page have?
Four to six is a good range. Only include questions people actually ask.