The Content API for Shopping Was Sunset on August 18: How to Know in 5 Minutes If It's Your Problem

A store owner recently posted a simple question in the Google Ads Community. He had received an email from Google about moving from the Content API to the new Merchant API, he uses Merchant Center Next, and he had no idea whether he needed to do anything. That question is not an isolated one. Most articles about this deadline are written for developers or for agencies, not for the store owner who just got an email and wants to know one thing: does this affect me?

The short answer: probably not. But "probably" is not the same as "certain," and certain costs you five minutes.

Updated November 5, 2026. When I wrote this in July, the deadline was still ahead. Google sunset the API on August 18, but the shutdown turned out to be gradual, not a single switch. I corrected this article, and I wrote a follow-up with the check I would run today: Google Shopping products not updating? A 5-minute freshness check.

Key insights

• Google sunset the Content API on August 18, but the shutdown is gradual. Requests without an active extension have failed intermittently since September 1, and full shutdown is planned for early 2027.
• Test the data, not the label. Compare five products with Merchant Center and read the Last update column. The "Content API" label can stay on a working connection.
• If you use a platform app, your platform partner manages the migration. That tells you about their work, not whether your data arrived.
• In my reading, feed URLs, file uploads and Google Sheets are not what the shutdown targets. They can still fail in their own ways, so the check applies to them too.
• Extensions do not reach past the planned early 2027 shutdown. Ask your provider, do not plan around it.

What actually happened since August 18

Google replaced the Content API for Shopping, the interface that tools and scripts have used for over a decade to push product data into Merchant Center, with the new Merchant API. Google's documentation says the old API "was sunset on August 18, 2026." That does not mean everything stopped on one day.

Since September 1, requests from integrations without an active extension fail intermittently with an HTTP 410 error. Google warns that failing requests "will become more frequent until all requests fail at decommissioning," which it places in early 2027, subject to revision. Google's sunset guide has the details.

An integration that fails some of the time sets off no alarm. Some updates get through, some do not, and nothing tells you which. That is the risk: it happens in a layer you never normally see, between your product data and Merchant Center.

Google announced the change on August 18, 2025, so there was a full year of transition time. If you never touched it, that is not bad luck, there was simply never a reason to look at that layer.

The five-minute test

Do not look for a label. Test whether your data arrives. Pick three to five products you changed recently: a new price, a sale price, a product that sold out or came back in stock. For each one, compare two places.

1. Your store. Note the price, the sale price and the stock status on the product page.
2. Merchant Center. Open Products and go to the All products tab. Menu names differ between versions of Merchant Center, so look for the table of your products. Check the price, sale price and availability, and read the Last update column, which Google describes as "When your product was last updated."

If both places agree and Last update is recent, that product is fine. If your store says one thing, Merchant Center says another, and Last update is older than your feed schedule, your data is not arriving. Judge against your own schedule: with an hourly feed, a three-day-old change is a red flag. With a daily feed, give it a day.

One thing not to rely on: the Data sources screen can show "Content API" as the source even when products come in through the Merchant API. Google says these instances are "expected and require no action from you." So the label is not a test. The full version of this check, with five product types and a question to send your provider, is in the freshness check.

Who needs to act, and who does not

Most coverage of this change buries the reassurance under alarming language and skips the question that matters: who is responsible for your connection?

If you sell through the official app of an ecommerce platform, Google says your platform partner manages the migration on your behalf and that no action is required on your part. That is a statement about your partner's work, not about your data, so run the check above.

In my reading, a feed URL that Google fetches on a schedule, a manual file upload or a Google Sheets connection is not the kind of connection the shutdown targets. Google's pages do not say this in so many words, so treat it as my reading, not a Google claim. These routes can still fail in their own ways, such as a schedule that stopped or a fetch that errors, and the check catches those too.

Who does need to act: stores with a custom-built integration that calls the Content API directly, because Google says developers "must update your applications to call the Merchant API," or a plugin or feed tool that never moved. That group is the real risk, not because it is common, but because it is invisible until it breaks. The route table in the freshness check shows who handles what for each route.

What goes wrong when updates stop

A broken connection rarely gives a clear signal, and it does not remove your products right away. Google says all products "expire from your Merchant Center account 30 days after the last refresh." Until then, a product stays in your account with the last data it received: the old price, the old stock status. Automatic item updates can correct some prices and stock levels, but Google says they "aren't a replacement for regular updates of your product data."

So your products can stay approved and your account can look normal while a share of your prices and stock levels is out of date. That is why a feed problem is always more expensive than an ad problem. A bad bid setting shows up in your results. A stale feed shows up in your revenue, weeks later.

Extensions: what they are and what they are not

Google has an extension request form for developers and providers who cannot migrate in time. Approved extensions "protect your projects from scheduled error responses through your approved extension window." But Google also says extensions "don't extend past final decommissioning in early 2027."

In July I wrote about extension dates of October 15 and December 31. I cannot confirm those dates on any Google page, so I removed them.

This is a question for your developer or feed tool provider, not something to plan your store around. If they tell you they have not migrated yet, ask whether they requested an extension, and until when.

Why this is a feed problem, not an ad setting

This entire story plays out in the layer between your product data and Merchant Center, not in your Google Ads campaigns. Your bid strategy, your audiences, your ad copy, none of that changes because of this deadline. What changes is the road your product information travels to get to Google in the first place.

That distinction is exactly why feed problems get overlooked so often. Everyone looks at the campaign when something breaks, while the cause sits one layer earlier. Anyone who knows the whole chain, from product data to feed to Merchant Center to the auction, sees a sunset like this for what it is immediately: a checkpoint in the pipeline, not in the ads. It is the same reason I never look at feeds and campaigns as separate worlds when I review an account, and it is worth checking your setup against the complete guide to Google Ads for ecommerce while you are in there, since a sunset like this is exactly the kind of gap a wider feed health check catches.

What to do now

Check today, not next week, whether your data arrives. Pick three to five products you changed recently and compare them with Merchant Center, including the Last update column. It costs five minutes. If the data is stale, ask whoever supplies your connection, whether that is your platform, plugin developer, feed tool provider or developer, one question: "Does the integration that sends my products to Merchant Center use the Merchant API, and when did it last send my products successfully?"

Want to know your whole feed and Merchant Center are healthy, not just this one setting? The free feed review covers exactly that: the 5 biggest fixes, in plain language, within 3 business days.

Frequently asked questions

How do I know if the Content API shutdown affects me?

You cannot reliably tell from Merchant Center. A data source can show "Content API" even when products come in through the Merchant API, and Google says this is expected and requires no action. Test whether your data arrives instead: compare a few recently changed products with Merchant Center and read the Last update column. If a third-party tool manages your feed, ask them directly.

Does this affect scheduled fetch, manual uploads, or Google Sheets feeds?

In my reading, probably not. The shutdown is about software that calls the Content API, and Google's pages do not say how it affects a feed URL, a file upload or a Google Sheet. They can fail in their own ways, so run the freshness check to be sure.

What happens now that the Content API has been sunset?

Google sunset the API on August 18, 2026, but the shutdown is gradual. Since September 1, requests without an active extension fail intermittently with HTTP 410, and Google says failures will become more frequent until final decommissioning, planned for early 2027 and subject to revision. A connection that fails now and then can go unnoticed while products keep their old prices and stock.

Can I still get an extension?

Google has an extension request form, and approved extensions protect a project from scheduled errors during the approved window. Extensions do not extend past final decommissioning in early 2027. Developers and providers request them, so ask yours whether they did and until when.

What happens to my products if updates stop arriving?

Google says all products expire from your Merchant Center account 30 days after the last refresh. Until then they keep the last data they received, including the old price and stock status. Automatic item updates can correct some values, but they are not a replacement for regular updates of your product data.