FAQ pages: when they help the journey and when they hide answers

Key takeaways

An FAQ page helps the customer journey when it collects practical answers in one place for buyers and customers who look for them. It hides answers when it becomes the only place for information buyers need on service pages, such as prices, areas and timescales. Answer key questions where they arise first, then use the FAQ page as an organised back-up, grouped by topic and written in customers' words.

• Answer key questions on the page where buyers ask them first.
• Use the FAQ page as a back-up, grouped by topic.
• Write questions in customers' words, from your inbox.
• Keep answers visible: accordions can hide content from readers who scan.

Do small business websites need an FAQ page?

Many do, but not as the main home for important answers. An FAQ page is useful for practical questions that apply across services, such as payment, cancellation, areas covered and how to prepare, and for existing customers looking for help. It should not replace answers on service pages, because buyers reading a service page rarely go looking for a separate FAQ.

• How to design a website around your customer journey
• Turn the questions customers ask into your website journey

When does an FAQ page hide answers?

An FAQ page hides answers when information that affects a buying decision lives only there. A buyer on the kitchen fitting page who wants to know rough costs, areas covered and how long they will be without a kitchen will not think to visit the FAQ. If those answers are not on the service page, the buyer leaves with the question unanswered.

• Consideration stage: help buyers compare without leaving
• Answer buyer objections on your website before they ask

How should an FAQ page be structured?

Structure an FAQ page by topic, in the order customers need it: before buying, during the service, after the service, and payments. Use customers' own questions, keep answers short and specific, and link to the page with more detail. The GOV.UK content guidance discourages FAQs that duplicate content, which is a fair warning: each answer should add something or point somewhere useful.

• Group by topic: before, during, after, payments.
• Use the questions customers actually ask.
• Answer in 40 to 60 words, then link to detail.
• Put the most common questions first.
• Review quarterly against your inbox.

• Self-service on your website: let customers help themselves

Should FAQs be hidden in accordions?

Accordions keep long FAQ pages tidy, but they hide answers from people who scan, and some visitors never open them. Use them only when the list is long, keep question text specific so it carries its own meaning, and consider showing the most important answers open. On service pages, show short answers in full rather than collapsing them.

• Does Google index content hidden on mobile?

Do FAQs help search and AI answers?

Clear question-and-answer content can help, because buyers type questions into search engines and AI tools, and a direct answer is easy to quote. Google has limited where FAQ rich results appear, so do not write FAQs only for rich results. Write them for buyers; the search benefit comes from answering real questions well.

• How AI search is changing the website customer journey
• Schema markup for small business websites

When is an FAQ page not needed?

An FAQ page is not needed if your service pages already answer the common questions and you have few existing-customer queries. It is also a poor choice as a place to put content that does not fit elsewhere; that usually signals a structure problem worth fixing.

What does this look like in practice?

A pattern we see on small business sites: a long FAQ page answers prices, areas, timescales and guarantees well, and the service pages mention none of them. GA4 shows the FAQ page gets a small share of visits, mostly from existing customers. New buyers on service pages never see the answers.

Copying the key buying answers into short blocks on each service page, and keeping the FAQ for the rest, puts the answers in the journey. Across our client work we have seen a 2.4x enquiry rate from conversion changes of this kind. Global Bridge Labs (GBL) places each answer where the question is asked.

• See client work
• Website Design & Development for UK businesses

FAQ page checklist

• Collect real questions from your inbox and calls.
• Put buying answers on the service pages first.
• Group the FAQ page by topic and stage.
• Keep answers short, specific and linked.
• Avoid hiding key answers in collapsed accordions.
• Review against your inbox each quarter.

• Map your website content to the customer journey

Next step

If your best answers live on an FAQ page few buyers visit, they are not doing their job. We will show which belong on service pages and which can stay.