Google Shut Down the Content API: Migrate to Merchant API or Your Feed Starts Erroring in September
Progressive Errors Are Why You Have Not Noticed Yet
Content API for Shopping was sunset on August 18, 2026. Starting September 1, 2026, requests experience progressive errors.
Progressive is the word doing the damage. A share of requests starts failing, and that share climbs from there, so nothing ever trips a pager. Right now your ERP or feed tool is probably still syncing most of your catalog, with a handful of timeouts that whoever is on call reads as transient, retries, and forgets.
By the time the failure rate is loud enough to notice, the items that missed their updates have been sitting stale for a while. Merchant Center items expire 30 days after their last refresh, which means the SKUs that quietly started failing on September 1 begin dropping out of placements in the first half of October.
One buffer may apply to you. Google crawls your site on its own schedule and refreshes items automatically when the product data validates, for example against schema.org markup on the page. Stores with clean structured data decay more slowly than that timeline suggests. The catch is that this only covers fields readable from the page, so price and availability, the two that move most, still depend on the feed. Treat it as slack, not as a reason to skip the migration.
That gap between September 1 and mid-October is what costs you. On the day the errors start you have no signal at all, and on the day you lose revenue you have already burned a month of your response window.
So before anyone schedules a migration, confirm whether you are in scope at all. Some stores never touch the API and would be rebuilding something that was never broken. Others run a feed platform that finished migrating months ago without telling anyone. Find out which you are before anyone writes code.
Which Stacks Are Affected, and a 30-Minute Check
Anyone pushing product data programmatically is in scope. Custom scripts, feed platforms like Feedonomics or Channable, ERP modules with a Google channel, and third-party Google sync apps installed on a Shopify store all call an API on your behalf.
Start by asking your vendor a single direct question: are you calling Content API for Shopping or Merchant API right now. That is the fastest path, and many vendors finished migrating earlier this year, in which case you have nothing to build.
Next, open API usage in Google Cloud Console and look at which service your project has enabled, the recent call volume, and the error rate. Content API for Shopping still carrying traffic, or an error rate that started bending upward in early September, answers the question on its own.
Third, grep the code. In a custom integration, search your repo for the host shoppingcontent.googleapis.com and the path segment content/v2.1. Every Content API REST URL begins https://shoppingcontent.googleapis.com/content/v2.1/, so a hit on either string puts you on the old API. If you call through an official client library the host may never appear as a literal, in which case check your dependency manifest for the shopping content library instead.
Worth ruling out first: manual file uploads, scheduled fetches, and Google Sheets feeds generally continue to work after the API shutdown, since none of them go through the API. A store running purely on a scheduled fetch has nothing to migrate, so confirm that before spending a sprint on it.
What Goes Dark When the Feed Stops
Items expiring in Merchant Center take more than Shopping ads with them, because several surfaces read the same product data.
| Surface | Result once items expire |
|---|---|
| Free listings | Products disappear from the Shopping tab, organic visibility goes to zero |
| Performance Max | Listing groups have no eligible products, that budget cannot spend |
| Standard Shopping | Affected SKUs stop serving |
| Products in AI Mode | Pulls from Merchant Center data, expired items are no longer eligible to be used |
| Local inventory | Store availability stops updating, online and in-store fall out of sync |
Performance Max is the line that gets underestimated. It does not throw a visible “no products” error. It reallocates toward whatever assets remain or simply underspends, and the report you look at shows softening conversions. That reads as competitive pressure or seasonality long before anyone suspects the feed underneath.
Products in AI Mode deserve their own mention. That surface pulls from Merchant Center, so an expired item is not ranked lower, it is out of the candidate set entirely. A growing share of product discovery happens in interfaces like that, which makes an expired catalog more expensive than it was a year ago.
The fastest early-warning signal is your active product count in Merchant Center. Compare today’s number against a month ago, and a drop means SKUs are aging out. Checking that number daily buys you roughly a month of lead time over waiting for an ads report to look wrong.
What Merchant API Takes Over
Merchant API is the replacement, and the scope matches what you were already doing: uploading products, managing inventory, managing Merchant Center accounts, and linking inventory to Google Ads. The work concentrates in repointing existing calls at the new endpoints, while the business logic around them mostly survives.
Sequence the migration so you always have a way back. Get a single product uploading and updating against the new endpoints in a test account first, which proves out authentication and field mapping. Then run both integrations in parallel against your full catalog for a stretch and compare item counts and statuses in Merchant Center. Only when the numbers agree do you turn the old calls off.
Field mapping takes longer than the endpoint swap. Product IDs, availability, price, and shipping do not necessarily carry the same structure in the new interface, and a mapping error does not surface as an API failure. The item lands in Merchant Center and gets flagged as non-compliant, sitting there with a warning nobody reads. After you cut over, walk the Merchant Center diagnostics page warning by warning. A 200 response from the API tells you far less than a clean diagnostics report.
If a third-party tool owns the integration, your job is chasing and verifying. Get a migration date from the vendor in writing, and after they ship it, confirm your item counts and statuses match what you had before. Verify it in your own Merchant Center rather than closing the ticket on the vendor’s say-so.
The Extension Form as an Emergency Lever
Google provides an extension request form. Extension requests submitted through the form are approved upon submission, provided the submitted Google Cloud project IDs are correct.
That condition is worth two extra minutes of care. A wrong project ID means the request accomplishes nothing, and you will most likely find out the next time errors show up rather than at submission time. Copy the value out of Cloud Console and check that you took the project ID and not the project name, since the two are routinely different. If several projects call the API, every one of them belongs on the form, because any project you omit keeps erroring.
Treat it as a buffer for teams whose roadmap genuinely cannot absorb the work this quarter. The first thing to do after an approved extension is put the migration on a calendar. The parallel-run and verification sequence above still applies, you simply get to run it without a fire behind you.
If you are already losing impressions, the order is: submit the extension form to restore the old calls and get product data flowing again, then audit Merchant Center for items that already expired and push them fresh, and last, book the engineering time for the migration itself.
Related Articles
Cloudflare Changed Its Defaults on September 15: The AI Agents Shopping for Your Customers May Be Locked Out
In July, Cloudflare split its single AI-bot switch into three separately managed categories: Search, Agent, and Training. From September 15, domains newly onboarding get a default that blocks Training and Agent bots on pages that display ads while Search stays allowed. Here is what each category covers, who the new default actually touches, and the dashboard audit that takes half an hour.
Amazon Synthetic Performer Image Labeling: XMP Metadata Compliance Guide for Sellers
Starting July 22 2026, Amazon requires all product images and A+ Content featuring photorealistic AI-generated people to carry contains-synthetic-performer XMP metadata. This guide covers what needs tagging, how to batch-add metadata with ExifTool and Adobe Bridge, and what happens if you skip it.
AI Product Data Enrichment Tools Compared 2026: Salsify, Feedonomics, and Productsup
The three vendors sound like they do the same thing. They do not. Salsify governs product content, Feedonomics runs feeds for you as a managed service, and Productsup gives you an enterprise catalog pipeline you configure yourself. Includes an honest section on when you need none of them.