Few page elements are as naturally suited to AI search as a good FAQ. A question, followed by a short, direct answer, is exactly the shape assistants and answer boxes look for. And yet most FAQ sections on the web are an afterthought: vague questions nobody asked, marketing answers that dodge the point, and an accordion that hides everything behind a click.
By the iSuggest.ai Team ยท Updated for 2026
This guide shows how to write a FAQ section that people find useful and that machines can use. It covers where to find real questions, how to write answers, how long they should be, how to mark them up, where to put them and what to avoid. The examples are illustrative and not drawn from any real company. We cannot promise any assistant will quote your FAQ, but a clear one removes the usual reasons it would not. For the broader picture, see what GEO is.
Why FAQs work for AI search
There are three reasons the format fits.
- It mirrors the query. People ask assistants full questions. A page that contains the same question, in similar words, with a direct answer beneath it, is an easy match.
- It is self-contained. Each question and answer pair makes sense on its own. A retrieval system pulling a passage does not need the surrounding page for context.
- It is structured. The pattern is predictable, and it can be described in structured data, which gives machines a second, explicit copy of the same information.
The wider trend adds to the value. Industry compilations report that roughly 68% of US Google queries are zero-click and that AI Overviews appear on about 48% of tracked queries (Digital Applied, SEO Sherpa). Those are dataset-specific figures, but they describe a world in which direct answers matter. A FAQ is a deliberate collection of them. We explain how fast the markup side can pay off in FAQ schema: the fastest way to earn AI citations.
Step 1: Find the questions people actually ask
The most common FAQ mistake is writing questions you wish people asked. "Why is our service the best?" is a slogan, not a question. Real questions come from real sources.
- Customer conversations. Sales calls, support tickets, emails and chat logs are the richest source. Note the words customers use, not the words you use.
- Search suggestions. Type your topic into a search box and look at the autocomplete and "people also ask" suggestions. They show the wording real people use.
- Assistants themselves. Ask an assistant the questions a newcomer in your field would ask. Look at which follow-up questions it suggests. Treat this as a prompt for ideas, not as authority.
- Community threads. Forums and question sites in your field show recurring confusion in plain language.
- Your own site search. If you have a search box, the queries people type are a list of things they could not find.
Collect more than you need, then group them. You will usually find a handful of themes: price, how it works, who it is for, comparison with alternatives, problems and policies. Each theme can become a section.
Step 2: Choose questions that deserve a place
Not every question belongs on the page. Keep a question if it passes these tests.
- Someone really asks it. You can point to a source.
- You can answer it factually. You have a specific answer that stays accurate.
- The answer is not already obvious from the page. The FAQ should add, not repeat.
- It is not a disguised ad. The answer should help even someone who never buys.
Aim for quality over volume. Eight to fifteen strong questions beat fifty weak ones. A very long FAQ is hard to scan and tends to dilute the best answers.
Step 3: Write the question the way people say it
Phrase each question in natural language, as a complete question, in the customer's words. Compare these illustrative pairs.
- Weak: "Pricing." Better: "How much does it cost?"
- Weak: "Our process." Better: "How long does setup take?"
- Weak: "Guarantee." Better: "What happens if I am not happy with the result?"
- Weak: "Why choose us?" Better: "How is this different from doing it myself?"
Include the main subject of the page in the question where it reads naturally. A question such as "How long does a roof inspection take?" is self-explanatory on its own, which matters when it is shown out of context.
Step 4: Answer first, then explain
This is the heart of it. Open every answer with the direct answer in one or two sentences. Then add the detail, the exceptions and the nuance. A model lifting the first lines should get something correct and complete enough to stand alone.
A weak answer
Q: How long does setup take? A: Every business is different, and we pride ourselves on a personalised experience, so timelines depend on many factors. Get in touch to discuss.
This tells nobody anything, and there is nothing to quote.
A stronger answer
Q: How long does setup take? A: Most accounts are ready within one working day. Larger accounts with several locations usually take three to five working days, because each location needs its details checked.
The figures here are illustrative; use your own true ones. The shape is what counts: a specific answer first, then the condition that changes it.
Step 5: Get the length right
There is no magic word count, but practical ranges help.
- Direct answer: one to two sentences, roughly 20 to 50 words, that stand alone.
- Supporting detail: a few more sentences, a short list or a small table where the answer is naturally list-like.
- Upper limit: if an answer needs several paragraphs, it probably deserves its own page, with the FAQ giving a short answer and a link.
Very short answers can be too thin to be trusted, and very long ones are hard to extract from. Aim for the shortest answer that is fully correct.
Step 6: Write answers with checkable facts
Specific beats vague. Wherever you can, include the concrete detail: a number, a date, a condition, a name. Models and readers both trust claims that can be checked.
- State prices or ranges and what changes them.
- State time frames and the conditions that alter them.
- State what is included and what is not.
- State policies in plain words: returns, cancellations, support hours.
- Add an "last updated" date so a reader can judge freshness.
Avoid claims you cannot support, such as "the best" or "number one". They add nothing and reduce credibility. Our post on writing content AI models want to quote goes deeper on this style.
Step 7: Mark it up with FAQ schema, correctly
Structured data lets you describe the questions and answers explicitly for machines. The rules are simple and worth following strictly.
- Mark up only what is visible. Every question and answer in the markup must appear on the page, in the same wording or very close to it.
- Use it for genuine FAQs. A page of marketing claims dressed as questions is not a FAQ and should not be marked up as one.
- Each question appears once. Do not repeat the same question across many pages just to multiply markup.
- Keep markup in sync. When you edit the visible answer, edit the markup. Mismatches are a common error.
- Validate it. Check that it parses without errors before and after publishing.
Be realistic about the benefit. Search engines have reduced how often they show FAQ rich results, so do not do this for a visual badge. Do it because it gives machines an explicit, clean copy of your best answers. The mechanics are covered in structured data for AI search engines.
Step 8: Place the FAQ where it helps
There are two good places, and many sites use both.
On the page it relates to
Put a short FAQ at the foot of a product, service or article page, covering the questions a reader of that page is likely to have next. It answers objections at the point of decision and gives that page more quotable passages.
On a dedicated page
A central FAQ or help page works well for general questions: pricing, policies, how things work. Group questions under clear headings and link to it from your navigation and from relevant pages.
Whichever you choose, make sure the text is in the HTML the server sends. If your accordion loads its answers with a script after the page opens, a crawler that does not run scripts may see only the questions or nothing at all. See what client-side rendering hides from AI crawlers. Collapsed accordions are fine as long as the answer text is present in the page source.
A full illustrative example
Here is a small FAQ for an imaginary bookkeeping service. It is an illustration, not a real business, and every figure is made up.
How much does bookkeeping cost for a small business?
Plans start from a flat monthly fee that depends on how many transactions you have each month. A business with a few dozen transactions pays far less than one with several hundred. The fee covers categorising transactions, reconciling accounts and a monthly report.
What do you need from me to get started?
Read-only access to your bank feed, a list of your regular suppliers and customers, and last year's accounts if you have them. Most people finish this in under an hour.
Can you work with my existing software?
Yes, if it can export transactions or connect to your bank. If you are unsure, send us the name of the software and we will say whether it works before you pay anything.
What happens if I want to stop?
You can cancel at the end of any month. We hand over your records in a standard export so you can take them elsewhere.
Notice what the answers do: each starts with the substance, states what changes it, and avoids slogans. Every one could be read aloud without context and still make sense.
Common mistakes
Questions nobody asked
If a question exists only to deliver a sales line, drop it. Readers and models both notice.
Answers that dodge
"It depends" can be true, but follow it at once with what it depends on and typical outcomes. An answer that never commits is worthless to quote.
Hiding the answer behind a click-through
"Contact us for pricing" as an answer to a pricing question leaves the question unanswered. If you truly cannot publish prices, give a range or explain what drives them.
Marking up content that is not on the page
Markup that does not match the visible text is a trust problem, and can lead to the markup being ignored.
Never updating it
A FAQ describing last year's prices is a liability. Review it on a schedule; see how often to re-audit your website.
Ignoring access
A perfect FAQ is useless if crawlers are blocked. Check access with our guide to GPTBot crawl checks.
A simple FAQ maintenance routine
- Monthly: read your last month of customer questions and add any that appear more than once.
- Quarterly: check every answer for accuracy, update figures and the visible date, and remove questions that no longer apply.
- After any change: if you alter a price, policy or process, update the FAQ the same day.
- Every few months: ask a few assistants your top questions and note whether your answers or your name appear. Answers vary between runs, so look at patterns over weeks.
Check your FAQ with a free audit
The free iSuggest.ai audit looks at the machine-readable side of a FAQ page: whether the text is in the HTML, whether structured data is present and valid, whether headings are sensible, and whether crawlers can fetch the page. You can read what an audit measures for the full list. Audits are free and not metered, so you can re-run one after every edit.
When your FAQ and the rest of your pages are in good shape, you can publish a factual snapshot of your business to the iSuggest.ai AI directory, with pages for ChatGPT, Claude and Gemini. Publishing spends credits, which are non-refundable, and improves findability without guaranteeing a citation. See how it works, run an audit on your FAQ page, then sign in at your account page when you are ready.