Google Is Shutting Down the Content API for Shopping on 18 August. The 3-Week Checklist for Shopify, WooCommerce and Magento Stores

Google is retiring the Content API for Shopping on 18 August 2026 and replacing it with Merchant API v1. Any system that still sends product data through the old endpoints stops syncing on that date. If you upload your products manually, or you use the official Shopify or WooCommerce apps, you are almost certainly fine and can stop reading after the next section. If a developer built you a custom feed integration, you have roughly three weeks to act.

That is the entire story. The rest of this post exists because the coverage so far has been written for developers, and most people who need to know about the Content API for Shopping shutdown are not developers. They are store owners who have no idea whether the thing being switched off is something they use.

So let us settle that first.

Am I actually affected? A 60-second decision tree

Open Google Merchant Center, go to Products, then Data sources. Look at how your main product source is described. Then find yourself below.

You upload a file — CSV, XML, Google Sheets, or a scheduled fetch from a URL. You are not affected. Not slightly, not partially. File-based uploads never touched the Content API for Shopping. Nothing changes for you on 18 August. Close the tab.

Your data source is named after an app or platform — Shopify, Google for WooCommerce, a feed tool. You are almost certainly covered. Google's migration documentation addresses this directly, stating that merchants using a third-party technology partner to sync product data — it names the Google & YouTube app on Shopify as its example — do not need to do anything, because the provider handles the migration. Your only job is to confirm your app is connected and running a current version.

Your data source is an API source you do not recognise, or a developer set up your feed years ago. You are at risk and you need to find out today. This is the group that gets caught out.

Nobody at your company knows how products get into Merchant Center. Treat yourself as at risk until proven otherwise. This is more common than people admit, especially where the original developer has moved on.

What is actually changing, in plain English

Since 2014, the Content API for Shopping has been the programmatic route for pushing product data into Merchant Center. Merchant API v1 replaces it. This is not a rename — it is a rebuild, which is why the shutdown has been given a two-year runway and why plugin vendors have needed all of it.

For anyone who wants the specifics, the changes that break existing code include a new base URL (merchantapi.googleapis.com instead of shoppingcontent.googleapis.com), a mandatory Developer Registration step linking your Merchant Center account to a Google Cloud project, a different product identifier format where the old colon-separated channel:contentLanguage:feedLabel:offerId becomes a tilde-separated contentLanguage~feedLabel~offerId with the channel element dropped, and a changed price format where amounts move to micros — one million micros equals one unit of your currency. The customBatch method is gone entirely, replaced by asynchronous parallel calls.

If none of that meant anything to you, that is genuinely fine. It is the checklist your developer needs, not you. Send them this section.

One detail worth flagging for anyone who started migrating early: Merchant API v1beta was itself discontinued on 28 February 2026. If your team adopted the beta, they had to migrate a second time, to v1. It is worth confirming they did.

Where each platform actually stands

Shopify. If you use the official Google & YouTube app, you are covered — this is the exact scenario Google names in its own documentation. Open the app, confirm it is connected to your Merchant Center account, and confirm products are syncing. That is the whole job. Be aware of a separate deadline: non-Plus Shopify merchants have until 26 August 2026 to migrate their Google tags and upgrade Order status and Thank you pages, which is a different change with a different consequence. Stores running bespoke feed logic alongside the app should have that logic reviewed as part of any Shopify development work you have planned this quarter.

WooCommerce. The official Google for WooCommerce extension (previously Google Listings & Ads) is maintained to work with Google's current APIs, so keeping it updated is the requirement. A quick way to confirm the extension is your actual sync source: product IDs it creates carry a gla_ prefix in Merchant Center, so a WooCommerce product with ID 23 appears as gla_23. If your Merchant Center products do not carry that prefix, something else is feeding them, and that something else needs checking. Custom feed code in a child theme or a bespoke plugin is the classic hidden risk here, and it is worth an audit alongside any WooCommerce development work.

Magento and Adobe Commerce. This is the platform most exposed to the Content API for Shopping shutdown, and it is worth being blunt about why. Magento feed integrations are frequently handled by extensions from small vendors, or by bespoke modules written for one store years ago. Neither is guaranteed to be maintained. There is no central authority pushing an update to you. Check your Adobe Commerce Marketplace extension for a recent release that mentions Merchant API support, and if the vendor has gone quiet, assume you need to act. Bespoke integrations built into a custom module will not update themselves and need a developer — this is standard Magento development work, but it needs booking now rather than in mid-August.

Third-party feed tools. Established platforms have had two years of notice and have generally handled it. Email your account manager and get written confirmation anyway. It takes five minutes and it moves the risk off your desk.

How to test before the deadline

Do not test on your live catalogue. Google provides a documented process for creating test accounts, which lets you validate authentication, data formatting and error handling without touching real listings. Merchant Center also has a page for verifying your account's connection to the Merchant API, which is the fastest confirmation that a migration actually worked.

The sensible sequence, if you or your developer are migrating: complete Developer Registration first, then migrate read operations such as listing products and retrieving statuses, then move write operations, then run both systems in parallel long enough to confirm the data matches. Parallel running is the step people skip when they are short of time, and it is the step that catches problems while they are still cheap to fix.

What a broken feed actually looks like

If a migration is missed, the failure is quiet rather than dramatic. Your products do not vanish in a puff of smoke on 19 August. They simply stop updating.

In practice that means Merchant Center shows your data source last updating on 18 August and never again. Prices and stock levels freeze at whatever they were that day. Over the following days, the mismatch between your website and your listings triggers errors — price mismatch and availability mismatch warnings are the usual first symptoms — and affected products move to disapproved. Shopping campaigns keep spending against increasingly wrong information until enough products drop out that delivery collapses.

That lag is the dangerous part. A store that only checks Merchant Center weekly could lose most of a week's Shopping performance before anyone notices anything is wrong.

If you cannot make the deadline

Here is the part almost no coverage mentions, and it is worth knowing before you panic-book emergency development time.

Google's own migration documentation includes a link to apply for extended access to the Content API for Shopping if you need additional time to migrate. It is a formal application, not a guarantee, and it should not be treated as a reason to relax — but if you have discovered this late and a proper migration cannot realistically be finished in three weeks, applying is a far better option than missing the date and hoping.

Plenty of otherwise careful sources have described this as a hard cutoff with no flexibility. Google's documentation says otherwise.

Your three-week plan

This week: identify how your products reach Merchant Center. Data sources tells you. If it is a file upload, you are done.

Next week: get written confirmation from whoever owns the integration — the app vendor, the extension developer, or your in-house team. "It should be fine" is not confirmation.

Week three: verify the connection, run parallel if you are migrating, and check Merchant Center daily through the changeover. If you are not going to make it, submit the extension application rather than letting the date pass.

Most stores will get through the shutdown without noticing it happened. The ones that do not will be the ones where nobody checked.

If you would like a second pair of eyes on your setup before 18 August, book a call and we will tell you honestly which of the four groups above you fall into. If the answer is "you are fine", we will say so.

Sources

• Google for Developers — Migrate from Content API for Shopping to Merchant API (sunset date, technology partner guidance, extension application, technical changes; page last updated 22 July 2026)

• Google for Developers — Content API for Shopping release notes (deprecation notice)

• Google Merchant Center Help — Introducing Merchant API

• Google Ads Help — Migrate your Google tags with the Google & YouTube app on Shopify (26 August 2026 Shopify tag deadline)

• WooCommerce — Google for WooCommerce FAQs (gla_ product ID prefix)

Last verified against Google's documentation on 30 July 2026. Deadlines and platform support can change — check the linked Google pages before acting.