Google pushes in‑search checkout guide

Google just published a step-by-step guide for merchants that want shoppers to buy without leaving Google’s own interfaces, including Google Search’s Artificial Intelligence Mode and the Gemini chatbot. The guide went live on April 8, 2026, and it tells developers how to plug checkout into Google’s shopping surfaces. (searchengineland.com) (developers.google.com) The tool behind that push is called the Universal Commerce Protocol, which Google describes as an open standard for turning Artificial Intelligence interactions into sales. In plain terms, it is a shared set of rules so a search engine, a merchant, and a payment provider can all pass product, identity, and payment data back and forth without building one-off connections for each store. (developers.google.com) (developers.googleblog.com) Google introduced the Universal Commerce Protocol in January 2026 at the National Retail Federation trade show in New York. At launch, Google said the protocol would support three pieces of the shopping flow: checkout, identity linking, and order management. (cnbc.com) (ucp.dev) The new guide matters because it turns that January pitch into an implementation checklist. Google’s developer pages now tell merchants to prepare a Merchant Center account, publish a Universal Commerce Protocol profile, expose checkout services, and choose either guest checkout or account-linked checkout. (developers.google.com 1) (developers.google.com 2) Google’s own documentation says these transactions are meant to happen on “Google AI surfaces,” which it names as Search and Gemini. That means the place where a shopper discovers a product and the place where the shopper pays for it can now be the same screen. (developers.google.com 1) (developers.google.com 2) At first, Google is keeping tight control of the buying experience. The checkout guide says Google will initially render the buyer interface itself, while promising “more agentic experiences” later, which means Google’s software will handle more of the steps on the shopper’s behalf over time. (developers.google.com) The plumbing is also very specific. Google asks merchants to publish a machine-readable profile at `/.well-known/ucp`, list their services and capabilities there, and provide signing keys so Google can verify messages and webhooks coming from the merchant’s servers. (developers.google.com) (github.com) Google says the protocol is built to work with existing retail systems rather than replace them. Its January engineering post said merchants can connect through application programming interfaces, Agent2Agent links between software agents, and the Model Context Protocol that many Artificial Intelligence tools use to call outside systems. (developers.googleblog.com) That changes the economics of search ads in a very direct way. If checkout happens inside Search or Gemini, the old handoff from ad click to retailer site stops being the only conversion path, and merchants have to treat Merchant Center feeds, checkout application programming interfaces, and payment readiness as part of acquisition, not just back-office operations. (searchengineland.com) (blog.google) Google has framed this as an industry standard, not a Google-only rail. The specification is published on GitHub under the Universal Commerce Protocol project, and Google says it co-developed the standard with industry partners so merchants, payment service providers, and credential providers can interoperate across the web. (github.com) (blog.google) The immediate takeaway is simple: Google is no longer treating search as just the place where shopping starts. With the April 2026 onboarding guide, Google is giving merchants the instructions to make search the place where shopping ends too. (developers.google.com) (searchengineland.com)