Short Answer
Did Google end FAQ rich results?
Yes. Google stopped displaying FAQ rich results on May 7, 2026. Related Search Console reports and Rich Results Test support are being removed in June 2026, with API support ending in August 2026. FAQPage still exists at Schema.org and Google still parses it. The display is gone, not the vocabulary or the parser. Most sites should leave the markup in place.
By Kai Williams | Updated July 2026 | AEO
Quick Summary
- Google stopped showing FAQ rich results in Search on May 7, 2026, completing a deprecation that began in August 2023 when FAQ visibility was restricted to health and government sites only.
- What was deprecated is the SERP display, the Search Console report, and the testing support. The FAQPage vocabulary at Schema.org remains valid, and Google still parses the markup. These are five separate layers that behave independently.
- Evidence for FAQ schema improving AI citation rates is genuinely mixed. A December 2024 study found no correlation between schema coverage and AI citations. Microsoft’s Fabrice Canel suggested structured data aids Copilot understanding. For ChatGPT, Perplexity, and Gemini, the claim is hypothesis-level with no published controlled study.
- Most sites should leave the markup in place. The cost of removing it is real. The upside is zero for Google’s SERP, and the potential AI-extraction benefit, however unproven, exists only if the markup stays.
- The August 2026 deadline is the one that affects technical teams: Search Console API support for FAQ rich results ends then. If you have automated pipelines filtering on FAQ search appearance, export your baseline data now and update your API calls before August.
Disclosure: This article separates confirmed platform facts from industry hypotheses throughout. Claims labeled as such are sourced to their origin. Last verified: July 2026.
Google stopped showing FAQ rich results in Search on May 7, 2026. The expandable Q&A dropdowns that SEOs spent years implementing across help centers and blog posts are gone from the SERP. Search Engine Land’s Barry Schwartz first reported the change from Google’s official developer documentation. What is less clear from most of the coverage is exactly what was deprecated and what was not, and what the evidence actually says about FAQ schema and AI search. Both questions matter and this article addresses them separately. The broader context of how AI is reshaping search behavior is part of why structured data decisions matter beyond the Google SERP.
What Google Actually Deprecated: A Five-Layer Breakdown
Summary: The coverage treats “Google deprecated FAQ” as a single event. It was not. Five separate layers of the structured data ecosystem changed on different timelines, and most are still intact.
Understanding exactly what changed, and what did not, prevents two common mistakes: removing markup that still has value, and retaining expectations about SERP features that are genuinely gone. The five layers operate independently.
| Layer | Status | Effective date | Practical consequence |
|---|---|---|---|
| Vocabulary Does FAQPage exist at Schema.org? |
Valid | No change | FAQPage, QAPage, Question, and Answer entities remain in the Schema.org vocabulary. Implementing them is syntactically correct and schema-compliant. |
| Parsing Does Google still read the markup? |
Active | No change | Google’s crawler still reads FAQPage markup. Google’s own deprecation notice says you can leave the schema in place. Other search engines may continue to process it. |
| Eligibility Can sites qualify for the feature? |
Ended | May 7, 2026 | No sites are eligible for FAQ rich results in Google Search as of May 7, 2026. Health and government sites lost eligibility along with all other site types. |
| Presentation Does the feature appear in search? |
Ended | May 7, 2026 | FAQ expandable dropdowns no longer show in Google Search results for any site. The SERP display is permanently gone. |
| Reporting Can publishers measure it? |
Being removed | June 2026 (UI), August 2026 (API) | FAQ search appearance, rich result report, and Rich Results Test support are removed in June. Search Console API support ends in August. Export your historical data now. |
The deprecation announcement from Google’s developer documentation reads:
FAQ rich results are no longer appearing in Google Search. We will be dropping the FAQ search appearance, rich result report, and support in the Rich results test in June 2026. To allow time for adjusting your API calls, support for the FAQ rich result in the Search Console API will be removed in August 2026.
This Was a Long Time Coming
Summary: The FAQ rich result was already effectively dead for most sites by August 2023. The May 2026 announcement is administrative closure of a feature that had not meaningfully worked for non-authority sites in almost three years.
Was this deprecation a surprise?
No. Google first restricted FAQ rich results to authoritative health and government sites in August 2023, and FAQ rich result impressions for non-authority sites collapsed to near zero almost immediately. The May 2026 announcement is the formal end of the road. For most sites, the SERP benefit of FAQ schema has been negligible for almost three years.
The trajectory was consistent. Google restricted HowTo rich results in the same August 2023 update. In the years that followed, Search Console data showed near-zero FAQ impressions for all but a narrow set of health and government properties. Publishers who continued implementing FAQ schema after 2023 were doing so for reasons other than the Google SERP display. The May 2026 announcement removes the infrastructure associated with a feature that had been functionally absent for most of the industry since late 2023.
If your site has been carrying FAQ schema for SEO reasons, the SERP benefit has been negligible for almost three years. The actual change in May 2026 is administrative cleanup: Google is closing the reports and APIs that SEOs were still pulling from. The underlying markup question, whether to keep it, depends on what else you are using it for.
What the Evidence Actually Says About FAQ Schema and AI Citations
Summary: The claim that FAQ schema increases AI citation rates is repeated across the industry but is not backed by a published, controlled study. One study found no correlation. One platform engineer suggested structured data aids comprehension. The honest answer is: probably useful, not proven.
What is confirmed vs. what is hypothesis
Confirmed by Google: FAQPage markup can be left in place. Google still parses it. Other search engines may continue to process it.
Confirmed at Schema.org: FAQPage, QAPage, Question, and Answer entities remain valid vocabulary.
Observed but not controlled: Microsoft’s Fabrice Canel stated in March 2025 that structured data helps Copilot understand content. This was said in the context of Copilot specifically and was not a published controlled study.
Conflicting evidence: A December 2024 study by Search/Atlas found no correlation between schema coverage and AI citation rates.
Not confirmed (hypothesis): FAQ schema increases citation rates on ChatGPT, Perplexity, Gemini, or Google AI Overviews. FAQ markup influences People Also Ask eligibility. FAQ schema improves voice search visibility.
Most articles on this topic carry a version of the phrase “FAQ schema still helps AI search engines.” The evidence behind that claim varies substantially by platform, and one study directly contradicts it. The following matrix applies the AEO Evidence Ladder, which grades recommendations by the strength of their evidence, to every major platform claim.
| Platform | Claim | Evidence level | Source or basis |
|---|---|---|---|
| Google AI Overviews | FAQ schema aids AI Overview eligibility or citation rate | Level 4, hypothesis | Not documented by Google. No primary source published. Repeated in industry without attribution. |
| Microsoft Copilot | Structured data helps Copilot understand content | Level 3, observed, no controls | Fabrice Canel (Microsoft), stated March 2025. Copilot-specific; not extended to other platforms by Canel. |
| ChatGPT | FAQ schema increases ChatGPT citation rate | Level 4, hypothesis | No controlled study published. ChatGPT retrieval via Bing; Bing structured data behavior is partially documented but not FAQ-specific citation claims. |
| Perplexity | Structured data aids extraction and citation | Level 4, hypothesis | No documentation from Perplexity. Community-derived from general crawling behavior observations. |
| Gemini | FAQ markup signals Q&A content to Gemini | Level 4, hypothesis | No primary source from Google on Gemini-specific structured data behavior for citation eligibility. |
| Industry finding | Schema coverage correlates with AI citations | No correlation found (Level 2 study) |
Search/Atlas, December 2024. Methodology and sample size not fully published. Directly contradicts hypothesis-level claims above. |
The honest position is this: FAQ schema is plausibly useful for AI extraction because it makes Q&A structure machine-readable in a way that does not depend on crawler HTML parsing. That is a reasonable argument. It is not the same as a documented finding. The practical recommendation, keep the schema because removing it costs more than it saves and the potential benefit still exists even if unproven, does not require overstating the evidence to be valid. If you want to measure directly whether FAQ markup is moving your AI citation rates, Profound tracks citation appearances across ChatGPT, Perplexity, Gemini, and Bing in near real time.
The AEO Angle: Why FAQ Schema Still Has a Role
Summary: FAQPage schema does useful work beyond the Google SERP, but that work is best described as making content more machine-readable, not as a citation-rate multiplier with proven ROI.
AI engines that crawl the open web can use JSON-LD to identify clean question-and-answer pairs on a page without having to parse document structure from HTML. Whether that parsing advantage translates to higher citation rates is the question the December 2024 study was unable to confirm. What is not in dispute is that schema markup makes content structure unambiguous for any system that uses it. That is a meaningful property even if the downstream effect on citation rates is unclear.
For sites doing AEO work, the reframing is practical: FAQ schema has shifted from being a SERP decoration to being a content legibility signal. The implementation is identical. The audience has changed from the Google SERP renderer to machine crawlers, AI retrieval systems, and Bing’s index, which ChatGPT draws on for 87% of its web citations. If you want to understand how each AI platform decides what to cite, the structured data picture is one component of a broader system that includes third-party validation, answer capsule formatting, and entity corroboration.
FAQPage versus QAPage: Which schema type applies?
FAQPage applies when one author or entity provides both the question and the answer, and the page is structured as a list of such pairs. This is the correct type for help centers, product FAQs, and editorial Q&A content where no community input is involved.
QAPage applies when a question has been answered by multiple community members, such as a forum thread, a Stack Overflow page, or a Reddit post. It uses the Question entity with multiple Answer entities, where each answer can have upvoteCount and dateCreated properties.
Adding FAQPage markup to a community forum, or QAPage markup to a brand help center, is a misuse. Neither schema type is a substitute for the other, and neither substitutes for Product, Review, or other surviving rich result types.
Should You Keep or Remove the Markup? A Decision Matrix
Summary: “Leave it because it cannot hurt” is not a complete decision framework. The real criteria are content parity, documented consumers of the markup, and maintenance cost.
| Condition | Recommendation | Reason |
|---|---|---|
| FAQ questions and answers are visibly displayed on the page and kept up to date | Keep | Content parity exists. Markup accurately describes on-page content. Any AI-extraction benefit requires the schema to be present. |
| Markup is on pages targeting AI citation use cases and you have a content refresh process | Keep and maintain | Structured data is one component of AI legibility. Keeping it is consistent with a broader AEO investment. |
| Removing the markup requires significant development effort and the pages are performing well | Keep | Developer cost exceeds any benefit of removal. Google said explicitly that removal is not required. |
| Markup describes Q&As that are not visible on the page (hidden content, dynamically loaded only) | Remove or fix | Content parity does not exist. Schema describing content not visible to crawlers is misleading markup and risks a manual action under Google’s spam policies. |
| FAQ content is stale, inaccurate, or no one owns the refresh process | Remove or update | Stale schema citing inaccurate information can surface incorrect answers in AI outputs. The risk of outdated markup is greater than the upside of leaving it. |
| Schema was added only for the Google rich result display and no other justification exists | Evaluate cost | The original justification is gone. If the content is well-maintained and visible, keeping the markup has no downside. If it is low quality, removing it is the better path. |
The Reporting Migration Runbook: What to Do Before August
Summary: The August Search Console API deadline is the one that can break automated reporting pipelines. If you pull FAQ search appearance data via API or BigQuery, act now.
Follow these steps before the June and August deadlines to avoid reporting gaps and pipeline failures.
- Export your FAQ rich results data now (before June). Go to Search Console, open the Search Results report, filter by Search Appearance: FAQ Rich Results, and set the date range to the maximum available. Export to CSV. Save the file with a date stamp. This is your only record of pre-deprecation FAQ rich result performance once the report is removed in June.
- Document your baseline. Before June, record total impressions, clicks, CTR, and average position for FAQ-marked URLs over the last 90 days. Store this alongside your export. You will need this for impact isolation when comparing pre- and post-deprecation performance.
- Identify any automated API pipelines filtering on FAQ data. Search your reporting codebase for
searchAppearance,faqPage, orFAQ_RICH_RESULT. Any query using these filters will return null values or errors after August. Update those calls to remove the FAQ-specific filter or replace it with a different dimension. - Update BigQuery exports if applicable. If you are ingesting Search Console data into BigQuery via the Data Studio connector or a custom pipeline, the
search_appearancedimension for FAQ data will stop being populated after August. Add a flag in your pipeline to mark the last valid date for this dimension to prevent downstream data quality issues. - Set up CTR comparison monitoring for the 60 days after May 7. Isolate FAQ-marked URLs and compare their CTR trend against matched non-FAQ URLs in the same category. This is the only way to separate the CTR impact of losing the rich result from concurrent ranking changes. After June, when the report disappears, you will no longer have the Search Console search appearance dimension to help you make this distinction.
Validating FAQ Schema After the Rich Results Test Update
Summary: The Rich Results Test will no longer show a FAQ eligibility preview after June. But syntax validation, content parity checks, and rendering tests can still confirm your markup is correct and machine-readable.
The removal of FAQ support from the Rich Results Test in June removes the ability to preview what the rich result would look like, not the ability to validate that your JSON-LD is syntactically correct. The following workflow replaces the Rich Results Test preview for FAQ validation purposes.
- Syntax validation: Use the Schema.org Validator (validator.schema.org) to confirm your FAQPage markup uses valid property names and data types. This validates against the Schema.org specification and is independent of Google’s feature support status.
- JSON-LD linting: Paste your script tag contents into a JSON validator to confirm there are no syntax errors, unclosed brackets, or encoding issues. Even syntactically correct schema can break if the JSON itself is malformed.
- Rich Results Test (syntax only): The Rich Results Test can still validate that your JSON-LD parses correctly. After June, it will no longer render a FAQ preview, but it will still flag structural errors in the markup. Use it as a syntax check, not an eligibility check.
- Content parity check: Manually verify that every question and answer in your FAQPage schema appears visibly on the page. If a Q&A is in the schema but not in the visible HTML, you have a content parity problem that may trigger Google’s spam policies.
- Rendered content check: Load the page with JavaScript disabled (Chrome DevTools: Settings > Debugger > Disable JavaScript). Confirm that FAQ questions and answers are still visible. If they disappear, your FAQ content is JavaScript-rendered and invisible to crawlers that do not execute JavaScript.
- Canonical URL check: Confirm the canonical tag on each FAQ page points to itself, not to a parent page or category. Schema markup on a non-canonical URL is ignored by most parsers.
How to Write FAQ Answers AI Systems Can Actually Extract
Summary: Schema markup makes Q&A structure machine-readable, but the answer quality determines whether the content is worth extracting. Vague, keyword-heavy FAQ answers fail even with perfect schema.
Most FAQ content on the web was written to satisfy a keyword checker or to fill a structured data requirement, not to answer a question directly. AI extraction systems prefer answers that work as standalone statements: a direct first sentence, a qualifying condition, and a named source or date. Here is the difference in practice.
| Before: keyword-heavy, vague | After: citation-ready, direct |
|---|---|
|
Q: What is Answer Engine Optimization? Answer Engine Optimization, or AEO, is a cutting-edge digital marketing strategy designed to optimize your content so that AI search engines and voice assistants provide your information as the answer to user queries, helping brands reach customers in the new era of AI-powered search and drive organic visibility across multiple platforms. |
Q: What is Answer Engine Optimization? Answer Engine Optimization (AEO) is the practice of structuring content so AI systems select it as a cited source or spoken answer. It differs from SEO in that it targets AI retrieval logic rather than keyword ranking. First documented as a distinct discipline in 2023, AEO focuses on entity authority, answer capsule formatting, and third-party corroboration. (The Prompt Insider, July 2026.) |
What makes the revised answer citation-ready:
- The first sentence is a complete, standalone definition that works without context before or after it
- A contrast with a related concept (SEO) is explicit, not implied
- A date is included, which supports freshness signals for platforms like Perplexity that weight recency
- A named source is attached, which helps AI systems cite rather than paraphrase
- The language is factual and neutral with no marketing phrases like “cutting-edge” or “drive visibility”
Apply this pattern to every question in your FAQPage markup. The schema makes the structure legible. The answer quality determines whether anything useful gets extracted.
Schema Types That Are Not Replacements for FAQ
Summary: Product, Review, Recipe, and Event schema continue to earn Google rich results, but they describe different entities. Adding them to pages where they do not apply is invalid markup, not a FAQ workaround.
Several articles list “schema types that still work” alongside the FAQ deprecation in a way that implies these types are alternative paths to FAQ-style SERP features. They are not. Each surviving rich result type has specific eligibility requirements and describes a distinct entity type. Using them outside those requirements risks manual actions, not new SERP appearances.
| Schema type | Use only when | Is it a FAQ replacement? |
|---|---|---|
| Product | The page describes a specific product with name, image, price, and availability | No. Describes a different entity type entirely. |
| Review | The page contains a critical evaluation of a product, service, or media item by an identifiable author | No. Requires a genuine review, not Q&A content. |
| Recipe | The page contains a specific recipe with ingredients, instructions, and cook time | No. Only applies to food and cooking content. |
| Event | The page describes a scheduled event with date, location, and organizer | No. Applies only to time-bounded events. |
| QAPage | The page contains community-contributed answers to a question (forum, Q&A platform) | Partial. Different entity than FAQPage. Correct when applied to community Q&A content, not brand FAQ pages. |
The Bigger Pattern
Summary: Google is simplifying its SERP and repositioning structured data as machine-readability infrastructure for AI rather than as a visual enhancement for human searchers.
Google has been systematically narrowing what earns visual SERP features. HowTo rich results were cut in 2023. FAQ visibility was restricted the same year and formally ended in 2026. The structured data types that survive are those tied to transactions and entities Google still wants to surface visually: Product, Review, Recipe, Event, and Breadcrumb.
For everything else, schema is becoming a machine-readability layer for AI systems rather than a SERP enhancement for human searchers. The work site owners do on structured data is increasingly about legibility to ChatGPT, Perplexity, and Bing rather than about earning a display feature that may not survive the next deprecation cycle. The structural divide between SEO and AEO is becoming clearer with every feature removal: what Google shows in the SERP and what AI systems retrieve are increasingly different problems requiring different strategies. For a broader view of what AEO involves beyond structured data, the entity, content, and distribution layers matter as much as the markup.
The job changed. The markup is the same. The audience is different.
Frequently Asked Questions
When did Google deprecate FAQ rich results?
Google stopped showing FAQ rich results in Search as of May 7, 2026. This followed an August 2023 restriction that had already limited FAQ rich results to authoritative health and government sites. The FAQ search appearance, rich result report, and Rich Results Test support are removed in June 2026. Search Console API support for FAQ rich results ends in August 2026.
Should I remove FAQPage schema from my site?
For most sites, no. Google explicitly stated you do not need to remove the schema. The cost of stripping it across a content library is real, and the upside of removal is zero. FAQPage markup is still parsed by Google’s crawler and may be used by other search engines. The one case where removal is justified is hidden or stale markup that does not correspond to visible on-page content, which can create content parity issues.
Was this deprecation a surprise?
No. Google first restricted FAQ rich results to authoritative health and government sites in August 2023, and impressions for non-authority sites collapsed to near zero almost immediately. The May 2026 announcement is the formal closure of a feature that had been functionally absent for most sites for almost three years.
Does FAQ schema still help with AI search visibility?
The honest answer is: possibly, but the evidence is mixed. Microsoft’s Fabrice Canel stated in March 2025 that structured data helps Copilot understand content. A December 2024 study by Search/Atlas found no correlation between schema coverage and AI citation rates. For ChatGPT, Perplexity, and Gemini, the claim that FAQ schema increases citation rates is hypothesis-level with no published controlled study supporting it. The practical case for retaining FAQ schema does not require overstating this evidence: the markup makes Q&A structure machine-readable, removing it has no benefit, and the potential upside still exists even if unproven.
What happens to my Search Console FAQ reports?
The FAQ rich result report and Rich Results Test support are removed in June 2026. Search Console API support for FAQ rich results ends in August 2026. Before June, export performance data for pages with FAQ schema so you have a record of pre-deprecation CTR and impressions. If you have automated API pipelines filtering on FAQ search appearance, identify and update those calls before August to prevent null returns or errors.
What is the difference between FAQPage and QAPage schema?
FAQPage applies when one author provides both questions and answers, as in a brand help center or editorial FAQ list. QAPage applies when a question has been answered by multiple community members, such as a forum thread or a Stack Overflow page. They are not interchangeable. FAQPage markup on community content, or QAPage markup on brand FAQ pages, is a schema misapplication that provides no benefit and may confuse parsers.
Which structured data types still earn rich results in Google?
Product, Review, Recipe, and Event schema continue to render as rich results in Google Search. These are not replacements for FAQ schema. Each type has specific eligibility requirements and describes a different entity. Adding Product or Review markup to a FAQ page to compensate for the FAQ deprecation is invalid markup and risks a manual action, not a new rich result.
Will this affect my organic traffic?
For most sites, the impact will be minimal. FAQ rich results have been suppressed for non-authority sites since August 2023. If your site is in the health or government vertical and was still earning FAQ rich results as of April 2026, expect a CTR drop on those pages over the following four to six weeks. For everyone else, the deprecation is administrative cleanup of a feature that had not materially contributed to organic performance for almost three years.
How do I validate FAQ schema after the Rich Results Test removes FAQ support?
Use the Schema.org Validator at validator.schema.org for syntax validation against the Schema.org specification. Use the Rich Results Test for JSON-LD structural error detection, which still works even after FAQ-specific preview support is removed. Manually confirm that every Q&A in your schema is visible on the page. Test with JavaScript disabled to confirm the content is not dynamically rendered and therefore invisible to crawlers. Check that the canonical tag on each FAQ page points to itself, not a parent URL.
Stay ahead of the AI search shift. Prompt Insider publishes weekly on AEO, AI search, and the playbook for staying visible inside AI answers. The brand citations platform breakdown is a good next read on how each engine actually decides what to cite.
About the author
Kai Williams
Kai Williams has been in marketing for years, with a long background in SEO before AEO had a name. He stepped into Answer Engine Optimization the moment AI started reshaping how people search, and has been tracking the shift ever since. At Prompt Insider, he covers AEO, AI marketing, and the future of search, breaking down what is changing and what brands need to do about it.
