Content API for Shopping Is Dead: What Breaks for Shopify Stores

August 19, 2026. Google shut down the Content API for Shopping yesterday. The date was set a year in advance and Google's own Merchant Center documentation states it plainly: access to the Content API was provided until August 18, 2026, after which the Content API would be shut down. Merchant API version 1 is the replacement and is generally available. The part that matters for e-commerce operators is not the deadline, which has passed, but the shape of the failure it causes, because a store whose feed integration died yesterday will look completely healthy today.

What changed and what did not

1. The Content API for Shopping stopped accepting product data on August 18, 2026. Integrations still calling it no longer deliver updates to Merchant Center.
2. Merchant API version 1 is the successor interface for programmatic product and account management, per Google's Introducing Merchant API documentation.
3. Only API based integrations are affected. Migration guidance across the feed tooling industry is consistent that manual file uploads, scheduled fetches and Google Sheets data sources continue to work unchanged.
4. Google opened an extended access request form for teams that could not finish in time. Reporting on that form, including by Search Engine Roundtable, describes selectable extension deadlines of October 15, 2026 and December 31, 2026.
5. Merchants on the official Shopify Google and YouTube channel or the WooCommerce Google Listings and Ads plugin have the migration handled by the platform, provided the app is on a recent version.

The failure is silent for up to thirty days

This is the finding that should change what you do this week. Google's Merchant Center rules state that products expire thirty days after the last refresh. A broken feed does not remove listings, it stops refreshing them, and the listings keep serving until the expiry clock runs out. A store whose integration stopped on August 18 will show live Shopping and Performance Max inventory throughout the rest of August and most of September, then begin dropping out somewhere around September 17.

That means every check performed today returns a false all clear. Anyone who logs into Merchant Center this morning, sees active products and concludes the migration was handled has confirmed nothing. The correct instrument is the last updated timestamp on the data source, not the product status. If that timestamp is on or before August 18, the integration is dead and you are inside a thirty day fuse.

Product schema is now a decay buffer

There is a second order effect worth knowing. Google states that it also refreshes products automatically by checking the merchant website, for example by crawling schema.org structured data on product landing pages, where that data can be validated. A store with clean, complete product markup therefore degrades slowly and partially when its feed dies, because Google can re-validate some items from the page itself. A store without it falls off in one step at day thirty.

Two stores with the identical broken integration will produce very different September revenue charts based on structured data work nobody connected to feeds. If you run e-commerce storefronts for clients, that is an argument for product schema that has nothing to do with rich results and everything to do with resilience.

What it means for operators

Do three things. First, open every Merchant Center account you touch and read the last updated date on each data source rather than the product count. Anything stale since August 18 is a live incident with roughly four weeks of runway. Second, identify which integration type each store actually uses, because the exposure is uneven in a way that is counterintuitive: stores on Google Sheets or a scheduled URL fetch were never in scope, and the exposed ones are mid market stores on custom or older third party API connections, which is to say the more sophisticated the setup, the more likely it broke. Third, if a store is on the official Shopify channel, confirm the app version rather than assuming, because platform handled migration is conditional on being on a recent build.

One caution on the Shopify channel specifically. Practitioners reported earlier this year that migrating the Google and YouTube app by uninstalling and reinstalling rewrote product IDs, changing identifiers of the form Shopify_US_12345_67890 to Shopify_ZZ_12345_67890, which would detach historical performance data keyed to those IDs. Google's Ads Liaison acknowledged in July that the team was looking into it. We have not been able to verify the current behaviour on Google or Shopify primary documentation, so treat it as a reported risk rather than a confirmed one, and take a performance snapshot before touching the app on any store where Shopping history matters. If you need this audited across a portfolio, that is the kind of work our Shopify app and integration team handles.