FAQ Sections for AI Search: Format and Placement

A good FAQ section answers the real follow-up questions buyers ask, in short, self-contained answers that AI engines can quote. Choose questions from search data, sales calls and AI prompts. Keep each answer to 2–4 sentences, put the section after the main content, and keep answers visible. FAQPage schema is optional: Google stopped showing FAQ rich results on 7 May 2026.

Why do FAQs matter for AI answers?

AI engines retrieve and combine passages that answer a question (arXiv). An FAQ is a set of question-answer passages that fit this pattern well. Users also ask AI assistants follow-up questions, and FAQs often match those directly.

How do you choose the questions?

Pick 4–8 questions per page. Each should be distinct and relevant to the page topic. Word questions the way buyers say them, not the way your team describes the product internally; buyers ask "Can I cancel anytime?", not "What is the contract flexibility policy?"

How should answers be formatted?

• Lead with the answer in the first sentence: "Yes", "No", a number or a definition.
• 2–4 sentences, around 30–80 words.
• Specific: prices, time frames, limits, conditions.
• Self-contained: repeat the subject instead of "it".
• Sourced where a fact needs support.

Illustrative.

Where should the FAQ go?

Keep answers visible on the page. Content hidden behind interactions that require scripts may be harder for some crawlers to read; check how your pages render (Google).

Is FAQPage schema worth it?

In August 2023, Google limited FAQ rich results to well-known, authoritative government and health websites (Google). From 7 May 2026, it stopped showing them in Search at all, and in June 2026 it removed the FAQ report, Rich Results Test support and documentation (Google Search Central). Google also said that unused structured data doesn't cause problems and there's no need to remove it proactively.

So:

• Don't expect FAQ rich results in Google; the feature is retired.
• Keep or add schema if it's easy; it describes the content and costs little.
• Don't rely on schema for AI visibility. Google says no special markup is needed for AI features (Google).
• Make sure the schema matches visible content exactly.

What does FAQPage markup look like?

Illustrative. If you use it, the markup should mirror the visible questions and answers:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Does Example CRM offer annual discounts?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Yes. Annual billing saves 20% compared with monthly billing on all plans."
    }
  }]
}

Which FAQ types work best by page?

Should FAQ answers link elsewhere?

Yes, where it helps. Give the full answer in the FAQ first, then link to a deeper page for detail. An answer that only says "see our docs" can't be quoted on its own and won't help a reader in a hurry.

How many FAQs are too many?

When answers start repeating or questions drift off-topic, stop. A long list of thin questions dilutes the page. Move broader questions to a dedicated FAQ or a separate guide.

How do you keep FAQs accurate?

• Assign an owner for each page's FAQ.
• Review it when pricing, features or policies change.
• Check AI answers about those facts monthly.
• Show a "last reviewed" date on the page.

A quick example

Illustrative. A SaaS pricing page has no FAQ. Sales says the top questions are about annual discounts, seat limits and cancellations. The team adds six FAQs with specific answers. In later scans, AI answers to "Does [brand] offer annual discounts?" quote the new answer instead of an old forum post.

What mistakes should you avoid?

• Vague, marketing-style answers
• Questions nobody asks
• Answers that contradict the main content
• Hidden answers that don't render without scripts
• Schema that doesn't match visible text
• Expecting FAQ rich results in Google after May 2026
• Copying the same FAQ block onto dozens of pages

Checklist

• [ ] 4–8 real questions per page, from data
• [ ] Each answer starts with the direct answer
• [ ] Answers 30–80 words and specific
• [ ] Section placed after main content and visible
• [ ] Schema (optional) matches visible content
• [ ] Owner and review date set

Related

• How to write answer-first content
• How to write a glossary AI engines use

Sources

• Google Search Central Blog, Changes to HowTo and FAQ rich results, August 2023
• Google Search Central, AI features and your website
• Google Search Central, Understand the JavaScript SEO basics
• Google Search Console Help, Performance report
• Lewis et al., Retrieval-Augmented Generation, 2020
• Google Search Central, Documentation updates, accessed 30 Oct 2026