The real cost of ignoring FAQ pages
The version of this that works is simpler than the version most people imagine. Nobody bills you for neglecting FAQ pages. The cost shows up somewhere else.
Pages that answer a real question outlive pages written to fill a slot in a sitemap. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.
Where the cost lands
- Time spent on work that should not have been necessary
- Enquiries that quietly never arrive
- Answer the questions sales actually gets asked
- Rework, once the problem is finally visible
Do not use it to hide bad news. The reasoning matters more than the rule, because the rule has exceptions. Anything you cannot measure here, you are deciding by taste, which is fine as long as everyone knows it.
A reasonable first step
Well-structured FAQs can win rich results. The reasoning matters more than the rule, because the rule has exceptions. It is the sort of thing that looks like polish right up until it costs you an enquiry.
In practice
Writing for the web is largely an editing job: the first draft is always longer than it needs to be. Three things worth confirming about FAQ pages before you move on:
- Someone can say what the current setup is without going to look
- Do not use it to hide bad news — and you know whether that is true here
- There is a way to tell whether the last change to this helped
Worth checking on your own setup before it becomes someone else's problem to fix.