FAQ content that answers the question
An FAQ section is a set of real customer questions with direct answers. Most are neither. They are marketing copy arranged as questions, which helps nobody and is read that way by an answer engine as well.
An FAQ section is a set of real customer questions with direct answers. Most are neither. They are marketing copy arranged as questions, which helps nobody and is read that way by an answer engine as well.
Short answer
Good FAQ content collects the questions customers genuinely ask, answers each one directly in a short paragraph, and marks up the set so machines can read the relationship. Questions invented to hold keywords do not help. Anything that needs more than a few hundred words deserves its own page instead.
The questions worth answering already exist. They are in your inbox, in your call notes, in the messages that arrive through your contact form, and in the things people say in the first minute of a conversation.
Collect them for a month before writing anything. Write down the wording people actually use, not the wording you would use. The gap between those two is where most FAQ sections go wrong from the first line.
Search suggestions help too. Start typing a question about your trade and watch what completes. Those completions are drawn from real queries, which makes them a better source than anything you invent at a desk.
The invented question is the commonest fault. Why should I choose a professional roofer is not a question anybody types. It is a sales line wearing a question mark, and readers see through it at once.
Equally bad is the question whose answer is a brochure. If the reply runs to four paragraphs of positioning before it says anything concrete, the question was never the point and the section is not an FAQ at all.
Then there is the duplicated question, asked slightly differently in three places so that three keyword variants are covered. That is the doorway habit applied to questions, and our page on doorway pages explains why it backfires.
Answer in the first sentence. Yes, no, it depends, it costs roughly this much. Then qualify. A reader scanning a list of questions is looking for the answer, and burying it makes the whole section useless to them.
Keep each answer to a short paragraph. If it will not fit, that is a signal rather than a problem. The subject deserves a page, and the FAQ entry becomes a two-line summary with a link to it.
Write the awkward answers honestly. We do not work weekends. We do not take that kind of job. Prices start higher than most people expect. Those entries build more trust than a dozen comfortable ones.
A useful FAQ covers the practical friction between interest and hiring. Money, timing, area, process and the things that go wrong. Every item below appears in real customer conversations across most trades.
Put the questions where the friction is. Pricing questions belong on the pricing page, process questions on the service page, area questions on the location page. A single distant page collecting all of them helps nobody.
Use real heading tags for the questions rather than styled text, and keep the levels in order. An answer engine reads the heading and the paragraph beneath it as a pair, which is exactly the relationship you want.
Where the set is genuinely a set of questions, structured markup can state that. Our page on structured data covers which types apply and the mistakes that turn markup into a liability.
Length is the first signal. An answer that runs past a few hundred words is a page. So is any question that people ask in several different ways, because each phrasing is a chance to be found.
Commercial weight is the second. If the answer changes whether somebody hires you, it deserves room, examples and a proper explanation rather than a paragraph squeezed between two unrelated entries.
Splitting is not a loss to the FAQ. Leave a short entry behind with a link onward, so the scanning reader still gets the direct answer and the serious reader reaches the full treatment.
Prices move, hours change, and services get dropped. An FAQ is the part of a site most likely to state something that used to be true, because it states things flatly and nobody rereads it.
Review it on a fixed schedule rather than when you remember. Our page on content freshness covers the routine, and an FAQ is the strongest argument for having one.
Delete freely. A section that has grown to forty entries is no longer scannable, and the weakest ones are dragging down the average. Fewer, better answered questions serve every reader more effectively.
Enough to cover the real friction and no more. For most small businesses that is somewhere between six and a dozen per page. A list long enough that nobody scans it has stopped being useful, however accurate each entry is.
Spread it. Pricing questions belong on the pricing page, process questions on the service page, coverage questions on the location page. A single distant page is rarely read by the person whose question it answers.
It states the relationship between a question and its answer in a form a machine does not have to infer. Use it where a genuine question set exists on the visible page. Do not add it to content a visitor cannot see.
Only if you would genuinely expect somebody to ask them. A new service will have questions before it has customers. What does not work is inventing questions to hold keywords, which reads as marketing to people and to machines.
15-day free trial. Card required. Cancel before day 15 and you pay nothing.