Ask an assistant for a recommendation and there is a good chance community discussion shaped the answer. Assistants treat forum threads as a proxy for what real users think, because that is where unsponsored opinions live. Reddit is the biggest of those surfaces.
Recommendation questions are trust questions, and assistants look for evidence that is hard to fake at scale: repeated positive mentions across independent threads, specific experiences, comparisons where your name comes up unprompted. A brand that only exists on its own website reads as unverified. A brand people discuss reads as real.
Astroturfing gets detected and torched by communities, which is worse than absence. The honest route: be findable when threads mention your category, answer questions as yourself where communities allow it, give users something worth discussing, and treat complaints in public threads as the highest leverage support tickets you have. Then track whether community mentions translate into assistant recommendations, which is part of the citation layer in how to get recommended by AI and the sourcing picture in where ChatGPT gets its information. The free shows whether the assistants currently name you.
Month one is listening: find the five threads and communities where your category gets discussed, read what people praise and complain about, and note which competitors get named unprompted. Month two is showing up: answer questions where community rules allow it, disclose who you are, and publish the resources people keep asking for so others have something worth linking. Month three is compounding: the discussions you contributed to start ranking, assistants start reading them, and your name begins appearing in answers with the context you earned rather than wrote yourself.
Measure it the same way you measure everything else in AI visibility: a fixed basket of buyer questions, checked monthly across the four assistants. Community work is slow, which is exactly why it defends so well once it lands. Pair this with the broader citation strategy in how to get recommended by AI.
Not all community presence weighs the same, and knowing the difference saves months. The threads that shape recommendations share three traits: they answer a buying question directly (best X for Y, is X worth it, X versus Z), they rank well enough in ordinary search for retrieval to find them, and they contain specific experience rather than drive-by opinions, pricing details, use cases, comparisons with named alternatives. A single well-ranked thread where three real users describe solving your buyer's exact problem with your product outweighs fifty scattered brand mentions. That is why the listening month matters: you are not looking for anywhere to appear, you are looking for the handful of threads and communities that retrieval actually reads for your category's moments.
The corollary: when a high-ranking thread about your category is wrong or stale, thin answers, dead product mentions, that is an opportunity, because a genuinely better answer posted honestly tends to earn its way up and into the reading list.
Community work is slow, which makes it easy to either abandon early or credit falsely. Instrument it like everything else: keep your fixed basket of buyer questions, and each month note not just who gets named but which sources the assistants cite. Community impact shows up first in the citations, your threads appearing among the sources, and only later in the recommendations themselves. Track mentions-with-context too: an answer that says users on forums report good experiences with your brand is community signal landing even before your name tops the shortlist. And watch one guardrail metric: if your posts start reading as promotional enough to get flagged or removed, you are borrowing against the exact trust you are trying to build. The full measurement loop lives in how to track brand mentions in AI search.
Since incentives blur judgment, write the rules down before anyone posts. Fair game: answering questions in your expertise with disclosure, publishing resources threads keep requesting, correcting factual errors about your product politely, and thanking users who recommend you. Out of bounds: undisclosed accounts, incentivized mentions, review-swaps, upvote coordination, and seeding questions your own team answers. The test that resolves gray areas: if the community learned exactly who you are and what you did, would the thread thank you or torch you? Manipulation risks the platform's penalties and the assistant-era version of a permanent record, models retrain on the aftermath, and a public unmasking becomes part of your brand's readable history. Participation compounds; manipulation compounds too, in the wrong direction.
No. Purchased mentions violate community rules, get removed, and poison the well. Earned presence in genuine threads is the only version that survives and the only version assistants should be learning from.
Assistants read the same public threads users do, and balance them against other sources. Responding well in public and fixing the underlying issue moves both human and AI perception over time.
Yes. Industry forums, Stack Exchange style communities, review platforms, and niche Slack and Discord write-ups that get indexed all feed the same trust layer.
Both. Retrieval favors whatever ranks and gets cited for your category's questions, which in specialized fields is often an industry forum, Stack Exchange site, or professional community rather than Reddit itself.
Citations can appear within weeks of a thread ranking; recommendation changes typically follow over one to three months as the signal accumulates alongside your other inputs.
Personal accounts with disclosed affiliation almost always land better. Communities tolerate a named founder answering questions; they reflexively distrust brand accounts, and assistants learn from how the community reacts.
You can tell happy customers where conversations happen and make being mentioned easy; scripting or paying for mentions crosses into manipulation and reads that way in the threads.
Encouraged with disclosure and a light policy: identify affiliation, help genuinely, never vote-brigade. An employee known as the helpful expert in a niche community is a durable asset.