Short answer
Most small business websites do not need a dedicated FAQ page by default. Put the questions that help a visitor decide whether to enquire on the relevant service page. Use a separate FAQ page only when the questions are broad, repeated across several services, or mainly about business-wide policies and process.
What belongs on a service page
Service-page FAQs should answer the questions that affect a buying decision for that exact service:
- what is included, and what is not included
- price range, or what changes the price
- turnaround time or booking lead time
- coverage area
- who the service suits
- the main objection that stops an enquiry
Example: on a builder’s kitchen extension page, “How long does an extension usually take?” and “Do you handle planning support?” belong there because they change that enquiry.
Example: a generic “What areas do you cover?” block copied onto every service page is weak if the answer is the same each time. One concise mention on the most relevant page is enough; repeating it everywhere adds bulk without adding clarity.
When a dedicated FAQ page is justified
A separate page makes sense when the same question appears on multiple pages and the answer is genuinely the same everywhere:
- payment terms, deposits and cancellations
- onboarding or what happens after an enquiry
- delivery, access or arrival process
- aftercare, guarantees or warranty terms
- company-wide policy questions
That page should hold the full answer once. Service pages can then use a short signpost such as “Questions about deposits and lead times are covered in the FAQ page.” If a question is only present because it might attract searches, not because it helps someone decide, leave it out. The same applies to whether a small business website actually needs a blog: a page deserves space only when it has a clear job.
How to avoid duplicated FAQ content
Give each question one main home:
- Put the full answer where it is most useful.
- Mention it briefly elsewhere only if it helps navigation.
- Do not copy the same FAQ block onto every service page.
- If the answer changes by service, keep it on each service page instead of forcing one generic version.
That keeps the site easier to maintain and stops the content from turning into near-identical pages that look thin and awkward to edit later.
Do FAQs help enquiries?
Yes, when they remove friction. A good FAQ answer reduces hesitation, cuts back-and-forth, and helps the visitor decide to call, fill in a form or request a quote. A bad FAQ answer just makes the page longer.
If the question does not change the decision, skip it. If it does, keep it close to the service. If the debate is really about the technical markup rather than where the text lives, that is a separate question covered in FAQ schema for small business websites.
For sites that feel cramped already, website structure help is usually the better fix than adding another page for the sake of it.
