Now live across the AI ecosystem: ChatGPT GPT Store · MCP Registry · mcp.so

Reference guide

What is GEO? Generative engine optimization, from the paper that named it

A TofuBofu reference guide, maintained from our own measurement.

The short version

GEO is generative engine optimization: adapting content so generative engines surface and cite it when composing an answer. Nearly every term in this field was coined by a vendor. This one was coined in a peer-reviewed paper, which means you can go and check the claim yourself instead of taking anyone's word for it.

Where the term actually comes from

GEO was introduced in "GEO: Generative Engine Optimization" by Pranjal Aggarwal, Vishvak Murahari, Tanmay Rajpurohit, Ashwin Kalyan, Karthik Narasimhan and Ameet Deshpande, associated with Princeton University and IIT Delhi. It was first posted to arXiv in November 2023 and accepted to ACM SIGKDD in 2024.

Its argument is the one the whole field now rests on: generative engines answer by gathering and summarising rather than by listing links, so the thing being optimised is no longer a ranked page but whether your content gets selected into a composed answer. The authors built a benchmark, GEO-bench, tested content-level optimization strategies against it, and reported that GEO can "boost visibility by up to 40% in generative engine responses".

Paper
GEO: Generative Engine Optimization
Authors
Aggarwal, Murahari, Rajpurohit, Kalyan, Narasimhan, Deshpande
Affiliations
Princeton University and IIT Delhi
Venue
ACM SIGKDD 2024, preprint arXiv 2311.09735, first submitted November 2023
Benchmark
GEO-bench, described as a large-scale benchmark of diverse user queries across multiple domains
Headline result
Visibility in generative engine responses boosted by up to 40 percent
The authors' own caveat
Efficacy of the strategies varies across domains, so domain-specific methods are needed

One note on a figure you will see quoted a lot. Secondary write-ups commonly describe GEO-bench as roughly 10,000 queries across nine datasets. We could not confirm those exact numbers from the paper's abstract, so we are not asserting them here. The abstract's own language is "a large-scale benchmark". If the precise size matters to your argument, read the paper.

The part almost everyone drops when they quote it

"Up to 40 percent" has been repeated across a thousand agency decks. The sentence next to it, in the authors' own abstract, is repeated far less often: the efficacy of these strategies varies across domains, underscoring the need for domain-specific optimization methods.

That is the paper telling you, unprompted, that its headline number is a ceiling observed under particular conditions and not a forecast for your situation. Two more scope conditions worth holding on to:

It measured a different kind of question

GEO-bench covers diverse user queries across multiple domains. A B2B vendor-recommendation question is a much narrower contest: a handful of company names competing for three to five slots in a shortlist, where the deciding evidence is largely on other people's domains. Nothing in the paper claims to have tested that.

It predates the engines you use

The work was submitted in November 2023. Google AI Mode, Microsoft Copilot in its current form and the retrieval behaviour of today's assistants all postdate it. The mechanism it describes has held up well. The specific numbers are from a different generation of systems.

It optimised content the authors controlled

The strategies operate on a source document. Much of what decides whether a B2B firm gets named sits on directories, review sites and roundups the firm does not control, which is a lever the benchmark design does not capture.

None of this makes the paper wrong. It is the most rigorous public work in the field and it established the central claim, that content can be deliberately optimised for generated answers, under controlled conditions. It is worth reading precisely because it is careful about its own limits in a way the marketing built on top of it is not.

GEO versus AEO versus SEO

Term
What it optimises for
Origin
SEO
A ranked link on a results page
Practitioner, 1990s
AEO
A citation inside a direct answer, including snippets and voice
Practitioner, predates AI chat
GEO
A mention inside a generated answer
Academic, Aggarwal et al., KDD 2024

GEO and AEO are functionally the same job and we treat them as synonyms. Anyone whose pitch depends on them being fundamentally different disciplines is selling a framework. The full practitioner version, with our own measurement behind each lever, is in the AEO guide, the measurement side is in AI visibility, and the funnel stage all of it is competing for is in TOFU, MOFU, BOFU.

The SEO row is where our own data has something to add. In a 15-region study of managed IT providers we checked engine answers against each region's own directory. Those directories held 228 firms. Only 89 of them turned up in an engine's answer; the remaining 139 did not. Ranking organically and being named in the generated answer are not the same achievement, and the second does not follow from the first.

What the benchmark tested, and what a vendor question is

Why the headline number may not be your number GEO-bench Diverse user queries, many domains. Optimises a document the author owns. Outcome: does this passage get used. Up to 40 percent, varying by domain. A B2B vendor question One narrow category, named companies. Evidence sits on domains you do not own. Outcome: are you one of three to five names. Untested by the paper. The mechanism carries across. The magnitude was measured on the left and is routinely quoted as though it were measured on the right. Measure your own baseline. It costs nothing and it is your number.

Measure your baseline before you spend on GEO

A free scan puts your buying questions to all six engines and shows every verbatim answer, including who got named instead.

Get your free audit

What GEO looks like in practice

The paper's structural insight is the useful one: a generative engine assembles an answer out of passages, so the unit of optimization is the citable claim rather than the ranked page. What follows from that, ordered by what our own data says moves the needle for B2B firms:

1

Write claims that can be lifted intact

A sentence that states a fact, with a number and a source, can be pulled into an answer whole. A paragraph of positioning language cannot. This is the closest practical translation of the paper's finding that adding citations, quotations and statistics to source content moves visibility.

2

Make sure the crawlers can fetch you

Nothing above matters if the engine cannot read the page. Of 28 distinct domains we tried to crawl, 11 returned zero pages while looking perfectly healthy in a browser.

3

Get the claim corroborated somewhere that is not your site

This is where the paper's design and B2B reality diverge most. The strategies it tested operate on a document you control. In vendor questions, the deciding evidence is usually on directories, review sites and roundups you do not.

4

Put the qualifying facts in plain text

Across 64 real answers we categorised, engines described the vendors they named using geography 88 percent of the time, compliance 73, vertical specialism 72 and size-fit 62. Facts trapped in images or PDFs are invisible to the thing writing the answer.

5

Measure per engine and hold the questions still

Engines disagree sharply on specific questions and answers vary between identical runs, so a single blended reading tells you very little. Fix the question set, sample repeatedly, and compare engines separately.

The reasonable position on GEO is the one the paper itself models. The mechanism is real and demonstrated. The headline number is a ceiling from a benchmark that did not test your query type. Do the cheap work now, measure your own baseline because it costs nothing, and let the gap you actually have decide what the expensive work is worth.

Frequently asked questions

What is GEO?

GEO stands for generative engine optimization: adapting your content so that generative search engines are more likely to surface and cite it when they compose an answer. Unlike most marketing acronyms it has a precise origin. It was coined in a 2023 paper by Aggarwal, Murahari, Rajpurohit, Kalyan, Narasimhan and Deshpande, published at ACM SIGKDD in 2024, which introduced a benchmark called GEO-bench and showed that targeted content changes could boost visibility in generative engine responses by up to 40 percent.

Who invented the term GEO?

Pranjal Aggarwal, Vishvak Murahari, Tanmay Rajpurohit, Ashwin Kalyan, Karthik Narasimhan and Ameet Deshpande, in the paper 'GEO: Generative Engine Optimization', arXiv 2311.09735, first submitted in November 2023 and accepted to ACM SIGKDD 2024. The authors are associated with Princeton University and IIT Delhi. This matters because GEO is one of the very few terms in this field with a peer-reviewed origin rather than a vendor blog post behind it, and the paper is short enough to read yourself.

What is the difference between GEO and AEO?

In practice, almost nothing, and the tactics are the same. AEO, answer engine optimization, is the older and broader term, covering featured snippets and voice answers as well as AI chat. GEO is the newer term and points specifically at generative engines. The honest distinction is one of provenance rather than method: GEO has an academic paper behind it, AEO grew out of practitioner writing. Both describe getting named and cited inside a generated answer. We use them interchangeably and so does most of the industry.

Does the 40 percent improvement from the GEO paper apply to my business?

Treat it as a demonstration that optimization is possible rather than a number you should expect. The paper itself states that the efficacy of its strategies varies across domains and explicitly calls for domain-specific optimization methods, which is a caveat most people quoting the headline leave out. It was also measured on generative engine responses to a broad benchmark of user queries, not on B2B vendor-recommendation questions where a small number of company names compete for three to five slots. That is a different problem and nothing in the paper claims to have tested it.

What GEO tactics actually worked in the study?

The paper's broad finding is that content-level changes, rather than link-level or authority-level ones, moved visibility in generated answers, and that adding citations, quotations and statistics to source content was among the more effective directions. The important structural insight is that generative engines assemble an answer from passages, so optimization operates at the level of the citable claim rather than the ranked page. If you want the specific per-strategy numbers, read the paper directly rather than any summary of it, including this one.

Is GEO the same as SEO?

No, and our own measurement shows the gap. SEO earns a ranked link; GEO earns a mention inside a composed answer. In a 15-region study of managed IT providers we checked engine answers against each region's own directory: those directories listed 228 firms, engines named 89 and passed over 139. Firms that rank organically routinely fail to appear in the AI answer for the same question. SEO is the floor, because being crawlable and indexable is a precondition for being retrieved at all. It is not the same game, because a generated answer is decided on corroboration rather than on rank.

Should I optimize for GEO or wait?

The cheap parts are worth doing now and the expensive parts deserve evidence first. Making sure AI crawlers can actually fetch your site, describing yourself consistently across third-party sources, and putting the facts an engine needs into plain readable text are all low cost and useful regardless. Large content programmes justified purely by a 40 percent figure from a benchmark that did not test your query type deserve more scepticism. Measure your own baseline across engines first, because it is free, and let the gap decide the spend.

Sources and further reading

Keep reading: What is AEO · AI visibility explained · AEO vs GEO vs SEO, compared · TOFU, MOFU, BOFU explained