What's the org structure for delivering GEO services inside an agency?

Q: How should a small agency staff GEO?

At 5-15 people, GEO is roughly 0.5 FTE absorbed by the existing SEO lead, with content production staying where it is. No dedicated hire needed until client count crosses 10-15.

Q: When does an agency need a dedicated GEO lead?

Around 15-40 people total agency headcount, or when GEO client count crosses 10-15. The lead owns prompt strategy, QBRs, and methodology, with 1-2 specialists executing the weekly tracking cycle.

Q: What is the right size for a GEO pod at a 60-person agency?

A practice lead, 1-2 strategists, one ops person, one content lead, and 0.5-1.0 FTE of shared technical-SEO dev time. This shape can serve 30-60 GEO clients depending on retainer depth.

Q: Should GEO report under SEO, content, or stand alone?

Standalone is best once the agency passes 30 people and 15 GEO clients. Reporting under SEO works at small scale but risks GEO being treated as a feature of SEO rather than a distinct methodology.

Question

What's the org structure for delivering GEO services inside an agency?

Maciej Grabek · Accepted Answer

There is no universal GEO org. There is an org that fits your agency size. At 5 people, GEO is half an FTE living inside whoever owns SEO. At 30, you need a dedicated GEO lead with 1-2 specialists. At 100, you build a small pod with a strategist, an ops person running the tracking platform, a content lead, and access to a shared technical-SEO dev. Bigger agencies sometimes build a 6-8 person GEO division, but that is usually overkill until GEO is 20%+ of revenue. Agency size: 5-15 people At this scale, GEO is not a separate function. It is a tag-along service inside SEO or content. The shape that works: SEO lead absorbs GEO strategy. They already pick keywords and write content briefs. Now they also pick the 30-50 prompts to track per client and write GEO-flavored briefs (FAQ structure, expert bylines, schema requirements). One tracking platform licence shared across all GEO clients. Whoever is most comfortable with dashboards (ops manager, junior SEO) pulls the weekly reports. Content production stays where it is. Same writers, slightly updated brief template. Total dedicated GEO time: ~0.5 FTE across everyone, no full-time hire. A 12-person B2B SaaS-focused agency we have spoken with runs eight GEO clients this way. Their SEO lead spends about 10 hours a week on GEO-specific work; the rest is absorbed into normal SEO and content workflows. Agency size: 15-40 people This is the scale where GEO becomes its own line item on the org chart. The shape: Dedicated GEO lead (1.0 FTE). Senior strategist who owns the practice. Picks prompts, writes briefs, runs client QBRs, sets the methodology, hires below them. 1-2 GEO specialists. Execute the weekly tracking-and-reporting cycle, draft monthly reports, manage the content backlog. Shared technical-SEO dev. 20-30% of one dev's time, schema/llms.txt/canonical work. Content production via existing content team or roster of freelancers. A 30-person agency with 15-25 GEO clients fits this shape comfortably. Revenue from GEO at this scale usually ranges from $30k to $80k MRR depending on retainer size. Agency size: 40-100 people Now GEO can sustain a real pod. Recommended shape: GEO practice lead. Sets vision, owns P&L, sells alongside account leads. GEO strategist (1-2). Client-facing senior who owns prompt selection, narrative, and the monthly review for 8-12 clients each. GEO ops (1). Owns the tracking platform, weekly scan cadence, dashboard hygiene, data QA. GEO content lead (1). Manages content backlog, briefs writers, reviews drafts against schema and brand-voice rules. Embedded technical-SEO dev (0.5-1.0 FTE). Shared with the SEO practice but with dedicated GEO hours. This pod can deliver 30-60 active GEO clients depending on retainer depth. Revenue at this scale is typically $150k-400k MRR from GEO alone. Agency size: 100+ At this scale, agencies sometimes spin up a 6-8 person GEO division with sub-practices: enterprise GEO, mid-market GEO, GEO content production as a separate sub-team. This works when GEO is at least 15-20% of total agency revenue. Below that ratio, the overhead of a division is heavier than the productivity gain. The trap to avoid: building a 12-person GEO division because the agency expects GEO to grow fast, before the revenue is real. Specialist headcount that does not have client work to do is the fastest way to kill margin. Hire one ahead of demand, not five. The roles that almost always get under-hired Two roles agencies routinely underestimate when they build a GEO practice: GEO ops. Running scans, cleaning data, building decks, scheduling. The work scales linearly with client count and quietly eats senior strategist time when there is no ops person. Hire ops at 10 GEO clients, not 25. Schema-literate dev. Most agencies assume their existing dev team can do schema. Most existing dev teams have never validated JSON-LD in their lives. Either upskill or hire a contractor; do not just hope. Reporting line: under SEO, under content, or standalone? Three options, each with a real trade-off: Under SEO. Easiest at small scale because the skills overlap. Risk: GEO gets treated as "SEO with extra steps" and never develops a distinct methodology. Under content. Good if your agency leads with content services. Risk: technical and tracking work gets neglected because content people are not wired for it. Standalone practice reporting to a partner or COO. Best at 30+ people. Forces GEO to develop its own P&L, methodology, and client outcomes. Worth the political cost.