Google removed FAQ rich results from all search results globally on May 7, 2026, ending a feature that had been available since 2019. This change affects how structured data shows up in search, but it does not kill FAQPage schema. Pages with FAQPage schema are now 3.2x more likely to appear in Google AI Overviews, which makes the schema more valuable than it was when it was just a visual dropdown in search results.
Google stopped showing FAQ rich results, the expandable question-and-answer dropdowns that used to appear directly under certain search listings. On the same date, How-To rich results were also removed globally. These two features had been available since 2019, and for years they gave pages extra visual space in search results without requiring a paid ad.
The removal was confirmed in Google's official Search Central documentation. The reason Google gave was overuse and abuse. So many sites had added FAQPage schema to every page, regardless of whether the content actually contained real questions and answers, that the feature lost its original purpose. Google decided to stop rewarding it with visual treatment in search results.
This is not a bug. It is a permanent policy change.
Product schema, Recipe, Video, Event, and Job Posting rich results are all unaffected. Review snippets remain active. If your site uses structured data for any of these content types, nothing has changed for you on the visual display side.
The removal was specific to FAQ rich results and How-To rich results. These were the two types most frequently added to content that did not genuinely warrant them. Every other rich result type continues to work as before, and Google has given no indication that further removals are planned for the active categories.
If you have a product-focused site, an events business, or a recipe blog, your schema work is not affected. Your visual enhancements in search results still appear. The change targets informational and how-to content specifically, which is where the schema abuse was most concentrated.
For service businesses, SaaS companies, and agencies that had been using FAQPage schema primarily to get those dropdown expansions in search results, the visual benefit is gone. But as covered in the next section, the underlying value of that schema has shifted, not disappeared.
Google's stated reason is that the feature was being overused to the point of manipulation. From 2019 onward, the SEO community quickly figured out that adding FAQPage schema to any page could double or triple the visual footprint of that listing in search results, pushing competitors further down the page.
By 2024, a majority of informational pages from large sites had FAQPage schema added, regardless of content quality. FAQ dropdowns became a standard SEO trick rather than a genuine signal of content structure. Google's systems could not reliably distinguish between pages that genuinely contained structured Q&A content and pages that had simply added the schema to claim more screen space.
This is a pattern Google has followed before. When a structured data type gets abused at scale, Google removes the visual reward rather than attempting to police individual implementations. The same thing happened with certain star rating schemas in earlier years. Google is not penalizing pages for having FAQPage schema. It is simply no longer giving a visual reward in traditional search results for that schema.
A contact page for a dental clinic should not have fifteen FAQPage entries about filling materials and anaesthetic types. A pricing page for a SaaS tool should not be wrapped in FAQPage schema listing questions that no real customer has ever asked. Both of these practices became common between 2020 and 2024 because the visual reward was too good to ignore. A listing with five FAQ dropdowns could take up roughly triple the vertical space of a standard result. That kind of competitive advantage attracted wide misuse, and Google's response was to switch the feature off entirely rather than trying to audit individual implementations at scale.
Yes, and the reason matters more now than the visual feature ever did. Pages with FAQPage schema are 3.2x more likely to appear in Google AI Overviews. That number is significant. AI Overviews now appear for a large share of informational queries, and the citations within those overviews drive real traffic.
The mechanism is straightforward. AI Overviews pull content from pages that are structured to answer questions clearly. FAQPage schema signals to Google's systems, including the AI models behind AI Overviews, that this page contains organized question-and-answer content. That structure makes the page easier to parse, cite, and surface in an AI-generated answer.
At Ranksiege & Co, we have been adding FAQPage schema to every client page as a standard practice since 2024. Across our SEO accounts, clients in B2B SaaS and professional services categories now see measurable AI Overview appearances. One client in the UAE accumulated 40+ AI Overview citations in a single quarter after we rebuilt their content architecture around structured Q&A blocks and added proper schema markup.
The point is this: FAQPage schema has moved from a display feature to a content signal. The reward is no longer a dropdown in search results. The reward is AI citation, which is where informational search is heading.
Want your pages showing up in Google AI Overviews? At Ranksiege & Co, FAQPage schema is included in every SEO engagement from $199 per month. We also run a free 200-point site audit that checks your current schema implementation. Start at free audit.
Keep your FAQPage schema. Do not remove it. The pages that already have it implemented correctly are in a better position for AI Overview citations than pages without it. Removing the schema now would be moving in the wrong direction.
What you should change is why you are adding it. If FAQPage schema was on your roadmap as a visual display tactic, that use case is gone. The new use case is AI citation readiness. That means the quality of your Q&A content matters more than ever.
Here is what a sound schema approach looks like after May 2026:
How-To rich results were removed at the same time as FAQ rich results on May 7, 2026. The same reasoning applies. How-To schema had been added to step-by-step content across thousands of sites, and the visual enhancement in search results had become a commodity rather than a quality signal.
For sites with genuine instructional content, How-To schema still has value as a content signal for AI systems. The structure of numbered steps, named steps, and step-by-step organization is still parsed and understood by Google's models. The visual rich result is gone. The underlying signal for AI understanding is not.
If your site has pages with How-To schema, keep the schema. Review whether the underlying content is genuinely instructional with clear steps. If it is, the AI citation benefit applies here too.
The short-term effect is a loss of visual real estate in search results for pages that had FAQ rich results showing. A listing that used to expand to show three to five dropdown questions now looks like a standard blue-link result. That change alone can reduce click-through rate, particularly for informational queries where the expanded listing was drawing attention.
The medium-term effect depends on whether AI Overviews replace some of that lost visibility. For queries where AI Overviews now appear, a citation inside the AI Overview can deliver a different kind of traffic, smaller in volume but higher in intent, because the user has already been given context and is clicking to go deeper.
The sites that will feel this change least are the ones that had been producing high-quality, structured content with real Q&A sections. Their FAQ schema was legitimate to begin with. The sites that feel it most are the ones that had been adding schema tactically to thin content pages. Those pages lose both the visual enhancement and, typically, have weaker AI Overview positioning because the underlying content does not answer questions well.
If you are checking your Google Search Console data after May 7, look at your CTR for the pages that previously had FAQ rich results showing. A drop in CTR without a corresponding drop in average position is the clearest signal that the visual loss is the cause. That diagnosis matters because the fix is different from a ranking problem. You are not trying to recover rankings. You are trying to build AI Overview visibility as the new channel for those queries. Content quality, structured answers, and FAQPage schema working together are how that happens.
Structured data in 2026 is less about visual enhancements in traditional search results and more about content signals for AI systems. That shift was already underway before May 7. The FAQ removal makes it more visible.
The schema types that carry the most weight right now are the ones that help AI engines understand content context: Article, FAQPage, Author, Organization, LocalBusiness, Product, and BreadcrumbList. These do not all produce visual rich results. Most of them work silently as content signals that inform how AI systems categorize and cite your pages.
For businesses that want a clear starting point, every page on your site should have at minimum: Article schema (or the appropriate content type), BreadcrumbList schema, and Organization schema on the homepage. Pages with genuine Q&A content should add FAQPage schema. Service pages can add Service schema. Local businesses should have LocalBusiness schema on location pages.
This is standard practice in our SEO service at our SEO service. We implement schema across client sites as part of onboarding, and we audit schema health quarterly because Google updates how it interprets structured data often enough that annual checks are not sufficient.
One practical note on implementation: schema added through Google Tag Manager or a WordPress plugin carries the same value as schema hard-coded in your page HTML, as long as it renders before Google's crawler finishes parsing the page. The format (JSON-LD, Microdata, RDFa) matters less than the accuracy of the data you put in it. Google's own documentation recommends JSON-LD for its simplicity and ease of maintenance. If you are not sure whether your current schema is implemented correctly, Google Search Console's Rich Results Test will tell you exactly which pages are passing validation and which have errors that need fixing before the schema works as intended.