# [Generative engine optimization services: what recurs](https://rebilder.com/solutions/generative-engine-optimization-services)

> GEO is usually sold monthly, but its highest-impact work happens once. Which parts genuinely recur, which do not, and how to scope the difference.

- **Updated:** 2026-08-17

Generative engine optimization services are priced as a retainer. The work that moves the number most is a one-time change to what your server sends, so it is worth knowing which half you are renting.



## What you get

- A clear split between one-time and recurring GEO work
- What a fair recurring scope looks like
- The one-time half, free and self-hostable
- Measurements that survive changing providers

## What genuinely recurs, and what does not

GEO borrowed its commercial shape from SEO, where continuous work makes sense because competitors keep moving. Much of GEO does not have that property: once your server answers content negotiation correctly, it keeps answering correctly without anyone touching it.

| Work | One-time or recurring | Why |
| --- | --- | --- |
| Content negotiation setup | One-time | It is middleware. It does not drift |
| Bot and CDN rule review | One-time, revisit yearly | Config changes rarely |
| Fact-position restructuring | One-time per template | Templates are stable |
| Structured data corrections | One-time, then maintenance | Only changes when the template does |
| New pages answering real questions | Recurring | Genuinely continuous |
| Working the miss log | Recurring | New gaps appear as demand shifts |
| Re-scoring after site changes | Recurring, cheap | A rebuild can regress it silently |

A fair recurring scope is the bottom three rows. If a monthly fee is mostly the top four, the engagement is charging rent on a change that already finished.

## The one-time half, in full

It is not hidden and it is not proprietary. The SDK is open, free, unmetered and self-hostable; the readability spec is published with its arithmetic; the command-line scanner uploads nothing at all.

middleware.ts

```ts
import { gateway } from '@rebilder/gateway'

export default gateway({
  source: { kind: 'document', resolve: myPages },
})
```

On the reference document capture, that change took a services page from 13,581 bytes to 1,412 and moved the first fact from character 10,152 to line 8, with nothing about the facts altered. Quote the capture that matches your own site rather than the more impressive one.

## Keep the measurements portable

The reason to care about where things live is that providers change and results should not restart when they do.

- **Scores against a published spec** can be re-run by anyone, including your next provider. A proprietary score cannot.
- **Middleware in your own repository** keeps serving after a contract ends. A vendor proxy does not.
- **A miss log from your own server** is your data. A miss log inside somebody’s dashboard is a subscription.

> **The reporting question again** Agent fetches fire no beacon, so a page-view tool cannot see this traffic. If the monthly report is built on one, it is describing human visitors and calling them GEO results.

## What this does not do

- We do not sell GEO services. We make the software the one-time half runs on, and this page recommends no provider.
- It cannot make an assistant mention you. Assistants are not deterministic and no vendor controls their output, so a guaranteed citation is not a thing anyone can sell.
- It does not change what Google sees. Content negotiation returns the same substance in another format, and search crawlers keep receiving canonical HTML.
- We do not rank or review GEO providers. Publication about a named third party requires that domain owner’s verified opt-in.

## What are generative engine optimization services?

Work aimed at getting your pages used when AI systems compose answers. It divides into a one-time technical half covering how your server responds to agents, and a recurring half covering content and the gaps that keep appearing.

## Should GEO be a monthly retainer?

Partly. New content, working the miss log and re-scoring after site changes genuinely recur. The serving-layer setup does not, so a retainer that is mostly setup is charging monthly for something that happened once.

## How much of GEO can we do in-house?

The whole one-time half, for most teams: the SDK is free and self-hostable and the scan needs no account. What is harder in-house is sustained writing that answers the questions your buyers actually ask.

## Does GEO work conflict with our SEO?

No. Content negotiation returns the same substance in a different format and search crawlers keep receiving canonical HTML. The two compete for your attention, not for your rankings.

## Related

- [GEO vs SEO: what actually changes](https://rebilder.com/learn/geo-vs-seo)
- [Generative engine optimization agency](https://rebilder.com/solutions/generative-engine-optimization-agency)
- [AEO services](https://rebilder.com/solutions/aeo-services)
- [AI SEO services](https://rebilder.com/solutions/ai-seo-services)
- [AI search optimization: the definitive guide](https://rebilder.com/learn/ai-search-optimization)