Community threads carry weight in AI answers about software because they contain comparative language that vendor sites never produce. Google says so in its own words: it has access to Reddit’s Data API and will “display, train on, and otherwise use” that content.
You cannot write that kind of sentence about yourself, and no amount of blog output substitutes for it.
Why does AI read community threads at all?
Because at least one major platform pays for structured access and says what it does with it. Google’s February 2024 announcement states that “Google now has access to Reddit’s Data API, which delivers real-time, structured, unique content from their large and dynamic platform,” and that it will use this “to better understand Reddit content and display, train on, and otherwise use it in the most accurate and relevant ways.”
Read the verbs. Display, and train on. That is both halves of how an engine can know about you: retrieval today, and memory in the next model generation.
Note also what the same announcement clarifies, that the partnership “does not change Google’s use of publicly available, crawlable content for indexing, training, or display.” The API is an addition to ordinary crawling rather than a replacement, so community content was already reachable and is now also structured.
What do threads contain that your own site cannot?
The comparison. This is the whole mechanism and it is worth being precise about, because it explains why output volume does not fix it.
| Sentence type | Your site | A community thread |
|---|---|---|
| “We are good at X” | Constantly | Rarely |
| “We chose A over B because of Y” | Never credibly | Routinely |
| “A is better if you have this constraint, B if you have that one” | Almost never | Routinely |
| “We tried A and moved off it after six months” | Never | Frequently |
Rows two and three are exactly the shape of a buyer’s question. When somebody asks an engine which tool suits a particular situation, the sentences that answer it directly are the ones written by people comparing options with constraints attached, and those sentences do not exist on vendor sites.
You can publish a hundred pages saying you are the best choice. None of them is the sentence an engine needs, which is somebody else saying why they picked you over a named alternative.
How do you find out what the threads actually say?
Read them, and read what the engines do with them. Three steps, in order of how much they tell you.
Microsoft’s AI Performance report is worth using here because it also gives “citation counts for specific URLs from your site,” so you can see which of your own pages compete with the community version of the same question. If a thread is winning a question your docs answer better, that is a retrievability problem on your side rather than a community problem.
What can you actually do about it?
Less than you want, and more than nothing. The honest split matters here because the wrong move is genuinely damaging.
What works is being genuinely present where your users already are, under your own name, answering technical questions without pitching. Most communities permit that and some formally encourage it. It is slow, it does not scale, and it is the only version that survives contact with moderators.
What also works, and is easier, is making the accurate version of a contested fact retrievable elsewhere. If a thread says you lack an integration you shipped last year, the fix is a plain-language page stating the integration exists, so retrieval has something current to find. That is the same repair described in third party sources ai citations audit.
What does not work is manufacturing threads. Beyond the obvious risk, it fails on its own terms: the comparative sentences that carry weight are specific and situational, and invented ones read as marketing to humans and moderators alike. A removed thread carries no weight at all.
What if the threads are wrong about you?
Treat it as an accuracy problem with a public correction, not as a reputation problem with a private one. Replying in the thread with the correct fact, identified as who you are, is both the permitted move and the effective one, because the correction becomes part of the retrievable text.
Do not expect it to propagate quickly. Retrieval can pick up a correction within days, but a model’s absorbed impression of you moves on training cycles, which is the two-clock problem in why does AI give outdated information about my company.
And check whether the thread is actually the cause before you spend a week on it. A drop confined to a few prompts across several engines points at a shared source going stale, which is the diagnostic in what sources does AI use for brand information. If the threads have not changed and your numbers have, the cause is somewhere else.