Skip to content
Working with an agency

What's Actually in a GEO Retainer Each Month

A month-by-month breakdown of GEO retainer deliverables: crawler checks, page rewrites, citation tracking and outreach, and what a report should contain.

By Jeremy ZavaAI-assisted, reviewed by Ibrahem Helal6 min read

A normal GEO retainer covers four things every month: crawler and technical checks, rewrites of your highest-intent pages, citation tracking against a fixed set of real buyer questions, and outreach to the third-party pages assistants actually cite. The mix shifts over time, but all four stay in scope for as long as the retainer runs.

This breaks down the deliverables in how to choose a GEO agency into what actually shows up on a monthly invoice and a monthly report. If you're still in the first month, GEO agency onboarding covers how this scope gets set up before the retainer settles into its normal monthly rhythm.

On this page

What does the technical work cover month to month?

In the first month, this is usually the heaviest line item: confirming every major AI crawler can reach your site, fixing any firewall or CDN rules blocking one of them, and clearing a backlog of pages that render incompletely without JavaScript [1]. By month two or three, this shrinks to monitoring — periodic re-checks to catch a new block introduced by an unrelated infrastructure change, since these things tend to regress quietly when nobody's watching for them.

A retainer that bills the same technical hours in month six as it did in month one is either padding the invoice or hasn't actually cleared the initial backlog. Ask to see how this line item is expected to change over the engagement, and treat a flat answer with some suspicion.

It's worth naming what "technical checks" covers concretely, because the phrase alone hides a lot. It means testing your site with each crawler's real user agent and confirming a full response, not just a robots.txt read. It means checking whether your hosting provider's default firewall rules — often written to stop scrapers, and often catching AI crawlers in that net by accident — are quietly blocking traffic nobody's looking for. And it means confirming that content requiring JavaScript to render is actually visible to a crawler that may not execute scripts the way a browser does. Each of these is a specific, testable thing, not a vague line item.

Regression matters here more than most retainer scopes admit up front. A crawler block that was fixed in month one can come back in month four because of an unrelated change — a new CDN rule, a security plugin update, a migration nobody flagged as relevant. That's why the technical line item never actually drops to zero even once the initial backlog clears; it shifts from active fixing to periodic re-verification, which is real, billable work even though it produces no visible change most months.

How many pages get rewritten, and which ones first?

Priority goes to the pages a buyer's exact question maps to most directly — pricing, specifications, comparison pages, FAQs — because those are the pages an assistant reaches for when it's building a specific answer rather than a general overview [2]. A reasonable monthly pace is a handful of these pages, chosen deliberately rather than worked through alphabetically, with each one rewritten so its opening sentences stand alone as a complete answer.

The rewrite itself follows a fairly consistent pattern regardless of which page it's applied to. Each section under a heading opens with two or three sentences that answer that heading's question completely on their own, with the supporting detail following after rather than before. Numbers get a named source and a date next to them instead of floating unattributed. And anything padding a section out to hit a word count gets cut, because a longer page isn't a stronger source here — it's a page with a weaker opening sentence, which is the only part likely to get quoted.

Not every page needs this treatment, and a retainer that tries to rewrite the whole site in month one is usually wasting hours on pages nobody would ask about anyway. The discipline is in choosing well: a dozen pages that map directly to real buyer questions, done properly, outperform fifty pages touched lightly across the board.

What does citation tracking actually involve each month?

A fixed set of twenty to forty real buyer questions gets run on a repeating schedule across every AI engine in scope, with each run logging whether the brand was named, whether it was linked, and which specific URL got cited [3]. This prompt set should not change month to month except deliberately — swapping it after a weak month resets the baseline and destroys the one thing the tracking was measuring in the first place.

How the deliverable mix shifts over a typical engagement
DeliverableMonth 1Month 4+
Technical fixesHeavy — clearing the backlogLight — periodic re-checks
Page rewritesHighest-intent pages firstBroader coverage, lower priority pages
Citation trackingBaseline establishedTrend reported against baseline
Third-party outreachFirst pitches sentOngoing relationship maintenance

What does the third-party outreach line actually look like?

This is the part of the retainer most often left vague in a proposal, and it's worth pinning down specifically. It includes claiming and completing profiles on review platforms and professional directories you control, and pitching inclusion — on the merits, with a disclosed interest — in comparison posts and roundups that already rank for your category and already get cited when assistants answer buying questions.

Claimed profiles are close to a one-time task with light ongoing maintenance. Pitching for inclusion in someone else's content is genuinely ongoing: most pitches don't land, response times vary widely, and a retainer should budget a steady cadence of outreach every month rather than a single burst early on that tapers to nothing once the initial list of targets is exhausted.

A reasonable monthly cadence looks like a fixed number of new pitches sent, a handful of follow-ups on ones still open, and at least one profile refreshed or newly claimed. Ask an agency to name that cadence in numbers rather than describing it as "ongoing outreach," since the second phrase can mean anywhere from one pitch a month to twenty.

Who signs off on rewritten pages, and how often should that happen?

This should be specified in the retainer, not left to whoever happens to be available that week. A clear, fast approval path — ideally a single named person on your side — is what keeps the page-rewrite line item moving at the pace it's budgeted for. A retainer that quietly stalls because approvals sit in a queue for two weeks is still billing the same hours for slower progress, which is worth catching early rather than discovering at a quarterly review.

What should the monthly report actually contain?

Specific URLs cited, the exact prompts that triggered them, the engine, and the date — compared explicitly against the baseline established in month one, not restated as a single blended visibility score with nothing underneath it. A report that lists activity — pages rewritten, pitches sent — without tying any of it back to a citation number is telling you the retainer was busy, not that anything moved. How long GEO takes covers how to read that trend realistically over the length of an engagement, month by month, rather than judging any single report in isolation.

  1. Ask for last month's actual report

    Before signing, ask to see a real monthly report from an existing client, not a template with placeholder numbers.

  2. Confirm the four deliverables by name

    Technical checks, page rewrites, citation tracking and third-party outreach — get each one named specifically in the scope document.

  3. Set the approval path in writing

    Name who signs off on page changes and how fast, so the rewrite line item doesn't quietly stall in a queue.

The retainers that work are the ones where a client can tell you, off the top of their head, what all four parts of the scope are. If they can only describe it as 'AI optimization,' the scope was never specific to begin with.
Jeremy ZavaCo-founder, RankPearl

One thing no retainer, including ours, can honestly promise: a specific citation on a specific date. Can you guarantee ChatGPT mentions covers why that's true, and what a GEO agency does covers the underlying deliverables in a bit more depth than this monthly breakdown does.

Questions people also ask

  • What should a GEO retainer include at minimum?

    Crawler and technical checks, page rewrites for AI extraction, citation tracking against a fixed prompt set, and ongoing third-party outreach. A retainer missing any one of these four is missing a real part of the work.

  • How many pages get rewritten in a typical month?

    It varies by site size, but a reasonable pace is a handful of your highest-intent pages per month, prioritized by which ones a buyer's exact question maps to most directly, rather than a fixed number applied evenly.

  • Should the retainer scope shrink after the first few months?

    The mix shifts more than it shrinks. Technical fixes taper off once the backlog clears, and outreach and maintenance become a larger share of the ongoing work.

  • What should a monthly report actually contain?

    Specific URLs cited, which prompts triggered them, on which engine, compared against the baseline — not a single blended visibility score with no detail behind it.

Sources

  1. Overview of OpenAI crawlers — OpenAI (checked 23 September 2026)
  2. AI features and your website — Google Search Central (checked 23 September 2026)
  3. I tracked 13,184 AI citations across 4 LLMs: here's what I learned — Orbit Media Studios (checked 23 September 2026)
  4. Introducing AI Performance in Bing Webmaster Tools — Bing Webmaster Blog (checked 23 September 2026)

Want to see a real month-by-month GEO scope?

Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.

Who wrote this

Jeremy ZavaCo-founder

Leads growth and client partnerships.

Works on: CRO, SEO

Reviewed before publishing by Ibrahem Helal, Co-founder.

Posts by Jeremy Zava

More on this