# FAQPage Schema After May 2026: What It Still Does

> Google stopped FAQ rich results on 7 May 2026. What FAQPage markup still does, what it no longer does, and what a store should keep or remove.

Source: https://angeo.dev/faqpage-schema-after-2026/
Updated: 2026-09-26

Guide

# FAQPage Schema After May 2026: What It Still Does

**Google stopped showing FAQ rich results on 7 May 2026, for every site.** FAQPage is still valid schema.org, and Google says leaving it in place does no harm - but it no longer earns anything in Google Search, and there is no published evidence that it makes AI assistants quote a page. Keep it where real questions are visible; stop adding it as an SEO trick.

**In one sentence**
Harmless, valid and no longer rewarded by Google - keep it for real, visible Q&A only.

## What Google changed

| Date | Change |

| August 2023 | FAQ rich results limited to well-known government and health sites |

| 7 May 2026 | FAQ rich results no longer appear in Google Search, for any site |

| June 2026 | FAQ search appearance, rich result report and Rich Results Test support removed from Search Console |

| August 2026 | FAQ support removed from the Search Console API |

Google's John Mueller put it plainly: for most sites nothing changes, because the markup was already ignored. There is no need to remove it, and you may remove it if you added it only for Search.

## What FAQPage still does

- **It is valid schema.org.** `FAQPage` remains a normal type. Google says leaving it in place causes no problems.

- **Other parsers can read it.** Other search engines and AI systems that parse structured data may use it. None of them publishes how much.

- **It structures content you already show.** Clear question-and-answer text on the page is useful to people and easy to quote, with or without markup.

## What it no longer does

- No expandable FAQ result in Google.

- No FAQ report or test in Search Console.

- No proven boost in AI citations. Claims that FAQPage markup gets you quoted by ChatGPT or Perplexity have no published evidence behind them.

## What to do on a store

1. **Keep FAQPage where the Q&A is visible** and real: shipping, returns, sizes, compatibility. The markup must match the text on the page.

2. **Remove it where it was added only for Search** - hidden FAQs, generic filler, questions nobody asks. They were never a good idea.

3. **Spend the effort on schema that still counts:** Product with [offers.availability](https://angeo.dev/offers-availability-definition/), shipping and return policy, and a consistent [@id](https://angeo.dev/entity-id-definition/) graph.

4. **Fix old promises.** Guides and checklists that still say "FAQ schema gets you into the answer box" are out of date.

**How the angeo audit treats it**
In `angeo/module-aeo-audit`, `faq_schema` has the lowest weight, 0.5, which makes it informational: a missing FAQPage never fails a store on critical severity. See the [AEO score](https://angeo.dev/aeo-score-definition/) for all weights.

## Questions

Does Google still show FAQ rich results?
No. Since 7 May 2026 FAQ rich results no longer appear in Google Search for any site.

Should I remove FAQPage schema?
There is no need. Google says markup left in place causes no problems. Remove it where it was added only for Search or where the questions are not visible on the page.

Does FAQPage help with AI answers?
There is no published evidence that FAQPage markup makes ChatGPT, Perplexity or Google's AI features cite a page. Clear, visible answers to real questions are what can be quoted.

Is FAQPage still valid schema.org?
Yes. FAQPage remains a valid schema.org type; only Google's rich result for it was retired.

Can I still test FAQ markup in the Rich Results Test?
No. FAQ support was removed from the Rich Results Test in June 2026. Use validator.schema.org to check the markup.

## Related

- [Product JSON-LD for AI search](https://angeo.dev/magento-2-product-schema-json-ld-ai-search/)

- [offers.availability - definition](https://angeo.dev/offers-availability-definition/)

- [Entity @id in JSON-LD - definition](https://angeo.dev/entity-id-definition/)

- [AEO score - definition](https://angeo.dev/aeo-score-definition/)

- [Magento SEO audit 2026](https://angeo.dev/magento-seo-audit-2026/)

## Sources

- [Google Search Central: FAQ structured data (deprecation notice)](https://developers.google.com/search/docs/appearance/structured-data/faqpage)

- [Search Engine Roundtable: Google drops FAQ rich results (with John Mueller's comment)](https://www.seroundtable.com/google-drops-faq-rich-results-41298.html)

- [schema.org: FAQPage](https://schema.org/FAQPage)

Checked 24 September 2026 against Google's FAQ structured data documentation and Search Central changelog, as reported with quotes by Search Engine Roundtable. faq_schema weight from the source of angeo/module-aeo-audit 4.2.3.

## More on this topic

- [Hyvä Theme's Product Schema Gap: What the Code Shows (2026)](https://angeo.dev/hyva-theme-product-schema-gap/)
- [The Magento product description that AI can't read](https://angeo.dev/magento-product-description-invisible-ai-chatgpt/)
- [Magento 2 JSON-LD Schema Module  -  Free](https://angeo.dev/modules/rich-data/)