Generative engine optimization services: what recurs

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.

Read the quickstartTwo lines of middleware. Free tier is 1,000 agent visits a month.

Your business

Products, services and policies

What is missing

Details a customer needs

A clearer answer

Information you can publish

Services page, bytes an agent reads
89.6%
docs/demo/agent-before-after-document.md (13,581 → 1,412 bytes)
Tokens saved on the same page
9.7×
docs/demo/agent-before-after-document.md

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.

WorkOne-time or recurringWhy
Content negotiation setupOne-timeIt is middleware. It does not drift
Bot and CDN rule reviewOne-time, revisit yearlyConfig changes rarely
Fact-position restructuringOne-time per templateTemplates are stable
Structured data correctionsOne-time, then maintenanceOnly changes when the template does
New pages answering real questionsRecurringGenuinely continuous
Working the miss logRecurringNew gaps appear as demand shifts
Re-scoring after site changesRecurring, cheapA 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
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.

What this does not do

Frequently asked questions

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.