Google Killed FAQ Rich Results: What Should Webflow Sites Do?

Google quietly ended FAQ rich results on May 7, 2026. The expandable dropdown that has appeared under search listings for the last seven years is gone. The schema itself, FAQPage from schema.org, is still valid and Google still parses the markup to understand pages. For the 70 plus Webflow projects I have shipped at Phoenix Studio, the FAQPage block is one of the most copied components in B2B SaaS templates. Most of those clients ran FAQ schema purely to harvest SERP dropdowns. Now the dropdowns are gone but the markup still earns its place in AI Overviews and AI Mode citations if the answer copy is written for extraction. In this piece I walk through what changed, what to keep, what to rewrite, and how Search Console reporting changes through June and August 2026.

What exactly did Google deprecate on May 7, 2026?

Google ended FAQ rich results in Search on May 7, 2026. The expandable dropdown answers no longer appear under listings. The FAQ structured data documentation at Search Central was updated the same week with an upcoming deprecation notice. The FAQPage schema type itself remains valid; only the rich-result rendering has been removed from the Search interface.

The change is documented on the Google Search Central FAQPage page. Search Engine Land, Search Engine Journal, and Search Engine Roundtable covered the change within 48 hours. The framing in Google's own documentation is unusually direct for a deprecation. The page no longer describes how to win rich results, because there are no rich results to win. It describes how to mark up FAQs for site understanding, which is a meaningfully different goal.

Is FAQPage schema still valid on my Webflow site?

Yes. FAQPage remains a valid Schema.org type and Google still uses the markup to understand page structure. The schema continues to help AI Overviews, AI Mode, and other LLM-based search surfaces parse the question and answer pairs on a page. Removing the markup would lose that signal without recovering any rich-result real estate.

For Webflow B2B SaaS sites, the practical answer is to keep the FAQPage block in the CMS template and keep the JSON-LD output script. The question is not whether to keep the schema. The question is whether the content inside the schema is written for AI extraction, which is a different writing pattern from the keyword-harvesting style that worked for SERP dropdowns. A question that ends in a vague three-word answer was fine for a dropdown. It is useless to an AI Overview that needs a self-contained 40 to 60 word block to cite. The piece I wrote on AEO answer block patterns covers the writing discipline that earns AI citation in 2026.

Why did Google kill FAQ rich results after seven years?

Google has not published a stated reason. The most likely read from outside is that AI Overviews and AI Mode now occupy the visual space that FAQ dropdowns used to live in, and the rich result was crowding the same answer twice on the same query. Removing the dropdown cleans the SERP for the AI surfaces. The pattern matches the September 2023 HowTo rich result deprecation, which preceded a similar consolidation.

The structural read matters because it predicts what comes next. The pattern of the last three years is consistent. Google retires older rich results that compete visually with AI Overviews, and reuses the underlying structured data to feed the AI surface. Sites that read this pattern early and rewrote their content for AI extraction rather than for rich-result harvesting are positioned for the next two years. Sites that retire the schema entirely lose the AI citation signal too, which is the wrong direction.

How does this change affect AI Overviews and AI Mode citations?

The change does not directly affect AI Overviews or AI Mode citations because both surfaces parse the entire page, not just the rich result. The schema markup continues to help these systems understand which questions and answers are on the page. The deprecation removes the SERP dropdown but does not remove the signal that the markup provides to AI extraction systems.

For B2B SaaS Webflow sites, the practical implication is that the writing pattern for FAQ blocks should change. Until last week, the optimization was to write questions that matched search queries and answers that triggered the dropdown rendering. As of May 7, the optimization is to write answers that an AI Overview can quote verbatim as the authoritative response. The piece I wrote on how Google's AI surfaces actually pick sources covers the citation-selection pattern that determines what gets quoted.

Should I rip out my Webflow FAQ component entirely?

No. Keep the Webflow FAQ component, keep the FAQPage schema, and rewrite the questions and answers for AEO extraction rather than rich-result harvesting. The component still earns its place as a structured answer surface that AI systems can cite. The rewrite is a content pass, not a teardown.

For a typical B2B SaaS Webflow site with 8 to 15 FAQ items per template, the rewrite takes about 2 to 3 hours per template. The pattern I follow at Phoenix Studio is to take the top three questions per page based on Search Console click data, rewrite the answers as self-contained 40 to 60 word blocks that work without the question for context, and leave the remaining questions as supporting prose. Each rewritten block is testable against a single AI Overview query within a week of publication.

What happens to Search Console FAQ reporting in June 2026?

Google has stated that FAQ enhancement reporting in Search Console will be removed in June 2026. After removal, the FAQ section will no longer appear in the Enhancements menu, and any historical FAQ click and impression data will not be available through the standard reporting interface. The Search Console API will continue returning FAQ data until August 2026.

For Webflow B2B SaaS sites that have used Search Console FAQ reporting to track which FAQ items earned the most rich-result clicks, the practical implication is to export that data this month. Open Search Console, navigate to the Enhancements section, find FAQ, and export the last 12 months of click and impression data to CSV. This historical baseline is useful for the rewrite pass, and once June 2026 arrives the data is no longer accessible through the standard interface.

How do I rewrite FAQ sections for AEO extraction instead of rich results?

Rewrite FAQ sections for AEO extraction by writing each answer as a self-contained 40 to 60 word block that makes sense without the question for context. Start with a direct answer in the first sentence. Add one supporting sentence with a verifiable detail. Close with one sentence that anchors the answer to a specific source or platform state. Use the question only as a header.

The Webflow Designer side of the rewrite is to keep the existing FAQ component structure unchanged. The change happens in the CMS, in the answer rich-text field. Each answer goes from a 15 to 25 word dropdown-style response to a 40 to 60 word standalone block. The JSON-LD output script renders the same FAQPage schema with the new answers automatically. No changes to the Designer or to the schema script are required for the rewrite. The discipline is purely editorial. For more on the underlying writing pattern, see my notes on AEO answer block patterns.

Does keeping FAQ schema hurt my Webflow site's performance?

No. FAQPage JSON-LD markup adds a small amount of inline script to the page, typically under 5 kilobytes for a 10-question FAQ. The performance cost is negligible and does not affect Core Web Vitals scores. Removing the schema to chase performance gains is the wrong trade-off because it removes a useful signal for AI search systems while saving microseconds.

For Webflow sites specifically, the JSON-LD output script lives in the Page Settings custom code section or in a Designer embed. It executes on page load alongside other site scripts and does not block rendering when implemented correctly. Site audits I have run on Phoenix Studio client builds show FAQPage schema contributing under one percent of total page weight on a typical 800 kilobyte marketing page. The CWV math is settled. Keep the schema.

When does the Search Console API stop returning FAQ data?

The Search Console API stops returning FAQ enhancement data in August 2026. After that date, programmatic access to historical FAQ click and impression data will not be available through the API. Sites running automated reporting workflows that depend on FAQ data should migrate to alternative metrics or capture a final data snapshot before August 2026 arrives.

For Webflow B2B SaaS sites with automated SEO reporting workflows, the August deadline is the harder cutoff because reporting pipelines do not respond as gracefully to a missing API field as a manual dashboard does. The practical pattern this month is to audit which workflows reference FAQ data, capture a 12-month snapshot before the API access ends, and migrate the dependent reporting to alternative signal sources like AI citation tracking or organic click data on the FAQ-bearing pages themselves.

Where else can structured data still move the needle in 2026?

Structured data still moves the needle in 2026 through Product, Article, Organization, BreadcrumbList, Event, Recipe, and Video schemas, each of which Google continues to support with rich-result rendering. For B2B SaaS Webflow sites, the highest-leverage schemas remain Article for blog posts, Product for paid plans, BreadcrumbList for navigation, and Organization for the company entity itself.

The schema map I deploy on Phoenix Studio B2B SaaS builds is consistent: Article on every blog post, BreadcrumbList on every CMS-driven page, Organization in the site footer global embed, Product on the pricing page if the SaaS plans qualify, and FAQPage on FAQ blocks for AI extraction rather than rich-result chase. This stack survives the May 7 change without modification. The FAQ section is the only piece that needs a rewrite pass for AEO. Everything else continues exactly as before. The piece I wrote earlier this year on the AEO closed loop covers how the schema map integrates with the answer-extraction discipline.

If you are auditing a Webflow B2B SaaS site for the May 7 FAQ change and want to talk through the rewrite pass for your specific templates, drop me a line and tell me how many FAQ blocks live across the site today. I will share the rewrite pattern I am running this week at Phoenix Studio. Let's chat.