Signs it is time to revisit FAQ pages
It comes up on almost every project, usually later than it should. A few signals that FAQ pages is due some attention.
Content is the part of a project most likely to be underestimated and most likely to delay a launch. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.
The signals
- Nobody can say when it was last reviewed
- The answer depends on who you ask
- Answer the questions sales actually gets asked
- Do not use it to hide bad news
The practical version
Well-structured FAQs can win rich results. In practice this is a scheduling problem more than a technical one. Doing this properly once is usually cheaper than doing it approximately three times.
What this looks like day to day
Pages that answer a real question outlive pages written to fill a slot in a sitemap. Three things worth confirming about FAQ pages before you move on:
- Someone can say what the current setup is without going to look
- Answer the questions sales actually gets asked — and you know whether that is true here
- There is a way to tell whether the last change to this helped
None of this needs a rewrite. Most of it is a morning's work once someone decides to do it.