Google Removed FAQ Rich Results: Should You Keep FAQ Schema?

By Rahul S., SEO Strategist at Search Counsel Co. Last updated August 2026.

What Google removed—and what it did not

Google’s current documentation log records a three-part retirement. FAQ rich results stopped appearing in Google Search on May 7, 2026. In June, Google removed the FAQ rich-result documentation and dropped FAQ-specific support from its reporting and testing surfaces. The Search Console API documentation says support for the FAQ search appearance is scheduled for removal in August 2026.

This retirement concerns a Google Search appearance and its supporting tools. It does not erase useful question-and-answer content from the web, and it does not remove the FAQPage type from Schema.org. That distinction matters because teams often make one sitewide decision about four different things.

If you need the broader implementation model for JSON-LD, supported Google features, validation, and template deployment, use the technical schema markup guide. This article owns the narrower keep-or-remove decision after the FAQ retirement.

Should you keep or remove FAQ schema?

There is no responsible sitewide answer. Classify the page first. The best decision depends on whether the FAQ content is genuinely useful, whether FAQPage accurately describes the page, whether another system consumes that data, and whether your team can keep the content and markup synchronized.

Keep the visible FAQs and the markup

This can be reasonable when the page is genuinely an FAQ resource, every marked question and answer is visible, the information is accurate, and your organization has a documented non-Google use for the structured data. The markup should be generated from the same source as the visible answers so the two cannot drift apart.

Do not call this an AI-ranking tactic. Google’s guidance for AI features says normal SEO requirements apply and no special schema is needed. Accuracy and maintainability are the justification—not a promised citation.

Keep the visible FAQs but remove FAQPage markup

This is often the cleanest answer for articles, products, services, and location pages where a short FAQ section helps the reader but is not the page’s main purpose. The questions can stay as ordinary semantic HTML. Your SEO plugin can continue producing the page’s appropriate Article, Product, LocalBusiness, or Breadcrumb markup when the visible content qualifies.

Remove or consolidate the FAQ content and markup

Remove both when the section is generic boilerplate, repeats the main article, appears unchanged across hundreds of URLs, contains stale claims, or exists only because an old SEO checklist demanded five FAQs. Before deletion, check whether any question earns impressions, supports conversion, or belongs on a stronger dedicated page. A disciplined content refresh protects useful demand while removing noise.

Do not replace FAQPage with QAPage by default

QAPage is not a substitute for a site-authored FAQ section. Google’s Q&A documentation is for a page centered on one question where users can submit answers. A company writing its own list of common questions and official answers does not become a community Q&A page simply because the FAQ rich result disappeared.

How to audit every FAQ implementation

1. Build the inventory

Crawl the site and identify pages that output FAQPage, Question, or Answer. Record the URL, template, CMS source, canonical, indexability, visible FAQ count, and whether the markup comes from a plugin, block, theme, or custom code. Do not assume the CMS label tells you what reaches the rendered page.

2. Compare markup with visible content

Google’s general structured-data guidelines require markup to represent visible page content. Check every marked question and answer against what a user can read. Flag hidden answers, stale prices, mismatched wording, duplicate entities, and schema that remains after an editor deletes the FAQ block.

3. Decide who owns each question

A useful question should support the current page’s intent. If it needs a full explanation, move the complete answer to the correct owner and use a concise contextual link. This is ordinary on-page SEO: one page owns the main job, while supporting pages make the relationship clear.

4. Inspect the complete schema graph

Do not review the FAQ block in isolation. Check what Yoast, Rank Math, Shopify, WordPress blocks, custom templates, and tag managers output together. Multiple valid blocks can still produce conflicting URLs, authors, organizations, breadcrumbs, or duplicate questions. Remove hand-written Article or Breadcrumb JSON-LD when the site plugin already supplies it correctly.

5. Use the right validator

Google’s Rich Results Test is for structured-data types that generate supported Google rich results. For generic Schema.org validation, use the Schema Markup Validator. A syntactically valid FAQPage result does not restore Google FAQ rich-result eligibility. Validation answers “Is this data formed correctly?” It does not answer “Will Google show a retired feature?”

Fix Search Console reports and API workflows

The retirement affects measurement as much as markup. Google removed the FAQ search appearance, FAQ rich-result report, and FAQ support in the Rich Results Test in June 2026. Its Search Console API documentation says FAQ search-appearance support is scheduled for removal in August 2026. Google gives a month, not an exact day, so verify your integration instead of assuming a universal cutover hour.

Review every scheduled export, Looker Studio source, spreadsheet, alert, and API query that filters for FAQ search appearance. A zero or missing FAQ value after the retirement is not proof that rankings or total organic visibility fell. It may simply mean the dimension no longer exists.

1. Preserve the old baseline. Export historical FAQ appearance data with the date range, property, search type, country, device, and aggregation documented.
2. Remove obsolete filters. Update API jobs and dashboards so a retired dimension does not break refreshes or generate false alarms.
3. Replace the KPI. Monitor the affected pages through clicks, impressions, CTR, position, query groups, and organic conversions. The Search Console workflow should now evaluate the whole page rather than a retired FAQ appearance.
4. Annotate the timeline. Mark May 7 and the June reporting changes so stakeholders do not interpret the discontinuity as a site-caused loss.
5. Test after cleanup. Run scheduled reports manually and confirm downstream charts, formulas, alerts, and client exports still work.

What should replace the FAQ rich-result tactic?

Replace the old “add five FAQs and wait for dropdowns” routine with page-specific work. Keep questions that reveal a real decision, answer them directly, and connect them to deeper proof. Remove questions that merely restate headings or manufacture long-tail variations.

Use supported schema only when the page qualifies

An ecommerce product can use accurate Product structured data. A genuine local business can use the appropriate LocalBusiness markup. Articles and breadcrumbs can be described by the site’s SEO plugin when the graph matches the visible page. A supported type still does not guarantee a rich result, but it at least maps to a current Google feature.

Write answers that work without special markup

Use a descriptive question heading followed by a specific answer. Define the entity, give the decision rule, state the limitation, and link to the next useful step. This improves readability and gives conventional search results and AI features clear textual content to evaluate without claiming a special schema advantage. Our guide to featured snippets and AI Overviews covers the wider answer format.

Measure the page’s job

Track whether the page earns relevant impressions, clicks, qualified visits, and conversions. For support content, add task completion, fewer repeated enquiries, or assisted conversions where your analytics setup can measure them. A retired rich-result count should not remain the success metric for useful FAQ content.

A fictional example

This example is illustrative, not a SearchCounselCo client result. A service website has 120 indexable pages, and one CMS template outputs the same six FAQ questions everywhere. A crawl finds that only 18 pages contain genuinely page-specific questions. The team keeps and rewrites those 18 visible FAQ sections, removes FAQPage from the global template, consolidates the duplicated questions into one support resource, and updates its dashboard to track the affected landing pages rather than FAQ search appearance. The decision is based on relevance and maintenance—not a belief that removal will raise rankings.

Common mistakes after the FAQ retirement

• Deleting useful answers with the markup. The search display ended; the reader’s question did not.
• Keeping boilerplate for an alleged AI boost. Google documents no special schema requirement for AI Overviews or AI Mode.
• Replacing FAQPage with QAPage. The two types describe different page experiences.
• Treating Schema.org validity as Google eligibility. A vocabulary can remain valid after Google retires a feature.
• Reading missing FAQ report data as a traffic loss. Check total page and query performance before drawing a conclusion.
• Adding a second JSON-LD graph by hand. Inspect what the SEO plugin already generates before adding code.
• Leaving stale questions in templates. Markup maintenance begins with keeping the visible answer accurate.

FAQ

The one thing to do next

Export a crawl of every URL producing FAQPage, then classify each template as keep, remove markup, rewrite, or consolidate. If several plugins, themes, reports, or API jobs generate conflicting output, a technical SEO audit can turn the inventory into one developer-ready implementation plan.