An FAQ page that answers what customers really ask, answer first, helps people book and helps AI search tools understand you. Here's how to write one.
Every small business FAQ page I open has the same first question: “Why should I choose you?” Nobody has ever typed that into Google. Not once. The answer is always “We’re passionate about quality,” which is also not something anyone has ever searched for.
Meanwhile the questions people actually ask (how much, how long, do you come to me, what happens if it rains) are buried in a voicemail somewhere. That’s a shame, because a good FAQ page is one of the cheapest ways to show up when somebody asks ChatGPT or Google’s AI who to call.
The short version
Yes, but not the kind most sites have. A useful FAQ page answers the five or ten things customers ask you every single week, so they don’t have to call to find out.
Think about the last ten calls or texts you got. I’d bet half of them were some version of “how much does it cost,” “are you open Saturday,” and “do you serve my area.” Those are your FAQs. You already know them. You’ve answered them so many times you could do it asleep (and some days you probably have).
The fake FAQ is the one written by a marketing brain. “What makes us different?” “What is our mission?” It’s an About page wearing a fake mustache. Nobody falls for it, and the robots don’t either.
Because an FAQ is already shaped like the thing AI tools are trying to produce: a question and a short, direct answer. When someone asks an assistant “how much does a pressure washing job cost in Palm Coast,” it goes looking for a page that answers that exact kind of question clearly.
If your answer is “Pricing varies depending on many factors, please contact us for a free consultation,” you just handed the robot nothing. It’s going to quote the competitor who wrote “Most driveways cost about the same as a nice dinner out for four, and I’ll give you an exact number after a quick look.” Specific beats polite every time.
When I set up AI search on a client site, answer-first FAQ blocks are one of the first things I add, right alongside the schema and the llms.txt file. It’s not magic and nobody can promise an AI will pick you. But you can make damn sure it understands you if it does look.
The ones that stop people from booking. Every question a customer has to ask before they’re comfortable is a little speed bump between them and your calendar.
Here’s where I’d start:
That last group is the one people skip, and it’s the one that builds the most trust. Anybody can answer “do you offer free estimates.” The business that calmly explains its refund policy looks like it’s done this before and isn’t going to pull some BS when things get messy.
Answer first, explain second. The first sentence should work completely on its own, as if it were the only line anyone reads, because sometimes it is.
Bad: “That’s a great question! At our company, we believe every customer is unique, and…” By the time you get to the answer the reader has left and so has the AI.
Good: “Yes, I work Saturdays. Weekday slots fill faster, so book a week out if you can.”
Keep it short. Two to four sentences per answer is plenty. Use the words your customers use, not industry words. If people call it “the AC,” don’t write “HVAC climate system.” And write it like you’d say it, contractions and all. Robots are surprisingly good at spotting a page that sounds like a person, and people are even better at spotting one that doesn’t.
Both. Keep a main FAQ page for the general stuff, and put the service-specific questions on the service pages they belong to.
If your gutter cleaning page has its own three questions about gutter cleaning, that page answers more searches by itself. It’s the same reason I keep telling people their services need their own pages. One giant page with forty questions about everything is a junk drawer. Technically everything’s in there. Good luck finding the batteries.
Then add FAQPage schema markup to those blocks so search engines can read the question and answer pairs cleanly. I wrote about schema markup as a name tag for the robots if you want the plain English version. One honest note: Google cut way back on the fancy FAQ dropdowns in search results back in 2023, so don’t add FAQs hoping for those. Add them because they answer people, and because clean question and answer pairs are easy for any machine to understand.
Usually somewhere between eight and fifteen. Enough to cover what people really ask, not so many that it turns into a novel. If you’re padding it to hit a number, stop.
It can help you tidy them up, but the questions have to come from your actual customers. An AI will happily invent “What is your commitment to excellence?” and you’ll end up right back at the fake mustache.
Any time your prices, hours, service area or policies change, and give it a quick look every few months anyway. A wrong answer is worse than no answer, because now the AI is confidently repeating your old prices to strangers.
Your FAQ page should sound like you on a good day, answering the same question for the hundredth time with a smile you mostly mean. Write down what people ask, answer it straight, and spread it where it belongs. It’s a boring afternoon of work that keeps paying off for years, which is more than I can say for that slider on your homepage. If you want help turning your phone calls into a page that actually answers people (and makes sense to the robots too), tell me about your project and I’ll take a look.
The outreach Autobot I run for businesses, learning your voice and talking to the right people every day so more of them find you and reach out.
Card adds a 3.5% processing fee ($51.75). Venmo or Zelle is a flat $50.
Venmo @chenzowebguy ยท $50 ยท memo CZ-AUTOBOT-STARTER
Zelle 386-569-1227 ยท $50 ยท memo CZ-AUTOBOT-STARTER