Google removed FAQ schema entirely on May 7, 2026, after progressively restricting it for over a year. If your site still carries FAQPage markup expecting the rich result it used to earn, that markup is now doing nothing for display — and depending on how much of it you have, it may be doing something worse: signaling to Google’s spam systems that a page is stuffed with schema aimed at gaming a result that no longer exists. This is a good moment to rebuild schema priorities around what actually still matters, not around what used to work.
What Got Cut, and Why
The March 2026 core update had already reduced rich result eligibility for FAQ, Review, and How-To schema on pages where that content wasn’t the primary purpose of the page — a product page with three bolted-on FAQ items aimed at snippet real estate, for instance. The May removal of FAQ schema display was the harder cutoff: the rich result is gone regardless of how the page is structured. Review and How-To schema are still restricted but not fully removed, which means the same “primary content” test still applies to them and is worth re-auditing rather than assuming they’re safe.
The Reframe: Schema as a Trust Signal, Not a Display Trigger
Google and Microsoft have both confirmed structured data helps their AI systems understand, verify, and cite content, independent of whether it produces a visible rich result in classic search. That’s the frame worth building a 2026 schema strategy around: the goal is machine clarity about what an entity is and what a page asserts, not chasing a SERP feature. Google has stated plainly that no special schema is required for AI Overviews or AI Mode inclusion — structured data helps Google understand a page, but understanding is not the same as a guarantee of citation, ranking, or feature eligibility.
Where to Spend the Effort Now
| Schema Type | 2026 Priority | Why |
|---|---|---|
| Organization | High | Anchors entity recognition across the whole domain — foundational for both classic search and AI citation trust |
| Product | High for e-commerce | Directly feeds price, availability, and review data into both Shopping surfaces and AI-generated product comparisons |
| LocalBusiness | High for service-area businesses | Location-based AI queries lean on this data for basic factual grounding |
| Event | High for time-sensitive content | High citation rates in AI assistants for “what’s happening” style queries |
| FAQPage | Remove or demote | No display benefit remains; leaving large volumes on thin pages reads as a spam signal rather than a helpful one |
| HowTo / Review | Keep only on genuinely primary content | Still restricted to pages where this is the page’s actual purpose, not a bolted-on addition |
A Practical Migration Checklist
- Crawl the site for FAQPage schema instances and separate them into “primary FAQ content” (a dedicated FAQ or help page) versus “bolted onto unrelated content” (a blog post or product page with three tacked-on questions).
- Remove FAQPage markup from the bolted-on category outright — it isn’t earning display and isn’t worth the ambiguity risk.
- For genuine FAQ pages, keep the markup for machine clarity, but don’t expect a rich result from it.
- Audit Review and How-To schema against the same primary-content test the March core update introduced, since these haven’t been fully removed and can still earn display when the content genuinely qualifies.
- Prioritize adding or fixing Organization, Product, LocalBusiness, or Event schema — whichever applies — since these carry the highest confirmed value for AI-era search, not the schema types that used to be popular for snippet capture.
- Validate everything against the current Schema.org vocabulary and Google’s structured data documentation directly rather than against an older guide, since eligibility rules have moved twice in five months.
