( WEBSITE CONTENT ) Nov 14, 2026
FAQ Pages: Which Questions Actually Deserve an Answer
01The Page That Fills Up With Questions Nobody Asked
Most FAQ pages are written in one sitting. Someone sits down with a blank document, thinks about what a customer might want to know, and types ten questions. A good share of them turn out to be things the business would like to be asked. Why choose us? What makes your service different? Nobody has ever phoned a pool company in Sarasota to ask that.
The real questions sound different. Do you service Venice, or only Sarasota? Is there a fee if I cancel the day before? Can my daughter approve the estimate while I am still up north? Those come from people who are close to hiring you and have one thing left to settle.
Susan Farrell of the Nielsen Norman Group, a user experience research firm, made the same point in a December 2014 article titled FAQs Still Deliver Great Value. She called invented questions a bad practice the firm had long warned against, and wrote that the questions on an FAQ page “should echo the real concerns people contact you about.” This post is about how to find those concerns, how to decide which of them earn a place on the page, and how to answer them.
02Where the Real Questions Are Hiding
You already own the research. It is in your phone log, your inbox and the memory of whoever answers the front desk. Farrell put it this way in the same article: “If you’re listening to your users, you know what their questions are. It’s that simple.” The work is in writing them down, because memory keeps the unusual questions and forgets the ordinary ones.
Try a two-week tally. Keep one sheet of paper by the phone, or one shared note on everyone’s phone, and make a mark every time a customer asks something before they have booked or bought. Write each question the way the person said it, not the way you would file it. Look in these places:
- Phone calls, including the voicemails that begin with “quick question.”
- Emails and messages sent through your contact form. Search your sent folder for replies you have typed more than twice.
- Direct messages and comments on Facebook and Instagram. Farrell’s article suggests bringing questions that people ask on social media back to your own site.
- Questions asked in person at the counter, on the estimate visit or at the end of an appointment.
- Reviews, which often mention the thing a customer wishes they had known beforehand.
Keep the customer’s wording. Farrell wrote that “people don’t search for your solution, they search for their problem,” and that questions should reflect the vocabulary of your visitors. A roofer might file a question under wind mitigation inspections. The homeowner in Bradenton asked whether a new roof would lower her insurance bill. Her version belongs on the page.
03Which Questions Earn a Place
After two weeks you will have a messy list, and not everything on it belongs on the website. Put each question through a short filter.
- Was it asked more than once, by different people? A single odd question is a conversation, not a page entry.
- Does the answer hold for most customers? If it depends entirely on the job, say what it depends on, or leave it for the phone call.
- Can you answer it honestly in a short paragraph? If you find yourself dodging, the question is probably about price or timing, and a range with a reason is better than silence.
- Does it come up before someone becomes a customer? Questions that arrive after the sale usually belong in a welcome email or on the invoice.
Then ask whether the answer should live somewhere else as well. In a July 2013 post on the UK Government Digital Service blog titled FAQs: why we don’t have them, content designer Sarah Richards argued that FAQ pages are “convenient for writers” but “more work for readers,” and that they tend to duplicate content. Her sharpest line was this: “If a question is frequently asked, it means you need that content on your site.”
A small business does not need to go as far as removing the page, but the warning is useful. If half your callers ask whether you serve Lakewood Ranch, your service area should be stated on the home page and on each service page, not only in the ninth item of a list. The FAQ can repeat it briefly. Our post on how to structure service pages covers where that kind of detail fits.
Most small businesses end up with eight to fifteen questions that pass. That is a rule of thumb from the filter above, not a researched figure. If only five survive, publish five.
04Answering Plainly
Put the answer in the first sentence. If the question is whether you work on Saturdays, the answer begins with yes or no, and the explanation follows. A reader who came for one fact should be able to leave after one line.
Farrell’s article offers a test worth borrowing. It asks whether the answers on a page seem “factual and frank or more like marketing hype.” Compare two replies to the question about a cancellation fee. The first says that the company values flexibility and works with every client to find a solution. The second says there is no fee with a day’s notice, and that a same-day cancellation is charged a set amount because the crew has already been scheduled. Only the second answers the question.
A few habits keep answers plain:
- Give the number, the day or the town when you have one. “Usually within two business days” is more useful than “promptly.”
- When the honest answer is that it depends, name the two or three things it depends on.
- Write each answer so it makes sense alone. People arrive in the middle of the page and do not read the items in order.
- End with the next step where there is one, such as a link to the booking form or the phone number. Our contact page guide covers what should be waiting at the other end.
Local conditions produce their own questions, and they are worth answering directly. A property manager can say what happens to bookings when a storm is forecast. A home service company can explain whether it will work on a house while the owners are away for the summer, and who it will take instructions from. Customers who spend half the year elsewhere ask these things every season.
05Layout: A List, Groups or an Accordion
For a short page, a plain layout is hard to beat. Farrell wrote that the traditional list of questions followed by the individual questions and answers “is still the best underlying design” for short and medium-length FAQs. She added that larger ones should be chunked by topic so that readers can scan them. For a local business that might mean three small groups, such as Booking, Pricing and Service Area.
Many sites hide each answer until the question is tapped. The W3C, the body that publishes web standards, describes this accordion pattern as “a vertically stacked set of interactive headings” that let users reveal or hide the sections beneath them. In a January 2015 follow-up article, An FAQ’s User Experience Deconstructed, Farrell noted that closed accordions are not always implemented well on desktop but are “generally used to good effect on mobile.” If you use one, make sure the whole question row responds to a tap and that the open answer is easy to read.
Whichever layout you choose, make the questions stand out from the answers. The 2015 article criticized one FAQ because its typography did not separate the two, and suggested a bold font for the questions. A customer with reading glasses pushed up on his forehead should be able to find his question without squinting.
An FAQ does not have to be a separate page, either. A short set at the bottom of the home page or a service page can do the same job. The questions section on our own home page is built that way.
06Keeping It Current, and What an FAQ Will Not Do
An FAQ page ages quietly. Prices change, a service is dropped, the Saturday hours end, and the page goes on saying otherwise. Farrell’s 2015 article described a good FAQ as one whose content keeps changing as the questions the organization receives change. For a small business, a calendar reminder twice a year is enough, and early fall, before seasonal residents return, is a sensible time for one of them. Add what people have started asking, remove what they have stopped asking, and check every number.
Treat the list as feedback too. Farrell suggested using FAQs “as clues” to problems that some other part of the organization can fix. If everyone asks where to park, the answer may be a sentence in the confirmation email or a sign by the driveway, and the question can come off the page.
One thing an FAQ page will not do is change how your listing looks on Google. For several years, pages with a particular kind of markup could show expandable questions beneath their search result. According to the documentation updates log on Google Search Central, that FAQ rich result feature stopped appearing in Google Search on May 7, 2026, and Google removed the documentation for it in June 2026. No one can guarantee a position on Google in any case. Write the page for the person who is about to call you.
Start with the tally sheet this week. In two weeks you will have the raw material, and an afternoon is enough to turn it into a page. If your site needs an FAQ section built, or the answers need to be worked into the pages around it, you can tell us about your project.
When you are ready to talk about your own site, the Sarasota web design page covers what is included at each level and what drives the cost.
Ready for a website that reflects your business?
Start a project ↗