How to write FAQ pages that AI assistants actually cite

In short

• Google stopped showing FAQ rich results from 7 May 2026, so an FAQ page no longer earns a special box in Search. Its value now is the answers themselves.
• AI assistants pull short, self-contained passages from pages. A question in a heading followed by a direct answer is one of the easiest formats for them to lift.
• Write questions your customers really ask, answer them in the first sentence or two, keep the text visible in the page, and back each answer with specifics.

What changed for FAQ pages

For years, many businesses added FAQ sections mainly to win extra space in Google. That reason has gone. In September 2023 Google limited FAQ rich results to well-known, authoritative government and health websites. Its Search Central changelog then recorded that the feature would no longer appear in Google Search from 7 May 2026, and in June 2026 Google removed the documentation, noting that the FAQ rich result is no longer shown.

That does not make FAQ pages pointless. It changes who they are for. The reader is now two audiences at once: the customer who wants a quick answer before calling you, and the AI tool that is assembling an answer for that same customer.

Google's guidance on AI features says there are no extra requirements or special optimisations to appear in AI Overviews or AI Mode. A page must be indexed and eligible to show with a snippet, and Google adds that these features may run several related searches across subtopics to build one response. A good FAQ page is well suited to that: it covers the side questions around a topic, each with its own clear answer.

Why AI assistants like question-and-answer formats

Microsoft published unusually direct guidance in October 2025 on how content gets into AI search answers. It explains that AI systems break pages into smaller sections and pull out concise, "snippable" pieces, sometimes a single line, sometimes several snippets from different sites combined into one answer.

On Q&A formats specifically, Microsoft says direct questions with clear answers mirror the way people search, and that assistants can often lift these pairs word for word into their responses. It lists the traits that help a passage get chosen: concise one- to two-sentence answers, structured formatting such as lists, tables and Q&A blocks, strong headings that show where an idea starts and ends, and self-contained phrasing that still makes sense out of context.

That last point is the one most FAQ pages miss. An answer like "Yes, see above" or "It depends on the package" means nothing once an AI tool lifts it out of the page.

If you are new to how AI answers are built, our guide to SEO, GEO and AEO explains how the layers fit together.

How to write each question and answer

Start from real questions. Go through enquiry emails, WhatsApp messages and sales calls, and write down the questions people actually ask, in their own words and in the language they use. A Hong Kong renovation customer may ask "Do I need building approval to remove a wall?" long before they ask about your "end-to-end solutions".

Put the question in a heading. Use the full question as an H2 or H3, not a vague label like "Process" or "Learn more". Microsoft gives the same advice: descriptive headings act like chapter titles for AI systems.

Answer in the first sentence. The opening line should answer the question on its own: yes or no, a timeframe, a range of options, a clear condition. Put the explanation, exceptions and examples after it.

Name things. Repeat the subject instead of writing "it" or "this service". Say which district, which type of project, which step. Microsoft also warns against vague words like "innovative" without specifics; anchor claims in facts a reader can check.

Keep one idea per answer. If an answer needs three separate points, it may be three questions.

Show who is answering. Google's helpful content guidance asks whether content shows clear sourcing, evidence of expertise and background about the author or site. An FAQ answered by a named team, with links to real work such as our portfolio, is more credible than an anonymous list.

Common mistakes that keep FAQs out of AI answers

• Hiding answers behind clicks. Microsoft advises against putting important answers in tabs or expandable menus, because AI systems may not render hidden content. If your design uses an accordion, make sure the full answer is in the HTML when the page loads.
• Answers only in PDFs or images. Microsoft notes that PDFs often lack the headings and metadata HTML provides, and that text inside images adds complexity. Keep core answers as plain page text.
• Writing for search engines first. Google lists warning signs such as content made mainly to attract search visits, or written to a set word count. Padding an FAQ with keyword variations of one question helps nobody.
• Mismatched markup. If you keep FAQPage structured data, which schema.org defines as a web page presenting one or more frequently asked questions, make sure every marked-up question and answer matches the visible text. Google's AI features guidance asks for structured data that matches what is on the page.
• One giant FAQ for everything. Questions about pricing structure, timelines and aftercare often work better on the service page they belong to, close to the content they explain.

A practical routine

1. Collect 20 to 30 real customer questions from the last few months, in English and Traditional Chinese.
2. Group them by service or stage of the buying journey, and place each group on the most relevant page.
3. Write each answer with the direct reply first, then detail, then a link to proof.
4. Check the page with JavaScript turned off, or view the source, to confirm every answer is present as text.
5. Every month, ask a few of those questions in ChatGPT, Gemini, Copilot and Google's AI Mode, and note whether your pages are cited.

This is the same routine we use in our AI marketing and GEO service, starting with an audit of the questions your customers ask.

Wrap-up

The FAQ rich result has gone from Google Search, but the reason FAQ pages work has not. AI assistants look for short, clear, self-contained answers to real questions, and a well-written FAQ is exactly that. Write the questions your customers ask, answer them plainly in the first line, keep the answers visible, and support them with evidence. If you would like a second pair of eyes on your current FAQ pages, contact us.