Do FAQ Pages Still Help in 2026? What Changed After Google Dropped FAQ Results

The short answer

Yes, FAQ pages still help in 2026, but not for the reason they used to. Google stopped showing FAQ rich results entirely on May 7, 2026, so FAQPage markup no longer wins extra space in search results. Well-written FAQ content still answers real questions in plain text, which is what both searchers and AI systems quote, and it doubles as source material for your chatbot or support team.

What happened to FAQ rich results

FAQ rich results were the expandable questions that once appeared under many search listings. Google wound them down in two steps.

• August 8, 2023: Google announced that FAQ rich results would only be shown for well-known, authoritative government and health websites.
• May 7, 2026: According to Google's documentation changelog, the feature stopped appearing in Google Search altogether. A deprecation notice went up on May 8.
• June 15, 2026: Google removed the FAQ rich result documentation, noting the feature is no longer shown.

So, as of October 2026, there is no search-results benefit from FAQPage structured data on Google. Google said back in 2023 that unused structured data causes no problems, so you do not need to rush to remove existing markup.

Do FAQ pages help with AI answers?

Here it helps to separate the markup from the content.

The markup: Google's guide to generative AI features, added May 15, 2026, states that structured data is not required for generative AI search and that no special schema.org markup is needed. Its separate AI features page says the same: pages need to be indexed and snippet-eligible, with no additional requirements. Other platforms have not published comparable guidance on FAQ markup, so any claim that FAQ schema boosts ChatGPT or Perplexity citations is unverified.

The content: This is where FAQ pages still earn their keep. AI assistants answer questions; a page that states a question in your customers' words and answers it directly in the first sentence is easy to understand and quote. Google's guide also says you do not need to chop content into tiny chunks for AI, and that pages full of generic, commodity content add little. That is a warning against the kind of FAQ page built from twenty filler questions.

For which structured data is still worth adding, see schema markup for AI search.

What makes FAQ pages useful in 2026

Weak FAQ page	Useful FAQ content
Twenty generic questions written for keywords	Questions taken from real emails, calls and sales objections
Vague answers ("It depends, contact us")	A direct first sentence, then the conditions that change it
One giant page for the whole business	Short Q&A sections on the service or product page they relate to, plus a hub
Answers hidden in accordions loaded by script	Answers in the HTML, visible or expandable without extra requests
Written once, never updated	Reviewed when prices, policies or rules change

Where to find the right questions

• Your inbox and call notes: the questions people ask before they buy.
• Search Console queries phrased as questions, filtered to your service pages.
• "People also ask" boxes and the follow-up questions AI Mode suggests for your topics.
• Reddit and industry forums, which show how customers phrase worries in their own words. Map each to the right search intent.

FAQ page, guide or service page: which format fits?

Not every question deserves a FAQ entry. A simple rule helps decide where an answer should live.

• One-line facts (Do you work weekends? Is parking free? Do you ship to Quebec?) suit a FAQ section on the relevant page. They are quick to scan and easy for any system to quote.
• Questions that need a process (How do I prepare for a roof inspection? What happens after I file a claim?) deserve their own short guide with steps. Squeezing them into a two-sentence FAQ answer leaves out what people need.
• Questions about price, scope or fit belong on the service page itself, near the call to action. These are the questions that decide whether someone enquires, so do not hide them at the bottom of a separate FAQ.
• Comparison questions (Option A or option B?) usually work best as a dedicated comparison page with a table.

A central FAQ hub is still useful for navigation, but it should link out to these deeper pages rather than try to hold everything. That structure also helps internal linking, because each answer can point to the page that covers it in full.

How to write an answer that gets quoted

Write the first sentence so it would make sense if it were the only thing someone read. "Most kitchen renovations in the GTA take six to ten weeks once permits are approved" works on its own; "Great question, it really depends" does not. Follow with the factors that change the answer, then a link to the detail. Use the same terms your customers use, and include specific numbers, dates or conditions wherever you can stand behind them.

The hidden benefit: FAQ content powers your own AI

A clean, current set of questions and answers is also the best raw material for a website chatbot, an AI receptionist or a staff help desk. Systems that answer from your own documents, explained in what RAG is, are only as good as the content you give them. A FAQ library that marketing maintains for the website and support reuses for the bot means one source of truth instead of two drifting versions.

If your bot gives wrong answers today, the fix often starts here; see AI customer service without the rage.

Checklist

• Keep existing FAQPage markup if it is accurate; do not add it expecting a rich result.
• Rewrite answers so the first sentence fully answers the question.
• Move service-specific questions onto the pages they belong to.
• Source every question from real customer contact or search data.
• Set a quarterly review date and an owner.

Frequently asked questions

Should I remove FAQ schema from my website?

There is no need to. Google has said unused structured data does no harm. Remove it only if it no longer matches the visible content, since markup should always reflect what is on the page.

Does Google penalise FAQ pages?

No. There is no penalty for FAQ content. Thin, mass-produced pages of any kind can fall foul of Google's spam policies, but a genuine FAQ is ordinary helpful content.

How many questions should a FAQ section have?

There is no ideal number. Answer the questions customers actually ask about that page, often three to eight, rather than padding to a target.

Sources

1. Changes to HowTo and FAQ rich results — Google Search Central Blog, August 8, 2023
2. Latest Google Search Documentation Updates — Google Search Central
3. Optimizing your website for generative AI features on Google Search — Google Search Central, updated July 10, 2026
4. AI features and your website — Google Search Central

How Flowmatix can help

We put this into practice for businesses in Toronto and around the world through our SEO & Performance Optimization, content & video production, ai agents & ai solutions services. Want to know what it would take for your business? Get a personalised quote in about 3 minutes.