Google has ended FAQ rich results in Search, meaning FAQPage schema no longer creates expandable Q&A listings. The markup can stay, but the visible SERP feature and related reporting are being phased out.
Highlights:
- FAQ rich results are removed from Google Search.
- FAQ schema no longer creates visible dropdowns.
- The phase-out began already in 2023.
- Search Console, Rich Results Test, and API support are being removed.
What Google Changed
Google’s update affects both the visible search result and the reporting systems connected to FAQ rich results. The most important distinction is between the following:
- FAQ content
- FAQ schema
- FAQ rich results
FAQ content is the actual question-and-answer content on a page. FAQ schema is the structured data markup that labels that content for search engines. The rich results were the visible SERP presentation that Google could show based on that markup.
Google has removed the presentation layer. The structured data can still exist, and the content can still help users, but the rich result display is no longer supported.
FAQ Rich Results No Longer Appear in Google Search
As of May 7, 2026, FAQ rich results stopped appearing in Google’s SERP. This means users will no longer see expandable FAQ dropdowns below organic search listings as a result of FAQ structured data.
For most websites, the immediate impact may be limited because Google had already restricted the rich results heavily in 2023. Many commercial, affiliate, ecommerce, SaaS, and publisher sites had already lost eligibility or visibility for these results before this final removal.
Still, the update matters because it officially ends FAQ rich results as a Google Search feature. SEOs can no longer rely on FAQPage markup to earn extra SERP space, improve listing size, or create a more prominent organic result through FAQ dropdowns.
FAQ Reporting Is Being Removed From Search Console
Google is also removing FAQ-related reporting from Google Search Console. This includes the FAQ search appearance filter and the FAQ rich result report.
That matters for SEO reporting because some teams used Search Console to track impressions, clicks, and performance for this. Once the reporting disappears, those views will no longer be available in the same way.
Teams performing search engine optimization should update any reporting workflows that still include FAQ rich result performance. If dashboards, monthly reports, or client templates refer to rich visibility, those sections should be revised so they do not rely on a feature Google no longer supports.
FAQ Support Is Being Removed From the Rich Results Test
Google will also remove FAQ support from the Rich Results Test in June 2026. The Rich Results Test has been used to validate whether structured data is eligible for Google rich result features.
Once FAQ support is removed, the tool will no longer validate FAQ markup as a supported rich result type for Google Search. This does not necessarily mean the schema is invalid as Schema.org markup. It means Google no longer supports FAQPage markup for the purpose of generating FAQ rich results.
This is an important difference. A page can still contain structured FAQ markup, but SEOs should not expect Google’s rich result tools to treat it as an active rich result opportunity.
Search Console API Support Ends Later
Google is giving teams more time to adjust API workflows. Support for FAQ rich result data in the Search Console API will be removed in August 2026.
This matters for teams that pull structured data performance into custom dashboards. We are talking about for example:
- BigQuery exports
- Looker Studio reports
- Internal SEO tools
- Client reporting systems
If those systems still request data for such rich results, they may need to be updated before API support ends.
The practical action is simple: identify whether your reporting setup depends on FAQ rich result data, export any historical data you want to keep, and remove or replace those API calls before support ends.
Timeline: How Google Phased Out FAQ Rich Results
The removal of did not happen all at once. Google had been moving away from broad FAQ rich result visibility for several years.
FAQ rich results launched as a way for pages with structured question-and-answer content to earn a larger, more interactive search listing. Over time, the feature became widely used by SEOs, sometimes as a way to take up more space in the SERP rather than to improve the actual page experience.
Google later restricted the feature and eventually removed support completely.
2023: Google Reduced FAQ Rich Results
In August 2023, Google significantly reduced the visibility of such rich results. Instead of showing them broadly across many types of websites, Google limited them mainly to well-known, authoritative government and health websites.
That change meant most websites no longer had a realistic chance of showing of rich results for FAQ, even if they had valid FAQPage markup. For many businesses, FAQ structured data had already stopped creating visible search enhancements long before the 2026 removal.
This 2023 restriction was the first major step in the phase-out. It turned FAQ rich results from a common SEO tactic into a feature available only in narrow cases.
May 2026: FAQ Rich Results Stopped Showing
On May 7, 2026, FAQ rich results stopped appearing in Google Search. This was the point where Google ended the visible SERP feature.
From that date forward, FAQPage markup no longer generated FAQ dropdowns in the SERP. The feature was no longer available even for the limited categories that had remained eligible after the 2023 restriction.
For SEOs, this marked the end of FAQ schema as a visibility shortcut in Google Search.
June 2026: Search Console Features Begin Going Away
In June 2026, Google began removing the Search Console and testing features connected to FAQ rich results. This includes the following:
- FAQ search appearance
- Its result report
- Support in the Rich Results Test
This stage affects measurement and validation. Even if a site still contains FAQ structured data, Google will no longer provide the same dedicated rich result reporting or testing support.
SEO teams should treat this as a reporting cleanup period. Any dashboards, audits, or structured data checks that still focus on FAQ rich result eligibility should be updated.
August 2026: Search Console API Support Ends
In August 2026, Google will remove Search Console API support for FAQ rich result data. This gives developers and SEO teams time to adjust automated reporting systems.
The API change is especially relevant for larger websites, agencies, enterprise SEO teams, and companies with custom analytics setups. If FAQ rich result data is being pulled into automated reports, those workflows should be reviewed before the data source disappears.
“For many businesses, FAQ structured data had already stopped creating
visible search enhancements long before the 2026 removal.”
After this point, they will not only be gone from Search, but also removed from the supporting Search Console reporting ecosystem.
Why it Matters for SEO
Google drops FAQ rich results at a time when many SEO teams are already rethinking the role of structured data, rich results, and AI search visibility.
The change matters because they were once used to improve SERP visibility, increase listing size, and potentially improve click-through rates. Their removal reduces the value of FAQ schema as a direct search appearance tactic.
But it does not remove the value of helpful FAQ content. The SEO focus needs to shift from “How do we get a rich result?” to “How do we make this content clearer, more useful, and easier for both people and systems to understand?”
Less SERP Visibility for FAQ-Heavy Pages
Pages that previously earned FAQ rich results may lose visual space in the SERP. Without expandable questions beneath the listing, those pages may appear more like standard organic results.
This can affect click-through rate if the FAQ rich result previously made the listing more noticeable or helped users identify the page as relevant. However, for most sites, the impact may be smaller because their visibility had already been limited since 2023.
The main SEO takeaway is that FAQ-heavy pages can no longer depend on FAQ dropdowns for extra visibility. Any performance gains must now come from:
- Stronger titles
- Meta descriptions
- Content quality
- Topical relevance
- Internal linking
- Overall search intent satisfaction
Reporting Gaps in Google Search Console
The removal of FAQ reporting creates a measurement gap for teams that tracked FAQ rich result performance separately.
Once Google removes the FAQ search appearance and rich result report, SEOs will no longer be able to isolate FAQ rich result performance in the same way. Historical data may still be useful, but ongoing reporting will need to shift toward broader page-level performance metrics.
This means teams should monitor affected pages by looking at:
- Clicks
- Impressions
- Average position
- Click-through rate
- Changes in organic traffic
Instead of tracking FAQ rich result appearance, the focus should move to whether the pages continue to satisfy search intent and maintain visibility.
Lower Value From FAQ Schema as a Standalone SEO Tactic
FAQ schema no longer has the same tactical value it once had. In the past, some SEOs added FAQPage markup primarily to win extra SERP real estate. That reason is now gone for Google Search.
This does not mean all FAQ schema should be removed. It means it should be treated as descriptive markup, not as a direct visibility lever.
If a page contains a real FAQ section, markup may still describe the content accurately. But adding FAQ schema to chase a Google rich result no longer makes sense because the rich result feature no longer exists.
Another Sign Google Is Simplifying Rich Results
The removal of FAQ rich results fits a broader pattern in Google Search. Google has reduced or removed several rich result types over time, including restrictions around HowTo rich results and other structured data search appearances.
This suggests that Google is being more selective about which structured data types produce visible search enhancements. The direction is clear: it may still help search engines understand content, but not every type of markup will result in extra SERP display features.
For SEOs, this means this data should be part of a broader content and technical SEO strategy. It should not be treated as a guaranteed path to better search visibility.
Should You Remove FAQ Schema From Your Website?
In most cases, there is no urgent need to remove FAQ schema from your website. Google has indicated that unused structured data does not cause problems for Search, and FAQPage remains a valid Schema.org type.
The better question is not simply whether the markup should stay or go. The better question is whether the FAQ content itself is useful, accurate, and worth keeping.
If the FAQ section helps users, answers real questions, and supports the topic of the page, it can still be valuable. If it exists only because someone once wanted a rich result, it may be time to improve or remove it.
When It Is Fine to Leave Existing FAQ Schema in Place
It is generally fine to leave existing FAQ schema in place when the page contains a genuine FAQ section and the markup accurately reflects the visible content.
If the questions and answers are helpful to users, there is no immediate SEO reason to remove the schema. Other search engines may still process structured data, and the markup can still describe the content in a machine-readable way.
“The main SEO takeaway is that FAQ-heavy pages can no longer
depend on FAQ dropdowns for extra visibility.”
Leaving existing schema in place can also be the most practical option for large websites. Removing it across thousands of pages may not be worth the development time if the markup is valid and does not create errors.
When FAQ Schema Is No Longer Worth Adding
FAQ schema is no longer worth adding as a standalone optimization tactic for Google rich results. If the only reason for adding FAQPage markup is to earn expandable FAQ dropdowns in Google Search, that opportunity is gone.
However, if a page already includes high-quality FAQ content, adding structured data may still be acceptable as a way to describe the content. The key is to avoid treating the markup as the main strategy.
The priority should be the content itself: useful questions, clear answers, real customer language, and relevance to the page topic.
When You Should Clean Up or Remove Poor FAQ Markup
You should clean up or remove FAQ markup when it no longer matches the visible content on the page, marks up content that does not exist, or supports a low-quality FAQ section.
FAQ sections that are thin, generic, keyword-stuffed, or disconnected from user intent should be improved. If the content does not help visitors, the schema will not make it valuable.
This update is a good reason to audit FAQ sections across your site. The loss of rich results removes the cosmetic benefit, so the content now has to stand on its own.
Why FAQ Content Still Matters Without Rich Results
FAQ rich results are gone, but FAQ content is not dead. In many cases, good FAQ content is still beneficial for aspects such as:
- SEO
- User experience
- Topical depth
- AI search visibility
The important shift is that the value now comes from the content, not the search appearance. A strong FAQ section can still answer long-tail questions, reduce friction, support conversions, and make a page more complete.
FAQ content should be written for real users first. When it is clear, specific, and directly connected to the page topic, it can still help both people and search systems understand the value of the page.
FAQ Content Captures Long-Tail Search Intent
FAQ content is one of the most efficient ways to capture long-tail search intent. Each question can target a specific concern, comparison, objection, or informational need.
People often search in question form. They want to know how something works, whether it applies to them, what has changed, what they should do next, or whether a specific action is necessary. FAQ sections can answer these micro-intents directly.
Good sources for FAQ questions can be for example:
- People Also Ask results
- Autocomplete suggestions
- Customer support tickets
- Sales calls
- Internal site search data
- Reddit discussions
- Real customer conversations
The goal is not to add generic questions. The goal is to answer the questions your audience actually asks.
Question-and-Answer Formatting Supports AI Search Visibility
AI search systems and answer engines often work well with clearly structured content. Question-and-answer formatting mirrors the way users ask questions and the way AI systems generate responses.
This does not mean FAQPage schema is required for AI visibility. The stronger signal is often the clarity of the content itself. A direct question followed by a concise, useful answer can be easier for AI systems to interpret and cite.
For SEO teams, this means FAQ content can still play a role in AI search strategy. The focus should be on clear answers, strong topical context, and trustworthy information rather than markup alone.
FAQs Improve Topical Depth and Relevance
A strong FAQ section can help a page cover a topic more completely. It allows the page to address related subtopics, edge cases, objections, and follow-up questions without disrupting the main flow of the article.
This can improve topical depth. A page that explains the main topic and also answers the natural questions around it may be more useful than a page that only covers the surface-level explanation.
For a topic like Google dropping FAQ rich results, relevant FAQ-style content might address whether schema should be removed, what happens in Search Console, whether traffic will decline, and whether FAQ content still matters for AI search.
FAQs Help Users Make Faster Decisions
FAQ sections improve user experience by reducing uncertainty. A visitor may not want to read an entire article to find one practical answer. A well-structured FAQ section helps them quickly understand what changed and what action they should take.
For commercial pages, FAQs can answer objections before a user contacts sales, books a demo, or makes a purchase. For informational pages, FAQs can clarify confusing details and make the content easier to use.
Even without rich results, this user experience value remains important.
FAQs Can Support Internal Linking and Conversion Paths
FAQ content can also support internal linking and conversion paths. A question about reporting can link to an SEO dashboard guide. A question about schema can link to a structured data audit service. A question about AI search visibility can link to a related AI SEO resource.
This makes FAQ sections useful beyond search visibility. They can guide users to the next helpful resource and support the broader structure of a website.
“The stronger signal is often the clarity of the content itself.”
The key is to avoid forced links. Internal links should be relevant to the question and useful to the reader.
What SEOs Should Do After Google Drops FAQ Rich Results
After Google drops FAQ rich results, SEOs should shift from markup-led optimization to content-led optimization.
The update does not require panic. Most sites do not need to remove FAQ schema immediately. But it does require a change in how FAQ content is planned, measured, and justified.
Instead of asking whether a page can win such rich results, SEO teams should ask whether the FAQ section helps users, answers real questions, supports topical coverage, and improves the page.
Audit Existing FAQ Sections for Quality
Start by auditing existing FAQ sections. Look for pages where FAQs were added mainly to support schema rather than to help users.
A useful FAQ section should answer real questions in clear language. The questions should reflect how users actually search or speak. The answers should be direct, accurate, and specific.
Weak FAQ sections often include:
- Generic questions
- Vague answers
- Keyword repetition
- Content that does not match the page’s purpose
Those sections should be rewritten, consolidated, or removed.
Update SEO Reports and Dashboards
SEO reports should be updated to reflect this removal. If your reports include FAQ search appearance, FAQ rich result impressions, or FAQ rich result clicks, those sections will become outdated.
Instead, track the performance of the affected pages at the page level. Watch for changes in:
- Clicks
- Impressions
- Click-through rate
- Average position
- Organic sessions
If a page loses traffic after the removal, do not assume the cause is only the FAQ update. Compare timing, rankings, SERP changes, seasonality, and broader site performance before drawing conclusions.
Check Any Search Console API Dependencies
If your team uses the Search Console API, check whether any calls depend on FAQ rich result data. API support for FAQ rich results ends in August 2026.
This is especially important for agencies, enterprise sites, and teams using automated reporting. If dashboards pull FAQ data directly from the API, those workflows should be updated before support disappears.
It may also be worth exporting historical rich data for FAQ before it becomes unavailable, especially if you need it for year-over-year comparisons or client reporting.
Stop Treating FAQ Schema as a Visibility Shortcut
FAQ schema should no longer be treated as a visibility shortcut in Google Search. The tactic of adding FAQ markup to win extra SERP space is over.
That does not make structured data useless. It simply means it should be used to accurately describe content, not to chase a rich result that no longer exists.
The SEO value should come from helpful content, technical clarity, internal linking, strong page structure, and trust signals.
Rework FAQs Into Helpful On-Page Content
Some FAQ sections may need to be reworked. If the content is useful, make it stronger. If the questions are weak, replace them with questions users actually ask.
Strong FAQ answers usually get to the point quickly. They avoid unnecessary introductions, answer the question in the first sentence, and then add context where needed.
For best results, FAQs should be connected to the main topic of the page. They should not feel like a separate block of filler content added only for SEO.
Monitor Changes in Clicks, Impressions, and CTR
After the removal, monitor affected pages in Google Search Console. Focus on clicks, impressions, CTR, and average position.
If a page previously received FAQ rich results, CTR may change because the listing no longer takes up the same amount of space. However, changes may vary depending on the query, ranking position, page type, and whether the site had already lost FAQ visibility after the 2023 restriction.
The goal is to understand whether the page still performs well without the rich result. If performance declines, improve the page itself rather than trying to replace the lost feature with more markup.
How This Change Fits Into Google’s Bigger SERP Strategy
The removal of FAQ rich results fits into a broader pattern. Google has been reducing certain rich result opportunities while expanding its own answer-led search experiences.
This does not mean structured data has no value. It means SEOs should be careful about building strategies around specific SERP features that Google can change or remove.
A more durable strategy is to create content that is useful, clear, trustworthy, and easy to understand across traditional search, AI Overviews, chat-based search, and other discovery surfaces.
Google Is Reducing Some Traditional Rich Result Opportunities
FAQ rich results are not the only example of Google reducing rich result visibility. Google has also changed support for other rich result types over time.
This pattern suggests that Google is simplifying parts of the SERP and being more selective about when third-party content receives enhanced display features.
For SEO teams, the lesson is to avoid over-reliance on any single rich result format. Rich results can be useful when available, but they should not be the foundation of an SEO strategy.
Search Is Moving Toward AI Overviews and Answer-Led Results
Search is becoming more answer-led. AI Overviews and chat-based search experiences are changing how users discover information and how content is surfaced.
In this environment, the structure and clarity of content matter. Pages that answer specific questions clearly may be easier for AI systems to understand and reference.
FAQ content can still support this shift, but the value comes from the quality of the answers rather than the existence of FAQ rich results.
Structured Content Still Has Value Beyond Rich Snippets
Structured content still matters even when a specific rich result disappears. Clear headings, question-led sections, concise answers, schema where appropriate, internal links, and complete topical coverage can all help search engines and users understand a page.
The removal of FAQ rich results should not lead teams to abandon structure. It should lead them to use structure for the right reasons.
The goal is no longer to trigger a specific FAQ display in Google Search. The goal is to make the content more useful, more understandable, and more connected to the questions users actually ask.
Final Thoughts: FAQ Content Is Not Dead, But the SEO Playbook Has Changed
Google drops FAQ rich results, but FAQ content still has a role in SEO. The important change is that FAQ schema no longer creates visible FAQ dropdowns in Google Search.
Website owners do not need to rush to remove existing FAQ schema if it accurately describes real FAQ content. But they should stop treating FAQ markup as a shortcut to more SERP visibility.
The better approach is to audit FAQ sections for quality, update reporting systems, check API dependencies, and improve the actual content. FAQs should answer real questions, support long-tail intent, improve topical depth, and help users make decisions faster.
The SERP feature is gone. The value of useful question-and-answer content remains.
- Google Drops FAQ Rich Results From Search Results - June 6, 2026
- Google May 2026 Core Update Released - May 27, 2026
- Servicios de traducción del español al sueco para la web - May 15, 2026