GEO: making a catalog readable and citable by AI agents.

What is GEO?

GEO, for Generative Engine Optimization, covers the practices that make content visible and citable in the answers produced by generative engines: ChatGPT, Perplexity, Google AI Mode, Gemini. The term was formalized in 2024 by a Princeton team in a paper published at the KDD conference, which also introduced a dedicated benchmark (GEO-bench) and demonstrated that optimizing content for these engines can boost its visibility by up to 40% in their answers. Established

The distinction with SEO is sharp, and the practitioner's line captures it well: SEO gets you ranked, GEO gets you quoted. A classic engine returns a list of links the user clicks. A generative engine synthesizes an answer from several sources and cites only a few. Being absent from that synthesis means not existing for that shopper. This video lays out the definition and the differences in two minutes.

Why machine readability becomes decisive

The hub states it as one of its five structuring claims: SEO remains necessary but is no longer sufficient. Being rankable is a prerequisite; being retrievable and citable is the new objective. The reason is mechanical: an agent preparing a recommendation does not look at your page like a human. It sees neither typography, nor layout, nor badges rendered as images. It reads the code, at machine speed, and discards what it cannot extract.

This sensitivity to missing information is now measured. A study by researchers at Columbia, Yale and the University of Chicago, simulating thousands of AI agent shopping sessions in a controlled environment, establishes a 20 to 40% drop in a product's selection probability when a key piece of information is missing (review, price, attribute). An agent does not infer absent data the way a forgiving shopper would: a metadata gap becomes a visibility gap. Established

What an agent actually reads on a product page

Making a page readable by an agent means exposing clean data in the surfaces it consumes. Five layers of code matter, and each maps to a concrete audit point.

• Server-rendered HTML. Price, availability and description must exist in the source, not only after JavaScript runs.
• schema.org structured data. A complete Product type, with Offer (price, currency, availability), Brand and AggregateRating, gives the agent data it can compare across stores.
• Reviews in plain HTML. Many apps load reviews in JavaScript: exposed as AggregateRating in the HTML, they become a usable trust signal.
• Policy pages. Shipping, returns, warranties: accessible and explicit, not buried in a script. What is ambiguous for a human is blocking for an agent.
• Discovery files. A complete sitemap, a robots.txt open to AI crawlers, the llms.txt file, and agent surfaces such as agent-card.json.

These five points are the operational translation of the semantic layer of the UCP framework: making catalog data machine-addressable. It is the foundation without which the Agent and Transaction layers have nothing to work with.

Claims and proof: the coherence agents verify

An agent does not just read a promise, it looks for the structured proof that confirms it. A claim without verifiable proof is treated as less reliable. This is the machine transposition of the E-E-A-T signals (experience, expertise, authoritativeness, trustworthiness) Google uses to judge quality.

Concretely: a displayed price must match the price declared in the Offer; a visible rating must match the AggregateRating; a shipping promise must point to an accessible policy page. Coherence is not a presentation detail, it is the condition of the trust an agent grants, or denies, to your offer.

The GEO tactics that work, sourced

The Princeton paper does not just define GEO: it tests methods and ranks them. The clearest gains come from adding sourced statistics, inserting citations and quotations from reliable sources, and more broadly from factual, verifiable content. Conversely, keyword stuffing, a reflex inherited from old SEO, degrades visibility in a generative engine. Established

For a catalog, this translates into simple moves: factual, self-sufficient descriptions (composition, dimensions, compatibility), quantified attributes rather than superlatives, reviews exposed in plain text, and promises backed by proof. These are not tricks: they are the signals a generative engine prefers because they reduce its risk of error.

Measuring a catalog's GEO readiness

You only improve what you measure. GEO readiness is audited on the surfaces an engine or agent actually reads: AI crawler accessibility, schema.org completeness, reviews in HTML, claim/proof coherence, sitemap and discovery file health. It is diagnostic work, page by page, before any acquisition spend.

Several instruments exist to do it. For Shopify stores, VerityScore offers a GEO audit that reads a store the way a language model, a buying agent and a real shopper would, then returns a fix plan product page by product page. The tool structures its diagnostic across three complementary dimensions: a GEO Readiness Score (is the store citable and visible to generative engines), an AI Buyer Score (would an autonomous buying agent recommend the product), and a Claims & Proof analysis (are the promises backed by verifiable evidence). Its documentation cites its academic and industry sources, and the audit applies anti-hallucination verification before displaying a result. Emerging

GEO and UCP: two sides of the same shift

GEO and the Universal Commerce Protocol address two distinct moments of the same shift, the move to commerce that is addressable by agents. GEO is about discovery: being read, understood and cited by engines and agents at the moment of recommendation. UCP is about the transaction: being queryable and purchasable by a delegated agent once the recommendation is made.

Both depend on the same foundation, data quality. As the Implement UCP guide notes, the protocol carries your offer, it does not improve it: a poor catalog stays poor, whether exposed via UCP or read by a generative engine. GEO is the discipline that strengthens that foundation on the readability and citation side. That is why, in the framework, it belongs to the same semantic layer as merchant readiness.

Frequently asked questions