Tag: Google Merchant Center

  • Google UCP and SEO: How I’m Preparing for AI Commerce

    Google UCP and SEO: How I’m Preparing for AI Commerce

    Google's Universal Commerce Protocol changes the path from search to sale

    For as long as I’ve worked in search marketing, I’ve viewed the path to purchase as a simple sequence: search query → click → buy.

    I’ve approached SEO through much the same model, using organic traffic, impressions, and click-through rate (CTR) as the primary measures of success.

    Google’s Universal Commerce Protocol (UCP) tells me that this familiar path is changing. Google is evolving from a discovery engine into a transaction layer where searching and buying can happen inside the same experience.

    With the rise of “agentic commerce,” I’m seeing Google gain the ability to discover, evaluate, compare, and purchase products on a user’s behalf within AI-powered experiences such as AI Mode, Gemini, YouTube, and Gmail.

    I believe the SEO implications are substantial. Instead of optimizing only for clicks, I now need to think about optimizing for AI-assisted transactions. If a brand cannot communicate through UCP and the product data that supports it, it risks becoming invisible to the next generation of shoppers.

    Here’s how I understand UCP, why I think it will reshape digital marketing, and what I recommend doing now to prepare an SEO strategy for agentic commerce.

    UCP: The infrastructure behind AI transactions

    I think of UCP as an open-source, vendor-agnostic standard that supports the entire commerce lifecycle inside an AI interface. That lifecycle can extend from product discovery and cart creation through checkout, fulfillment, and post-purchase tracking.

    Google co-developed UCP with Shopify, Walmart, Target, Wayfair, Etsy, and other commerce leaders. From my perspective, it acts as a universal translator between AI shopping agents and the systems merchants use to operate their online stores.

    Google UCP - Pay with GPay

    The clearest analogy I can make is that UCP may become the ecommerce equivalent of HTTPS. HTTPS standardizes secure communication between browsers and servers; UCP standardizes how AI agents interact with online stores. Instead of building a custom one-to-one integration for every merchant, an AI agent can use a shared framework to browse inventory securely and complete purchases across many stores.

    How I see AI transactions flowing through UCP

    Imagine I ask AI Mode to “find and order a replacement water filter for a 2021 Samsung French-door fridge with the fastest shipping.” UCP can coordinate that transaction through a structured workflow.

    Capability publication

    First, I expect the merchant to publish the capabilities its store supports, including product search, live pricing, fulfillment options, and accepted payment methods. This gives the AI agent a clear picture of what it can request and complete.

    Three mobile screens show a Monos suitcase listing, Google Pay order review, and completed checkout through Google’s Universal Commerce Protocol.
    From product discovery to payment and confirmation, this mobile shopping sequence shows a Monos suitcase purchase completed with Google Pay through Google’s Universal Commerce Protocol.

    Handshake

    Next, the AI agent reads the merchant’s profile, compares those capabilities with its own, and establishes a secure path forward. I see this step as the point where the systems can align on details such as loyalty programs and supported digital wallets.

    Action execution

    Once the systems are aligned, the AI searches for the product, verifies real-time inventory, builds the cart, and uses the Agent Payments Protocol (AP2) to complete a secure, tokenized transaction.

    Human escalation

    If the transaction needs my input—perhaps to select a delivery window or confirm a shipping address—UCP can pause the process and prompt me. After I respond, control returns to the AI so it can finish the workflow.

    Dig deeper: How Google’s Universal Commerce Protocol could reshape search conversions


    Why I believe UCP matters for search and SEO

    I don’t see UCP as merely a technical update. I see it changing the way AI discovers, evaluates, and purchases products—and that makes it directly relevant to SEO.

    1. I’m shifting from click-throughs to buy-throughs

    In an agentic search environment, I can no longer treat website traffic as the only measure of business value. Features such as Universal Cart can let shoppers add products from multiple retailers to one Google cart and check out with Google Wallet, dramatically shortening the buying journey.

    A shopper may never visit my homepage, category page, or product detail page. That changes my SEO objective: I need to earn product selection within the AI recommendation layer so a search query can become a sale even when it generates no intermediate website visit.

    2. I’m planning for hyper-personalized queries

    I’m also rethinking keyword research. Shoppers are moving beyond broad searches such as “men’s running shoes” and using detailed, situational prompts like “Best running shoes for flat feet under $150 that can arrive by Friday.”

    To match a request that specific, I know a search engine needs more than polished on-page copy. It needs rich, structured, and queryable product attributes. UCP helps bridge that gap by giving AI agents a way to match merchant inventory with a shopper’s precise requirements.

    3. I expect less checkout friction

    I continue to see cart abandonment as a major ecommerce challenge, especially when shoppers encounter long forms, broken checkout flows, or unexpected shipping costs. Because UCP can work with secure digital wallets and automatically pass verified user data, I expect it to eliminate many of those friction points.

    Glowing blue streams of people converge on a search bar and digital portal, symbolizing SEO traffic, AI visibility, and customer acquisition.
    As AI reshapes search, every glowing path to discovery carries commercial value—turning SEO investment into a conversation about pipeline, risk, and customer acquisition costs.

    For high-intent, urgent, or repeat purchases, I believe merchants that support UCP may capture more conversions than competitors that send every shopper to a separate checkout experience.

    4. I can retain brand control and customer ownership

    One detail I consider especially important is that the merchant remains the Merchant of Record when a transaction takes place through UCP. I can still control pricing, fulfillment, and return policies while retaining the customer relationship and first-party data. UCP provides the transactional infrastructure without replacing the merchant’s role.

    Dig deeper: Winning the AI decision layer: From AI discovery to agentic commerce

    How I recommend preparing a brand for UCP

    If I limit an SEO strategy to blog articles and meta descriptions, I overlook the technical infrastructure that powers AI commerce. To make products eligible for UCP-powered experiences, I recommend focusing on the following priorities.

    I would optimize the Merchant Center feed

    I no longer view Google Merchant Center (GMC) as a tool used only for Shopping ads. I see it becoming a primary source of product information for AI discovery, which makes feed quality central to both visibility and transaction eligibility.

    • Enable the native_commerce attribute: To opt into UCP-powered checkouts, I would add the native_commerce attribute to the product feed. Google recommends using supplemental feeds to apply it at the product level without changing the primary feed.
    • Map product identifiers: I would make sure every product ID in the GMC feed maps one-to-one with the corresponding ID in the internal checkout API. If the identifiers differ, I would use the merchant_item_id attribute to align them.
    • Complete policy data: I would keep returns, shipping, and customer-support information complete and current. Clear policy data gives an AI agent the details it needs to evaluate a merchant confidently.

    I would align structured data with the product feed

    Because AI search depends on consistent information, I would keep the Product, Offer, and Review schema on the website synchronized with the Merchant Center feed. If the price, availability, identifiers, or other details conflict, validation problems could make a product ineligible for AI-powered checkout.

    I would prepare for conversational attributes

    As Google introduces semantic attributes designed for conversational AI search, I would prepare inventory and product-information systems to supply richer answers. In particular, I would prioritize:

    • Real-time inventory availability.
    • Direct answers to product FAQs, such as “Is this jacket machine washable?”
    • Detailed compatibility information, including accessory pairings, sizing guides, and model-specific replacements.

    I would treat these details as more than feed enhancements. They are the signals that help an AI agent decide whether a product satisfies a nuanced request involving price, fit, compatibility, delivery speed, or another real-world constraint.

    Beyond clicks: The next SEO opportunity I see

    To me, the Universal Commerce Protocol reflects a broader transformation in search. It expands the role of SEO beyond generating traffic and brings product data, inventory systems, checkout infrastructure, and conversion readiness into the search conversation.

    By prioritizing structured product data, reliable commerce information, and readiness for agentic transactions, I can position a brand to capture demand at the exact moment a shopper expresses intent.

    I don’t believe the future of search will be only about getting found. Increasingly, it will be about making sure the products I represent can be evaluated, selected, and bought.


    Inspired by this post on Search Engine Land.


    crushpress.ai community screenshot
  • Google Merchant Center Drops “Next” in Simple Rebrand

    Google Merchant Center Drops “Next” in Simple Rebrand

    I’m adjusting how I refer to Google’s shopping platform now that Google has dropped “Next” from Merchant Center Next. Going forward, the product is simply called Google Merchant Center.

    Google made the change official in a Merchant Center announcement, saying, “The platform you use today will simply be referred to as Google Merchant Center.” For anyone managing product feeds, shopping campaigns, or merchant accounts, this is mainly a naming update rather than a product change.

    I remember when Google Merchant Center Next was introduced in 2023 as the newer version of the old Google Merchant Center. Over the past few years, more merchants, site owners, and advertisers moved into that updated experience.

    At this point, it appears that Merchant Center Next has effectively become the standard experience. So Google is removing the “Next” branding and returning to the simpler name: Google Merchant Center.

    Futuristic data archive with glowing server-like filing cabinets, stacked documents, and network lights symbolizing AI marketing data infrastructure.
    Rows of illuminated data cabinets and paper files stretch into the distance, capturing the pressure on marketers to turn fragmented customer data into a smarter performance engine.

    Google said users will start seeing the “Next” branding removed from Help Center articles, email communications, and the Merchant Center interface.

    Google also clarified that no action is required and that the name change does not affect existing accounts. In other words, I do not need to update settings, migrate anything, or make account-level changes because of this rebrand.

    Why does this matter? When I talk about Google’s merchant tools now, I can leave off “Next” and just call the platform Google Merchant Center. Honestly, that is what many of us were already calling it anyway.


    Inspired by this post on Search Engine Land.


    crushpress.ai community screenshot
  • Google Merchant Listings Gain Powerful Sale Data Updates

    Google Merchant Listings Gain Powerful Sale Data Updates

    I’m seeing Google expand merchant listing structured data with support for sale duration and the Product.category property. The update brings Google Search’s merchant listing structured data closer to the capabilities already available in Google Merchant Center feeds.

    Sale duration. Google added a new Sale duration section to its Merchant listing structured data documentation. In that update, Google said the guidance explains how to use the validFrom, validThrough, and priceValidUntil schema.org properties to define the effective date range for sale prices.

    I find this useful because Google’s guidance also covers best practices and examples for placing those properties on either Offer or PriceSpecification nodes. Google said the change aligns schema.org usage with the Merchant Center feed attribute sale_price_effective_date, giving merchants clearer instructions for handling sale price timing in structured data.

    Screenshot of Google's merchant listing structured data documentation explaining sale duration properties with JSON-LD examples for validFrom and priceValidUntil.
    Google's sale duration guidance shows merchants how to define when a sale price starts and ends in structured data, including Offer and UnitPriceSpecification JSON-LD examples.

    Here is the new sale duration section Google added:

    Product category. Google also updated the same Merchant listing structured data documentation to include support for the Product.category property.

    Google merchant listing documentation showing Product.category structured data with Text and CategoryCode examples.
    Google’s merchant listing guidance now shows how product categories can mix custom text labels with Google Product Category codes in structured data.

    Google wrote that the documentation now explains how Product.category can be used with both Text and CategoryCode types. According to Google, this aligns with Google Merchant Center feed specifications for the product_type and google_product_category attributes.

    From my perspective, this makes the structured data more practical for merchants because it lets them provide both merchant-defined and Google-defined category details directly in schema.org markup. Google said this can enhance product information for Google Search and Shopping.

    Neon Google search bar with microphone icon over a futuristic digital data background, representing search technology and SEO updates.
    A glowing Google search bar cuts through streams of digital data, capturing the fast-moving world of search, shopping visibility, and SEO innovation.

    Here is what Google added for product category support:

    Why I care. If I maintain merchant listing structured data for Google, these additions are worth reviewing. Product category support can help Google better understand the products being provided, which may improve how those products match relevant queries.

    I also see sale duration support as a practical improvement for planning promotions. When I update merchant listing structured data, I can now define sale price timing more clearly and align that markup more closely with Google Merchant Center feed behavior.


    Inspired by this post on Search Engine Land.


    crushpress.ai community screenshot
  • Discover Google’s New AI Tools for Enhanced Retail Performance

    Discover Google’s New AI Tools for Enhanced Retail Performance

    Today, I’m thrilled to share that Google has unveiled exciting new tools in the Merchant Center, all geared towards boosting retailer visibility on AI-driven shopping platforms. Announced at Google Marketing Live 2026, these tools are set to transform how products are discovered.

    Driving the news. Let me introduce you to AI Performance Insights, a fresh reporting feature that gives merchants a snapshot of their brand’s performance across AI platforms.

    This handy tool lets me compare my brand’s share of voice with similar competitors, ensuring I stay on top of AI-driven discovery metrics.

    Google is also introducing Conversational Attributes, enhancing how we optimize our product listings to align with natural, conversational searches.

    How it works. I can now add conversational attributes and update descriptions directly in the Merchant Center. Google’s AI can utilize this structured data to meet conversational search queries seamlessly across AI Mode, Gemini, and other AI platforms.

    These updates are crafted to enhance discoverability as AI continues to reshape shopping experiences.

    Moreover, Ask Advisor integrations are soon to be part of my Merchant Center tools.

    Why we care. Structured product data is now more essential than ever as AI shopping experiences proliferate across Search, Gemini, and Maps.

    By adapting product descriptions for conversational discovery, I can better position my products within AI-generated recommendations and shopping paths.

    These new reporting tools also give me early visibility into how my brand performs in AI-powered environments.

    What to watch. With the rise of conversational search behavior, optimizing product feeds for AI visibility is becoming increasingly critical. I’ll also be keeping an eye on how Google defines and measures “share of voice” within these AI-powered shopping ecosystems.

    Availability. AI Performance Insights will soon roll out in the U.S., Australia, Canada, India, and New Zealand. Meanwhile, Conversational Attributes are launching globally.

    Dig deeper. Here are some more updates from Google Marketing Live 2026:


    Inspired by this post on Search Engine Land.


    crushpress.ai community screenshot