Google no longer shows FAQ rich results. The display ended on May 7, 2026, per a notice dated May 8, and the FAQ documentation was removed on June 15, 2026. FAQPage markup is still valid schema.org vocabulary, but it earns nothing in Google Search. Leave valid markup that matches the page, fix or remove markup that does not, and put the real effort into a visible FAQ section.
The timeline, with the dates pinned
| Date | What happened | Where Google recorded it |
|---|---|---|
| Aug 8, 2023 | FAQ rich results restricted to well-known authoritative government and health sites | Search Central blog post on HowTo and FAQ changes |
| Sep 14, 2023 | FAQ documentation edited to state that restriction | Search updates log |
| May 7, 2026 | Last day the feature was due to appear | Wording in the May 8 notice |
| May 8, 2026 | Deprecation notice added to the FAQ documentation | FAQ page changelog |
| Jun 15, 2026 | FAQ documentation removed; feature recorded as no longer shown | FAQ page changelog |
Secondary sources disagree on a few of these dates because the notice came a day after the end date. We use the wording of Google's own changelog entries and the blog post.
What FAQ markup still does and does not do
- Google rich result: none. The feature is gone for every site.
- Google AI features: Google's AI optimization guide says no special markup is needed to appear in generative AI search. See the evidence on schema and AI.
- Bing and Copilot: Microsoft's guidance names FAQ sections, meaning visible content, among the structures that help surface key information, and says assistants can lift question-and-answer pairs from pages. It does not say FAQPage markup is required.
- Validity: the vocabulary is still on schema.org, so markup can stay valid even though Google ignores it.
What to do with markup you already have
| What you have | Action | Why |
|---|---|---|
| Valid markup, same questions visible on the page | Leave it, or remove it when you next touch the template | No documented harm, no documented gain |
| Questions in markup that readers cannot see | Show them or remove the markup | Google's general guidelines say not to mark up content that is not visible to readers |
| The same block printed twice by theme and plugin | Keep one source | See how to find the second source |
| One identical FAQ pasted on every page | Write page-specific questions or drop the block | Repeated copy gives each page nothing unique |
| Markup but no visible FAQ at all | Write the visible section first | Markup that describes nothing is the wrong way round |
An example of a visible answer (invented)
This example is invented to show the shape. Imagine a pricing page for a fictional invoicing tool. A weak entry reads: "Our flexible plans fit every team." A usable entry reads: "Can I change plans later? Yes. You can move between plans from the billing page, and the new price applies from the next billing date." The second names the action, the place and the condition, so a reader, a search snippet or an assistant can use it without the rest of the page. Check each answer against that test: does the first sentence stand alone?
Build the visible section instead
- Collect real questions from sales calls, support tickets and Search Console queries.
- Put the answer in the first sentence, with the number, limit or condition that makes it specific.
- Keep each answer readable on its own, since an assistant may quote one pair and nothing else.
- Place the questions under a heading in the main content, not in a widget that keeps them out of the page text.
If you still want markup, the FAQ schema generator writes it from your question list. To check what a page already outputs, run the schema checker, and see which type a page needs.
Questions people ask
Why do some pages say May 7 and others May 8?
Google's changelog entry is dated May 8, 2026 and says the feature stops appearing starting May 7, 2026. One is the posting date, the other is the end of display.
Will leftover FAQ markup cause a manual action?
Google has not said so for valid markup that matches visible content. Its structured data guidelines do warn against marking up content readers cannot see.
Does a visible FAQ section help in AI answers?
Microsoft's guidance lists FAQ sections among helpful structures. Google says no special markup is needed. Neither company has published a measured effect, so write the section for readers first.
Is FAQ markup the same as Q&A or HowTo markup?
No. Q&A is a separate feature that remains in Google's gallery, while HowTo display ended in 2023. See the rich results status table.
Related
Sources
- Google Search Central: FAQ structured data page and changelog, accessed 2026-11-12.
- Google Search Central blog: Changes to HowTo and FAQ rich results (Aug 8, 2023), accessed 2026-11-12.
- Google Search Central: Search documentation updates, accessed 2026-11-12.
- Google Search Central: General structured data guidelines, accessed 2026-11-12.
- Google Search Central: AI optimization guide, accessed 2026-11-12.
- Microsoft Advertising: Optimizing your content for inclusion in AI search answers (Oct 8, 2025), accessed 2026-11-12.
- Bing Webmaster Blog: AI Performance in Bing Webmaster Tools (Feb 10, 2026), accessed 2026-11-12.