If you've been following SEO news, you may have seen the announcement: as of May 7, 2026, Google deprecated FAQ rich results. The expandable question-and-answer dropdowns that used to appear in Google search listings are gone. Search Console will stop reporting on FAQ schema in June, and API support ends in August.
For WordPress bloggers who added FAQ schema to improve their search visibility, this news understandably raised a question: was all of that work for nothing?
No, but to understand why, you need to distinguish between two things people often confuse: the visual display Google removed and the underlying FAQ structured data markup, which still serves important purposes.
What Actually Changed on May 7, 2026
Google updated its Search Central documentation on May 7, 2026, with a deprecation notice for FAQ rich results. The update states that, as of that date, FAQ rich results no longer appear in Google Search.
The deprecation completes a process that started in August 2023, when Google first restricted FAQ rich results to well-known authoritative government and health websites. For most of the web, FAQ rich results have been gone for nearly three years. The May 2026 announcement removes them for everyone, including the sites that retained them after the 2023 restriction.
The timeline for what gets removed is straightforward:
- May 7, 2026: FAQ rich results stop appearing in Google search results
- June 2026: FAQ search appearance filter, rich result report, and Rich Results Test support removed from Search Console
- August 2026: FAQ rich result data removed from the Search Console API
What's notably absent from this list is any instruction to remove the FAQ schema from your pages. Google's documentation still notes that FAQ structured data can stay in place. Sites with FAQ structured data don't need to rush to remove it. Google has previously said that unused structured data doesn't cause problems for Search, and FAQPage is still a valid Schema.org type.
That distinction matters more than it might seem.
The Difference Between a Display Feature and Structured Data
Here's the core concept that most coverage of this change has glossed over.
FAQ rich results were a display feature. This is a visual enhancement that uses your structured data to render expandable question dropdowns in Google's search results page. That display feature is now gone.
FAQPage structured data is a different thing entirely. It's markup you add to your page that labels your content for machine reading — telling search engines and AI systems that your page contains specific questions and answers in a recognized format. The FAQPage Schema.org type is still valid, and the markup can stay on your pages without causing problems.
To use an analogy: Google removed the storefront window display, not the product itself. The underlying markup — the way your content is labeled and structured for machines — continues to serve purposes beyond that one display feature.
What FAQ Schema Still Does for Your WordPress Site
With the rich results display gone, the value of FAQ schema has shifted rather than disappeared. Here's what it continues to deliver:
Google Still Uses It to Understand Your Content
Google says structured data can help it understand page content. FAQPage markup no longer produces a visible FAQ rich result in Google Search, but the markup may still contribute to how accurately Google interprets what your content covers — which can affect how well your pages match question-based search queries.
AI Overviews and AI Search Visibility
This is the most significant remaining benefit, and potentially a more valuable one than the rich results ever were. Some SEO testing suggests that well-implemented schema may help with AI Overview visibility, but Google has not confirmed FAQPage markup as a direct AI Overview ranking or citation factor. That said, as Google's AI-generated search summaries become an increasingly prominent feature at the top of search results pages, well-structured FAQ content gives your pages a clearer signal about what questions your content answers — which may improve the likelihood of being cited as a source in AI-generated summaries. For WordPress bloggers targeting question-based topics, this is a meaningful reason to maintain well-structured FAQ sections.
Bing, Perplexity, and Other AI Crawlers
FAQPage structured data remains a valid Schema.org type and continues to be crawlable by Bingbot, PerplexityBot, and various retrieval-augmented generation crawlers indexing the open web. Structured FAQ content may make answers easier for search engines and AI systems to parse, though source selection depends on many signals beyond schema alone.
People Also Ask
Visible FAQ sections may still help you address question-based searches and topics that appear in People Also Ask, even though FAQ rich results are gone. People Also Ask is driven by Google's own systems and the visible content on your page, rather than by the FAQPage schema specifically, but a well-written, genuine FAQ section remains useful for both readers and search engines interpreting your content.
What Types of WordPress Content Still Benefit From FAQ Schema?
The content types that work best with FAQ schema haven't changed. The markup adds value to posts that naturally contain genuine questions and answers:
- How-to guides and tutorials where readers commonly have follow-up questions
- Topic explainer posts covering concepts your audience is learning about
- Product or service pages where common questions and objections arise
- Resource pages covering a subject in depth
- Any post where you've already written a natural FAQ section for your readers
FAQ sections created specifically to trigger rich results — thin questions, vague answers, and topics loosely related to the page — are exactly what Google's 2023 restriction and 2026 deprecation were responding to. FAQ content that genuinely serves your readers is what earns AI citation and content comprehension benefits.
Should You Remove FAQ Schema From Your Existing WordPress Posts?
No, and Google's guidance is clear on this point. You can remove the FAQ structured data from your code if you want, or leave it. There is no penalty for keeping it in place, and the content comprehension and AI search benefits give you reason to keep it.
The one exception is when you added FAQ schema to posts that don't actually have a visible FAQ section. Those posts are worth cleaning up — not because the schema causes harm, but because the underlying FAQ content was never genuinely useful to readers.
For posts with real, substantive FAQ sections that serve your readers, keep the markup. The display feature that surfaced in search results may be gone, but the structured signal it sends to search engines and AI systems remains.
The Bigger Picture: Structured Data Is Still Worth Doing
It's worth stepping back from the FAQ-specific news to note what hasn't changed. Product, Article, LocalBusiness, Event, and Review/AggregateRating all continue to produce rich results in Google Search. Structured data as a practice — labeling your content accurately for machine reading — is as relevant in 2026 as it has ever been. The AI search era makes it arguably more important, not less.
The FAQ schema is one type within that broader practice. Its display feature in Google search is gone. Its role as a content comprehension and AI search signal is not.
For WordPress bloggers who have already added FAQ schema to their posts: keep it, maintain it when you update your content, and focus on making your FAQ sections genuinely useful. For those who haven't yet added it: the case is different from what it was a year ago, but there's still a reasonable argument for doing it, particularly if AI Overviews visibility matters to your content strategy.