Key takeaways
- Google's own agentic-commerce protocol is UCP, announced at NRF 2026; it covers discovery through checkout and post-purchase, and it explicitly does not control which product an agent presents first.
- UCP is confirmed as the rail reaching Gemini and Google AI Mode: Google's own developer documentation states that adopting UCP enables agentic actions on both surfaces, starting with direct buying.
- Whatever the plumbing, the lever you control is the same one you already run for Google: a complete, accurate Merchant Center feed and broad Shopping Graph coverage, not ad spend.
- In the ACES simulation, Gemini was the most price-sensitive model tested and rewarded platform endorsements the most strongly of the three.
- Gemini's behavior is a moving target: the study documented a model update that reshuffled market shares, which is why this page carries a last-verified date.
How Google AI Mode surfaces products
Google already runs the two systems that matter for agentic shopping: the Merchant Center feed merchants submit, and the Shopping Graph that indexes billions of product listings across the web. Conversational surfaces (Gemini and AI Mode in Search) layer on top of that existing product understanding rather than replacing it. So the merchant question is not "how do I get into a new system," it is "how completely is my catalog represented in the systems Google already has."
The newer piece is the protocol layer. Google introduced the Universal Commerce Protocol (UCP) at NRF 2026 on 11 January 2026 as an open standard that lets agents complete discovery, checkout, and post-purchase without leaving the AI surface, and it is described as vendor-agnostic, standardizing the transaction rather than controlling product-presentation logicSpec-factGoogle, NRF 2026 remarks (blog.google). That last clause matters for this page: even Google's own protocol disclaims the selection step, which is exactly the layer a merchant has to win. See UCP in the glossary.
The rail question is now settled. Google's own UCP developer documentation states that adopting UCP enables agentic actions on AI Mode in Google Search and Gemini, starting with direct buying, layered on the Merchant Center feed and Shopping Graph merchants already runSpec-factGoogle: Universal Commerce Protocol developer guide. That confirms UCP as the rail this page is written around, so the strategy below rests on a documented fact, not an inference.
UCP in one minute
You do not need to implement UCP to read this page, but you should know where it sits. UCP is Google's answer to the same problem OpenAI and Stripe's ACP solves for ChatGPT: a standard way for an agent to move from finding a product to paying for it. The scope differs, and which protocol reaches which engine is the whole point of choosing where to invest. We lay the two side by side in UCP vs ACP: which gets you selected. The short version for a Google-focused merchant: UCP is the Google-native rail, ACP is the ChatGPT-native one, and the practical move for most catalogs is to be legible to both rather than betting on one.
Crucially, being UCP-ready is an eligibility step, not a ranking one. Passing a readiness check makes you transactable; it does not make an agent choose you. The gap between "an agent can buy from me" and "an agent does buy from me" is the selection layer this handbook is about, and on Google that layer is fed almost entirely by the quality of your existing product data.
Feed quality is the lever, not ad spend
Because Gemini and AI Mode draw on the Merchant Center feed and Shopping Graph, the highest-leverage work is the same feed discipline you would do for Google Shopping, pushed to completeness rather than mere validity. On Google surfaces the dominant selection lever available to a merchant is feed quality and Shopping Graph coverage (filling every attribute an agent can score and keeping price and availability accurate) rather than paid placement, because the agent is reasoning over structured product data, not an ad auctionHypothesis (our analysis). This is an inference from how agents weigh structured signals, not a measured ranking rule; treat it as a direction with an unknown magnitude.
What that looks like in practice is covered in depth in make your product feed AI-readable: lead titles with the category and use-case a shopper actually types, fill product identifiers and availability, and reconcile any price that disagrees between feed and page. The point specific to Google is that you are not building a new feed: you are raising the completeness of the one Merchant Center already ingests, so the Shopping Graph has more to match against a conversational query.
What ACES suggests about Gemini specifically
The strongest public evidence on how a Gemini agent chooses comes from the academic ACES framework, a controlled simulation in which vision-language-model agents pick from a mock storefront, analyzed with regression. Every figure below is from that simulation, not from live Google sales, and each is specific to the Gemini model ACES tested (Gemini 2.5 Flash). Read them as evidence of what kinds of signals Gemini weighs and how its weighting differs from other engines, not as a ranking formula for your catalog.
Two patterns stand out for Gemini. First, price. ACES estimated a log-price (ln Price) coefficient of −2.190 for Gemini 2.5 Flash, the most price-sensitive of the three models it tested, notably stronger than the −1.6 range it found for Claude Sonnet 4 and GPT-4.1ReportedACES, Allouah et al., arXiv:2508.02630 (2025-12-17). Second, endorsement. A platform endorsement such as an "Overall Pick" badge lifted a baseline 10% selection probability to 42.6% for Gemini, the strongest endorsement response of any model in the studyReportedACES, Allouah et al., arXiv:2508.02630 (2025-12-17).
The other two signals move Gemini in the same directions the other engines showed, at Gemini's own magnitudes. Raising a product's rating by 0.1 stars lifted Gemini's baseline 10% selection probability to 16.0%ReportedACES, Allouah et al., arXiv:2508.02630 (2025-12-17), and, consistent with agents penalizing paid-looking tags, tagging a product "Sponsored" pushed Gemini's baseline 10% down to 7.9%ReportedACES, Allouah et al., arXiv:2508.02630 (2025-12-17).
Put together, the ACES reading for a Google-focused merchant is that competitive pricing and legitimately earned endorsement signals are the two levers with the most apparent pull on a Gemini agent, with the standing caveat that manufacturing endorsement badges is the dark pattern this finding tempts, not a tactic we endorse. The general per-model comparison, including the position and description-rewrite effects, lives on how AI shopping agents choose products.
Why model updates can reshuffle your ranking
Nothing above is stable. The single most important caveat for optimizing to Gemini is that its selection behavior shifts when the model changes. The ACES authors documented that a model update can drastically reshuffle market shares, observing exactly that between Gemini 2.5 Flash Preview and Gemini 2.5 FlashReportedACES, Allouah et al., arXiv:2508.02630 (2025-12-17). A discount or a description that wins today can matter less (or more) after Google ships the next Gemini revision.
This is why AgentMint.net types every model-behavior claim by source and date, and why this page carries a last-verified stamp above. Do not treat any single quarter's Gemini behavior as a fixed target; treat it as a reading you re-take. The durable strategy is the feed-quality work in the section above, which pays off regardless of how the model reweights its signals; the model-specific coefficients are the volatile part.
Measure your Gemini win rate
Because the model moves, the only way to know how Gemini treats your catalog is to measure it rather than infer it from a study. Track your agent win rate (the share of agent shopping sessions in which your product is the one recommended or bought) on Gemini and AI Mode specifically, and re-take that reading after major model updates. The repeatable protocol we use, including prompts, sampling, and honest error bars, is documented in how we test agent selection; our own results stay in a "data collection in progress" state until real numbers exist, and this page will never fill that gap with an invented figure.