How to Write a Website FAQ That Brings Enquiries

Most people who visit a small business website are not ready to buy. They are ready to ask. How much does it cost? How long does it take? Do you work in my area? What if I am not happy? If the page does not answer these questions, the visitor either guesses (usually pessimistically) or leaves to find a site that does. A well-built FAQ section removes that friction, and it also gives search engines and AI assistants something clear to quote.

Why a FAQ is worth the effort

A FAQ is not a place to dump leftover information. Done properly, it does three jobs at once:

• It lowers hesitation. Every unanswered doubt is a reason not to call. Answering it in advance shortens the path to an enquiry.
• It saves your time. If the same five questions arrive by phone every week, the website should handle them, so conversations start further along.
• It helps you be found. Real questions in plain language match how people search, and AI tools prefer pages where a question is followed by a short, direct answer. We explain this in more detail in our article on AI search visibility.

1. Collect real questions, not invented ones

The best source is your own inbox. Go through the last few months of emails, WhatsApp messages and call notes and write down every question a customer asked before buying. Ask whoever answers the phone for the top five. Then add questions people type into Google: start typing your service plus your city and see what the suggestions offer, and check the "People also ask" box on the results page. A list of 15 to 20 raw questions is a good start.

2. Pick the questions that block a decision

Not every question belongs on the page. Keep the ones that stand between a visitor and an enquiry. For most small businesses they fall into a handful of groups:

• Price: what it costs, what changes the price, whether there are extra fees
• Time: how long a job takes and when you can start
• Process: what happens after the first message, what you need from the customer
• Area and availability: where you work, opening hours, how quickly you reply
• Risk: guarantees, what if something goes wrong, how payment works

Aim for six to ten questions per page. A wall of thirty questions is rarely read, and it buries the ones that matter.

3. Answer in the first sentence

Write each answer so the first sentence is the answer itself, and the following sentences add detail. "A simple five-page website usually takes two to three weeks from the first brief" is better than a paragraph that begins with "It depends on many factors". You can add the nuance afterwards, but give the reader something concrete first. Keep each answer to roughly 40 to 100 words, in the same plain language your customers use.

4. Put the FAQ where the doubt appears

A single FAQ page that nobody opens is a missed chance. Place short question blocks on the pages where the doubt arises: pricing questions next to the price, process questions near the contact form, delivery or returns on product pages. Each main service page can carry its own five or six questions at the bottom, just above the call to action. Keep one general FAQ page only for questions that apply to the whole business.

5. Make it easy to scan

Use a clear question as a heading or an accordion title, with the answer directly below. Accordions are fine for design as long as the answer text is in the page and not loaded later by a script, so that search engines and screen readers can read it. Add a link inside an answer when the reader may want the next step, such as a contact form or a related guide.

6. Add structured data when it fits

FAQ content can be marked up with schema.org FAQPage data in JSON-LD, so that machines can read the questions and answers as clean facts. Two rules apply. The markup must match the text visible on the page, word for word, and it should only be used for real questions with real answers, not for advertising copy. Google shows FAQ rich results only for a limited set of sites today, so treat the markup as a clarity signal for search and AI tools, not as a guaranteed way to get extra space in the results.

7. Keep it current

An FAQ with an old price or last year's timelines does more harm than none at all. Review it every few months, and add a new entry whenever a question comes up three times. Your FAQ should grow with the questions your customers really ask.

A quick FAQ checklist

• Questions come from real emails, calls and Google suggestions
• Six to ten questions per page, focused on price, time, process, area and risk
• Every answer starts with the answer, in plain language
• Questions sit on the pages where the doubt appears
• Answers are real text on the page, not hidden behind scripts
• FAQPage markup matches the visible text exactly
• The list is reviewed a few times a year

A FAQ will not fix a weak offer, and it cannot promise more enquiries. What it can do is remove the small doubts that quietly cost you messages. It works best as part of a page that is already clear, which is the theme of our conversion checklist.

How we build this

When we build a website or landing page, we draft the FAQ together with you from your real customer questions and add the structured data. If you send traffic from Google Ads, a good FAQ on the landing page helps paid visitors decide faster, and if you receive many repeat questions by message, AI automation can answer the simple ones instantly. Not sure where to start? Use the form below, or see what the turnkey launch includes.