Community managers spent a decade proving their value in page views and then in engagement. Those numbers are going the wrong way now, and they aren't coming back.

Marius Ciortea thinks that's an opening rather than a loss. In this episode, he makes the case that generative engine optimization is a community job: SEO lived in marketing, and GEO will live in or next to the community team, because your community is usually the only user-generated content your brand actually owns and can influence.

He and host Chris Heuer work through what that means for the person with a queue of unanswered posts and a metrics deck due Friday. How AI systems read a community thread. Which signals make an answer legible to a model: recognized author authority, employee and support attribution, community endorsement, answers marked correct, content that isn't stale. Why the highest-leverage work here isn't a file format but the practice of recognizing authority and retiring outdated material. And what you put in front of your executives when traffic stops being the story.

Chris also introduces the Work Map, an open inventory of the jobs community managers actually do, and identifies GEO as a gap it doesn't yet cover. That one will be getting built in public, with your help.

If the only way you justify your existence has been traffic, you're already in trouble. This episode is about the other way.

Sponsored by Higher Logic and supported by Inflection Point.

Chapters

00:00 Cold open: GEO belongs to community
00:57 Welcome, and why this show exists
03:01 Amplification, not replacement
04:32 Underfunding and the business case problem
05:48 Bots now outnumber humans on the web
07:14 The support question that never reached the forum
08:12 How AI reads a community thread
09:51 Authority signals: badges, staff attribution, upvotes
12:00 Temporality, llms.txt, and ontologies
13:17 The prediction: do the community work, not the file format
15:23 What replaces traffic as the metric
16:26 "If traffic is your only ROI, you're already in trouble"
16:49 Citations, bot-versus-human data, and GEO dashboards
18:11 Why GEO belongs to the community team
20:28 Attribution, and the ad model that's coming
21:34 The Work Map, and owning its gaps
23:51 Why Marius is doing this
26:47 "I've always been lazy": outcome-driven automation
28:54 Translation, humans don't scale, and the reframe
33:09 AI slop, and why the brand doesn't care
35:15 Close

Key takeaways

GEO is a credibility opening for community teams. Community is usually the only user-generated content a brand owns and can influence, which makes the community team the natural home for it.

The signals that make an answer legible to a model are things community managers already control: who answered, their standing, whether the community endorsed it, whether it was marked correct, and whether it's current.

The highest-leverage GEO work is not a technical file. It is about recognizing authority, consistently marking correct answers, and retiring stale content.

More of the web is now crawled by bots than browsed by humans, which breaks the page-views story community managers have been telling executives.

Citation and bot-traffic data is starting to appear in platform back ends, which gives community managers a replacement metric for the traffic they're losing.

Automation in community is not new. Profanity filtering, unanswered-question queues, and translation each moved work off the plate. AI is the next turn of that wheel, not a break from it.

The brand's interest is that the member got a correct answer and can use the product. Insisting that the answer come from the community is the wrong hill to die on.