How to build FAQ pages that AI engines actually use

A good FAQ is the closest thing to writing an AI engine's answer for it. The question is phrased the way the user phrases it, the answer is short, direct and self-contained, and both sit in plain HTML. Studies of ChatGPT citations in 2026 repeatedly found question-and-answer formatting and FAQ blocks over-represented among cited pages. The catch is that most FAQ pages are not built from real questions, so they answer nothing anyone asks.

Step 1: Collect the questions people actually ask

Sources, in order of value: your sales inbox and call notes from the last six months; support tickets; the Q&A section on your Google Business Profile; the questions in Google's People Also Ask for your services; the follow-up questions Perplexity and AI Mode suggest under an answer; Reddit and forum threads in your sector; and the questions your staff are tired of answering. Aim for 30 to 50 raw questions. Group duplicates, keep the customer's wording.

Step 2: Decide where each question lives

Questions about one service go on that service page (two to five each). Questions about the company, pricing philosophy, process, guarantees, areas served and how to get started go on a central FAQ hub. Questions that need a long answer become their own guide page, with a short FAQ answer that links to it. Never paste the same block onto every page; engines treat duplicated content as low value and it dilutes which page should be cited.

Step 3: Write the answer as the first sentence

Forty to ninety words per answer. The first sentence is the answer, complete on its own. The rest qualifies it. "Yes, we cover Hastings. Travel is included for jobs within 15 miles of Bexhill; beyond that we add £0.45 per mile, which we state on the quote." A reader or an engine can stop after sentence one and still have the answer.

Step 4: Make it specific

Prices, timescales, limits, exclusions, names, places. "It depends" is not an answer. If it does depend, state the range and what moves it: "Between £400 and £900 for a standard three-bed; loft conversions and older wiring push it towards the top of the range." Specific answers are quotable; vague ones are skipped in favour of a competitor's.

Step 5: Keep it in the HTML

Use plain headings and paragraphs, or a native details element if you want a collapsed look. Avoid FAQ plugins and widgets that load answers by JavaScript on click; check with View Page Source that every answer is present. If the answers are not in the source, most AI crawlers cannot read them.

Step 6: Add FAQPage schema that mirrors the visible text

One FAQPage block per page with a Question and acceptedAnswer for each visible pair, text identical to the page. Do not mark up questions that are not on the page and do not add FAQPage to pages whose main content is not the FAQ. Our structured data guide has the pattern.

Step 7: Link out from answers

Where an answer touches a deeper topic, link to the relevant service page or guide. FAQ pages are strong internal linking hubs, and engines follow the links to understand what your site covers.

Step 8: Review quarterly and date it

Prices change, policies change, new questions arrive. Review the hub every quarter, update answers with real changes, retire questions nobody asks any more, and show a visible "Last reviewed" date. Keep dateModified accurate in the page's schema.

How to know it worked

Ask ChatGPT, Perplexity and AI Mode your top ten FAQ questions with your company name and without it. With the name, the engine should answer from your FAQ. Without it, your FAQ should start appearing as a cited source for the generic version over the following weeks, especially in Perplexity, which reacts fastest.

Common mistakes

• Questions written by marketing ("Why choose us?") rather than by customers ("Do you charge for a quote?").
• Answers that restate the question and then say "contact us".
• A JavaScript accordion that renders empty in the source.
• FAQPage schema on every page of the site, including ones with no FAQ.