A well designed FAQ page takes the questions your customers genuinely keep asking, puts the most asked one first, and answers each one in plain words with the answer sitting in the very first sentence, so a visitor gets what they came for inside a minute and never has to write to you at all. That is the whole design brief, honestly. The rest of the subject is the distance between reading that sentence and getting the thing built, and nobody crosses that distance through definitions. People cross it the way the man this page follows crossed it, standing at his packing table on a Wednesday evening, typing out the very same shipping answer for the ninth time in a month and feeling his patience going somewhere thin.
He prints and frames pictures and sells the whole of it online, a one-man shop with a part-timer on Fridays. The questions that reach him hardly change from one week to the next. How long does delivery take. Will my own photo print alright at that size. What happens if the glass arrives cracked. He could answer them half asleep, and in a sense he was doing, on account of the answering having long ago stopped involving any thought, the fingers doing the whole of it while his mind sat somewhere else entirely. So one Saturday he went and built himself a FAQ page, and made most of the mistakes there are to make on the way to a good one, which is exactly why he is useful to follow. This page walks through his drafts one at a time. Where the questions come from, what order they sit in, what the page itself should look like, how the answers want writing, and then the part at the end about what no FAQ page will ever fix for you, because somebody should say that part out loud too.
Where do the questions on a FAQ page come from
His first draft never asked a single question his customers ask, and this is the mistake to get out of the way before any talk of layout, since no amount of clever layout goes and rescues a page built on the wrong questions. He sat down with a blank page and wrote what sounded professional to him. What makes our framing different. Which woods do we use. A question about his journey as a maker, which nobody in the history of the shop has ever asked him, not once. The draft read fine to him and would have helped nobody, and the reason is plain enough when you say it out loud, the questions came out of his own head instead of out of his inbox.
The real list was sitting in his sent-mail folder the whole while, mind you. Two months of replies, and when he finally went and counted, the tally told him things he half knew and had never once acted on. The shipping question came up more than everything else put together, or near enough. Sizes and photo quality after that, maybe a dozen times each, then returns and cracked glass a small handful, and after those a long tail of one-off questions that no page on earth needs to carry. The top dozen from that tally, that is the FAQ page. Not the questions you would like to be asked. The ones you are actually asked, counted honestly, and if the counting embarrasses the shop a little, well, fair is fair, the page was never for the shop anyway.
You can run the very same exercise your own self in an hour, to be honest with you, open the sent folder and go back two months, three if the shop is quiet, and tally what people actually wrote in about. Let the tally set the list, however it comes out.
What order should the questions go in
Most asked, first. He got this wrong in his second draft, and the way he got it wrong is common enough to be worth describing properly. He ordered the page the way the shop looks from inside of it, opening with the framing process he is proudest of, and the shipping question, the one actually filling his inbox, sat ninth on the page, below the fold on any phone made this decade. A customer with a shipping worry scrolls past eight entries she never asked about on the way to her own, and somewhere around the fifth she stops scrolling and writes in instead, and now the page has gone and cost him a reply rather than saving one.
The same rule holds again inside each answer, funnily enough. First sentence answers, the rest of it explains. His delivery entry eventually opened with, three to five working days inside the UK, and only then came the detail for whoever wanted detail, the courier he uses, the tracking email, the bit about larger framed pieces travelling in wooden crates. A person in a hurry reads one sentence and leaves happy. A person with a stranger situation keeps reading and finds their situation waiting further down. Both got served without writing in, and that, near enough, is the whole trick of ordering, on the page and inside every answer on it.
What should a FAQ page actually look like
Draft one was a single long page. Question in bold, answer underneath, next question after that, and a link in the site footer where every customer alive already knows to go looking the minute something arrives cracked. And here is the thing the template sellers will not tell you, for a list of a dozen questions that plain shape is not the beginner option, it is the correct one. Everything sitting open on one page means the browser's own find function works, means the page prints, means a person can skim the lot in under a minute. He should have stopped there for a good long while.
He did not stop there, on account of his nephew, who looked at the page during a half-term visit and pronounced it old fashioned. So draft three folded every answer into an accordion, the collapsing kind where you tap a question and the answer opens underneath. Accordions look tidy, no two ways about it, and on a phone a long list folds down into something a thumb can manage. But a folded answer is invisible until somebody opens it. Invisible to a skimming eye, and invisible to the find function too, and he sat and watched a friend hunt for the returns answer by tapping questions open one at a time, like a man checking doors. If the list is short, leave the answers open. If you love the folded look anyway, have it, only know what it is costing you.
The third shape he never needed for himself, but he saw it on the bigger shop he buys packaging from, and it is the right shape at the right size. The grouped page, orders under one heading, delivery under another, returns under a third, each group holding its own small handful of entries so a visitor's eye has somewhere sensible to start. That layout starts earning its keep somewhere past twenty questions, maybe thirty, mind you, once a single list has turned into hunting. Past that again sits the search-first page, a search box up top with the questions behind it, and for a FAQ page that is usually the sign it has stopped being a FAQ page at all, a point this page comes back to before the end.
How do the answers themselves want writing
The best writing advice he ever got on this arrived sideways, from a customer who replied to one of his emails with, thanks, that is all I wanted to know. All I wanted to know. A person reading a FAQ entry is carrying exactly one worry. The answer that serves them says the thing, in roughly the words they used when they asked it, and then stops.
Plain words, always, because the customer's words were plain. He had a draft entry that said items damaged in transit are eligible for replacement subject to photographic verification, and the entry that finally worked said, if the glass arrives cracked, send us a photo and we will send a new frame out. The same policy, every bit of it, in half the length, with no lawyer anywhere in the sentence.
Two things kept wanting to creep into his answers, and both had to go. The first was selling. An answer about delivery that pauses halfway to mention the premium frame range reads terribly to somebody who only wanted a date, so the marketing stays out, full stop. The second was length. His entry about preparing photo files grew steps, then a screenshot, then more steps, and an answer that has grown steps and screenshots has outgrown the page its self. It wants to be an article of its own somewhere with room to breathe, which again is the thread the next section picks up.
And answers go stale quietly, which deserves saying while we are here. The page he built in spring said free UK shipping. The courier put prices up in the autumn, the shop started charging on small orders, and the page went on saying free for six more weeks. Every complaint that arrived out of that gap between the page and the truth was sharper than any question the page had ever saved him, and he had no answer to them, since the customer was simply right. Somebody has to own the page, and whoever owns it reads it their own self once a season, the whole of it, against whatever the shop is actually doing that week.
What a FAQ page will not do for you
A fair design guide owes you the limits as well, so here they are, plainly said.
It will not fix a policy people hate. If returns cost the customer postage and the mail about it comes in angry, an entry stating the rule up front means people find out sooner, it does not mean they mind it less. The page states the policy. Fixing the policy is a different job, and no amount of page design goes and does that job for you.
It will not empty the inbox either, and it was never supposed to. What a well designed page does is thin the inbox out, quietly, over a month or two, until one day he noticed the shipping question had more or less gone from his life. The strange ones kept coming, the photo of a wall with a question about which size would suit it, the wedding print needed by a Thursday, and those were the emails he was glad to have, since those are the ones where being a small shop with a person inside it is the entire advantage.
And it will not scale forever. That is the limit that sneaks up. Somewhere past a couple of dozen questions the single page turns into hunting, the grouped layout buys you some time, and then individual answers start wanting steps and screenshots and pages of their own with a proper search over the top, and at that point your FAQ page has gone and turned its self into a knowledge base without asking permission. When that day comes, this is the one place we will mention that the knowledge base software we build over here at Maxdesk ships on every plan including the $0 one, with no per-agent charge on any of them, so the page growing up costs you nothing extra, though fair warning while we are being honest, the free workspace shows supporting ads and puts Maxdesk branding on outbound email. If your FAQ page is already bursting at the seams, the honest next step is knowledge base software, run on the same sent-folder method you started with.
The questions people ask about FAQ pages themselves
How many questions should a FAQ page have
Fewer than you fear. The sent-folder tally usually hands you a top ten or twelve that cover most of the mail on their own, and a page carrying twelve honest answers serves people better than a page carrying forty, since the extra thirty mostly stand in the way of the one entry a reader came for. When genuine demand pushes the count past twenty or so, group the page under a few headings, and when it pushes well past that, go back and read the section above this one, because the page is telling you something.
Do FAQ pages help with search rankings
They can, though only when the page was written for customers first. A question phrased the way real people type it, with the answer landing in the first sentence, can surface for the long tail of question searches, and the AI answer engines lift from exactly that shape as well, the plain question with the plain answer sitting under it. A page stuffed with phrases for the machines reads stuffed to the human, and the human is the one deciding whether to order a frame from you. Write for the person with the worry and let the engines take what they take.
Should the answers be collapsed or left open
Left open, if the list is short enough to skim, and after an honest tally it usually is. Collapsing into an accordion is defensible on a phone once a list has grown long, only remember what the folding costs, the find function stops seeing your answers and so does a skimming eye. His page ended up open, all fourteen entries of it, and nobody has ever once complained that it looks old fashioned, except the nephew, who does not buy frames anyway.
Where his page ended up
Fourteen questions on one long page, most asked first, every first sentence doing the answering, and a read-through once a season with the shop's current prices open in the next tab. Building it took him one afternoon, and most of the afternoon went on the tally, which is as it should be, since the tally was the part that made the page belong to his shop and not to whichever template he happened to start from. His evenings did not empty out, they quietened, and the mail still arriving is mail he does not mind. Yours is an afternoon away too, honestly, and the sent folder is already holding each bit of it.