I get asked to add frequently-asked questions pages to websites. I do my best to talk my clients out of this.
FAQs are a blight. Once an FAQ section takes hold, it demands regular feeding — which comes at the expense of the rest of the site. After all, the easiest way to deal with anything that comes up is to just toss it in the FAQ and be done with it. If organizing the content on your website doesn’t matter, then, why not just have everything on a single page? Why even bother putting things into a sensible order? Just make people read the ever-growing list of FAQs and be done with it.
To your visitors, FAQs are a frustrating game of hide-and-seek.
Still need convincing?
- Do FAQs reflect reality? We’ve all seen too many FAQs that should be called Questions We Frequently Wish Our Customers Were Actually Asking Us.
- “FAQ” is an internally-focussed term when most websites are meant for external audiences. The name itself is written from the perspective of the website owner, not the visitor. That should set off alarms bells, because as the publishers/owners/authors you are not its audience. This is one of the most fundamental aspects of building and maintaining an effective website.
- FAQs shift the effort onto the visitor. Everyone says they want a user-friendly website, but FAQs are inherently user-hostile — not in terms of their actual content, of course — but because of the extra effort their structure imposes on visitors.
- What an FAQ page conveys to your visitors: “We could’ve answered your shipping question on the Shipping page, but it was easier for us to add it to the FAQ than to edit the copy on the Shipping page; your wasted time, frustration, and inconvenience do not matter to us.”
- FAQs hide bigger, underlying problems. FAQ pages are especially appealing to those hoping to mask deeper organizational, structural, technical, or policy problems. These can appear in the form of confusing copy, outdated/inconsistent/inaccurate information, or internal governance issues (e.g. who is in charge of what internally). Dumping the costs of these issues on visitors (by taking shortcuts like FAQ pages) may seem acceptable, but it’s an opportunity your competitors will thank you for.
How should you handle these questions?
Of course the content and layout of your home page (or your customer support page, your products pages, etc.) should be informed by the questions you’re asked. Give priority to the most common and most important issues, near the tops of those pages. Rewrite or reorganize the pages to highlight the answers.
If something isn’t important enough to belong in the right context, in the most appropriate place — and the only place it seems to fit is an FAQ page — then it’s time to question whether it needs to be there at all.
Eliminating FAQs — by putting answers where they belong — is a great way to simplify a site.