Most FAQ pages are written the same lazy way: someone on the team sits down and imagines what a visitor might want to know. The result is usually five questions that are technically accurate and practically useless, because they answer what the founder thinks matters instead of what real people are actually confused about.
Research the Questions Before You Write the Answers
There are two sources that tell you the truth, and neither one is your own imagination. The first is search data. Tools like Answer the Public take a topic or product category and surface the actual questions people are typing into Google around it — real phrasing, real intent, sorted by how often people ask it. Run your product category or core problem through it and you'll usually find questions you'd never have guessed to include.
That's not just useful for the FAQ content itself. Questions with genuine search volume are also small, low-competition SEO opportunities in their own right, especially phrased as a question and answered directly on the page.
The Second Source: Your Own Support Inbox
The other place real questions live is wherever your customer service or sales conversations already happen — email, chat logs, sales call notes. Go do an actual audit. Pull the last month or two of support tickets and sales questions and tally what comes up repeatedly. This is usually more valuable than the search-data research, because it's not just what people wonder about in the abstract, it's what actually stops them from buying or actually confuses them once they're using the product.
If the same question shows up three or more times in your support inbox in a month, it belongs on your FAQ page. That's not a guess, that's a pattern your own customers already handed you.
Adapt, Don't Copy
Once you've gathered questions from both sources, the work is adapting them to your specific product and niche, not just listing generic industry questions. A question like "how does pricing work" needs an answer specific to your actual tiers and terms, not a vague placeholder. Generic answers to specific-sounding questions are almost worse than not having the question at all, because they signal the page wasn't actually written with care.
Write Answers Like You're Actually Answering, Not Marketing
An FAQ answer isn't a second chance to run your sales pitch. It's a chance to be genuinely useful in a way that makes the reader trust you more. If the honest answer to "does this work with X" is "not yet, but it's on our roadmap," say that. A dodgy non-answer erodes more trust than an honest limitation ever will.
Keep It Updated
An FAQ page isn't a one-time project. As your product changes, your support patterns change too — new features raise new questions, old limitations disappear. Revisit your support inbox every quarter or so and check whether the FAQ still reflects what people are actually asking now, not what they were asking six months ago.
Frequently Asked Questions
How many questions should be on an FAQ page?
Enough to cover the real recurring objections, usually somewhere between six and twelve. Beyond that, split into categories or move deeper questions to a dedicated help center, so the main FAQ page doesn't turn into an overwhelming wall of text.
Should FAQ content also live in a help center or knowledge base?
Ideally both, with different depth. The website FAQ handles pre-purchase objections briefly. A help center or knowledge base handles deeper, post-purchase how-to questions in more detail for existing customers.
Does FAQ content actually help SEO?
Yes, especially when questions are phrased the way people actually search, and especially when marked up with FAQ schema so search engines can potentially surface them directly in results.
What if our support team says there are no repeated questions?
That usually means nobody's actually tracked it yet, not that the pattern doesn't exist. Pull real ticket data for a month before concluding there's no pattern — it's almost always there once you look.
Is Your Startup's Messaging Working?
Take the free Mission & Marketing Scorecard — 5 minutes to find out exactly where your messaging is strong and where it's costing you conversions.
Take the Free Scorecard →Need Help With Your Startup's Messaging?
If your website or pitch isn't landing the way it should, I can help you figure out why. Let's take a look.
Work With JT →