Google's Content API for Shopping Started Returning 410 Gone Yesterday. Most Coverage Forgot to Say Who Was Actually Affected.
Google's Content API for Shopping hit its sunset date on August 18. Calls to v2.1 endpoints now return HTTP 410 Gone, and Google has signalled no extension. The replacement, Merchant API v1, has been rolling out since April 22, 2026.
If you sell anything through Google Shopping, the useful question is not "is this bad." It is "did this touch me at all," and for a large share of small merchants the answer is no. That part got buried under a lot of deadline coverage.
What broke and what didn't
Broken: API-based integrations calling Content API for Shopping v2.1. Product data can no longer be pushed to Merchant Center through those endpoints. You get a 410 and the request is gone, not retried, not queued.
Still working: manual file uploads, scheduled fetches, and Google Sheets feeds.
That second list is the one worth reading twice. If your product feed is a spreadsheet Google pulls on a schedule, or a file you upload, or a URL Google fetches nightly, nothing happened to you yesterday. Those paths are not part of the deprecation.
This distinction matters more for solo operators than for anyone else, because the smaller the operation the more likely the feed is a Sheet. I would guess a majority of one-person ecommerce and affiliate setups never touched the Content API at all. They set up a scheduled fetch in year one and never revisited it.
The failure mode that should actually worry you
Here is the specific way this hurts someone who was affected.
A 410 on a feed push is not a loud failure. Your site stays up. Checkout keeps working. Merchant Center keeps showing your existing products, because they were already ingested. What stops is the update path. Prices go stale. Out-of-stock items stay listed. New products never appear.
If your sync runs on a cron and logs to a file nobody reads, the first signal is not an error page. It is a slow drift in Shopping performance over a week or two, followed by disapprovals when the stale data starts conflicting with what Google crawls on your actual product pages. By the time it is obvious, you have been quietly serving wrong prices to the highest-intent traffic you get.
That gap between "the integration broke" and "I noticed" is the real cost here, and it is a function of your monitoring, not of Google's timeline. A hard cutoff with a clean 410 is, honestly, the considerate version of this. Silent throttling would have been worse.
The ten-minute check
Work through these in order. Stop as soon as you get an answer.
One. Open Merchant Center, go to your feed settings, and look at how each feed is registered. If every feed says scheduled fetch, upload, or Google Sheets, you are done. Close the tab.
Two. If any feed is registered as an API source, find what is calling it. On a small setup this is usually one of three things: a plugin on your store platform, a third-party feed tool, or a script you wrote and forgot.
Three. For a plugin or a third-party tool, check the vendor's changelog for Merchant API support. The larger platforms have shipped this already, since the deadline has been known for months. Your job is to confirm you are on a version that includes it, which frequently means an update you have been deferring.
Four. For your own script, grep it for the v2.1 endpoint host and paths. Then run it once, manually, and read the response code. A 410 is unambiguous. This takes about ninety seconds and beats reasoning about it.
Five. Whatever the outcome, add an alert. Not a log line, an alert: if the sync exits non-zero or the last successful run is older than 48 hours, something should reach your phone. If yesterday's deadline cost you nothing but you leave with this one habit, it was a good trade.
What I'd actually do about the migration
If you are affected and you own the script, resist the urge to port it line for line. Merchant API v1 is not a renamed version of the old thing; it reorganises around sub-APIs and covers more than product data, including reporting and insights. A one-to-one translation of a v2.1 script tends to produce something awkward that you will rewrite anyway.
The pragmatic order is: get the product upload working on the new API first, ignore everything else it offers, ship it, confirm items are updating in Merchant Center, and only then look at whether the reporting endpoints replace something else you were doing by hand.
If you use a third-party feed tool and it has not shipped Merchant API support by now, that is information about the vendor. The deadline was public and dated. Missing it by a day is forgivable, missing it by a month tells you what their maintenance posture looks like, and you should have a replacement in mind.
The honest counter-take
I have framed this as mostly a non-event for small sellers, and I want to flag the way that could be wrong.
Scheduled fetches and Sheets feeds are safe from this specific deprecation, but they are not obviously safe forever. Google has been consolidating Merchant Center tooling for a while, and the direction of travel favours the API surface. Someone reading this and concluding "great, my Sheet is fine, never think about it again" may be right for a year and wrong after that.
The other soft spot: I am relying on Google's stated position that manual uploads, scheduled fetches, and Sheets continue to work. That is what the migration documentation and the feed-tooling vendors say. If your feed goes strange this week and you are on one of those paths, do not assume I am right, check Merchant Center's diagnostics before rewriting anything.
The check above still holds either way. Ten minutes to learn whether a dated cutoff touched your business is cheap regardless of the answer.
Author
Lukas
@lukcombinator