Digital Agency

Google Retired FAQ Rich Results: What to Do With Your FAQs Now

Illustration of a search result with its FAQ dropdowns removed

For years, adding FAQ schema was one of the easiest ways to make a search result bigger: a few expandable questions under your listing. That era is over. Google stopped showing FAQ rich results in Search on 7 May 2026, and has since been removing the related reports and testing tools in stages.

If you have FAQ sections across your website, you do not need to panic or delete them. You do need to change why you write them.

What changed

  • May 2026: FAQ rich results stopped appearing in Google Search for all sites.
  • June 2026: the FAQ search appearance filter, the FAQ rich results report and Rich Results Test validation for FAQs were removed from Search Console, according to coverage of Google's documentation changes.
  • August 2026: API support for FAQ data was removed from Search Console.

This was the end of a long decline. Back in August 2023, Google had already limited FAQ rich results mostly to well-known government and health websites, so most businesses had not seen them for a while.

What did not change

  • FAQPage is still valid Schema.org markup. It will not cause errors or penalties.
  • Questions and answers are still useful content. Clear answers to real questions help visitors decide and help search systems understand your page.
  • AI search still reads your page. Some SEOs suggest structured Q&A helps AI systems extract answers, but there is no confirmed evidence from Google that FAQ markup earns citations in AI Overviews or AI Mode. Treat that as unproven.

Should you keep FAQPage schema?

For most sites: keep it if it is accurate and already in place, but do not add it expecting a Google feature. Removing working markup costs time and gains nothing; adding new markup purely for a SERP feature that no longer exists is wasted effort. Spend that time on the content instead.

If you run a genuine question-and-answer community where users submit answers, QAPage markup is the more appropriate type. A single business answering its own questions does not qualify.

How to write FAQs that still earn their place

Many FAQ sections were written for the rich result, not for people: short, repetitive and stuffed with keywords. Now that the visual reward is gone, the only reason to have an FAQ is that it helps a reader. Good FAQs:

  • Come from real enquiries. Use the questions your sales team, WhatsApp inbox and email actually receive.
  • Answer in the first sentence. Then add detail. "Yes, we deliver across Pakistan. Orders in Lahore usually arrive in two working days..."
  • Handle objections. Price ranges, timelines, what is included, what happens if something goes wrong.
  • Link to the detail. A good answer often points to the service page, case study or policy that proves it.
  • Stay specific to the page. The same ten questions copied onto every service page add nothing.

Where to put the effort instead

  1. Answer questions inside the main content with clear H2 or H3 headings, so they work for readers, featured snippets and AI summaries alike.
  2. Use structured data that still powers features where it genuinely applies: Organization, BreadcrumbList, Article, Product and Review where eligible, and LocalBusiness for real local businesses.
  3. Improve titles and descriptions. Without a bigger listing, the click depends on a clear, compelling title and description.
  4. Check your click-through rate. Pages that relied on FAQ rich results may have lost clicks in May 2026. Compare CTR before and after in Search Console and rewrite the snippets of the worst affected pages.

A note on older advice

Plenty of guides, including some on our own blog, recommended FAQ schema as a quick win for rich results. For example, our earlier article on using FAQ schema for featured snippets was written before this change. The writing advice in it still holds; the rich result benefit no longer does.

Next steps

Review the pages that used FAQ markup, check their click-through rate since May, and rewrite the FAQs that were written for a search feature rather than a customer. If you would like help auditing your structured data and snippets, talk to our SEO team or our web development team.

Sources