FAQ for AI Search: Do FAQs Still Help Without Rich Results?

An FAQ for AI search is a section of real customer questions, each answered in two to four sentences that open with the direct answer, and it still helps after Google stopped showing FAQ rich results in May 2026. What changed is how a page looks in Google's results; each question and answer remains a passage engines can quote.

• Google's Search documentation updates say the FAQ rich result would no longer appear in Google Search starting 7 May 2026 (Google's Search documentation updates).
• On 15 June 2026, Google removed the FAQ rich result documentation, noting the feature is no longer shown in Search results.
• Bing's announcement of its AI Performance report on 10 February 2026 says clear headings, tables and FAQ sections help surface key information (Bing Webmaster Blog on AI Performance).
• Google's page on AI features, last updated 10 December 2025, says there is no special schema.org structured data to add and that structured data should match the visible text (Google on AI features and your website).

What changed when Google stopped showing FAQ rich results?

Google stopped displaying FAQ rich results, the expandable questions that once appeared under a page in its results, from 7 May 2026. FAQ content on your pages was not affected.

Google announced the change in its documentation updates on 8 May 2026, saying the feature would no longer appear in Google Search starting 7 May 2026, and on 15 June 2026 it removed the FAQ rich result documentation altogether. Neither entry says anything about the questions and answers on your pages, which are still ordinary text that Google can crawl, index and use in snippets like any other. What disappeared is the special display, not the value of the content.

For many owners the practical loss was small. Pages with FAQ markup had been getting extra space in results, and that space is gone, but the reason customers read an FAQ, to get a quick answer to a follow-up question, has not changed. The change is a good moment to look again at FAQ sections that were written mainly to win the display, because those are the ones that now earn nothing.

Why can an FAQ still help with AI engines?

An FAQ still helps because each question and answer pair is a short, self-contained passage that answers a real follow-up. That is exactly the kind of passage AI engines lift and cite.

When ChatGPT, Perplexity, Claude, Copilot or Google's AI features answer a question, they search, read candidate pages and quote the passages that answer most directly. Google says its AI Overviews and AI Mode may fan one question out into several related searches, so a customer asking about a service can trigger searches about notice, cost and what happens if something goes wrong. A good FAQ often answers precisely those smaller questions, each in a passage that makes sense on its own.

Bing is the one engine that names FAQ sections directly, listing them with clear headings and tables among the structures that help surface key information. Google's guidance is more general: its guide to generative AI search recommends a clear structure with headings and says no special formats are required (Google Search Central's guide to optimizing for generative AI search). Neither engine publishes how it picks passages, so the fair claim is that FAQs suit how engines describe their reading, not that an FAQ guarantees a citation.

Should you keep or remove FAQPage markup?

Valid FAQPage markup that matches the visible questions can stay, but it no longer produces a rich result in Google and is not needed for AI features. Do not add it expecting citations.

Google's update entries say nothing about removing FAQPage markup, and its AI features page says only that structured data should match the visible text on the page and that no special schema.org markup is needed. FAQPage is a type in the schema.org vocabulary that describes a page of questions and accepted answers, and markup that accurately describes your page does no harm. The other engines do not publish whether they read it, so its effect on ChatGPT, Perplexity, Claude or Copilot is unknown rather than proven.

The sensible rule is to keep markup only where it is accurate and maintained. If your FAQ markup lists questions that were later removed from the page, or answers that no longer match the text, fix or remove it, because mismatched structured data gives engines two versions of the truth. A minimal, accurate block for a hypothetical bakery looks like the example below, and every question and answer in it also appears word for word on the page.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "How much notice do you need for a celebration cake?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Our Leeds bakery needs 5 days' notice for a celebration cake. Larger tiered cakes need 10 days. We confirm the date when you order."
    }
  }]
}

How do you choose which FAQs to include?

Choose the follow-ups customers really ask about the page's subject, in their own words, and leave out anything that only repeats a keyword or a sales claim. Four to six good pairs usually beat twenty weak ones.

Start with what customers ask you before they buy: by phone, by email, at the counter and in reviews. A hypothetical plumber in Nairobi might hear "do you charge for a call-out?", "can you come on a Sunday?" and "do you guarantee the repair?" every week, and each of those belongs in the FAQ of the relevant service page. Questions about the subject of a different page belong on that page, so each FAQ stays specific to what the reader is already looking at.

Cut any question that exists only to repeat a phrase. "Why choose the best plumber in Nairobi?" is a sales line dressed as a question, and no customer asks it. Google warns that creating content primarily to manipulate rankings or generative AI responses breaks its scaled content abuse policy, and an FAQ stuffed with near-identical keyword questions is the kind of content that warning describes.

How long should each FAQ answer be?

Each FAQ answer should run two to four sentences, opening with the direct answer, often a yes or no, then the condition or detail that matters. Long answers belong in the page body.

The first sentence carries the answer on its own: "Yes, we cover emergency leaks on Sundays" or "A call-out costs our standard fee, which is deducted from the repair if you go ahead", written with your own real terms. The second and third sentences add the condition a careful customer needs, such as the hours, the area or what is included. A fourth sentence, if you need one, points to where more detail lives on the page.

The two to four sentence range is a working length, not a rule any engine publishes; Google says it has no preferred word count. It works because it is long enough for an answer and its key condition, and short enough to be lifted whole. If an answer needs several paragraphs, that is a sign the question deserves its own section with a question heading, or its own page, rather than a long FAQ entry.

Where should an FAQ sit on a page?

An FAQ should sit near the end of the page it supports, after the main answer and the sections that explain it. Each important page can have its own short FAQ.

The main answer always comes first. The FAQ is the last step of answer-first content: the page opens with a direct answer, the sections answer the main follow-ups, and the FAQ catches the smaller questions that did not warrant a section of their own. Putting the FAQ at the top delays the answer and turns the page into a list of fragments.

Page-level FAQs usually work better than one long FAQ page for the whole website. A question about cake notice sits naturally on the celebration cakes page, where a reader and an engine both have the context, while a central FAQ page mixing delivery, allergens, prices and opening hours answers each question with no surrounding detail. A central page can still be useful for general policies, as long as the answers there match the answers on the service pages word for word.

What should an FAQ never do?

An FAQ should never invent questions, hide its answers, duplicate the same answers across many pages or contradict the rest of the page. Each of these makes it less trustworthy to readers and engines.

Hidden answers are a common trap. Accordions that load their text only when clicked through a script can leave the answers out of what a bot reads, and Google advises making sure important content is available in textual form. An accordion is fine when the answer text is in the page's HTML from the start, so check the page source for one of your answers before relying on it.

Copying the same eight questions onto every page gives engines many identical passages and no reason to pick any one of them. Contradictions are worse: an FAQ that gives one opening time while the contact page and Google Business Profile give another forces an engine to choose, and it may choose the wrong one. Keep a single list of your key facts, update every copy on the same day, and date answers that change, such as seasonal hours.

How can you check whether your FAQ answers are quotable?

Check each FAQ answer by reading it alone: it should answer the question in its first sentence and still make sense without the heading. Then score the pages the way engines read them.

The manual test is quick. Copy one answer into a blank document without its question and ask whether a stranger would understand what it answers; if the first word is "Yes" with no subject, add the subject so the sentence stands alone. Then check that the answer appears as text in the page source rather than only inside a script.

For more pages, scan your website with the AI Search Visibility Checker, which gives each page an AI Citation Score out of 100, with 30 points for whether there is an answer to lift and 20 for evidence. It shows the question each page can win and the passage an AI engine would quote, so you can see whether your FAQ, your opening answer or something weaker is the passage engines would pick. The score predicts how quotable a page is rather than measuring whether engines quote it today.

Questions owners ask about FAQs and AI search

Should I delete my FAQ sections now that Google shows no FAQ rich results?

No. Delete only the entries no customer asks or that repeat the page, and keep the ones that answer real follow-ups. The content still helps readers and still gives engines short passages to quote.

Will FAQ markup bring back the expandable FAQ results in Google?

No. Google says the FAQ rich result no longer appears in Search from 7 May 2026, so markup cannot bring it back. Keep accurate markup if you wish, but expect no change in how the page looks in results.

How many FAQs should one page have?

Four to six is a sensible range for most business pages, chosen from the questions customers really ask. More is fine if every question is real and answered well, but a long list of weak entries buries the good ones.

Can my FAQ answers be the same on several pages?

Only for genuinely shared facts, such as a returns policy, and then the wording should match exactly. Most FAQs should be specific to the page they sit on, so each page offers engines something different.

Does Copilot use FAQs differently from Google?

Bing, which grounds Copilot's web answers, names FAQ sections among the structures that help surface key information, while Google does not mention FAQs in its AI guidance. Neither publishes exactly how it uses them, so write one FAQ that serves readers and it will serve both.

Audit your FAQ sections this month

Go through every FAQ on your website this month and keep only the questions customers really ask. Then rewrite each answer to open with the direct answer, and fix any markup that no longer matches.

Start with the pages closest to a sale. For each FAQ entry, ask whether a customer has asked that question in the last year; if not, remove it. Rewrite each remaining answer to two to four sentences, with the answer and the subject in the first sentence and your real figures in the second, and move any long answer into its own section with a question heading.

Then check the page source for the answer text and for FAQPage markup that lists old questions, and correct both. Compare your FAQ answers with your Google Business Profile and contact page, and change any fact that disagrees on the same day. Finally, run the checker and add one or two new questions a month as customers raise them, so the FAQ grows from real conversations rather than guesses.