Since 1 September 2026, Google has been progressively rejecting calls to the Content API for Shopping — the connection many online stores have quietly relied on for years to keep Google Shopping and Performance Max campaigns supplied with live product data. The access window Google promised closed on 18 August 2026, and the errors that follow don’t announce themselves with a dramatic outage. They show up as stock levels that stop updating, prices that quietly go stale, and products that eventually get flagged or disapproved — the kind of problem that looks like a bidding or creative issue long before anyone traces it back to a feed that stopped syncing weeks earlier.

What Google actually changed

Google has been retiring the Content API for Shopping in favour of a rebuilt Merchant API, now generally available as the primary way for developers and third-party tools to push product data into Merchant Center. According to Google’s own migration documentation, the company committed to keeping the Content API accessible “until August 18, 2026” — after that, requests to the old API begin encountering what Google describes as progressive errors, starting from 1 September 2026 and escalating from there rather than failing all at once.

The Merchant API isn’t a rename. Requests are structured differently, resources are addressed by name rather than numeric ID, and the new API supports real-time push notifications for product status instead of the old pattern of repeatedly polling for changes. That’s a genuine improvement for anyone building or maintaining an integration, but it also means the migration is a real development task, not a settings toggle — which is exactly why some integrations haven’t been moved over yet. Businesses that genuinely need more time can apply through Google for extended Content API access, but that’s a request to make, not something that happens automatically.

Who this actually affects

This only touches product data that reaches Merchant Center through a direct API connection. If your store’s feed is a manually uploaded file, a scheduled fetch from a hosted spreadsheet, or a Google Sheets-based data source, that upload method itself isn’t calling the Content API, so it isn’t directly affected by this particular deprecation.

The businesses genuinely exposed are the ones with an API-based integration somewhere in the chain: a custom connector a developer built between an inventory system or ERP and Merchant Center, an in-house script that syncs stock and pricing on a schedule, an agency-built automation running through a tool such as n8n, Make or Zapier, or a smaller or older feed-management plugin that hasn’t shipped a Merchant API update. Large ecommerce platforms with dedicated engineering teams behind their native Google integrations have had over a year of advance notice to migrate, but that’s a reason to verify, not assume — a store running an older plugin version, a heavily customised integration, or a workaround built by a previous developer can easily fall outside that coverage without anyone noticing until the data starts drifting.

How to check whether your own feed is affected

A handful of checks answer this fairly conclusively, and none of them require developer access on their own:

  • In Merchant Center, check Settings and your data sources for the primary feed. API-based sources are generally identified separately from scheduled fetches or manual uploads — if you’re not sure which one you’re looking at, that’s worth clarifying before assuming you’re safe.
  • Check the Diagnostics or Issues section in Merchant Center for messages referencing failed requests, item sync problems, or a prompt to move to the Merchant API — Google surfaces these directly rather than leaving them to be discovered through campaign performance.
  • Spot-check a handful of live products against your actual store: does the price, stock status and image in Merchant Center match what’s currently on the site? A mismatch that’s grown noticeably since late August is a fairly specific signal.
  • If a third-party app or plugin manages your feed, check the vendor’s own changelog or status page for confirmation that they migrated to the Merchant API — and note the date. A confirmation from before mid-2026 is more reassuring than one that predates the API’s general availability.
  • If a developer or agency manages the integration, ask the direct technical question: does the sync call the Content API for Shopping, or the Merchant API? It’s a factual question with a factual answer, and it’s worth having in writing.

What actually breaks when a feed stops syncing

Products that are already approved in Merchant Center don’t disappear the moment an API call fails — that’s what makes this easy to miss. What happens instead is that the data behind those listings stops refreshing. A price change on the website doesn’t reach the ad. A product going out of stock doesn’t get reflected, so Performance Max or Shopping campaigns can keep spending budget promoting something a customer can’t actually buy. A new product launch doesn’t reach Google at all until someone notices it’s missing from campaigns. And because Google does check listed data against reality over time, sufficiently stale information eventually risks disapprovals or suspensions on the affected products — turning a quiet sync failure into a visible drop in Shopping traffic that then gets investigated as a bidding or targeting problem, when the actual fault sits upstream of the ad account entirely.

What to do about it now

If an in-house or agency-built integration is confirmed to still be calling the Content API, migrating it to the Merchant API is the actual fix, and Google’s developer documentation for the new API is the reference point for that work. Where migration genuinely can’t happen immediately, requesting extended Content API access through Google buys time without leaving the feed to fail quietly in the meantime. If a third-party app manages the feed, the practical step is confirming directly with the vendor that their integration has moved over, rather than assuming a well-known platform name means it’s automatically covered.

For businesses working with an agency on Google Shopping or Performance Max campaigns, this is a reasonable and specific question to raise this week: has the product feed integration been confirmed on the Merchant API, and when was that last checked? It’s a technical question sitting slightly outside where most advertising conversations usually focus, which is exactly why it’s worth asking directly rather than assuming someone else already has.

Why this sits between the ad account and the tech stack

Many campaign reviews stop at bidding strategy, budget allocation and creative — all genuinely useful, but none of it fixes a Shopping campaign whose real constraint is the data feeding it. This is the kind of failure that many traditional agency setups can miss entirely, because the team managing the ad account and the system managing the product feed integration often sit in completely different places, with nobody specifically responsible for checking that the connection between them is still working. MRVS treats the technical integrations behind a campaign as part of the same review as the campaign itself, precisely because problems like this one live in the gap between the two and rarely get caught by looking at either side alone. The same logic applies to the broader shift Malaysian retailers are already navigating across marketplaces, social commerce and owned ecommerce channels — the acquisition strategy only performs as well as the product data underneath it.

Frequently asked questions

Do I need to do anything if my products are uploaded via a CSV file or Google Sheets?

Not directly — a scheduled file fetch or a Google Sheets-based feed isn’t itself calling the Content API for Shopping. It’s still worth confirming that whatever generates that file for you isn’t relying on the deprecated API somewhere further upstream, particularly if a plugin or third-party tool produces the file automatically.

How would I know if my Shopping ads are already being affected?

Look for a growing gap between what your website shows and what Merchant Center shows for the same products, unexplained disapprovals on previously approved listings, or a Diagnostics message in Merchant Center referencing failed item updates or a required move to the Merchant API. A sudden, unexplained dip in Shopping or Performance Max impressions after early September is also worth investigating from this angle rather than assuming it’s a bidding issue first.

Is there still time to get an extension from Google?

Google has said businesses that need more time can apply for extended Content API access, but this needs to be requested — it isn’t granted automatically just because a migration hasn’t happened yet. The realistic approach is to treat the extension as a way to buy a defined amount of time to complete the Merchant API migration properly, not as a long-term alternative to doing it.