Get a free consultation
Website Design

FAQ Rich Results Are Gone: What to Do With Your FAQ Schema in 2026

By Sigmato Editorial TeamUpdated 15 Nov 20266 min read

Modern workspace featuring a laptop, notebook, and pen on a wooden desk with a blurred whiteboard in the background.

Key takeaways

  • FAQ rich results, the expandable question-and-answer dropdowns under a search listing, no longer appear in Google Search as of 7 May 2026. Google removed its FAQ documentation on 15 June 2026.
  • This is a display change, not a penalty. Google said the same about the 2023 cut-back: it was not a ranking change.
  • Your visible FAQ section is still worth having. Real people still have these questions, and clear question-and-answer content is useful on the page.
  • Whether to keep the FAQPage markup is a small decision. Leaving it is harmless; removing it saves a little code. Do not spend a week on it either way.
  • Put the effort into structured data that still earns visible results, and into answers written for humans.
Modern workspace featuring a laptop, notebook, and pen on a wooden desk with a blurred whiteboard in the background.

What exactly happened to FAQ rich results?

For years, adding FAQPage structured data could make your search listing taller by adding collapsible questions directly in the results. It was one of the easiest rich results to win, which is also why it became crowded.

Date Change
8 August 2023 Google announced it was reducing FAQ rich results so they were shown only for well-known, authoritative government and health websites, and limiting How-To rich results.
13 September 2023 Google confirmed it had stopped showing How-To rich results on desktop too, so the type was effectively retired.
7 May 2026 FAQ rich results stopped appearing in Google Search. Google’s documentation added a deprecation notice the next day.
15 June 2026 Google removed the FAQ rich result documentation, noting the feature is no longer shown in Search results.

Third-party coverage also reports that the related Search Console reports and tool support were being removed through mid-2026. Check your own Search Console for the exact state of your account, because the timing of tooling changes can vary.

Did this affect rankings?

No. Rich results change how a listing looks, not where it ranks. In its 2023 announcement Google said the FAQ and How-To change was not a ranking change. The practical effect of the 2026 retirement is that listings which used to carry dropdowns now look like ordinary listings. If you saw a dip in clicks, it is more likely to be the loss of that extra visual space than a drop in position, so compare position and click-through rate separately in Search Console.

Should you delete your FAQPage markup?

Here is a decision guide. None of these options hurts you.

Option When it makes sense
Leave it in place Your CMS or SEO plugin generates it automatically and there is no cost. Google’s 2023 guidance said unused markup does no harm; it simply has no visible effect.
Remove it You want a leaner page, or the markup is hand-maintained and often out of sync with the visible text. Remember the rule that markup must match what visitors can see.
Keep it and treat it as a tidy data layer You like having your questions and answers machine-readable. FAQPage is still a valid schema.org type, but do not expect any Google rich result from it.

Our own approach on this site is the middle one: we keep the visible FAQ sections on our pages and the existing markup stays in place, but we no longer expect any rich result from it, and we do not measure our FAQs by that.

Is a visible FAQ section still worth writing?

Yes, if it is good. A well-built FAQ does three jobs that have nothing to do with a rich result:

  1. It answers the objections that stop a sale. Price, timeline, ownership, support, risk. People read these before they contact you.
  2. It covers long-tail questions that do not deserve a page of their own but do appear in searches, in “people also ask” style results, and in conversations with AI assistants.
  3. It reduces support load because visitors get the answer without writing to you.

Google’s own guidance on its generative search features is blunt about this: there is no special markup or file you need, and you should not rewrite content just for AI systems. What helps is clear, useful content organised into sensible sections, which is exactly what a good FAQ is.

How to write FAQs that earn their place

  • Start from real questions. Use your sales emails, support tickets, call notes and Search Console queries. Do not invent questions to hold keywords.
  • Answer first, then explain. Put the direct answer in the opening sentence and add detail after it. A visitor who reads only the first line should still be helped.
  • One question per heading. Use a subheading for each question so it can be linked to and scanned.
  • Keep answers short enough to read in a moment, usually two to five sentences, and link to the longer page when there is one.
  • Be honest about limits. “It depends, and here is what it depends on” beats a confident answer that is wrong.
  • Do not repeat the same answer across many pages. Pick the best home for it and link to it.
  • Keep them current. Review your FAQs when prices, policies or processes change.

Structured data that still earns visible results

The lesson of the last three years is that Google keeps trimming rich result types that are rarely useful. The ones that remain are the ones tied to clear user value. Before you invest in any markup, check Google’s current Search Gallery to see what is still supported, and test your page in the Rich Results Test. Common types that remain documented there include Product, Article, Breadcrumb, Organization, Local business, Event, Video and Review snippets, subject to eligibility rules. Always confirm in the gallery, because the list changes.

A sensible rule: add markup because it describes your page accurately and helps systems understand it, and judge it by whether it is valid and honest, not by whether it unlocks a visual effect today.

A 15-minute clean-up checklist

  1. Open Search Console and note the date FAQ items stopped appearing in your Performance reports, so you can explain the click-through change.
  2. Decide whether to keep or remove FAQ markup (see the table above) and apply it consistently across your templates.
  3. Read each FAQ block on your top ten pages. Delete questions nobody asks and tighten the first sentence of each answer.
  4. Check that the markup, if you keep it, matches the visible text exactly.
  5. Pick one page where a missing answer is costing you enquiries and add three honest questions.

What this tells us about SEO in general

FAQ markup was a shortcut: a technical trick that made a listing look bigger. Shortcuts of that kind are exactly the things search engines retire, because they are easy to overuse. The durable work is the unglamorous part: be clear, be specific, be honest about trade-offs, and make the page fast and easy to use. Our website redesign SEO checklist and our guide to Core Web Vitals are where we would spend the time you would otherwise spend on schema tweaks. If you would like a second pair of eyes on your content and technical setup, you can get in touch.

Frequently asked questions

Are FAQ rich results gone for every website?

Yes. Google says FAQ rich results stopped appearing in Search on 7 May 2026, and it removed the documentation on 15 June 2026. Before that, since August 2023, they were shown only for well-known government and health sites.

Is FAQPage structured data now invalid?

No. FAQPage is still a valid schema.org type. It just no longer produces a Google rich result. Whether to keep it is a housekeeping choice, and Google has said that unused markup does no harm.

Will my rankings drop because the FAQ dropdowns disappeared?

Rankings are not affected by this change. What can change is click-through rate, because listings that used to show dropdowns take up less space. Compare average position and click-through rate separately in Search Console.

Should I still publish FAQ sections?

Yes, when the questions are real. A good FAQ answers buying objections, covers long-tail questions and cuts support emails. It just should not be written to win a rich result.

What structured data should I use instead?

Use types that accurately describe your page and that Google still documents, such as Product, Article, Breadcrumb, Organization, Local business, Event or Video. Check the Search Gallery and the Rich Results Test before investing.

Sources and further reading

Sigmato Editorial Team

Written by

Sigmato Editorial Team

The Sigmato Editorial Team is made up of software engineers, UI/UX designers and AI specialists at Sigmato Solutions Pvt Ltd in Bengaluru, India and the UK. We write practical guides on web, mobile, cloud and AI development, drawing on the products we design and build for startups and enterprises worldwide.

Last updated 15 November 2026 · Talk to our team