Definition
An FAQ content strategy is the deliberate use of question-and-answer blocks to cover the specific things buyers ask, rather than a catch-all list bolted to the page. Unlike a support FAQ, which exists to deflect tickets, this version is written to be retrieved and quoted. A question heading followed by its answer matches how assistants search.
At a glance
- CategoriesContent
- Related fieldsAEO, Content
- DifficultyBeginner
At a glance
- An FAQ block is structurally close to what retrieval wants: one question, one self-contained answer, repeated.
- The questions come from sales calls, support tickets and assistant transcripts, not from a keyword tool.
- Google shows FAQ rich results to a narrow set of sites now, so the search reward has shrunk while the retrieval reward has grown.
- FAQPage markup describes the block to machines. It does not improve a weak answer.
- A question you answer honestly, including the awkward ones, is more likely to be quoted than a question you answer defensively.
A question heading is a match before anything is read
Retrieval compares a user’s question with the text of candidate passages. An FAQ block hands it a passage whose first line is already a question, phrased the way people phrase questions.
That is an unusually clean match, and it explains why FAQ sections get cited out of proportion to their length. The heading states the subject. The answer under it is short, self-contained and makes no reference to anything above it. Nothing has to be repaired before it can be used.
The structure also survives being cut. When a page is split into chunks, an FAQ block breaks cleanly at each question, so the piece that comes back is a complete unit rather than a fragment of an argument.
The FAQ block became the most valuable part of the page
For years the FAQ was where content went to die: written once, never updated, largely ignored by the team that owned the page.
That has flipped. A shopper asking an assistant whether a jacket is machine washable, whether a subscription can be paused, or whether a tool integrates with Xero is asking exactly the sort of question an FAQ answers. Whoever has answered it plainly gets named. If you have not, the answer comes from a forum, a reseller or a competitor’s comparison page.
The awkward questions are worth more than the easy ones. “Why is this more expensive than alternatives” and “what does it not do” are asked constantly and answered by almost nobody. A straight answer to either one is nearly unopposed in retrieval, and it is also the answer a serious buyer is looking for.
Source your questions from sales and support
Keyword tools will not give you this. The questions exist inside your own business.
- Pull the last few months of support tickets and sales call notes and group them by question, not by topic. The repeated ones are your list.
- Ask the assistants directly. Put your category questions to ChatGPT and Perplexity, read the follow-ups they suggest, and note which of those you cannot answer on your own site.
- Write each answer to stand alone. Restate enough of the question in the first sentence that the answer makes sense pasted somewhere else.
- Include the two or three questions you would rather avoid. Price, limitations, who the product is wrong for.
- Mark it up and keep it current. Google’s structured data documentation covers the FAQPage type, and content freshness applies here as much as anywhere.
Two kinds of FAQ, two different jobs
| Support FAQ | Retrieval FAQ | |
|---|---|---|
| Written to | Reduce inbound tickets | Be quoted in an answer |
| Question wording | Internal phrasing | The words a customer types |
| Answer length | As short as possible | Complete enough to stand alone |
| Awkward questions | Avoided | Included deliberately |
| Owner | Support | Whoever owns the page |
Frequently asked questions
-
Does FAQ schema still do anything?
FAQPage markup still describes your content to machines that parse structured data, and that remains useful. What it no longer reliably does is win you an expanded result in Google, which narrowed FAQ rich results to a small set of sites. Add the markup because it is cheap and accurate, not because it wins a listing.
-
Where should the FAQ go, on one page or spread across the site?
Spread it. Questions about shipping belong on the delivery page, questions about fit on the product page, questions about a concept on the page explaining that concept. A single site-wide FAQ page competes for everything and matches nothing well, because its chunks cover unrelated subjects.
-
Can I just reuse the questions my competitors answer?
You can, and you will place second. Their answers are already retrievable, so a near-duplicate gives a model no reason to switch sources. The value sits in questions they have ducked, and in answers where your factual density is higher than theirs.
-
Is any of this worth doing if we already have good product pages?
Usually yes, and it is among the cheapest work available: no new pages, no design, no build. The exception is a site whose pages cannot be crawled or rendered properly. Fix that first, because an excellent FAQ nothing can read is worth nothing.