Reddit Research
Using forums to find out how people actually describe their problems — in their words, not your category names.
Keyword tools tell you what people type into a search box. Forums tell you what they'd say to a friend.
The second is more useful, and it's free. People describing a problem to peers use different language from people searching — longer, more specific, and full of the context that makes content land.
This is a research method, not a marketing channel. Posting is a separate question with separate rules.
Read the research database guide · Request Your Free Systems Audit
What it's good for
The actual words. People say "I'm drowning in admin" rather than "operational inefficiency." Content written in the first register gets read by people who'd never search the second.
Problems before they're articulated as needs. Someone describing a frustration hasn't yet decided what would solve it. That gap is where useful content lives.
Objections, stated plainly. Forum threads contain the reasons people don't buy, written without the politeness of a sales conversation.
What didn't work. "I tried X and here's what happened" is the most useful content on any forum, and the hardest information to get any other way.
Whether a problem is real. A problem that appears repeatedly across months is real. One that appears once was an individual's bad week.
What it's not good for
Representative data. Forum users are not a random sample. They skew toward people who have problems and like discussing them online.
Quantifying anything. Frequency of mentions is a weak signal about frequency in the world.
Direct quotes in your content. Without permission, don't. Paraphrase the pattern, never reproduce a specific person's post.
The method
1 · Find where your people actually are
Not the obvious large communities — the specific ones. Trades, tools, business sizes, regions.
Search for your topic and see which communities keep appearing. Smaller, specific communities are more useful than large general ones, where everything is diluted.
2 · Read before you search
Spend an hour reading the most active threads in a community before searching for anything specific. You need to know what normal looks like there before you can recognise signal.
This also tells you what the community will and won't tolerate, which matters if you ever post.
3 · Search deliberately
Useful search patterns:
| Search for | Finds |
|---|---|
| "how do you handle" + topic | Process questions, current workarounds |
| "I tried" + tool or approach | Real experience, failure modes |
| "is it worth" + thing | Objections and hesitations |
| "anyone else" + frustration | Problems people think are theirs alone |
| "finally" / "solved" + topic | What actually worked |
Sort by top within the last year for durable themes. Sort by new to see what's current.
4 · Read the comments, not the posts
The post is one person's question. The comments are the community's accumulated answer, including the disagreements.
Disagreements are the most useful part. Where experienced people disagree, there's genuine complexity, and content that acknowledges it earns trust that confident content doesn't.
5 · Record patterns, not posts
In your research database, one note per pattern:
Pattern: People describe the problem as [X], not [your category name]
Appears across: [how many threads, over what period]
Typical phrasing: [paraphrased, not quoted]
Common attempted fixes:
What they say goes wrong:
Paraphrase. Never store or reproduce someone's words as if you have permission to use them.
6 · Look for the recurring unanswered question
The highest-value finding: a question asked repeatedly that never gets a good answer.
That's a piece of content with demonstrated demand and no competition.
Reading signal correctly
Repeated across time beats upvoted once. A problem raised every few months for two years is real. A single popular thread may have been a moment.
Pay attention to the thread where everyone disagrees. Consensus is usually already documented elsewhere. Disagreement means the question is live.
Note what gets dismissed. If every thread about a solution includes someone saying "that doesn't work for small operations," that's a positioning insight.
Watch for the frustrated expert. Someone who clearly knows the field, explaining the same thing again with visible impatience, is pointing at a genuine information gap.
Turning it into content
A good forum-derived piece usually has this shape:
The problem in their words. The reader recognises themselves immediately, because you're using the phrasing they'd use.
Why the standard advice fails. You've read fifty threads of people trying it.
What actually works, including the conditions where it doesn't.
The objection, addressed. You know what it is because you've read it stated plainly forty times.
That last element is what distinguishes forum-informed content from content written from assumptions.
If you participate
Separate activity from research, and treat it as a long game.
Read the community's rules. Most have explicit positions on self-promotion, and they're enforced.
Answer questions properly, without linking. Build a record of being useful first.
Only link when it genuinely answers the question, and sparingly.
Disclose who you are when relevant. Being found out is worse than being known.
Accept that it's slow. Communities are good at detecting people who turned up to extract value, and the penalty is permanent.
If that sounds like more than you want to invest, use it purely as research. That's a legitimate choice and it's where most of the value is anyway.
A sustainable cadence
Not continuous. An hour a month in your two or three main communities, with findings going into the research database as patterns.
Over a year that's twelve hours, and it produces a map of how your market describes its own problems that no keyword tool can give you.
Keyword tools give you the search box. Forums give you the conversation. Write for the second.
Want content built on what your market actually says?
A free systems audit covers your content process from research through to publication.