Online product discovery is shifting from page-by-page browsing to conversations with intelligent assistants that can understand intent, compare options, and complete purchases directly inside AI surfaces. Google’s Universal Commerce Protocol (UCP) and OpenAI-driven product discovery sit at the centre of this change, turning product data into the primary interface between brands and buyers rather than the website page itself. For digital leaders and eCommerce teams, this is already reshaping visibility, measurement, and where competitive advantage comes from.developers.googleblog+4
1. Introduction
Online discovery has evolved from directories and keyword search to highly contextual, AI-assisted journeys where users describe needs in natural language and expect curated, ready-to-buy answers. Instead of scanning search results and category pages, people are increasingly asking assistants to “find the best option for me”, expecting instant filtering, explanation, and in many cases a one-tap checkout.cnbc+3
Two developments make this moment structurally different from previous shifts in search and eCommerce:
- Google’s Universal Commerce Protocol (UCP) creates a standard way for AI agents and commerce systems to talk to each other from discovery through to payment and fulfilment.developers.google+1
- OpenAI’s product discovery and “instant checkout” capabilities allow users to move from conversational research to purchase inside ChatGPT and related experiences, powered by structured product data and open catalogues.bigcommerce+1
This matters now because these capabilities are live or rolling out across mainstream surfaces such as Google Search (AI Mode), Gemini, and ChatGPT, with major retailers already participating. The result is a gradual but real transfer of power from page-based SEO to protocol-based, assistant-led commerce where the quality of your product data, not the design of your category pages, determines whether you are present at the point of decision.ppc+3
Section summary: Discovery is becoming conversational and assistant-led, with UCP and OpenAI-style product discovery enabling end‑to‑end journeys inside AI environments rather than on traditional web pages.developers.googleblog+1
2. What Is Google Universal Commerce Protocol (UCP)?
UCP in simple terms
In plain language, UCP is an open standard that lets digital agents and commerce systems exchange all the information needed to research, buy, and support a product in a consistent way. Instead of every retailer building custom integrations for each platform or assistant, UCP defines a shared “language” for products, prices, availability, identity, payments, orders, and post‑purchase events.searchengineland+2
Google describes UCP as the backbone of “agentic commerce”, where AI agents can check stock, confirm shipping options, process payment, and handle post‑sale queries on behalf of users across different merchant systems. The protocol builds on existing Google commerce infrastructure such as Merchant Center and Google Pay, while remaining open and compatible with other protocols used by the wider ecosystem.cnbc+3
The problem Google is solving
Current eCommerce infrastructure assumes a human is clicking around websites and pressing “buy now” buttons, which breaks down when an autonomous or semi-autonomous agent is trying to act on behalf of a user. Without a shared standard, every assistant has to integrate separately with each retailer to understand cart, checkout, authentication, and order status – an expensive and fragile model at global scale.computerworld+2
UCP tackles several specific problems:
- Fragmented integrations: Assistants cannot reliably complete purchases across many merchants without bespoke work; UCP replaces this with a standard set of calls and data structures.ppc+1
- Trust and accountability: Existing flows are built for direct user interactions, not for agents, creating questions around consent, authorisation, and dispute handling; UCP embeds an “accountability trail” between merchant, identity provider, and payment handler.developers.google+1
- Friction at checkout: Users drop out when forced to re‑enter details or switch context; UCP is designed to support stored payment credentials (e.g. via Google Wallet) to keep the experience continuous and low-friction.developers.googleblog+1
How UCP differs from product feeds and web pages
Traditional product feeds (such as standard Merchant Center feeds) mainly describe a catalogue for advertising and basic shopping listings: title, description, price, availability, and some attributes. They are largely one‑way: you publish a feed, Google ingests it, and then surfaces products in search and shopping units.developers.google+1
UCP is different in several ways:
- Two-way and transactional: UCP covers not just “what is this product?” but “can we buy it now?”, “under what terms?”, and “what happened after purchase?”, enabling full lifecycle interactions.searchengineland+1
- Agent-first design: The protocol anticipates AI agents making programmatic decisions, not humans reading pages; data is structured for machines to evaluate options, not just for humans to read.ppc+1
- Protocol, not page: Instead of relying on page markup and crawling, UCP defines explicit APIs and events so that assistants can query stock, confirm the basket, and trigger payments reliably.developers.googleblog+1
What UCP exposes about products and commerce
Google’s documentation and related announcements highlight several categories of information that UCP can represent:developers.google+2
- Product fundamentals: Identifiers, titles, descriptions, images, variants, attributes, and compatibility information.
- Commercial terms: Pricing, promotions, taxes, shipping options, delivery windows, and returns policies.
- Operational status: Real‑time availability, inventory status, and channel-specific stock where relevant.
- Purchase readiness: Purchase URLs, checkout configuration, accepted payment methods, and tokenised credential support.
- Order lifecycle: Order creation, confirmation, fulfilment status, and post‑sale support hooks.
The aim is for an agent to have everything needed to move from “find a lightweight suitcase under £200 that fits carry-on rules” to “two options are in stock, can arrive by Friday, and can be purchased with your saved payment method” without improvising from semi-structured page content.ppc+1
Why Google is moving away from page-based discovery
Google is not abandoning pages entirely, but it is clearly rebalancing towards data and protocols because:blog+1
- AI modes in Search and Gemini work best when they can reason over structured, current information rather than parse long, unstructured pages.blog+1
- Product information changes rapidly (pricing, stock, shipping), making real-time or near real-time updates essential for trustworthy recommendations and autonomous buying.computerworld+1
- Assistant-led experiences compress multiple clicks into a single dialogue; the system needs a reliable way to retrieve and act on commerce data during that dialogue.cnbc+1
For merchants, this means that the richness and reliability of their product and commerce data, expressed via standards such as UCP, will increasingly determine visibility inside AI experiences, even when users do not land on the site.searchengineland+1
UCP in one paragraph for non‑technical readers
UCP is a common rulebook that lets Google’s AI and other digital assistants talk to online shops in a consistent way, so they can check stock, prices, delivery options, and even place orders on behalf of customers using saved payment details. Instead of relying on web pages and separate integrations for each retailer, UCP gives assistants a standard way to understand products and complete secure purchases across many different brands.searchengineland+3
Section summary: UCP is an open, agent‑focused standard that extends beyond product feeds to cover the full commerce journey, allowing AI experiences to move seamlessly from discovery to checkout using structured, trustworthy data rather than traditional page crawling.developers.googleblog+1
3. How OpenAI and Conversational Assistants Change Discovery
From searching to asking
Conversational assistants such as ChatGPT, along with specialist AI shopping tools, are changing user behaviour from “searching” to “asking”. Instead of typing a short query and scanning multiple listings, users describe their situation in natural language and expect the assistant to interpret constraints, apply preferences, and curate a small set of highly relevant options.bigcommerce+1
OpenAI’s product discovery experiences show this shift clearly:bigcommerce
- Customers describe needs and contexts (“I need running shoes for flat feet under £120”) rather than exact model names or filter combinations.bigcommerce
- The assistant returns a handful of tailored options with explanations, not pages of results with ads and organic rankings.bigcommerce
This conversational mode reduces cognitive load for users, but it also reduces the number of visible slots where brands can appear, increasing the importance of being included in the assistant’s candidate set at all.cnbc+1
How recommendations are formed without fixed rankings
In conversational systems, recommendations are typically generated in stages: retrieving candidate products from structured data, then ranking and filtering them dynamically based on context, constraints, and follow‑up questions. There is no fixed, global “position one” as in traditional search; every dialogue can produce a different ordering depending on the user’s goals and clarifications.ppc+1
Key implications include:
- Contextual relevance over static rank: The “best” result is defined by fit to the expressed need, not by a stable global ranking for a keyword.checkout+1
- Explanations as part of ranking: Assistants often justify recommendations (“this option balances weight and durability”), making clarity of underlying data critical.bigcommerce
- Continuous refinement: Users can ask follow‑up questions (“make it vegan and under 500 calories per serving”) that immediately reshape the result set.bigcommerce
Because of this, visibility becomes a function of being discoverable in the underlying product and content graph, rather than winning one of a small number of fixed slots on a search results page.ppc+1
Why clarity, consistency, and trust matter more than traffic
When purchases happen inside AI environments, traditional traffic-based measures (sessions, pageviews) only tell part of the story. What matters more is whether the assistant trusts your data enough to include and recommend your products within its answers, particularly when instant checkout is available.cnbc+2
Clarity and consistency have several dimensions:
- Clear product data: Accurate attributes, benefits, and constraints make it easier for models to match products to nuanced prompts.ppc+1
- Consistent information across channels: Conflicting prices or stock information between feeds, schema markup, and landing pages erode confidence for both users and agents.developers.google+1
- Trustworthy fulfilment signals: Reliable delivery windows, returns policies, and post‑sale support data encourage assistants to favour your offers where multiple merchants sell similar items.developers.googleblog+1
For digital leaders, this means that “assistant trust” in your product and operations data becomes a new leading indicator, even when you never see a traditional click.cnbc+1
The role of summaries, comparisons, and explanations
Conversational interfaces excel at summarising complex choices, comparing alternatives, and explaining trade‑offs in plain language. Instead of users manually opening five tabs to compare specifications and reviews, the assistant can compress that work into a narrative comparison aligned to their priorities.developers.googleblog+1
This changes how brands should think about:
- Content design: Structured, comparable attributes and clear claims feed into better summaries and side‑by‑side comparisons.ppc+1
- Brand voice: Where assistants surface brand-provided answers (for example through business agents), brands can still express tone and positioning within the assistant environment.cnbc+1
- Decision support: Explanation quality becomes part of the value proposition; users choose experiences that help them understand decisions, not just list options.bigcommerce
Section summary: Conversational assistants transform discovery from keyword search and scrolling to asking and receiving curated, explained options, making reliable, structured product data and cross-channel consistency more important than raw site traffic.cnbc+1
4. UCP vs Traditional SEO and eCommerce
Three models of discovery
Modern eCommerce visibility now spans three overlapping models:searchengineland+1
- Page‑based SEO: Optimising website pages and content to rank in organic search results for keywords.
- Feed‑based shopping: Supplying product feeds into platforms such as Google Shopping and marketplaces, mainly for ads and listing units.
- Protocol‑based discovery (UCP and similar): Exposing commerce data through open standards that allow agents to handle discovery, checkout, and post‑purchase flows.
Each model continues to exist, but their roles and relative importance are shifting as AI-driven and assistant-led experiences mature.blog+1
What still matters from traditional SEO
Several core SEO disciplines continue to matter:
- Search intent understanding: Knowing what problems and questions your buyers have remains essential for deciding what to expose and how.blog
- High‑quality content: Guides, comparisons, FAQs, and educational content still feed both traditional search and AI summarisation.blog+1
- Technical hygiene: Crawlability, performance, and clean markup support both classic indexing and extraction of structured information.blog+1
However, some tactics that focused purely on ranking specific pages for narrow keywords are likely to see diminishing returns as AI surfaces answer those queries directly inside the interface.searchengineland+1
Where brands may be over‑investing
Many brands continue to pour disproportionate effort into:
- Micro‑optimising meta tags for marginal ranking gains while neglecting product data quality and consistency.
- Building complex category navigation structures that matter less when assistants guide users directly to specific items.ppc
- Treating feeds as a compliance exercise rather than a strategic asset for discovery across multiple AI-driven environments.developers.google+1
The more discovery shifts into AI layers, the more value moves from page‑level tricks to robust, well-governed product and commerce data that can serve many surfaces simultaneously.searchengineland+1
Page, feed, and protocol: key differences
Discovery models in commerce
| Dimension | Page‑based SEO | Feed‑based shopping | Protocol‑based discovery (e.g. UCP) |
|---|---|---|---|
| Primary focus | Ranking web pages in SERPs | Supplying product listings to platforms | Enabling agents to execute full commerce journeys |
| Main consumer surface | Search results pages and site visits | Shopping ads, product listing units | AI modes, assistants, and agent‑led interfaces |
| Data structure | HTML pages with optional schema | Structured feeds (catalogues) | Standardised APIs and events across products and orders |
| Interaction type | Human reads and clicks | Human selects from product cards | Agent retrieves, reasons, and acts on behalf of user |
| Scope of journey | Discovery and research | Discovery and cart add | Discovery, checkout, payment, and post‑sale support |
| Update frequency | Crawl-dependent | Feed refresh cycles | Designed for near real‑time operational updates |
| Measurement focus | Sessions, rankings, clickthrough | Impressions, clicks, ROAS | Conversion at agent surface, protocol events, lifecycle value |
| Critical success factors | Content relevance, links, UX | Data completeness, bid strategy, feed quality | Data accuracy, protocol adoption, trust, operational reliability |
developers.google+3
Section summary: Page-based SEO and feed-based shopping remain important but are increasingly complemented, and in some journeys overshadowed, by protocol-based discovery where UCP gives agents direct access to commerce data and checkout capabilities.searchengineland+1
5. What This Means for eCommerce Strategy
Product data as a competitive advantage
In an assistant-led world, product data is not just a back-office detail but a primary competitive asset. Assistants and protocols reference data, not design, so brands with richer, more accurate, and more up‑to‑date data are more likely to be surfaced, recommended, and transacted.bigcommerce+2
This advantage operates across:
- Coverage: The proportion of your catalogue that is fully described with structured attributes and clear benefits.ppc+1
- Depth: The level of detail on compatibility, use cases, and differentiating features that help assistants match to specific user needs.bigcommerce+1
- Operational reliability: The consistency between promised and actual stock, price, and delivery performance, feeding trust signals back into the ecosystem.developers.googleblog+1
Why availability, accuracy, and completeness matter
AI agents are incentivised, and in some cases constrained, to favour offers they can execute reliably without surprises for the user. If your data says an item is in stock and available for next‑day delivery, but the reality differs frequently, the assistant risks recommending a poor experience and may adjust future behaviour accordingly.developers.google+2
Three dimensions are particularly important:
- Availability: Real‑time stock and fulfilment data reduce cancellations and substitution friction.developers.googleblog+1
- Accuracy: Precise pricing, taxation, and shipping information protect against cart shock and refunds.computerworld+1
- Completeness: Missing attributes or vague descriptions reduce matching quality, excluding your products from relevant high-intent prompts.ppc+1
Structured information across all platforms
The move towards protocols and assistant-led commerce raises the bar for structured data across every touchpoint, not just Google. OpenAI’s product discovery capabilities, for example, lean heavily on structured, machine-readable product information crawled from sites or supplied through partner programmes.bigcommerce+1
For brands, this means:
- Aligning schema markup, feeds, internal product information management (PIM) systems, and protocol implementations around a single, authoritative product data model.developers.google+1
- Treating conversational attributes (answers to common questions, use cases, alternatives) as data fields, not only as free‑text content.ppc+1
- Ensuring consistency across search, marketplace listings, retail media, and assistant-facing protocols to reinforce trust.developers.google+1
Implications for small vs large brands
Protocol-based and assistant-led discovery cuts both ways for smaller businesses:cnbc+1
- On the one hand, it can level the playing field by allowing smaller brands with strong data discipline to appear in curated recommendations alongside bigger players.bigcommerce+1
- On the other hand, larger retailers typically have more advanced data infrastructure and dedicated teams, making it easier for them to adopt new standards such as UCP quickly.cnbc+1
For smaller brands, focusing on a clean, consistent, and well-structured catalogue across a narrower product range can be a pragmatic route to visibility in AI-driven environments.ppc+1
Section summary: eCommerce strategy must shift from optimising pages in isolation to governing product and commerce data as a core asset, with accuracy, completeness, and operational reliability driving visibility and trust in assistant-led journeys.searchengineland+1
6. Visibility Without the Website Visit
Zero-click and assistant-led purchasing
“Zero‑click” in this context refers to journeys where the user’s goal is satisfied inside the assistant or AI surface without visiting a traditional website. In commerce, this can extend all the way to purchase, especially where protocols such as UCP or OpenAI’s instant checkout capabilities allow the assistant to complete transactions using stored credentials.developers.googleblog+2
Assistant-led purchasing typically looks like:
- The user describes a need and constraints in conversation.
- The assistant selects, explains, and confirms a product choice.
- The assistant completes the purchase inside the interface, using pre‑authorised payment and shipping details.developers.googleblog+1
This flow compresses search, research, comparison, and checkout into a single dialogue, delivering obvious convenience for users but reducing surface area for traditional brand touchpoints.cnbc+1
When the website is still needed
Websites remain essential in several scenarios:
- Complex or high‑risk decisions: High‑value B2B purchases, regulated products, or items requiring careful specification may still push users towards detailed pages and configurators.ppc
- Brand experiences: Storytelling, rich media, and community features are difficult to compress fully into assistant responses.blog
- Account self‑service and niche workflows: Certain post‑sale tasks or bespoke journeys may not be fully captured in protocols and generic assistants yet.computerworld+1
In practice, many journeys will be hybrid, with assistants handling initial scoping and shortlisting, and websites supporting deeper research or configuration where users want more control.blog+1
When the website may be bypassed
For routine or low-friction purchases, assistants may bypass the website entirely:developers.googleblog+1
- Re‑purchasing consumables and repeat items.
- Buying standardised products (e.g. commodity electronics, travel accessories) where comparison can be done on structured attributes.bigcommerce+1
- Triggering autonomous actions such as “buy when the price drops below £X” via agentic commerce features.ppc
In these journeys, measurement and attribution need to evolve from session-based analytics to protocol-level events, assistant surface conversions, and lifetime value tied to agent-mediated touchpoints.developers.googleblog+1
What brands must control without the visit
Even when users do not land on the site, brands still need to control:
- Product truth: One canonical source of product and offer data feeding all assistants and protocols.developers.google+1
- Commercial policies: Clear, codified rules on pricing, promotions, shipping, and returns that assistants can interpret.developers.google+1
- Brand guardrails: Approved descriptions, claims, and positioning that can be surfaced through business agents and structured content fields.cnbc+1
- Governance and compliance: Data ownership, consent, and audit trails across protocol interactions and post‑sale support.developers.google+1
Section summary: Zero‑click and assistant-led purchasing are already reducing the number of website visits needed to complete a purchase, making robust off‑site control of product truth, commercial policies, and brand guardrails critical.cnbc+1
7. Practical Actions for Businesses
1. Prepare and strengthen product data
Treat product data as a strategic asset, with clear ownership and standards:developers.google+1
- Consolidate sources: Map all systems that hold product information (PIM, ERP, CMS, feeds) and create a single source of truth.developers.google+1
- Standardise attributes: Define mandatory fields (e.g. dimensions, materials, compatibility, use cases) for each category and enforce them.bigcommerce+1
- Structure conversational elements: Capture answers to common questions, alternative suggestions, and cross‑sell relationships as discrete data, not just FAQ copy.bigcommerce+1
This work improves discoverability not only in UCP‑enabled experiences but also in OpenAI’s product discovery and other AI-driven environments that rely on structured data.ppc+1
2. Audit information quality
Regular data quality audits help identify where assistants may be receiving incomplete or inconsistent information:developers.google+1
- Completeness checks: Identify products missing key attributes, images, or policy details; prioritise high-margin and high-volume items.bigcommerce+1
- Consistency checks: Compare prices, availability, and attributes across website pages, schema markup, feeds, and internal systems.developers.google+1
- Freshness checks: Review update frequencies for inventory, pricing, and shipping, focusing on categories where these change quickly.computerworld+1
Where possible, connect these audits to real-world outcomes, such as cancellations, returns, or customer support contacts, to quantify the cost of poor data.ppc+1
3. Ensure cross‑platform consistency
Assistants operate across multiple surfaces; inconsistent data undermines trust:developers.google+1
- Align models: Use the same product IDs and attribute definitions across Merchant Center, marketplaces, retail media, and internal systems where feasible.ppc+1
- Synchronise updates: Automate updates so that changes to core product or commercial data propagate quickly to every downstream feed and protocol.developers.google+1
- Document rules: Maintain clear documentation on which system “wins” when conflicts arise, and how exceptions are handled.ppc+1
This reduces the risk of assistants seeing conflicting signals that cause them to down‑rank or exclude your offers.ppc
4. Future‑proof eCommerce setup
Preparing for protocol-based and assistant-led commerce does not require adopting every new technology immediately, but it does require building adaptable foundations:developers.googleblog+1
- Decouple data from presentation: Architect systems so product and commerce data can feed multiple channels and protocols independently from the website UI.developers.google+1
- Support open standards: Where practical, adopt and monitor emerging protocols rather than relying on closed, bespoke integrations.checkout+1
- Invest in observability: Build the ability to monitor performance on assistant and protocol surfaces, not just on-site metrics.developers.googleblog+1
These capabilities make it easier to participate in UCP and similar standards, and to experiment with assistant-specific experiences as they evolve.cnbc+1
5. Define internal ownership and collaboration
Because assistant-led commerce sits at the intersection of marketing, product, and technology, governance is critical:developers.google+1
- Data ownership: Assign clear responsibility for product and offer data quality, often within merchandising or product teams supported by data specialists.ppc+1
- Technical integration: Charge engineering or platform teams with implementing and maintaining standards such as UCP and structured data pipelines.developers.googleblog+1
- Experience and brand: Involve marketing, UX, and customer service in defining how brand voice and policies should appear inside assistant experiences.cnbc+1
Cross-functional forums or councils can help prioritise which categories and markets move first, and how learnings are shared across the organisation.developers.google+1
Section summary: Practical preparation involves strengthening product data, auditing quality, ensuring cross-platform consistency, building flexible architectures, and assigning clear ownership so that teams can support protocol-based and assistant-led commerce at scale.developers.googleblog+1
8. Risks, Limitations, and Open Questions
Data ownership and control
While protocols such as UCP emphasise that merchants remain the “merchant of record” and retain customer relationships, they also deepen dependence on platform infrastructure and standards. Questions remain around how data about assistant-led purchases and interactions will be shared back to merchants, and how granular that visibility will be compared with on-site analytics.cnbc+2
Brands must navigate:
- Contractual terms: What rights platforms have to use product, offer, and behavioural data beyond the immediate transaction.cnbc+1
- Customer relationships: How to maintain direct engagement (e.g. loyalty, service, community) when many interactions are mediated by assistants.cnbc+1
Platform dependency and competition
Relying heavily on protocols and assistant surfaces increases exposure to changes in platform policies, algorithms, and commercial models. At the same time, multiple ecosystems are emerging: Google’s UCP, OpenAI’s Agentic Commerce and product discovery initiatives, and alternative approaches from payment providers, retailers, and other AI platforms.checkout+2
Open questions include:
- How interoperable these standards will be over time, despite claims of compatibility.checkout+1
- Whether certain platforms will prioritise their own commerce offerings or preferred partners within assistant environments.cnbc+1
Transparency and trust
Assistant-led recommendations and purchases raise new questions about transparency:
- Ranking logic: Users and brands may want to understand why certain products are recommended over others; explaining this in simple terms without exposing sensitive models is challenging.bigcommerce+1
- Commercial influence: Where advertising or sponsored placements exist within assistant experiences, they must be clearly labelled to maintain trust.blog+1
- Error handling: Protocols need robust ways to handle disputes, returns, and mis‑fulfilment when the assistant initiated the transaction.developers.googleblog+1
These concerns are especially acute for regulated sectors and high‑value purchases, where mistakes carry outsized consequences.computerworld+1
Areas still evolving
Several aspects of agentic commerce and assistant-led discovery are still in motion:cnbc+1
- The precise mix of organic and paid visibility within assistant answers.
- How much control brands will have over how assistants describe and position their products.
- The standards by which regulators and industry bodies will judge fairness, transparency, and competition in assistant-led commerce.computerworld+1
Digital leaders should expect rapid change, pilot carefully, and plan for iterative adaptation rather than one‑off implementations.cnbc+1
Section summary: UCP and OpenAI-driven discovery introduce new dependencies and questions around data ownership, platform power, transparency, and regulation, requiring deliberate governance and ongoing monitoring rather than blind adoption.cnbc+1
9. Conclusion
The combination of Google’s Universal Commerce Protocol and OpenAI-driven product discovery marks a structural shift from page-centric, click-based commerce to assistant-led, protocol-driven journeys where product and offer data are the primary levers of visibility and growth. Discovery is becoming conversational, decisions are increasingly made inside AI environments, and purchases can be completed without ever loading a traditional product page.bigcommerce+2
For digital leaders, this is not a distant scenario but an emerging reality across Google’s AI surfaces, ChatGPT, and other agentic experiences that are already influencing how customers research and buy. Winning in this environment means treating product and commerce data as a first‑class strategic asset, investing in structured, consistent, and trustworthy information, and building architectures and teams that can support open standards such as UCP and evolving assistant ecosystems.blog+5
The organisations that adapt early will not only preserve visibility as traditional SEO alone becomes insufficient, but will also be best placed to shape how assistant-led commerce works in their category – turning AI agents from a black box into a powerful extension of their own commercial strategy.searchengineland+1
- https://developers.googleblog.com/under-the-hood-universal-commerce-protocol-ucp/
- https://www.cnbc.com/2026/01/11/google-launches-universal-commerce-protocol-bets-on-ai-powered-retail.html
- https://developers.google.com/merchant/ucp
- https://ppc.land/google-launches-protocol-for-ai-agents-to-shop-across-platforms/
- https://www.bigcommerce.co.uk/blog/chatgpt-product-discovery/
- https://blog.google/products/ads-commerce/agentic-commerce-ai-tools-protocol-retailers-platforms/
- https://searchengineland.com/google-universal-commerce-protocol-467290
- https://www.computerworld.com/article/4115682/google-launches-new-ai-protocol-for-e-commerce.html
- https://www.checkout.com/blog/openai-acp-google-ucp-difference
- https://www.google.com/
- https://www.commerce.com/press/press-release-google-ucp/