A practical checklist for FAQ pages
It comes up on almost every project, usually later than it should. Run through this the next time FAQ pages comes up.
Writing for the web is largely an editing job: the first draft is always longer than it needs to be. If two people in the business would answer this differently, that gap is the actual problem.
The checklist
- Answer the questions sales actually gets asked
- Do not use it to hide bad news
- Well-structured FAQs can win rich results
- Someone is named as the owner
- There is a date to review it again
Why it matters
Answer the questions sales actually gets asked. The cost of getting this wrong is rarely visible on the day it happens. Budget a little time for it every quarter and it never becomes a project of its own.
What this looks like day to day
Content is the part of a project most likely to be underestimated and most likely to delay a launch. 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
If any of that sounds like a description of your current setup, it is fixable.