An answer page covers exactly one customer question, states the question in the title and answers it fully in the first three sentences. This is followed by the reasoning, an example, limitations and a pointer to the relevant service. Unlike a collective FAQ page, each question has its own address, which Google and AI systems can find and cite individually.
Most SME websites answer customer questions somewhere: in a paragraph on the services page, in an FAQ list in the footer, in a blog post from 2021. For a human who already knows the website, that's enough. For a search engine or a language model looking for the best source for a specific question, it isn't. An answer page fixes this with a simple principle: one question, one address, the answer at the top.
The structure of an answer page
The pattern is always the same, regardless of industry and length. From top to bottom:
- Title (H1): the question exactly as customers ask it. "What does an annual financial statement cost?", not "Annual financial statements: our services".
- Short answer: two to four sentences that answer the question in full. Anyone who reads only this block knows where they stand. No introduction, no "it depends" without saying on what.
- Reasoning: why the answer turns out this way. This is where the factors, tables and figures go.
- Example: a worked-through or narrated case from your own business, noting clearly that it's an example.
- Limitations and exceptions: when the answer doesn't apply. This makes the page credible and protects against false expectations.
- Next step: the link to the service, the form, the strategy call. One sentence, not a sales page.
- Last updated and author: date of the last update, name and role of the person responsible.
Add to this a block with three to five follow-up questions, each with a two to four sentence answer. These aren't the questions from the main text, but the ones a customer asks next.
An answer page has 400 to 900 words. Shorter and it becomes thin, longer and it's usually two questions in one. The checkpoints such a page should additionally meet are listed in the AEO checklist.
Answer page or collective FAQ page?
Both have their place, but not for the same job.
| Collective FAQ page | Answer page | |
|---|---|---|
| Address | one page for 15 questions | one address per question |
| Depth | two to three sentences per question | complete answer with reasoning and example |
| Findability on Google | rarely ranks for individual questions | can rank for this exact question |
| Citability for AI | answers sit among unrelated topics | title, answer and evidence belong together |
| Maintenance | adjust one page | update each question individually |
| Useful for | formalities: opening hours, parking, payment methods | questions that decide whether you get the job |
The rule of thumb: whatever a customer googles before buying gets its own page. Whatever they want to know after buying can go in the collective FAQ.
How to find 20 questions
Twenty questions sound like a lot, but you can gather them in an hour if you look in the right places.
- Inbox and phone: What do prospects ask in the first email or the first call? The three most common questions from the last four weeks are your first three pages.
- Quote conversations: What question comes up before someone signs? It's usually about price, duration, process, and what happens if something goes wrong.
- Google Search Console: Under "Performance" you'll find the search queries your website already gets impressions for. Queries with "what does it cost", "how long" or "who needs to" are candidates.
- Google search itself: Type in your service and read the "People also ask" box and the suggestions at the bottom of the page.
- Declined quotes: Why didn't customers book? These objections are questions nobody asked out loud.
Other sources suited to current topics are described in Finding blog topics. For answer pages, one extra rule applies: only include questions you can actually answer. "What does a divorce cost?" is an answer page for a law firm, "Will I get custody?" is not.
Example: "What does an annual financial statement cost?"
This is what a fiduciary firm's page looks like, run through the pattern above. The figures are placeholders; the real page states the ranges the firm actually charges.
Title: What does an annual financial statement cost for an SME?
Short answer: "With us, an annual financial statement for a sole proprietorship with tidy bookkeeping costs between X and Y francs, and for a GmbH or AG with payroll accounting between Y and Z francs. The price depends on the number of entries, the condition of the receipts, and whether we handle the bookkeeping throughout the year. You'll get a fixed quote once we've had a look at your documents."
Explanation: a table with the three price drivers (volume of entries, receipt quality, legal form) and how they affect the workload.
Example: "Sample calculation: A painting business with two employees, around 600 entries a year and receipts sorted monthly, needs N hours with us, which works out to a price of ..."
Limits: Backdated postings for past years, missing receipts and audits are not included. A short paragraph explains what happens then.
Follow-up questions: By when does the statement need to be ready? What do I need to prepare? Can I switch fiduciaries partway through the year?
Date and author: "As of: October 2026, name, certified fiduciary expert".
This page answers a question that's asked in every region, with details only this firm can provide. That's exactly what makes it citable. For 25 more questions suited to fiduciary firms, see Blog for fiduciaries.
What answer pages don't replace
Answer pages are not a substitute for service pages, nor for a blog. The service page sells, the answer page explains, and the blog keeps the website moving and covers the questions that change throughout the year. Anyone running a blog on the same pattern gets both: a system like BlogPilot writes posts with the question in the title, the answer at the top, and an FAQ section, drawn from real search queries in the industry. How SMEs can appear in AI answers this way is described in Getting found in ChatGPT. It's best to write the first five answer pages yourself, though: you know best what your customers ask.
Frequently asked questions
How many answer pages does an SME website need?
Start with the five questions asked most often before a job is booked. For most businesses, twenty pages cover everything that decides a job. More only makes sense if the questions are genuinely different, not the same answer in new packaging.
Should I set up answer pages as blog posts or as fixed pages?
Both work, as long as each question has its own address. Fixed pages suit questions that barely change, such as those about the process. The blog suits questions that shift with laws, prices or the season, because it carries a visible date and is updated regularly.
Can the same question also appear on the FAQ overview page?
Yes, but only as a short version in one or two sentences with a link to the answer page. If both pages carry the same text in full length, they compete with each other on Google, and neither one wins out.
Do answer pages need FAQPage structured data?
Not necessarily. FAQPage markup describes the follow-up questions at the bottom of the page, not the main answer. The visible structure, the date and the author matter more. If your system generates the markup automatically, it doesn't hurt; you don't need to add it manually.