FAQ pages that are actually worth having

The typical FAQ page is written in one sitting by somebody guessing. The questions are invented to fill the format, and it shows: 'What makes you different from your competitors?', 'Do you care about quality?', 'Why should I choose you?'. Nobody has ever typed any of those into a search box or asked them on a phone call. They are marketing copy shaped like questions, and a visitor with a real concern reads three of them, concludes the page is decoration, and leaves.

The cost is not only the wasted page. A business that has an FAQ page believes it has addressed customer questions, which removes the pressure to find out what those questions actually are. The genuine concerns — whether the treatment hurts, whether you can come on a Sunday, whether the price quoted includes the consultation, whether you deliver to a particular PIN code — stay unanswered, and the people who had them leave without asking. The page has substituted for the work rather than doing it. This is why the honest starting position is that an FAQ page is worth having only if the questions on it came from outside the building.

You already have more of this material than any research exercise would produce. The support inbox is first: every email asking something is evidence, and the ones asking the same thing repeatedly are your list, in your customers' own words. WhatsApp threads are better still, because people write to a business there with the informality they use in a search box. The person answering the phone or standing at the front desk can usually recite the top five from memory if somebody thinks to ask them, and nobody ever does.

Search data adds the half your inbox misses. For a verified property, Search Console lists the actual queries that brought people to your pages, and the question-shaped ones are exactly this material — free, and specific to your business. The People Also Ask box shows question phrasings around your subject at a wider scale, and autocomplete extended with question words in front of your core term produces more. What none of the search sources give you is frequency you can trust, since volume figures are vendor estimates rather than published facts. That is fine here, because you are not sizing a market: you are collecting questions and then ordering them by how often you personally have been asked, which is knowledge you already hold.

An answer that avoids the question is worse than no page, because it demonstrates evasion at the moment the visitor was deciding whether to trust you. 'What does it cost?' answered with 'our pricing is competitive and tailored to your needs' tells the reader you did not want to say, and they now assume the reason is that it is expensive. If you can give a range, give the range and say what moves it. If you genuinely cannot, say why in a sentence — the cost depends on how many units are involved and here is what determines that — which is a real answer to a question you cannot price in advance.

The same applies to answers that are unfavourable to you. If you do not deliver outside your city, saying so plainly saves everybody an enquiry and earns more trust than an evasion. If a treatment involves discomfort, describing it honestly is what a nervous person is looking for. Short answers, in the words the question was asked in, without the industry vocabulary a customer does not use. Where an answer needs more room than a paragraph, that is a signal the question deserves its own page and the FAQ entry should be two sentences and a link to it.

This is the part where advice on the subject has gone stale in a way worth stating precisely, because a great deal of published guidance still recommends something that no longer does what it claims. FAQPage structured data was, for several years, a way to have your questions displayed underneath your search result as an expandable list. That presentation is gone. Google restricted it to government and health sites in August 2023, and then switched it off entirely on 7 May 2026, removing the supporting documentation shortly afterwards on 15 June 2026.

So the honest position: FAQPage markup no longer produces that display in Google Search, and any guide promising it is selling something that has been discontinued. The markup itself is not invalid and has not been withdrawn from schema.org — it remains correct, it is still read by other search engines and by assistants that consume structured data, and Google's own note said existing markup can stay on pages without causing problems. It is therefore not wrong to have. What is wrong is adding it in expectation of a Google presentation feature that was retired. The same caution applies to How-to markup, whose Google display was removed on 13 September 2023 for desktop as well as mobile. If you have either on your pages, leaving it is fine; adding it as a search tactic is not.

A single FAQ page collecting every question is the default and often the wrong shape. A visitor reading your pricing page with a question about pricing should not have to navigate elsewhere and scan thirty unrelated entries to find it. Answers belong where the question occurs to the reader, which usually means distributing most of them into the relevant pages and keeping a smaller page for the genuinely cross-cutting ones — payment methods, opening hours, service area.

There is a search consideration too, and it points the same way. A question with substantial interest behind it, where the answer runs to real depth, does better as its own page that can be found directly by someone searching that question, rather than as one entry among forty on a page about everything. The rough test: if somebody would plausibly type this question as a search and expect a full answer, it wants a page. If it is a detail someone needs while already reading a specific page, it belongs on that page. If it is a small general matter, the FAQ page is where it goes. Most businesses discover their FAQ page should be about a third its current length once the substantial questions have been moved out to where they belong.

Two failure modes finish this off. The first is a page that stops being true. FAQ answers embed specifics — prices, hours, turnaround times, service areas — and they are edited less often than any other page because nobody thinks of them as content. An answer stating a price from two years ago is worse than no answer, since a visitor who acts on it arrives with an expectation you will have to correct at the least convenient moment. Anything time-sensitive in an answer wants revisiting whenever the underlying fact changes, which in practice means putting the FAQ page on whatever list already prompts you to check your prices.

The second is padding. Once a business decides an FAQ page is good for search, the temptation is to grow it — questions invented to add entries, each answered thinly, until the page is long and mostly filler. This reverses the whole exercise. A page of eight questions people genuinely ask, answered properly, does the job. A page of forty, of which eight are real, buries those eight and tells any reader who scans it that the page was built for a machine rather than for them. The number of entries is not the measure of anything; whether each one came from a real person is.