Google Merchant API Changes: Migrate or Request an Extension by August 18, 2026

On August 18, 2026 Google permanently shuts down the Content API for Shopping — the interface stores have used for over a decade to send product data into Merchant Center. Its replacement is the new Merchant API. If your products reach Google through a custom integration, a feed plugin or a third-party service, you need to migrate to the Merchant API before the deadline — or officially request an extension. Here’s what changes, who is affected (and who isn’t), what breaks after August 18, and what to do right now.

What changes: Content API for Shopping → Merchant API

Google is sunsetting the old Content API for Shopping — the v2.1 REST API that retailers and tools have used for years to upload product data into Google Merchant Center automatically. The new primary programmatic interface is the Merchant API — in Google’s words, “a new, simplified API designed to help you manage your Merchant Center accounts”.

The key architectural difference: the Merchant API is modular. Instead of one monolithic API, it’s a set of independently versioned sub-APIs:

• Products — add and update product data;
• Inventories — local and regional inventory;
• Accounts — account, users, sub-accounts and access management;
• Data sources — primary, supplemental, inventory, promotions and reviews feeds;
• Reports — performance and market analytics;
• Promotions, Reviews, Notifications and other sub-APIs.

Technically almost everything changes: the request domain (shoppingcontent.googleapis.com → merchantapi.googleapis.com), the resource identifier format, added gRPC support alongside REST, and prices now sent in micros (amountMicros) instead of a string value. The batch method customBatch is gone — replaced by parallel asynchronous calls.

For a quick refresher on what the platform is and why a store needs it, see our guide “What is Google Merchant Center and what is it for”.

What Google’s notification looks like

Google notifies account owners by email (the Merchant Center newsletter) and shows a banner inside the interface itself. It looks like this:

The key date: August 18, 2026

The official shutdown date for the Content API for Shopping is August 18, 2026. After that date, calls to the old v2.1 endpoints stop working (developers report a 410 Gone response). This means any integration still relying on the Content API stops syncing: product uploads, prices and availability will no longer update.

The consequence for a store: products that came in through that integration stop being updated and can eventually disappear from Google Shopping, free listings and Shopping ads — once the data goes stale or gets disapproved.

Don’t confuse two dates. There is also February 28, 2026 — the deadline to move from the Merchant API beta (v1beta) to the stable v1. That one only affects those already on the new API’s beta. August 18, 2026 is the final shutdown of the old Content API for Shopping.

Who is affected — and who isn’t

This is a technical, API-level change, not a change to your Merchant Center account. So not everyone needs to react.

You need to act if you:

• have a custom integration with Merchant Center (nightly feed pushes, price/stock update scripts, custom product-sync code);
• use a third-party app or feed service that connects to Merchant Center via the Content API;
• are an agency or SaaS platform managing client product data programmatically.

You don’t need to do anything if you:

• manage products only through the Merchant Center UI manually;
• use Google Sheets, scheduled feed fetches by URL/FTP, or manual file uploads;
• work through a platform or plugin where the provider handles the migration (see below).

A note on feed plugins and platforms (Shopify’s Google channel, WooCommerce feed plugins, Channable, DataFeedWatch, Feedonomics, etc.). Here the vendor is responsible for migrating to the Merchant API — you don’t write the integration code yourself. Your job is simpler: confirm with your platform/plugin provider that they’ve already migrated to the Merchant API (or will before August 18). The real risk is abandoned plugins, unmaintained custom scripts and in-house integrations that nobody updates.

How to request an extension

Contrary to the widespread claim that this is a “hard deadline with no extensions”, Google officially provides extended access to the Content API for Shopping for those who need more time to migrate. The request is submitted through a Google Form linked from the official Merchant API support page.

1. Open the official Merchant API support page and follow the extended-access link — or use the direct Google Form link.
2. In the form, provide your account details (Merchant Center ID), a contact and the reason you need additional time.
3. Submit the request before August 18, 2026 — with a buffer, not on the last day, so access isn’t interrupted.

Google doesn’t publicly document the exact form fields, so refer to the live form. An extension is a safety net, not a reason to postpone migration: the old API will be turned off eventually anyway.

Checklist: what to do now

1. Determine how products reach Merchant Center. Manual / Google Sheets / scheduled feed — you’re safe. Via an API integration — you need to migrate.
2. If it’s a platform, plugin or agency — ask the provider whether they’ve migrated to the Merchant API and get a date.
3. If you run a custom integration — plan the migration now: audit calls → register a Google Cloud project → update endpoints and resource names → convert prices to amountMicros → drop customBatch → test → deploy.
4. Can’t finish before August 18 — submit the extended-access form.
5. Already on Merchant API beta — don’t miss the separate February 28, 2026 deadline (v1beta → v1).

The Spilno Agency view

This change sounds scarier than it is: the vast majority of stores that manage products manually, via Google Sheets or off-the-shelf plugins won’t be affected at all. But the blind spot is real — old custom or once-commissioned integrations that the business owner has long forgotten, yet which still feed the product data. That feed can silently “die” on August 18, and the store will only notice when products start dropping out of Google Shopping. Our advice for European businesses: don’t guess — check. If you’re not sure exactly how your products reach Google, we’ll audit your Merchant Center and tell you whether you need to act before the deadline. If the account already has issues, we help with Google Merchant Center unblocking.

Frequently asked questions (FAQ)

What changes in the Google Merchant API on August 18, 2026?

Google permanently shuts down the old Content API for Shopping. The new modular Merchant API becomes the primary programmatic interface for sending product data into Merchant Center. Integrations that stay on the old API stop working after that date.

Does this affect me if I don’t use the API?

No. If you manage products manually through the Merchant Center UI, via Google Sheets, a scheduled URL/FTP feed or manual file uploads — nothing changes for you. The change only affects programmatic integrations through the Content API.

I use Shopify / WooCommerce / a feed service. What do I do?

The platform or plugin provider is responsible for migrating the integration to the Merchant API. You just need to confirm with them that the migration is done (or will be by August 18, 2026). The only risk is abandoned or unmaintained plugins and in-house scripts.

What happens after August 18, 2026 if I do nothing?

Calls to the Content API for Shopping stop working. The integration stops updating products, prices and availability, and products can eventually disappear from Google Shopping, free listings and Shopping ads.

How do I request an extension for Content API access?

Google lets you request extended access through a Google Form linked from the official Merchant API support page. In the form you provide your Merchant Center account details and the reason you need more time to migrate. Submit it in advance rather than on the last day.

How does the Merchant API differ from the Content API for Shopping?

The Merchant API is modular: instead of one API it’s a set of sub-APIs (Products, Inventories, Accounts, Reports, Data sources and others), each independently versioned. The request domain, resource identifier format and pricing format (micros) change, gRPC support is added, and the customBatch method is removed.

What is the February 28, 2026 deadline and does it apply to me?

It’s a separate date: moving from the Merchant API beta (v1beta) to the stable v1. It only applies to those already on the new API’s beta. The shutdown of the old Content API for Shopping is a different date — August 18, 2026.