Google’s Old Shopping API Is Failing Intermittently, and the Error Goes to a Log Nobody Reads
Google sunset the Content API for Shopping on 18 August 2026. Since 1 September, requests from integrations without an active extension intermittently fail with HTTP 410 Gone. Full decommissioning follows in early 2027. The error is loud. It arrives somewhere your business never looks.
Google published both the mechanism and the reason. The progressive degradation exists to ensure developers observe deprecation notices in their application logs, and the 410 payload names the Google Cloud project that sent the request. This is not a silent failure. It is a well-signposted one, signposted to an audience of one developer.
The sunset applies to programmatic submission only. Product data sent by XML feed, scheduled fetch or manual upload runs on a separate path and is unaffected.
Our math: intermittent is harder than broken. A hard outage produces a moment. Somebody notices, somebody investigates, the cause is found that week. Intermittent failure produces no moment. Some requests succeed, so some products update and others do not, and the catalogue drifts out of alignment with the shop one item at a time. The campaign keeps spending at full rate against whatever data did land, and nothing in Ads or Merchant Center announces that a subset of writes failed, because from their side nothing did.
Three questions for whoever owns the integration, in order. Are we on the Content API or the Merchant API. If Content API, do we hold an active extension. Are there HTTP 410 responses in the application logs since 1 September. The last one is a yes or no and takes minutes.
Then check the shop rather than the platform. Compare live prices and stock on a sample of products against what Merchant Center currently holds. Drift between the two is the symptom the logs explain.
Our read: the diagnostic instinct is to interrogate the campaign, because that is where the budget and the dashboards are. This fault sits upstream of all of it, in the supply line feeding the ads rather than the ads themselves. That is a Stage 1 problem presenting as a Stage 5 problem, and the distinction decides the repair order. We set it out in Stage 1 and Stage 5.
How would I know my Content API integration was failing? Ask for HTTP 410 responses in the application logs since 1 September, then compare live prices and stock against Merchant Center. Intermittent failure produces drift rather than an outage.
Sources: Google for Developers, Content API for Shopping deprecation and sunset guide, which sets the 18 August 2026 sunset, the 1 September intermittent HTTP 410 responses, the early 2027 decommissioning, and the extension mechanism. Last verified 23 September 2026.
P&C is a marketing accountability firm. We trace paid spend through to deposited revenue, stage by stage. Request a Foundations Audit.