FAQ pages, and whether to have one
A dedicated FAQ page collects questions away from the pages where people ask them. That is convenient to build and usually the wrong place for the answers, which belong beside the thing they are about.
Learn
Short answer
Questions work best on the page where the doubt arises: pricing questions on the pricing page, process questions on the service page. A dedicated FAQ page suits genuinely cross-cutting questions and acts as a hub. Answering the same question in both places splits the value.
The case against a single page
A visitor with a question about price is on the pricing page. Sending them to a separate FAQ page to find the answer adds a step at the exact moment they were close to acting, and many will not take it.
It also weakens both pages. The pricing page loses the answer that would have resolved the doubt, and the FAQ page carries an answer out of the context that made it meaningful.
Our page on FAQ content covers finding the questions worth answering. This page is about where the answers should physically sit.
It also hides the strongest material. The questions people ask before buying are the most persuasive content a business has, and filing them away from the commercial pages wastes them.
What belongs on a distributed basis
Anything tied to a specific page. Price questions with the price, timing questions with the service, coverage questions with the service area, access questions with the booking route.
That placement means the answer arrives when the doubt does, which is what actually converts. It also makes each page more complete, so a visitor who lands there from search finds everything they need.
Structured markup can state the question and answer relationship where a real set exists. Our page on structured data covers when that is appropriate.
What a dedicated page is genuinely good for
Cross-cutting questions that belong to no single page. Payment methods, insurance, what happens if you are not home, how complaints are handled, whether you work weekends.
It is also useful as a hub: a page listing the common questions with links to wherever each is answered properly. That version adds navigation without duplicating anything.
And it suits businesses whose customers genuinely browse questions, which is more common in regulated services where people are researching obligations rather than shopping.
It is useful internally too. A single list of what customers ask is the clearest brief for whoever writes the rest of the site, even where the answers end up published elsewhere.
How to decide
The list below settles it for most businesses. Work through the questions you actually receive and put each one where it belongs rather than defaulting to a single page.
- Tied to a price, a service or an area, put it on that page
- Asked before anybody chooses a service, a dedicated page works
- Asked by existing customers, it belongs in support
- Legal or policy, it belongs with the terms
- Asked constantly, it deserves a page of its own
- Only ever asked once, leave it out
- Answered in two places, delete one
Never answer it twice
Duplicating a question and answer on a service page and an FAQ page splits whatever either would have earned and creates two pages competing for the same query.
Our page on duplicate content covers the mechanics. The practical rule is one answer, in one place, linked from anywhere else it comes up.
Where a question is genuinely relevant in two places, put the full answer where the doubt is strongest and a one-line summary with a link in the other.
Structuring the page if you keep one
Group by subject rather than listing everything. A page of forty ungrouped questions stops being scannable, and people give up rather than searching it.
Use real heading tags for the questions with levels in order. Our page on heading structure covers why styled text does not carry the same meaning.
Answer in the first sentence, because that is the part a scanning reader and an answer engine both take. Somebody scanning a question list is looking for an answer, and burying it under context makes the whole page useless to them.
Keeping it honest
FAQ answers state things flatly, which makes them the fastest part of a site to become wrong. Prices, hours, policies and timescales all drift and nobody rereads the FAQ.
Review it on a schedule, and delete freely. A question nobody has asked in two years is taking attention from the ones people do ask.
Our page on keeping content current covers the routine, and an FAQ section is the strongest argument for having one.
Questions people ask
Should I have a dedicated FAQ page?
Only for cross-cutting questions that belong to no single page, or as a hub linking to answers elsewhere. Questions tied to a price, service or area belong on that page, where the doubt actually arises.
Can I answer a question in two places?
No. That splits whatever either page would have earned and creates two pages competing for the same query. Put the full answer where the doubt is strongest and a one-line summary with a link elsewhere.
How should an FAQ page be structured?
Grouped by subject, with real heading tags in order, and each answer given in its first sentence. A page of forty ungrouped questions stops being scannable and people give up rather than searching it.
How often should it be reviewed?
On a fixed schedule. FAQ answers state things flatly, which makes them the fastest part of a site to become wrong, and nobody rereads their own FAQ. Delete questions nobody asks any more.
Keep reading
See your website built from a conversation
15-day free trial. Card required. Cancel before day 15 and you pay nothing.