FAQ Page Examples That Turn Doubts Into Enquiries

An FAQ page is a sales page wearing a cardigan. Its real job is clearing away the last few reasons someone has for not getting in touch.

When you study FAQ page examples that work, the same three jobs keep showing up.

• They remove doubt. Price, timing, process, guarantees, and "what happens next" get answered before the visitor has to ask.
• They cut repetitive admin. If your front desk answers the same parking question twelve times a week, put it online.
• They give search engines and AI tools clean answers. A plainly worded question with a direct answer underneath is the easiest kind of content for Google, ChatGPT, and similar tools to understand and quote.

A simple filter: if a question would never stop someone buying, booking, or calling, it probably doesn't belong. "When were you founded?" is trivia. "Do you charge for quotes?" is a decision.

Most small businesses only do one. In many cases the best setup is both: a central FAQ page for general questions, plus three to six focused questions on each important page.

The in-page version often does more selling. Someone reading your bathroom renovation page wants bathroom answers, not a link to a 40-question library. Our service page examples show where a short FAQ block earns its place.

These are illustrative patterns, not real businesses. The point is the question set, which matters more than the styling.

Notice what repeats across all seven. Money, time, risk, and process. If your FAQ page doesn't touch all of them, you've found your first rewrite.

Good FAQ pages look simple because the structure underneath does the work. Here's an order that tends to perform well.

1. A plain heading and one-line intro. "Questions about booking, pricing, and what to expect." Nobody needs a welcome paragraph.
2. Category groups. Three to five headings such as Pricing, Booking, The Process, and Aftercare. This lets visitors jump straight to their worry.
3. The deal-breaker questions first. Price and availability usually beat company history. Order by how often the question blocks a sale, not by how much you like answering it.
4. Answers that start with the answer. Yes, no, a number, or a timeframe in the first sentence. Context comes second.
5. Links to deeper pages. When an answer needs more than a short paragraph, summarise it and link to the full explanation.
6. A route for unanswered questions. A short line with your phone number or a simple form, so the page doesn't become a dead end.
7. A closing call to action. Once someone has read your answers, they're about as ready to enquire as they'll ever be. Give them the button.

If your FAQ has a contact route but no call to action, it's answering questions politely and then showing the visitor out. The contact page examples guide covers how to make that final step feel easy rather than formal.

Most weak FAQ answers sound careful. Every sentence is hedged, every number is missing, and the reader learns nothing new.

An FAQ answer should sound like your best staff member on a good day: direct, friendly, and specific enough that the customer stops worrying.

Here's a sample rewrite for a hypothetical renovation business. The first version is the one you see on a lot of sites.

• Before: "Pricing varies depending on a range of factors including scope, materials, and site conditions. Please contact us for a custom quote tailored to your needs."
• After: "Most of the bathroom renovations we quote fall in a typical range, and we show that range on our pricing page. The final number depends on layout changes, tiling, and fixtures. Quotes are free, and we'll usually have one to you within a week of the site visit."

The second version still doesn't promise a fixed price. It just gives the reader something to work with.

If writing isn't your thing, our breakdown of what website copywriting costs in NZ explains when it's worth paying someone to sharpen pages like this.

Making up questions at your desk is how FAQ pages end up full of "Why choose us?" You already have better material.

1. Your inbox and phone log. Repeat questions from the last three months are your first draft.
2. Lost quotes. Ask what made people hesitate or go elsewhere. Those objections are your most valuable answers.
3. Whoever answers the phone. Front desk staff know the real questions better than anyone.
4. Google's People Also Ask boxes. Search your main service and location and note what Google shows.
5. Reviews, yours and competitors'. Complaints about surprise fees or slow replies point to questions customers wish someone had answered earlier.
6. Your own analytics. Site search terms and Search Console queries show what people looked for when they arrived. Our GA4 guide for small business covers where to find that data without drowning in reports.

Twenty minutes with these sources usually beats an afternoon of brainstorming.

The accordion (click a question, the answer drops open) is the default layout for FAQ pages, and it's popular for good reason. It keeps long lists scannable, especially on a phone. It does come with a few traps.

First, accordions need to work for everyone. That means they open with a keyboard, announce whether they're expanded or collapsed to screen readers, and don't trap focus. The W3C publishes an accordion example in its ARIA Authoring Practices Guide that developers can build from, and native HTML details and summary elements cover a lot of the basics with less code. Our guide to website accessibility for small business covers the wider basics.

Second, don't hide everything. If you only have five questions, show them open. Making visitors click to reveal the one answer they came for is a small tax on their patience, and small taxes add up.

Third, match the layout to the list size.

• Under 8 questions: a simple open list or a single accordion works fine.
• 8 to 30 questions: group them under category headings with jump links at the top.
• 30 or more: add a search box, or consider splitting into a proper help centre with separate pages.

For years, adding FAQ structured data to a page could earn those expandable question dropdowns under your Google listing. That's over. Google narrowed FAQ rich results to well-known government and health sites back in 2023, and its FAQPage documentation now notes that as of 7 May 2026, FAQ rich results no longer appear in Google Search at all.

That doesn't make FAQ content pointless. FAQPage is still a valid Schema.org type, and other systems can still read it. What it means in practice:

• Don't add FAQ schema hoping for dropdowns in Google. They won't appear.
• Don't rush to rip out accurate markup either. If it matches what's visible on the page, it does no harm.
• Put your effort into the visible answers. Clear question-and-answer content is still the format AI Overviews, answer engines, and featured snippets find easiest to lift.

Google has also said there's no special markup required to appear in its AI features. Good structure, crawlable pages, and genuinely useful answers do the work. For the bigger picture, see our guides to schema markup for small business and how to rank in Google AI Overviews.

None of these will crash your website. They just leak trust, one visitor at a time.

• Fake questions. "Why are you the best plumber in town?" Nobody has ever asked that.
• "Contact us" as the answer. An FAQ that answers "How much?" with "Get in touch" has turned a question into a toll booth. Give a range, a starting price, or at least the factors that move the number.
• Sixty questions in one long list. Without categories, a big FAQ becomes a wall. People skim, miss their answer, and assume it isn't there.
• Answers that contradict other pages. Your FAQ says quotes take three days, your service page says 48 hours. Now the visitor trusts neither.
• Out-of-date information. Last year's prices or holiday hours suggest nobody is minding the shop.
• No next step. The visitor has their answers and nowhere obvious to go. Add the button.

Most of these are trust problems in disguise. Our guide to website trust signals covers the wider set of cues that make visitors comfortable enough to enquire.

An FAQ page is one of the cheaper pages to get right, because most of the value comes from knowing the questions. Here are rough, typical New Zealand ranges. Quotes vary with scope and who writes the copy.

A good FAQ page answers questions at 11pm that you'd otherwise answer on the phone at 8am. For more on how pricing information affects enquiries, the pricing page examples guide pairs well with this one.

We treat FAQs as part of the sales structure, not a page to fill in at the end. During planning we map the questions that block enquiries, then decide which belong on a central FAQ page and which sit beside a service, price, or booking button.

We're a young studio, so we won't pretend to have a wall of case studies. What we can do is show you exactly where your current site leaves questions unanswered. Request a free website audit and we'll point out the gaps, or compare our website packages if you already know you need a rebuild. Our concept demos are labelled as concept work, so you can see the standard without us passing them off as client sites.

The best FAQ page examples aren't clever. They're honest about price, clear about timing, calm about risk, and quick to point people toward the next step. That's a lot of selling for a page most businesses write in ten minutes.

Pull your questions from real customers, answer them like a person, and put the important ones beside the decisions they affect. Write answers good enough that a customer, a search engine, or an AI tool would happily quote them.

If you'd like a second pair of eyes on what your site isn't answering yet, start with a free audit. It's the quickest way to turn "people just aren't enquiring" into a specific list of fixes.