How to write an FAQ page customers actually read.

What a useful FAQ page does

Many FAQ pages are written by the business, for the business: "Why choose us?", "What makes us different?". Nobody asks those. A useful FAQ page is the opposite: the questions customers really ask before they book, buy or turn up, in their words, each answered in its first sentence.

It saves time on both sides. Every question answered on the page is a call or an email your team does not have to answer again, and a visitor at 10pm gets the answer without waiting until morning.

It also has limits. People open an FAQ page when they cannot find something, so the answers that decide a purchase, such as the price or what is included, belong on the service page first. The FAQ page holds the rest, and points to the service pages for detail.

Where the questions come from

Do not make the questions up. Collect them for two weeks from everywhere customers ask:

• The phone: a notepad beside it, or a shared note, with each question written down as the caller put it.
• Email and the website form: search for question marks, "do you", "can I" and "how much".
• Chat and social messages, including Instagram and WhatsApp, if customers write to you there.
• Reviews: a complaint often hides a question you never answered, such as "nobody told me the car park was so far away".
• The front desk, or whoever meets customers on the day: what do people ask when they arrive?
• Google Search Console: the searches containing question words that already bring visitors to the site.

Write each question exactly as the customer put it. "Can I bring my dog?" is the question. "What is your pet policy?" is how a business rephrases it, and few customers would type that.

Keep a tally of how often each comes up. Ten people asking about parking is a question for the top of the page. One person asking whether a coach can park outside is probably a question for a phone call.

Sort the questions before you write

Before you write a single answer, sort the questions into four piles:

• Questions that decide a purchase: the price, what is included, how long it takes, whether you cover their area, when the next slot is. Answer these on the service page, and give a short answer on the FAQ page with a link.
• Practical questions that apply across your services: parking, access, payment methods, cancellations, what to bring, whether children are welcome. This is what the FAQ page is for.
• Questions caused by a problem you can fix. If people keep asking "did you get my form?", the fix is a clearer message after the form is sent, not an FAQ entry.
• Questions that need a person: a quote for one particular job, a question about someone's own health, legal or money situation, a complaint. The answer says how to ask and who replies, and does not attempt the answer itself.

The fourth pile matters most in clinics, law firms and financial services, where a general answer can be read as advice for one person. "Can you tell me whether my knee needs surgery?" needs "We cannot say without seeing you" and a link to book an assessment, not a paragraph about knees.

Answer in the first sentence

Someone scanning on a phone reads the first line of an answer and moves on if it answers them. So every answer follows the same order:

• The first sentence is the answer: yes, no, the day, the time, the price or the rule.
• Then the detail or the exception, in a sentence or two.
• Then a link to the page with more, or the way to book or ask.

Here is the same question answered twice by a physiotherapy clinic:

• Weak: "Do I need a referral?" "Referrals can be an important part of your care, and we work closely with local doctors and insurers to make your experience as smooth as possible."
• Strong: "Do I need a referral?" "No. You can book with us directly. If you are claiming on health insurance, check whether your insurer needs a referral, and bring it to your first appointment."

Use the customer's words in the answer as well as the question, so someone who searched for parking sees the word parking in the reply. Keep each answer short enough to read on one phone screen. If it needs more, the topic deserves its own page, and the FAQ answer becomes a short version with a link.

Say the awkward answers as plainly as the good ones. A cancellation fee, a minimum spend or a waiting list belongs in the FAQ, because customers who find it later feel tricked. The wording for a fair policy is in how to write a no-show and cancellation policy.

FAQ questions for three trades

Each set below is the kind of list that comes out of two weeks of collecting. The answers have to come from your own facts.

A wedding and event venue:

• Can we bring our own caterer?
• What time does the music have to stop?
• Is there a minimum number of guests?
• Can we look round before we book?
• Where can our guests stay nearby?
• What happens if it rains on the day?
• How much is the deposit, and can we get it back?

A car repair garage:

• Can I wait while you do it?
• Will you call me before doing extra work?
• Do you work on electric and hybrid cars?
• Can I bring my own parts?
• Do you have a courtesy car?
• Will a service here affect my manufacturer's warranty?

A dog groomer:

• Do you take nervous or older dogs?
• Can I stay with my dog?
• What happens if my dog's coat is matted?
• How long will my dog be with you?
• What should I bring?
• Do you groom cats?

Notice what is missing from all three lists: "Why choose us?" Nobody asks it.

Group and order them by the moment they come up

Group the questions by when customers ask them, not by department or by service:

• Before booking: price, availability, the area you cover, what is included.
• Getting ready: what to bring, parking, access, forms to fill in beforehand.
• On the day: how long it takes, whether they can wait, who they will see.
• Afterwards: paying, aftercare, warranties, rebooking and how to complain.

Inside each group, put the most-asked question first, using your tally. If one group runs longer than a couple of phone screens, split it, or move the answers that concern one service to that service's page.

Give each group a short heading, such as "Before you book" or "On the day", so a visitor can skip to their moment.

Make it easy to scan on a phone

On a phone, a long FAQ page is a long scroll. Make one answer easy to find:

• Show every question. If the page is long, let each answer open with a tap.
• Make each question a heading or a real button, so a screen reader can jump between them and say whether an answer is open.
• Put a list of the groups at the top that jumps to each one.
• Give each question its own link, so your team can send a customer straight to one answer.
• End with how to ask anything else: the phone number, the form and when you reply.

Keep the answers as text on the page, never in a PDF or a slideshow. And do not hide the phone number to push people through the FAQ first. Some customers will always want to ask a person, and they are often the ones about to book.

Put the deciding answers on the service pages too

Think of the FAQ page as an index. The answers that decide whether someone books belong where they are deciding: on the service page, near the button. A visitor reading about a full groom should see "Do you take nervous dogs?" answered right there, not on a page they may never open.

A simple rule keeps it tidy. If a question comes up about one service, answer it on that service's page. If it comes up about all of them, answer it on the FAQ page. Where it belongs in both places, write the full answer once and link to it from the other, so the two never disagree.

Booking confirmations and reminders are a third home for the practical answers. Parking, what to bring and how to move the appointment are most useful the day before, which is when a reminder arrives. Booking and calendar automation covers sending them.

What an FAQ page does in Google now

For years Google showed some FAQ pages in its results with the questions listed underneath, which searchers could open without visiting the site. That has ended. In 2023 Google limited the display to well-known, authoritative government and health websites, and its documentation changelog says the feature no longer appears in Google Search from 7 May 2026.

So an FAQ page no longer earns extra room in the results. It can still be found when someone searches a question it answers well, the same way as any other page, and plain questions like "do you take nervous dogs" are the kind people type.

If your site already has FAQ markup, there is no need to rush to remove it: when Google limited the display in 2023, it said structured data it does not use causes no problems. Spend new time on the answers instead. Do not add questions only to catch searches. Pages written for search engines rather than customers tend to read badly to both.

How Google's AI answers use pages like this is covered in how a local business shows up in Google's AI answers.

The same answers serve your team and your chatbot

Once the answers are written and approved, use them wherever the same questions arrive:

• Whoever answers the phone keeps the page open, so every caller hears the same answer.
• Saved email replies start from the FAQ answers and are edited for each person.
• New staff read the page in their first week. It is the quickest way to learn what customers worry about.

It is also what a chatbot needs if you add one. A chatbot that answers only from information you approve works from exactly this: questions in customers' words and answers you have signed off. The AI chatbots we build answer from that kind of source, say so when the answer is not there and pass the question to your team.

When an answer changes, change it once at the source and everywhere it is used. Two versions of the cancellation policy are worse than none.

Keep it current

An FAQ page goes wrong quietly. Prices rise, a service stops, the parking changes, and the page still says what was true last year. Give one person the page, and make these habits:

• Change an answer on the same day a price, policy or service changes.
• Once a month, read the questions customers asked by phone, email and chat, and add any that came up more than once.
• Remove questions nobody asks any more, such as a notice about building work that finished long ago.
• Check that each answer matches the booking tool, your terms and your Google Business Profile.
• Date anything seasonal, such as holiday opening hours, and take it down when the season ends.

Mistakes that make FAQ pages useless

• Questions nobody asks, written to sell: "Why choose us?"
• Answers that start with marketing and reach the point in the third sentence.
• "Please contact us for more information" as the whole answer.
• Bad news hidden in the terms, such as a cancellation fee the FAQ never mentions.
• Answers that disagree with the service page or the booking tool.
• One long page in a PDF.
• Holiday hours from last year still at the top.
• A page written once at launch and never read again.

Where to start

If you have no FAQ page, or one nobody reads, work through it in this order:

• For two weeks, write down every question customers ask, in their words, with a tally mark each time one repeats.
• Sort the questions into the four piles, and move the answers that decide a purchase onto the service pages.
• Write the rest with the answer in the first sentence.
• Group them by the moment they come up, most-asked first.
• Ask the person who answers your phone to read the page and add what is missing.
• Put a monthly reminder in the calendar to add the new questions.

Then watch the questions that still reach you. If people keep asking something the page already answers, the answer is in the wrong place, or it is written in your words rather than theirs. Move it or reword it, and count again next month.