Last updated: April 2026
The community teams that win the AI era will be the ones who know exactly what to automate and exactly what to protect. This is how I think about that line.
Make your community machine-legible so the corpus gets cited, not skipped.
Defend the irreplaceable layer: lived experience, peer trust, belonging, and cultural memory.
Discovery is moving inside AI assistants. When someone asks ChatGPT, Claude, or Gemini a product question, the model doesn't return ten blue links — it synthesizes an answer. The brands with the cleanest, most structured, most credible corpus get cited. The rest get skipped. Community is one of the most powerful assets for winning that citation layer — if you structure it correctly.
Communities produce the validated, source-credited content LLMs need to trust a citation. Staff-endorsed solutions, accepted answers, and superuser-verified posts are not just UX signals — they're machine-readable trust declarations.
A well-formed llms.txt at the domain root tells any model ingesting your site what your most important content is, how your knowledge is organized, and who verifies it. It's the bridge between an enormous community archive and the models that would otherwise ignore it.
Board titles, thread taxonomies, and solution markup should be descriptive enough for a model to infer context without reading a full thread. Every taxonomy decision gets evaluated for both human navigation and machine legibility.
Staff posts and knowledge base articles get reformatted to lead with the direct answer before supporting detail — the inverted pyramid structure LLMs favor when extracting quotable, citable content.
The hardest conversation in community right now is happening in boardrooms: if AI can answer product questions instantly, why do we still need a community? The answer isn't defensive. It's strategic. There are entire categories of value that only human communities can produce — and the leaders who can articulate exactly what those are will protect the right budgets and cut the right costs. Here's what community does that AI structurally cannot.
AI can synthesize documentation. It cannot replicate a member who has used your product for five years describing the exact workaround they discovered at 2am. That tacit knowledge doesn't exist in any training set until a human writes it down in a community thread. Communities are where undocumented expertise becomes documented.
When a customer is frustrated, angry, or grieving a canceled feature, they don't want an empathetic-sounding LLM. They want another human who also cared about it. Community is where belonging gets produced. AI can simulate care. It cannot generate it.
People trust other users in ways they categorically don't trust brands or AI. A superuser saying "I had the same issue, here's what worked" carries weight no chatbot can match — not because the information is better, but because the source relationship is different. Trust is a property of the speaker, not the content.
Communities produce the signal that improves your product. AI can analyze that signal — but it can't generate it. The data has to come from somewhere. Kill the community and you kill the upstream source of the insight that keeps your roadmap honest.
The best brands — the ones with fans, not just customers — have people whose identity is partly wrapped up in the product. You don't get that from an LLM. You get it from rituals, in-jokes, recurring events, and shared history among members. Culture is a human artifact.
Your community is a living record of how real people have actually used and felt about your product over time. That archive is irreplaceable institutional memory. It's also the single most valuable training-grade signal you own. No model can regenerate it after the fact.
The teams that treat community as infrastructure for AI citation AND as the irreplaceable human layer will win both arguments — the GEO argument with the marketing team, and the headcount argument with the CFO. This is not a contradiction. It is the work. The community leaders who can hold both ideas at once are the ones worth hiring, funding, and listening to right now.
"Build for the models. Protect the humans. Do both on purpose."
I advise community and digital experience teams on exactly this balance — what to build for AI discovery and what to protect as irreplaceable human infrastructure.