Google Merchant API migration: What changes before the August 2026 deadline (and how to prepare)

Google is retiring the Content API for Shopping on August 18, 2026, and replacing it with the new, modular Merchant API. If any part of your product data reaches Google Merchant Center through a programmatic API connection, this transition affects you, and the window to act is closing soon.

If you manage your Google feeds through Productsup, this is largely handled for you (more on that below). If you don't, here's exactly what's changing, who needs to act, and how to migrate without breaking your listings.

What is the Google Merchant API, and why is Google replacing the Content API?

The Google Merchant API is Google's latest API for managing product information, pricing, inventory, promotions, and Merchant Center accounts. It replaces the legacy Content API for Shopping, which has powered Google Merchant Center integrations for many years.

While both APIs serve the same purpose, the Merchant API introduces a more modern architecture that is easier to extend and better aligned with Google's evolving commerce platform.

Google designed the Merchant API to provide:

• A modern, REST-based API structure
• Better scalability for large product catalogs
• Improved resource organization
• Faster access to new Merchant Center capabilities
• A foundation for future commerce features

Some of the key improvements include:

• Faster issue resolution with richer product status and diagnostics, making it easier to identify disapprovals, price mismatches, and other listing issues.
• Real-time product status notifications, eliminating the need to poll for updates repeatedly.
• Improved inventory management, including dedicated support for local and regional inventory.
• Programmatic management of supplemental data sources, making it easier to layer pricing, availability, or promotional data onto existing product feeds.
• Support for future Merchant Center features, as Google has confirmed that all new capabilities will be built exclusively on the Merchant API.

The migration is primarily an infrastructure update. Merchants can continue using Google Shopping, Performance Max, and free listings as before; only the way product data is submitted changes.

The Content API sunset timeline

Google has already begun phasing out the Content API.

For most businesses, August 18, 2026 is the only deadline that matters. If your systems still depend on the Content API after this date, product updates will no longer be delivered through that integration.

What’s changing: Merchant API vs. Content API

The Merchant API replaces the Content API without changing the core purpose of managing product data. The biggest differences are in the underlying architecture and how developers interact with Google's services.

From a merchant's perspective, the goal remains to keep product information accurate and synchronized in Google Merchant Center. For developers and technology teams, however, migrating requires updating API integrations to use the new Merchant API endpoints and resources.

Do you actually need to migrate?

No, not everyone. It depends on how your product data reaches Google Merchant Center.

You likely need to migrate if you:

• Push product data to Google Merchant Center using the Content API for Shopping
• Use custom-built API integrations or in-house data pipelines
• Have reporting or automation tools that connect directly to the Content API
• Rely on an older third-party integration that still uses the Content API

You may not need to migrate if you:

• Upload products using CSV or XML files
• Use scheduled fetch to import product feeds
• Manage products through Google Sheets
• Use a feed management platform or ecommerce solution that already supports the Google Merchant API

The first step is understanding how your product data reaches Google today. Once you know that, it becomes much easier to determine whether any work is required before the deadline.

What happens if you don't migrate?

Businesses that continue relying on the Content API after the deadline risk losing their ability to keep product information accurate. Potential consequences include:

• Product updates stop syncing
• Inventory changes are not reflected in Merchant Center
• Price updates fail
• New products are not published
• Existing listings become outdated
• Shopping campaigns may use stale product information

The exact impact depends on your implementation, but the safest approach is to complete the migration well before the deadline rather than waiting until existing integrations fail.

How Productsup supports Google Merchant API migration

For Productsup customers, the transition is designed to be straightforward.

If you manage your Google feeds through Productsup, you don't need to take action on this migration. Productsup manages the Google Merchant Center integration layer and is aligning its connectors with the Merchant API ahead of the August deadline, so your product data keeps flowing without disruption. If anything does require action on your side, your Customer Success Manager will reach out, and you can always confirm your current setup with the Productsup support team.

And, if you're evaluating feed management solutions or planning your migration strategy, choosing a platform that already supports Google's latest API can reduce implementation effort and minimize disruption.

Want a quick demo of how Productsup supports Google Merchant Center? Connect with us today!