The Content API for Shopping is gone, and the grace period is already over. Google's long-standing API for managing Merchant Center product data reached sunset on August 18, 2026, and from September 1, 2026, requests made without an active extension began failing intermittently with HTTP 410 Gone. Full decommissioning is planned for early 2027, though Google notes the timing is subject to revision. The replacement is the Merchant API, and any integration still pointed at the old endpoint is living on borrowed time.
Google set out the deprecation timetable in advance, and the milestones have arrived on schedule. The Content API for Shopping reached sunset on August 18, 2026, which marked the end of the line for new development on the old interface. Then, from September 1, 2026, requests sent without an active extension began failing intermittently, returning HTTP 410 Gone — the status code that means the resource is permanently gone. The failures are intermittent rather than total, which is exactly what makes them dangerous: a feed can look healthy on one sync and fail on the next.
The final step is full decommissioning, planned for early 2027, with Google noting that the timing is subject to revision. That caveat should not be read as a reprieve. A date that can move is still a date, and the direction of travel is one way — the old API is not coming back, and every month between now and decommissioning narrows the window for a careful migration. Teams that treat early 2027 as a hard deadline will be in far better shape than teams that treat it as a rough guess.
The most important warning from Google is aimed at the teams tempted to patch around the failures. Retrying a failed legacy request may temporarily succeed, because the intermittent nature of the errors means some calls still get through, but Google is explicit that this will not provide a lasting solution. Every successful retry is luck, not stability, and it teaches the wrong lesson — that the integration is fine — right up until the day it stops working altogether. Monitoring dashboards can even hide the problem, since a feed that succeeds nine times out of ten still looks green.
That is why the migration matters now rather than later. The Merchant API is the replacement, and moving to it is the only fix Google offers. A feed integration is infrastructure, and infrastructure that fails intermittently is worse than infrastructure that fails loudly, because it erodes trust in the data without ever producing a clean error to act on. The teams that migrate on their own timetable get to test, fix and verify; the teams that wait get to migrate under pressure when the old endpoint finally goes dark.
The first job is an inventory. Find every system, script and third-party tool that talks to Merchant Center and check which API it uses — the Content API for Shopping is the one that has to go. Anything still on the legacy endpoint needs a migration plan to the Merchant API, with time set aside for testing against real product data before the old calls are switched off. Do not forget the forgotten integrations: the cron job someone set up years ago, the reporting script, the agency tool that syncs prices in the background.
For SEOs and link builders, a broken product feed is a visibility problem, not just an engineering one. Products that stop syncing can drop out of shopping surfaces, and a catalogue that goes stale undermines the pages that earn links and the listings that earn clicks. Feed health is part of search health, and the sunset is a reminder that the plumbing underneath a store's visibility needs maintenance too. Check the migration now, while the old API still answers some of the time, and the switch becomes a routine upgrade instead of an emergency.
Sources: Google Content API deprecation timetable; KAP SEO Services, November 3, 2026.
Related reading on this site: Facebook Answers' 6 Million AI Pages Are Google's Scaled-Content Test, November Click Spikes in Search Console Are Bot Traffic, Not a Ranking Win, What Gets Cited by ChatGPT: Ahrefs' 1.4 Million-Prompt Study, AI Share of Voice Is Not Organic Rankings — and the Overlap Is Small, Google Can Temporarily Protect Important URLs From Falling Out of the Index and 3 in 4 Homepages Lost Organic Clicks, Analysis of 110 Sites Finds.
Linkbaits helps you create content that earns citations and backlinks. Start with the free tools and build your first linkable asset this week.
Start free trial