Most FAQ pages are written backwards. Somebody sits down, imagines what a customer might ask, and produces eight questions nobody has ever asked, answered in the voice of a brochure. "What makes your service different?" is not a frequently asked question. It is a sales pitch wearing a question mark, and customers recognize it immediately.

The pattern worth designing around is that people try to answer their own questions before contacting anyone. Gartner surveyed 5,801 customers in January and February 2025 and found that 51 percent of customer service journeys now begin on third-party platforms such as search engines, YouTube, and chatbots, while only 22 percent of customers start, stay, and resolve their issues entirely within a company's own channels. Gartner was measuring service journeys rather than people shopping around, but the habit is the same one: the question gets asked somewhere before it gets asked of you. For a small business, an FAQ page is the cheapest way to make sure the answer found is your own.

Collect real questions before writing anything

The raw material is already in the business. Open the last two months of emails and note every question a customer asked in their own words. Do the same with voicemails, text messages, and the questions that come up on estimate visits.

Ask the person who answers the phone which question they are tired of answering. That question, phrased the way callers phrase it, is the first entry on the page. Reception staff and dispatchers usually name three or four without pausing.

Check the reviews, including the good ones. Customers frequently mention what worried them before booking, and those worries are questions the page should handle.

Look at what people search. Terms containing "how much," "how long," "do you," and "can I" reveal the questions being typed into Google about your kind of work, and local keyword research turns that into a list. A page built this way tends to be uncomfortable to write, because the real questions are about price, delay, and what happens when something goes wrong. Those are exactly the ones worth answering.

Answer the awkward questions properly

The value of an FAQ page is concentrated in the questions a business would rather avoid. How much does this cost. Why are you more expensive than the quote down the road. What happens if the work fails. How long until somebody can come out.

Answer them directly. A business that will not discuss price anywhere on its site reads as evasive, and visitors assume the worst rather than calling to find out. A range with the reasons it varies is enough, and the pricing page can carry the detail.

Include the unwelcome answers too. A roofer booked five weeks out who says so on the FAQ page loses the customers who needed somebody tomorrow and keeps the ones who can wait, which is a better outcome than a wasted call for both parties.

Keep answers short. Two to four sentences handles almost every question, and a page of two-paragraph answers stops being scannable. If a question needs 600 words, it is an article, and the FAQ entry should answer briefly then link to it. That is also how Optuno structures content for small business sites, with the short answer where somebody is looking and the depth one click away.

Structure the page so answers are findable

Group questions by theme once there are more than eight of them. Pricing and payment, scheduling and timing, the work itself, warranties and guarantees, service area. Grouping turns a wall of text into something a visitor can navigate in a glance.

Put the most-asked questions first within each group. Order by frequency, not by what the business would prefer people read.

Write the questions the way customers say them. "How much does it cost to unblock a drain?" works. "What is the pricing structure for drainage services?" does not, because nobody searches that way and nobody scans for it either.

Make each question expandable if the list is long, but keep the answers present in the rendered page rather than fetching them only on click, so they are there to be read. Do not build the page around FAQ structured data. Google stopped showing FAQ rich results on 7 May 2026 and removed the related documentation the following month, so the markup no longer produces anything visible in search. Google has said existing markup can stay because it causes no problems, but adding it now buys nothing. A plain page of visible questions and answers is easier to maintain and works just as well for the people reading it.

What separates a useful FAQ page from a filler one

The useful ones are specific to the business. Answers name the service area, the brands carried, the hours, the warranty length, and the actual process. Generic answers that would fit any competitor add length without adding value.

They carry numbers. Response times in hours, warranty periods in years, price ranges in dollars, lead times in weeks. Numbers are what the visitor came for, and a page that avoids all of them has answered nothing.

They are maintained. An FAQ page listing 2024 prices or a service the business stopped offering does active harm, because it is the page customers trust for facts. A twice-yearly review takes twenty minutes.

They point somewhere. Each answer that raises a next step should link to it, whether that is the contact page, a service page, or the About page when the question is about who does the work. An FAQ page that answers everything and offers no route forward leaves visitors to find their own way. Before rewriting the page, Optuno's free local SEO report gives a snapshot of rankings, listings, and reviews so you can see which questions people already reach the site with.

How many questions, and where the page should live

Between eight and twenty questions suits most small businesses. Fewer than eight and the page looks like an afterthought. More than twenty and it needs grouping, or splitting so that service-specific questions sit on their own service pages.

Service-specific questions often work better on the service page itself. A question about how long a bathroom refit takes belongs on the bathroom page, where somebody is already reading about bathrooms. The central FAQ page then handles the questions that apply to the whole business.

Link to the page from the main navigation or the footer, and from the contact page, since somebody about to make contact is exactly who benefits from finding an answer first.

Keep it out of the sales funnel. An FAQ page that turns each answer into a pitch stops being a reference and becomes a liability, because the one page people trusted to be straight with them is not. The restraint is the product. If maintaining this alongside the rest of the site is more than you want to take on, Optuno's plans include the content work with no long-term contracts, no setup fees, and a dedicated contact.

Frequently asked questions

How many questions should an FAQ page have?
Eight to twenty for most small businesses. Below eight the page reads as unfinished, and above twenty it needs grouping by theme or splitting, with service-specific questions moved onto the relevant service pages.

Should FAQ answers include prices?
Yes, at least as a range with an explanation of what moves it. Sites that avoid the subject entirely lose visitors who assume the price is being hidden for a reason, and a range filters out enquiries that were never going to convert.

Does an FAQ page help with SEO?
It can, because the questions match how people search, particularly longer conversational queries. The larger benefit is usually that the page answers questions which would otherwise become phone calls or lost enquiries.

Should I use FAQ structured data?
It no longer earns anything visible. Google stopped showing FAQ rich results on 7 May 2026 and removed the related documentation the following month. Existing markup can stay, since Google has confirmed it causes no problems, but adding it now will not change how the page appears.

Where should the FAQ page sit in the navigation?
Main navigation or footer, plus a link from the contact page. Somebody about to send an enquiry is the visitor most likely to find an answer there first, which saves a call for both sides.

How often should the FAQ page be updated?
Twice a year, and immediately whenever prices, hours, warranties, or services change. It is the page visitors treat as factual, so outdated information on it does more damage than the same error elsewhere on the site.