← Back to blog

Technical SEO · July 15, 2026 · 8 min read

FAQ and HowTo Schema After Google's Rollback: What Still Earns Rich Results

FAQ schema rich results ended May 2026. Learn which sites still qualify, what schema types still work, and where to redeploy your structured data effort.

By FluxWriter Team

FAQ schema rich results are officially dead for most websites — Google pulled the last of them on May 7, 2026, ending a three-year retreat that began in August 2023. But the markup itself is not dead, and knowing the difference between the feature and the signal is what separates teams that adapt quickly from those that rip out perfectly useful structured data.

What Actually Happened, in Order

Google's rollback was not a single event. It played out in stages:

August 2023. Google announced that FAQ rich results would be limited to "well-known, authoritative government and health websites." Everyone else lost the expanding accordion snippets overnight. At the same time, HowTo rich results were dropped from mobile entirely.

September 2023. HowTo rich results were removed from desktop as well. A brief two-week window where some desktop HowTo snippets still appeared closed without announcement.

2024–early 2026. The government and health carve-out for FAQ rich results continued, but enforcement tightened. Sites that had previously qualified started seeing zero impressions in the FAQ report in Search Console.

May 7, 2026. Google deprecated FAQ rich results completely, for all sites. The FAQ search appearance filter in Search Console was removed the same month. The FAQ rich result report itself disappears in June 2026, and the Search Console API endpoint for FAQ data goes dark in August 2026.

If your analytics team is pulling FAQ impression data from the API, update those queries before August or you will get silent NULLs in downstream dashboards.

Why Google Pulled It

Google's public explanation across both the 2023 and 2026 announcements pointed to the same two factors: clutter and abuse.

The clutter problem was real. By 2023, a meaningful percentage of result pages contained FAQ accordions that had nothing to do with the page's primary purpose — a product page with an FAQ section about shipping, or a blog post with bolted-on question markup covering topics the article barely touched. The SERP became visually noisy, and click-through rates on organic results below the expanded FAQ blocks dropped measurably.

The abuse problem compounded it. FAQ schema became a growth hack. Once SEOs discovered that adding five questions to any page could produce an accordion that dominated the SERP real estate above the fold, the markup proliferated far beyond pages where it made editorial sense.

The March 2026 structured data update, which preceded the May deprecation, made this explicit: Google narrowed rich result eligibility across multiple types to pages where the schema describes the primary content purpose. Supplementary FAQ markup on pages whose primary purpose is something else no longer qualifies for any rich result type.

What Still Earns Rich Results in This Space

With FAQ and HowTo gone, the two closest schema types still generating rich results are:

QAPage. This is for pages where a single question has multiple community-submitted answers — think Stack Overflow threads, Reddit posts, Quora answers. Google still renders a rich result for these in certain queries, showing the top-voted answer in the snippet. If your site runs a genuine community Q&A section where users post questions and other users answer, QAPage is appropriate and still active.

Speakable. Speakable schema marks sections of content as suitable for text-to-speech by voice assistants. It does not generate a traditional visual rich result, but it directly influences which passages Google's Assistant and AI Mode read aloud in voice responses. It is worth implementing on pages with short, definitional paragraphs that answer discrete questions.

The Case for Keeping Your FAQPage Markup

Here is the counterintuitive recommendation: do not remove FAQPage structured data from pages where it accurately describes the content.

Google confirmed post-deprecation that it will continue parsing FAQPage markup as a comprehension signal, even though it no longer renders rich results from it. More importantly, every major AI platform that generates answers from web content — ChatGPT, Perplexity, Google AI Overviews — uses structured data as a primary parsing signal. FAQPage markup makes the question-and-answer structure of your content machine-readable in a way that unstructured prose does not.

One data point that circulated after the May 7 announcement: pages with FAQPage markup were cited in Google AI Overview responses at a rate roughly 3x higher than equivalent pages with the same content but no structured data. This is not a controlled study, but it matches the directional logic — AI systems doing passage retrieval prefer content where the question and answer are explicitly tagged.

Google's own language on this is careful but consistent: they will "continue to use FAQ markup to understand pages." That is a smaller promise than "we will show you a rich result," but it is not nothing.

What to Remove vs. What to Keep

Remove FAQPage schema that was added as a rich-result hack — markup applied to pages where FAQ content is a minor section appended for SERP purposes, not a meaningful part of the page. If the FAQ section represents fewer than 20% of the page's content and is not the primary reason a user would land on the page, the markup is vestigial.

Keep FAQPage schema on:

• Dedicated FAQ pages
• Support documentation pages built around Q&A
• Product pages where the FAQ section is substantive (6+ questions, full answers, not just one-liners)
• Any page where a user's primary intent is getting an answer to a specific question

Where to Redeploy Your Structured Data Effort

If you previously invested time in FAQ and HowTo markup for rich result purposes, the highest-leverage redeploy targets in 2026 are:

Article and NewsArticle schema. These feed directly into the Top Stories carousel and AI Overviews citation boxes. Sites that have Article markup implemented correctly show up in AI-generated summaries far more consistently than sites without it.

Product schema with Review markup. Still one of the most reliable rich result types. Properly implemented product pages with aggregate rating markup earn star displays in results, and these have not been deprecated.

Event schema. Google continues to surface Event rich results aggressively for local and time-bound content.

Breadcrumb schema. Boring but durable. Breadcrumb markup earns rich results on nearly every eligible page and has never been deprecated.

VideoObject schema. YouTube embeds without VideoObject markup increasingly miss the video carousel. If your content strategy includes video, this is an easy win.

A Practical Redeployment Checklist

If you had FAQ or HowTo markup across a large site, here is a reasonable audit sequence:

1. Pull your structured data coverage report from Search Console before the FAQ report disappears in June.
2. Identify pages that had FAQ impressions in the last 12 months — those were your working implementations. Retain markup on these pages if the content is genuinely Q&A-focused.
3. For pages where FAQ markup was decorative, audit whether Article, Product, or Breadcrumb schema applies instead. Implement the appropriate type.
4. If you have step-by-step content that previously used HowTo schema, leave the markup in place — Google still parses it — but add VideoObject markup if the process is demonstrated in video.
5. On FAQ pages with short, direct answers, consider adding Speakable markup to the two or three answers that are most self-contained. Voice AI is a real source of traffic for informational queries.

FAQ

Is it worth adding FAQPage schema to new content in 2026?

Yes, if the page is genuinely built around Q&A content. There is no rich result payoff anymore, but FAQPage markup still signals content structure to Google's comprehension systems and to AI platforms that use structured data for citation selection. On pages where FAQ is the primary content format, the markup costs almost nothing to implement and retains meaningful signal value.

Will removing FAQ schema help a page rank better?

No evidence suggests removing FAQPage markup improves rankings. Google has consistently said structured data is not a ranking factor in either direction. The only reason to remove it is cleanup — if the markup inaccurately describes the page or was added purely to chase a rich result that no longer exists.

What is the difference between FAQPage and QAPage, and which still works?

FAQPage is for pages where the site owner provides both the question and the official answer. QAPage is for pages where one question has multiple user-submitted answers (community forums, Q&A threads). QAPage still generates selective rich results in Google Search. FAQPage no longer generates rich results but retains value as an AI comprehension signal.

The practical takeaway: audit your FAQ and HowTo markup for intent-fit rather than making a site-wide removal decision. Pages with genuine Q&A content should keep the markup and shift the success metric from Search Console impressions to AI citation frequency. Pages that had schema bolted on for SERP gains are good candidates for richer, more appropriate structured data types.

If you are managing structured data across a large site and want to test which schema types are driving AI Overview citations versus traditional impressions, content tools like FluxWriter can help you map markup coverage to traffic sources systematically — useful when you are deciding where to redeploy the effort that previously went into FAQ rich result optimization.

← All posts