Home / Merchant Center issues / Content API for Shopping sunset (August 18, 2026)
The Content API for Shopping was sunset on August 18, 2026: what do store owners need to do?
The Content API for Shopping (v2.1) was sunset on August 18, 2026, and integrations must move to the Merchant API (v1). Since September 1, 2026, requests from clients without an active extension fail intermittently with HTTP 410 Gone. The fix is in Merchant Center or your feed, not on your storefront.
What it usually looks like on a store
Nothing on your storefront changes. What breaks is product syncing: a custom script, an old plugin or an in-house integration that pushed products through the Content API starts getting HTTP 410 errors, so prices and stock in Merchant Center quietly stop updating. Stores on the Shopify Google & YouTube app or a maintained feed app are covered by the provider.
What Google says
The Content API for Shopping (v2.1) was sunset on August 18, 2026, and integrations must move to the Merchant API (v1). Since September 1, 2026, requests from clients without an active extension fail intermittently with HTTP 410 Gone. Full shutdown, with every request failing, is planned for early 2027 and may move. Extensions can be requested on a form. Merchants who sync products through a third-party partner such as the Google & YouTube app on Shopify don't need to do anything: the provider handles the migration. Only custom or self-built API integrations need work.
The Google Content API for Shopping officially reached its sunset on August 18, 2026.Google, Deprecation and sunset
All developers must migrate existing integrations to the Merchant API as soon as feasible.Google, Deprecation and sunset
Requests without an active extension begin intermittently failing with HTTP 410 Gone.Google, Deprecation and sunset
Full shutdown. All endpoints are turned down and all requests fail.Google, Deprecation and sunset
Also seen as: "HTTP 410 Gone", "Content API for Shopping was sunset on August 18, 2026 for GCP project", "Migrate from Content API for Shopping to Merchant API".
How to fix it
Based on Google's help pages, in plain language:
- Find out how product data reaches Merchant Center: file/Sheets upload, a third-party app or partner, or your own Content API integration.
- If a third-party partner (e.g. the Google & YouTube app on Shopify) syncs your data, you don't need to do anything; confirm the app is current.
- If you or a developer built a Content API integration, migrate it to the Merchant API v1 (new request URLs, register the Google Cloud project with developerRegistration:registerGcp).
- Check logs for HTTP 410 Gone responses from Content API endpoints.
- If you need more time, submit the Content API for Shopping extension request form.
Requesting a review
Not a review issue. Failing 410 requests mean product updates from that integration aren't reaching Merchant Center.
Questions
Can a website scan fix "Content API for Shopping sunset (August 18, 2026)"?
Not directly. The cause sits in your product data, your Merchant Center settings or what you sell, and a website scan can't see any of those from outside. Follow the steps from Google's help pages above, then check the diagnostics page in Merchant Center.
Sources
- developers.google.com/merchant/api/guides/compatibility/overview
- developers.google.com/shopping-content/guides/sunset
Quotes checked against Google's pages. Listvane is an independent tool made by Great Work LLC. It isn't affiliated with, endorsed by or sponsored by Google. Google and Google Merchant Center are trademarks of Google LLC.