Google Merchant API Migration: Is Your Feed at Risk?

A quiet error message rarely makes headlines, yet for a growing number of online retailers it has meant their best-selling products quietly disappearing from Google Shopping. Since early September, stores still pulling product data through Google’s old Content API for Shopping have been running into failures that get worse the longer they go unaddressed. The cause is not a bug on the retailer’s side. It is a scheduled retirement that many merchants only noticed once their listings started thinning out.

Google has spent the past two years steering merchants toward its newer Merchant API, and the older Content API for Shopping formally shut down on 18 August. A Google Merchant API migration is not a marketing footnote for a Singapore retailer running a custom-built storefront or an older feed integration. It decides whether products keep surfacing in the free and paid Shopping listings that many e-commerce sites now rely on for a meaningful share of their organic visibility.

What Actually Changed

The Merchant API is Google’s newer platform for managing product and store data, built around smaller, specialised sub-APIs covering areas such as order tracking, product issue resolution, and review management, none of which existed in the older system. As Search Engine Land noted when covering Google’s Merchant API announcement, the move gives Google a single platform for managing product data across both paid and organic Shopping surfaces instead of two separate systems.

The Content API for Shopping stopped accepting new integrations on 18 August, and unmigrated accounts began seeing a rising share of failed requests from 1 September. Google’s official migration guide confirms that short extensions are available to businesses that formally apply for extended access, though this is a bridge, not a long-term option, since the older API is being switched off for good.

Why This Sits Squarely Inside SEO, Not Just Development

It is easy to file this under “engineering problem” and move on, but the feed that flows through the Merchant API is also what populates Google’s free product listings, the organic Shopping results that sit alongside paid ads. A broken or stale feed does not just interrupt an advertising campaign. It quietly removes a product from search entirely, in exactly the same way a blocked page or a broken canonical tag would.

The stakes are rising because product data increasingly feeds more than the classic Shopping tab. Google’s AI-powered shopping features and shopping-adjacent AI Overviews draw directly on structured product feeds rather than crawling a page the way a person would read it, so an outdated GTIN, price, or availability field can cost visibility across several surfaces at once, not just one.

For a small Singapore retailer, this can feel disproportionate. A one-line change buried in a developer changelog ends up deciding whether a product page earns a click at all, long before anyone gets to judge the copy, the images, or the price.

Who Actually Needs to Check This

Not every business is exposed in the same way. Merchants using an official sales channel app, such as the Google & YouTube integrations built into Shopify or WooCommerce, are generally migrated automatically by the platform and do not need to act. The risk sits with anyone maintaining a more direct or custom connection to Merchant Center, including:

• Retailers with an in-house developer maintaining a direct feed integration built before the Merchant API existed
• Businesses running older middleware or a custom product information system connector that has not been updated since 2024
• Agencies managing several Merchant Center accounts on behalf of clients through a shared script or tool
• Enterprise catalogues with thousands of SKUs that update programmatically instead of through manual uploads
• Anyone who received (and set aside) a migration notice inside Merchant Center over the past year

What Happens If the Migration Gets Missed

The practical effect is rarely a single dramatic outage. It tends to look like a slow leak: a handful of failed feed updates one week, a batch of products marked as having errors the next, then a steady decline in how many items are actually eligible to show. By the time the drop is visible in a traffic report, the underlying cause is usually weeks old.

The timing makes this a priority to sort out well ahead of the next big shopping event. Singapore’s retail calendar moves quickly from one seasonal push to the next, and a feed quietly losing products in the background is the last thing any online store wants heading into a peak trading period, when every listing needs to be working at full strength.

Turning a Deadline Into a Product Data Audit

A migration already underway is a good opportunity to look past the API itself and at the quality of the data travelling through it. Many of the same fixes that resolve migration errors, such as consistent identifiers and complete attribute coverage, overlap closely with getting structured data for e-commerce products in proper order, so a business tackling one can reasonably tackle both in the same sprint. A practical checklist for that review might include:

• Confirming with your platform, developer, or agency that the migration to the Merchant API has actually been completed, not just scheduled
• Checking Merchant Center’s diagnostics page for any outstanding warnings tied to feed fetch or product data errors
• Verifying that GTINs, pricing, and stock availability are updating on the expected schedule instead of sitting on cached values
• Re-testing scheduled feed fetches and any custom scripts in a staging environment before relying on them in production
• Reviewing which endpoints or fields your integration still calls that belong to the deprecated API
• Treating any extended access grant as a short-term buffer to finish the work, not as a reason to delay it further

Whether the feed is managed in-house or through an agency, this deadline is a useful prompt to check that product data is not just technically passing through Google’s systems but genuinely visible to shoppers browsing, comparing, and increasingly asking AI tools for recommendations. If your team would like a second pair of eyes on a Merchant Center setup or a broader product feed health check, feel free to get in touch with IT.com.sg.