What is shutting down
Google built the Content API for Shopping over a decade ago as the programmatic way to push product data into Merchant Center. It worked reliably for years. On August 18, 2026, it stops working entirely. Any call to that endpoint returns HTTP 410 Gone, and every product listing that depends on it disappears from Google Shopping.
The replacement is the Merchant API. Google announced the migration timeline well in advance. The August 18 date has not moved.
Who this actually affects
The shutdown only hits programmatic integrations — code or tools that call the Content API directly to push product data into Merchant Center. If you upload products via a scheduled file (CSV, XML, or Google Sheets), you are not affected. Nothing changes for that setup.
You are likely affected if you use:
- The Shopify Google & YouTube app (older versions used Content API)
- The WooCommerce Google Listings & Ads plugin
- A third-party feed management tool like DataFeedWatch, Feedonomics, Channable, or similar
- A custom-built integration your development team wrote in-house
The good news for Shopify and WooCommerce merchants: the official apps have already migrated to the Merchant API. Update your app to the latest version and you are covered. The real exposure is third-party tools and custom code.
The silent mispricing trap
This is the part most migration guides do not mention. The Merchant API changes how prices are formatted.
The Content API accepted prices in decimal format: {"value": "15.99", "currency": "USD"}. The Merchant API uses amountMicros — a 64-bit integer representing the price in millionths of the base currency unit. The correct value for $15.99 is 15990000.
If an integration passes 15.99 directly into amountMicros, Google reads it as roughly $0.000016. If someone passes 1599 instead of 15990000, the price becomes $0.001599. In either case, the product appears active in Merchant Center immediately. There is no instant error.
What follows is slower and harder to trace. Google's systems detect the mismatch between your website price and what was submitted, then disapprove the product — sometimes days after the upload. The error surfaces as a price mismatch violation, not a malformed price field. Without knowing to look for the amountMicros conversion specifically, it is easy to spend hours debugging in the wrong place.
Check this conversion carefully if your vendor says the migration is finished or if you are running a custom integration.
What to do before August 18
You have 16 days. Here is where to put your attention.
Go to Merchant Center and check your primary data source. If it lists "Content API" as the source type, that feed is at risk.
Contact your feed tool vendor and ask directly: has the integration migrated to Merchant API, and when did that migration complete? A migration that started but stalled is as dangerous as one that never happened. Get written confirmation.
If you have a custom integration, your developer needs to audit against the Merchant API documentation now. The amountMicros format change is the most common source of silent errors in migrations. Flag it explicitly in the review.
After any migration, use the Merchant Center diagnostics tab to verify that product prices match your website. Do not wait until August 18 to find a price mismatch that has been compounding for days.
If you are not sure whether your setup is affected, the free Gromerce audit tool can give you a clear read on your Shopping feed health in about three minutes.
The window is narrow
Sixteen days is enough time if you act in the next 48 hours. Feed tool vendors are handling a spike in migration requests right now. Saying "we'll get to it next week" puts you in line behind every other merchant who said the same thing.
Your Shopping listings are not the thing you want to discover are gone on August 19.
Sources: Google Merchant API documentation, Google Developer Blog, August 2026.
