On many business websites, the FAQ section is the fastest thing ever written and the least often read. It usually appears on one afternoon when somebody notes down whatever a company can think of about itself: thirty entries that were hardly ever asked in that form on the phone, phrased in company language and answered with sentences that were already contained in the question. The result is a page that takes up space and settles nothing. Yet the value of an FAQ section sits somewhere else entirely. It answers questions before they reach the phone, and it clears up the points where an enquiry otherwise stalls. This article reverses the order. First you collect what people actually ask. From that you build a short list in your customers' own words. Only then do answer format, placement, technology and markup come into play.
Why most FAQ sections are invented
You can spot an invented FAQ section by the shape of its questions. It asks “What does our service portfolio comprise?”, “What sets our company apart?” or “Why should you choose us?”. Those are not questions, they are headings with a question mark attached. Hardly anyone types that into a search box, and on the phone such a sentence practically does not occur. The answers underneath match: they repeat what the home page already says and end with an invitation to get in touch. Anyone arriving with a real question does not find it there.
The reason is rarely carelessness. An FAQ section is usually built at the very end of a website project, when the structure and the copy are done and time is short. The quickest available route wins: write down whatever comes to mind. On top of that sits the belief that more questions beat fewer, because every question is another chance at visibility. Together the two produce pages with thirty entries, of which perhaps four reflect a genuine question. If you plan the content differently from the start, the groundwork is in the article on the website brief covering goal, audience and content.
How little such a section achieves shows in the self-service figures. When something goes wrong with an order, only 28 percent (Bitkom e.V.) of online shoppers would use an FAQ section on the website, while 62 percent (Bitkom e.V.) want to reach a human contact as quickly as possible and 52 percent (Bitkom e.V.) would choose email. The Bitkom Research survey questioned 1,006 (Bitkom e.V.) internet users aged 16 and over during calendar weeks 1 to 3 of 2025. The second figure from the same survey is the revealing one: those who do use the FAQ section reach a satisfactory outcome in 60 percent (Bitkom e.V.) of cases. For comparison, chatbots sit at 50 percent (Bitkom e.V.) and direct human contact at 86 percent (Bitkom e.V.).
So an FAQ section is rarely approached, but it works reasonably well once it is. That is exactly where the leverage sits. Not in more questions, but in questions somebody actually asked, answered in a way that settles something instead of handing the reader on to a contact form. Why visits often fail at precisely these open points is covered in the article on the most common reasons enquiries do not arrive.
The one-sentence test
An FAQ section is not marketing copy in question form. It is a record of what people actually ask.
Two weeks of collecting: four sources for real questions
The basis for a usable FAQ section is not built at a desk, it is built during normal working days. Two weeks are enough in most cases, because questions repeat quickly. The effort is small: a notepad next to the phone, a shared notes file, or one item on the agenda of the Monday meeting. What matters is writing things down while the question is still fresh. Questions reconstructed from memory already sound like website copy again.
Note every question on the phone
One line per call, in the caller's own words. Not “price enquiry” but “what does it cost if you come out at night?”. The exact wording is the real harvest, because it later supplies the phrasing of the question. Two weeks often produce thirty to forty entries in a small business.
Read the inbox backwards
Search the last six months of mail for question marks and for words such as “cost”, “how long”, “possible” and “also”. Email questions are valuable because they arrive fully phrased and usually cover exactly the points that need clearing up before an order is placed.
Ask the whole team once
Whoever works at reception, in sales or on site hears different questions than management does. Half an hour spent on “what do people keep asking you?” reliably surfaces topics that appear in no report at all, such as parking, dogs on the premises or paying by card.
Read the actual search queries
The performance report in the search console shows which phrasings bring people to your site. The default view covers three months (Google Search Central) and groups the data by queries, pages, countries and devices among others. How to read that data is covered in the article on analysing search queries.
The collecting phase pays off because it shows how much contact actually happens and where it gets stuck. 71 percent (Verbraucherzentrale Bundesverband) of respondents had contacted a company's customer service within twelve months, and 21 percent (Verbraucherzentrale Bundesverband) reported negative experiences. Among the dissatisfied, 77 percent (Verbraucherzentrale Bundesverband) had to follow up more than once, 76 percent (Verbraucherzentrale Bundesverband) complained about long waiting times, and for 88 percent (Verbraucherzentrale Bundesverband) the problems occurred during telephone contact. The representative forsa survey commissioned by the German consumer organisation Verbraucherzentrale Bundesverband covered 1,151 people, 364 of them with negative experiences. Every question answered in advance is one call fewer in that calculation.
- The exact wording of the question, without editorial smoothing
- Date and channel, so that clusters and seasonal peaks become visible later
- The trigger: what situation the question came out of, such as damage, a move or a price comparison
- The service or page the question belongs to, for later placement
- Whether answering it took more than two minutes, as a signal of explanation needed
- Whether the enquiry went ahead afterwards or not, as a signal of pre-qualification
Two weeks are a sample, not a full year
Turning notes into questions in customer language
The collected notes are raw material. Eighty or ninety entries first become topic groups and from there eight to twelve questions. The most important step is refusing to translate them back into company language. If the phone brings “when is somebody coming?”, that is what goes down, not “how is our appointment allocation organised?”. Customer language has three advantages: it is recognised, it contains the words people type into search boxes, and it forces an answer that fits the situation rather than the category.
| How it often reads on the website | How people actually ask | What the second version does better |
|---|---|---|
| What does our service portfolio comprise? | Do you take small jobs under 500 euros? | Answers a decision instead of a category |
| How is our pricing structured? | What does a night call-out cost? | Names situation, timing and cost in one sentence |
| In which regions are we active? | Do you come out as far as us? | Uses the word that comes up on the phone |
| What is our appointment availability? | How long is the wait for an appointment? | Asks about waiting time instead of availability |
| What qualifications does our team hold? | Who is coming into my home? | Hits the actual worry behind the question |
| How is a collaboration structured? | What do I need to prepare before you arrive? | Turns a process description into an action |
Order the list by frequency in your notes, not by internal logic. The question that came up most often goes first, even when it is uncomfortable. Cases with few mentions go further down. Anything that did not appear once in two weeks and does not show up in the inbox either stays off the list for now. How to shorten sentences so they land on first reading is covered in the article on writing website copy customers actually read.
Eight to twelve beat thirty
The answer format: statement, reasoning, link
Answers in FAQ sections usually fail at the run-up. They open with context, add a qualification, and the actual statement lands in the final sentence or nowhere at all. Somebody with a question, however, reads the first sentence and decides from there whether to continue. So the order is fixed and identical for every answer.
- First sentence: the answer. Yes, no, an amount, a range, a timeframe. No preamble and no hedging.
- Two to four sentences: the reasoning. What limits the statement, what it depends on, what the most common case is. Figures and conditions belong here, not in the opening sentence.
- One internal link: the next step. Exactly one pointer to the service page, the pricing page or the form, with anchor text that names the destination.
An example from the trades: “A call-out outside regular hours costs more than a weekday appointment.” Then the reasoning: surcharges apply to labour and travel time but not to materials; agreeing a binding all-in price beforehand removes the uncertainty; the German consumer organisation Verbraucherzentrale explicitly advises agreeing a fixed price that already includes travel and surcharges before placing the order (Verbraucherzentrale). On cost estimates the guidance is that overruns of 15 to 20 percent (Verbraucherzentrale) against the estimated cost are tolerable, beyond which the business has to inform the customer. And finally the link to the matching service page.
Price statements need care
On length: four to six sentences cover almost every question. If the answer grows beyond that, the question is really a page. Then the content belongs on its own page and the FAQ section carries the short version plus a pointer. That keeps the accordion readable and stops important content from disappearing behind a collapsed element. For questions that lead towards an actual enquiry, a pointer to a well-built contact form helps more than another paragraph of explanation.
If the first sentence does not answer the question, the answer has missed its job, however good the remaining sentences are.
The uncomfortable questions belong in there
The real courage lies in the selection, not the collecting. Precisely the questions that feel awkward internally are the ones where enquiries get stuck. People ask them anyway, just on the phone, after the drive, or during the appointment. Answering them up front costs a few enquiries, saves appointments that would not have converted anyway, and wins enquiries that previously never happened out of uncertainty.
The price range
Not the exact amount, but the order of magnitude and what moves it. Finding out at the appointment that the range does not fit wastes the customer's time and yours. An honest range with conditions is the most effective filter before the first enquiry.
The waiting time
“Currently two to three weeks, emergencies same day” is a statement somebody can plan around. A website that hides waiting times produces enquiries from people who need an appointment tomorrow, and disappointment in the first phone call.
The service area
A clear radius with place names saves trips that do not pay and calls that end in a refusal. If special rules apply outside that area, they belong in the same paragraph rather than in a footnote.
What the business does not do
Possibly the single most useful question. Stating which work you do not take on makes everything else more credible. A pointer to the right trade or specialism turns a refusal into a helpful hint.
Payment and invoicing
Card or cash only, deposit or not, instalments possible or not, invoice by email or on paper. These questions come up on nearly every job and are almost everywhere answered only in conversation.
Complaints and warranty
For repair work and the manufacture of an item the period is two years (Verbraucherzentrale), for work on buildings five years (Verbraucherzentrale). Naming that proactively reads as confident rather than evasive.
The effect of that openness is visible in the mix of enquiries. Fewer arrive, but they fit better. In practice the share of conversations that end after two minutes because a basic condition does not match goes down (project experience). For businesses whose first contact is mostly by phone, the article on how a tradesperson website turns visits into enquiries is worth a look as well.
A no on the website is cheaper than a no after forty kilometres
Placement: the question belongs where it arises
The most common build is a central collection page under an “FAQ” menu item. It has one practical advantage for the editorial side, because everything sits in one place, and one severe disadvantage for use: the question does not arise there. It arises on the drain cleaning page, at the moment the price appears, while looking at the service area. Anyone who first has to open a menu, load another page and search there will rather ask on the phone.
| Criterion | Central FAQ collection page | FAQ under the individual service page |
|---|---|---|
| Where the question sits | Far from the trigger, requires a page change | Directly under the section that triggered it |
| Topic mix | Questions from every area sit side by side | Only questions belonging to the service being read |
| Length | Grows to thirty entries and more over the years | Stays manageable at three to five questions per page |
| Upkeep | One large page that few people read in full | Small blocks updated alongside the service itself |
| Search results | One page competes with itself across many topics | Each service page covers its own phrasings |
| Effect on enquiries | Answers the question late or not at all | Clears the last objection right before the form |
In practice that means three to five questions under each service page, directly above the section with the contact option. Cross-cutting topics that belong to no single service still work well bundled, such as directions and parking, payment methods or availability. For the last of those, the article on keeping opening hours and availability permanently current is worth reading. A collection page is therefore not forbidden, it is simply not the first place.
A simple check before going live
Technology: keyboard, aria-expanded and text in the HTML
An FAQ section is almost always an accordion, and accordions are among the most common places where operability is lost. The cause is usually the same shortcut: the heading becomes a clickable element with no role, no state and no keyboard support. The W3C ARIA Authoring Practices Guide describes a clear structure for this pattern: the title of each question sits in an element with role button, that element is wrapped in a heading with an appropriate level, and it is operated with Enter or Space (W3C ARIA Authoring Practices Guide).
- Role and nesting: the question title sits in an element with role button, wrapped in a heading with a suitable aria-level (W3C ARIA Authoring Practices Guide).
- State: when the answer panel is visible, the button carries aria-expanded set to true, otherwise false (W3C ARIA Authoring Practices Guide).
- Association: aria-controls points to the ID of the element containing the answer text (W3C ARIA Authoring Practices Guide).
- Keyboard: Enter and Space expand and collapse, Tab and Shift+Tab move focus, and all focusable elements of the accordion sit in the page tab sequence (W3C ARIA Authoring Practices Guide).
- Visible focus: the focus indicator must not be removed and, under success criterion 2.4.11, must not be entirely hidden by author-created content (W3C WCAG 2.2).
- Target area: controls should measure at least 24 by 24 CSS pixels (W3C WCAG 2.2) or meet the defined spacing; a full-width row as the button clears that anyway.
The underlying success criteria are not new: criterion 2.1.1 requires all functionality to be operable through a keyboard interface (W3C WCAG 2.2), and criterion 4.1.2 requires the name, role and state of controls to be programmatically determinable (W3C WCAG 2.2). WCAG 2.2 adds nine (W3C WCAG 2.2) new success criteria compared with its predecessor and exists as a W3C Recommendation in the update dated 12 December 2024. Which obligations can follow from that for companies is covered in the article on accessible websites under the European Accessibility Act.
The answer text belongs in the HTML
What FAQ markup still delivers today
For years FAQ markup counted as a safe bet for eye-catching search results. That time is over, and it ended in two steps. From 2023 the enhanced display was shown only for well-known, authoritative government and health websites (Google Search Central). Since 7 May 2026 (Google Search Central) the FAQ rich result no longer appears in Google Search at all; the documentation was updated accordingly on 15 June 2026 (Google Search Central). For an ordinary business website that means anyone adding the markup for the sake of a richer listing is building for an effect that no longer exists.
That is not an argument against the markup, it is an argument against a false expectation. FAQPage remains a valid type in the schema.org vocabulary, and unused structured data causes no problems in Search (Google Search Central). The value today sits in three other places: with people who find an answer without calling; in the relief for the phone, which converts directly into working hours; and in how usable the content is inside machine-generated answers. 50 percent (Bitkom e.V.) of internet users now at least occasionally use an AI chat instead of classic search, while 42 percent (Bitkom e.V.) of them have already received false or invented information and only 36 percent (Bitkom e.V.) feel that answers are sufficiently backed by links. The survey questioned 1,156 (Bitkom e.V.) people aged 16 and over during calendar weeks 39 to 43 of 2025.
Context instead of duplicate work
Upkeep: the twice-a-month rule
An FAQ section ages faster than the rest of a website because it sits close to prices, deadlines and procedures. So it needs a rule that works without a project: any question asked twice in a month goes on the list. And any question that has not mattered for twelve months comes off it. That is deliberately coarse, because a rule only gets applied when it is easy to remember.
- The notepad next to the phone stays there, including after launch. Two weeks of collecting is the start, not the end.
- Once a quarter the list gets reviewed: add new questions, remove expired ones, check amounts and deadlines.
- On every price or service change the FAQ section is touched first, because that is where the concrete figures sit.
- Every answer containing a figure carries a visible date, so outdated statements are noticed before somebody relies on them.
- The order is realigned once a year to actual frequency, so the most important question sits at the top.
Multilingual sites carry an extra task: questions and answers have to be at the same version in every language, otherwise the English page still shows last year's waiting time. How to connect language versions cleanly is covered in the article on the multilingual website with hreflang. In XICflow the questions emerge from the brief as industry-typical suggestions, the accordion is built with the correct state and keyboard operation, and changes to an answer are carried across all maintained languages in sync.
The total effort stays modest: two weeks of noting things down on the side, half an hour with the team, one afternoon for selection and phrasing, then four dates a year. In return the website answers questions that previously had to be answered one at a time. If you are weighing up whether a new site is worth it at all, the calculation sits in the article on when a new website pays off; if you are still choosing a route to build it, the comparison is in the article on builder, agency or AI.
The question behind the question
Sources and studies