When I talk to DTC founders about their conversion friction, FAQ pages come up constantly. "We're rewriting the FAQ." "We added an accordion section." "We organised it by topic." There's always a next version of the FAQ page being worked on, and it always feels like productive work.
I spent a long time thinking the same way. The logic seems sound: if shoppers have questions that stop them buying, and you provide clear answers, the friction goes away. It's not wrong. The delivery mechanism is almost entirely broken.
Shoppers Don't Go Looking for Answers
of shoppers with a question navigate to the FAQ page (Forrester Research)
Forrester's research on customer self-service behaviour makes this stark. The overwhelming majority of shoppers who have a question do one of three things: they search on-site (and often find nothing useful), they look for the information on the product page itself, or they leave. The fraction who navigate to a dedicated FAQ or Help section is small enough to be irrelevant at the conversion-rate level.
The Real Problem
The FAQ page is not where the buying decision happens. The buying decision happens on the product page, in the moment of hesitation, when the shopper is still in purchasing mode. An answer that requires navigation to find might as well not exist. By the time a shopper goes looking for it, they've already half-decided to leave.
The Intent-Friction Gap
There's a gap between the moment a shopper forms a question and the moment they give up trying to find an answer. That gap is measured in seconds, not minutes. And within that gap, the question needs to be answered in the exact context where it arose. Not tucked away in a separate section the shopper has to choose to find.
The question about return policy should be answered on the product page, adjacent to the add-to-cart button. The question about sizing should surface when the shopper is looking at the size selector. The question about shipping speed should appear when they're weighing whether to complete the order today.
You don't need a better FAQ page. You need the answer to follow the shopper, not the other way around.
What This Means for How You Build
The practical implication is a shift in how you think about information architecture. Instead of asking "where do we put the answers?", ask "where does the question arise?". Map your friction points to product page moments, not to help-centre categories. Build for the context of the question, not the taxonomy of your support team.
This is harder than building a FAQ page. But it's the work that moves conversion rate. The FAQ page might give your support team fewer tickets to answer. It will not move your revenue needle. The contextual answer, delivered in the right place, at the right moment, will.