Content API Shutdown: What to Check in Your Feed
Ishant
Published : September 17, 2026 at 11:30 am
Updated : September 18, 2026 at 4:02 am
Ishant
Ishant Sharma is the Founder and CEO of Hustle Marketers, a Google Partner digital marketing agency. With 12+ years of experience in Google Ads, Meta Ads, SEO, and e-commerce PPC, he has helped 2,500+ brands generate $780M+ in trackable sales. Upwork Top Rated Plus with 100% Job Success Score. Ishant Sharma is the digital marketing specialist, not the Indian cricketer of the same name.
The Content API for Shopping shut down on 18 August 2026. It was replaced by the Merchant API, which Google made generally available in August 2025.
Most of the coverage was written for developers, by feed tool vendors, and it mostly said “migrate now”. That was not much use if you are a store owner or a marketing manager who does not write code and has no idea whether anything in your setup even touched the Content API.
So here is the version nobody published: how to tell in about twenty minutes whether you were affected, what to check in Google Ads that almost everyone missed, and what to do if your products quietly stopped serving.
Short answer: The Content API for Shopping closed on 18 August 2026 and was replaced by the Merchant API. If your products reach Merchant Center by scheduled fetch, manual upload, Google Sheets or the website crawl, nothing changed for you. If you use a platform app, a feed tool or a custom integration, check that your data source still fetched in the last 24 hours and that your feed labels still match your Google Ads campaigns.
Migrations like this are where weak feed foundations get exposed. When we rebuilt Silicon Lightworks’ Merchant Center setup the fix was structural rather than cosmetic, and that is what got them live on Google Shopping. If you need to remap attributes before you migrate, our feed attribute mapper handles that step.
First, work out whether this affects you at all
The Content API was one specific thing: the programmatic interface for pushing product data into Merchant Center. Google describes the Merchant API as replacing “the Content API for Shopping as the primary interface for programmatic access”.
Merchant Center supports several other ways to get products in, and those are separate mechanisms. Find how your products arrive and read across.
| How your products get into Merchant Center | Affected by the shutdown? | What you need to do |
|---|---|---|
| Scheduled fetch of a file at a URL | No | Nothing. This is a file fetch, not the API |
| Manual file upload | No | Nothing |
| Google Sheets data source | No | Nothing |
| Automatic from your online store (website crawl) | No | Nothing |
| Manual entry in the product editor | No | Nothing |
| Ecommerce platform app or channel (Shopify, WooCommerce, BigCommerce, Magento) | Maybe | Depends on whether your app version migrated. Check it |
| A third-party feed tool (DataFeedWatch, Channable, Feedonomics, GoDataFeed, Productsup and similar) | Maybe | Most migrated for you. Confirm rather than assume |
| A custom integration your developer built | Yes | It had to be rewritten against the Merchant API |
If you are in the top five rows, you can stop reading and go back to work. If you are in the bottom three, keep going.
The part that actually breaks revenue: feed labels
Here is the failure mode that catches people out, and it is not the one you would expect.
The feed label is the value that connects a data source in Merchant Center to the listing groups in your Google Ads Shopping and Performance Max campaigns. If the label changes, your campaigns are pointing at a label that no longer exists, and they stop serving products. Not with an error. Not with a warning email. They simply return nothing.
Search Engine Land reported ahead of the cutoff that feed labels do not automatically transfer during migration, and that if they are not manually updated in Google Ads, Shopping and Performance Max campaigns can stop serving without warning. Their framing was that this is “not a cosmetic backend change”.
This is why the check below starts in Merchant Center and then goes straight to Google Ads. Checking only one side tells you nothing.
The twenty minute check
Step 1. Find out what your data sources are actually called
In Merchant Center, open Products then Data sources. For every primary data source, write down three things:
- The data source name
- The feed label
- The country and language it targets
Then check the last update timestamp on each one. If a source has not updated since mid August 2026, that is your answer and you can go straight to Step 4.
Step 2. Match those labels against Google Ads
In Google Ads, open each Shopping and Performance Max campaign and look at the campaign settings for the feed label, then at the listing groups or asset group listing groups.
The feed label in the campaign must match the feed label in Merchant Center exactly, including case. “US” and “us” are not the same value. If a campaign references a label that no longer appears in your data source list, that campaign is serving nothing.
Step 3. Check product coverage, not just errors
A clean diagnostics screen is not proof that anything is working. Look at the actual count of active products and compare it to what you sell.
| Where to look | What you want to see | What a problem looks like |
|---|---|---|
| Merchant Center, Products, All products | Active item count close to your real catalogue size | A step drop dated around mid August 2026 |
| Merchant Center, Data sources, last fetch | Updated within the last 24 hours | A date that stopped moving |
| Google Ads, Shopping or PMax, product level report | Impressions continuing at normal levels | Impressions falling to near zero on a specific date |
| Google Ads, campaign level | Spend tracking to budget | Budget suddenly underspending with no bid change |
Step 4. Check the app or tool doing the pushing
If something has stopped, the cause is usually the connector rather than Merchant Center itself.
- Update the app or plugin to its current version. Migration support shipped in updates, so an old version is the single most common cause.
- Disconnect and reconnect the Merchant Center link inside the app. This re-authorises against the current API.
- Read the app’s own sync log if it has one, rather than relying on Merchant Center to tell you what happened.
- Ask your feed tool’s support directly whether your account is on the Merchant API, and get it in writing.
Platform by platform
| Platform | Where to look | Known issues merchants have reported |
|---|---|---|
| Shopify (Google & YouTube channel) | Channel settings, Google Merchant Center connection | Products syncing but a stale second data source still present from an older connection, creating duplicates |
| WooCommerce (Google for WooCommerce) | Marketing, Google for WooCommerce, then Settings and the sync log | Migration reported as failed, prices syncing without VAT, product status jobs pausing on an error, catalogue resubmitting on a loop through Action Scheduler |
| WooCommerce (Product Feed PRO, CTX Feed and similar) | The plugin’s feed list and schedule settings | These generate files rather than pushing through the API, so most were unaffected. Confirm which method yours uses |
| BigCommerce, Magento, PrestaShop | The Google channel or connector extension settings | Older extension versions that were never updated |
| Third-party feed tools | The tool’s Google Merchant Center connection page | Generally handled centrally, but connections that were authorised years ago sometimes need re-authorising |
| Custom build | Your developer or agency | Needs a rewrite against the Merchant API. There is no compatibility shim |
The WooCommerce side is worth calling out. The official plugin’s support forum carried a run of migration problems through the second half of 2026, including one thread about prices syncing without 25% VAT that ran to twenty replies. If you are on WooCommerce and something looks wrong, check your prices in Merchant Center against your prices on the site before you assume the sync is fine.
Content API for Shopping versus Merchant API, in plain terms
| Content API for Shopping | Merchant API |
|---|---|
| One API covering products, accounts, inventory and reporting | Split into sub-APIs by function, so a tool can use only what it needs |
| The long-standing interface, first released over a decade ago | Generally available since August 2025 |
| Shut down 18 August 2026 | The primary interface for programmatic access now |
| Beta users lost access earlier, on 28 February 2026 | Ongoing |
For a store owner, the practical difference is small. The disruption came from migration side effects, not from the new API being harder to use.
Symptoms and what they usually mean
| What you are seeing | Most likely cause | First thing to check |
|---|---|---|
| Campaigns running but zero product impressions | Feed label mismatch between Merchant Center and Google Ads | Campaign settings, feed label field |
| Shopping ads stopped completely after adding new products | The new batch went to a source or label the campaigns do not reference | Which data source the new products landed in, and its feed label |
| Active item count dropped sharply in August | The connector stopped pushing | Data source last fetch date |
| Products present but prices or stock are stale | Partial sync, or the website crawl taking over | Compare a sample of products against the live site |
| Duplicate products appearing | A new data source was created alongside the old one | The full data source list, including any you did not create |
| Prices wrong by a fixed percentage | Tax handling lost in migration | Whether your feed is sending tax-inclusive or tax-exclusive prices |
| Everything looks fine and performance is flat | Probably genuinely fine | Nothing. Move on |
If you find duplicates, that is a data source conflict rather than an API problem, and it is worth understanding properly because it causes disapprovals and, in bad cases, suspensions. If the symptom is Performance Max specifically, our guide to diagnosing a Performance Max campaign that is not performing works through the feed, tracking, bids and assets in turn.
Stop this happening again
The Content API shutdown was announced a year in advance and still caught people out. The reason is that almost nobody monitors the feed layer. Campaign performance gets watched daily and the plumbing underneath it gets watched never.
A monthly check of five things would have caught this, and will catch the next one.
| Check | Where | What good looks like |
|---|---|---|
| Active item count vs catalogue size | Merchant Center, All products | Within a few percent of your real product count |
| Last fetch on every data source | Merchant Center, Data sources | Every source updated in the last 24 hours |
| Feed labels match campaigns | Merchant Center and Google Ads side by side | Exact match, including case |
| App and plugin versions | Shopify admin or WordPress plugins page | Current, with auto-update on where you trust it |
| Merchant Center announcements | The notifications panel in the account | Read, not dismissed. Google moved these in-platform in May 2025 when it discontinued the email archive |
That last row matters more than it looks. Google discontinued the Merchant Center email archive in May 2025 and moved notifications into the platform. If you were relying on emails to tell you about deadlines, you stopped receiving some of them over a year ago.
If you manage feeds across several client accounts, Merchant Center for Agencies became generally available worldwide on 11 May 2026 and gives you a single place to see account health rather than logging into each one.
How to report this internally
If you did find a problem, the conversation with a client or a finance team goes better with specifics. Something like this:
Google retired the Content API for Shopping on 18 August 2026 and replaced it with the Merchant API. During the migration, the feed label connecting our Merchant Center data source to our Shopping and Performance Max campaigns changed, which meant those campaigns had no products to serve from [date] onwards. We identified this on [date], corrected the feed label, and confirmed [number] products are active again. Impressions resumed on [date]. Estimated lost revenue over the affected period is [figure], based on the daily average for the four weeks prior. We have added a monthly feed health check to prevent a repeat.
Name the cause, the window, the fix and the prevention. That is a much better conversation than “Shopping was down for a bit”.
Frequently asked questions
Do I need a multi-client account to manage several Merchant Center accounts?
Only if you manage feeds for clients or separate legal entities. A single business selling in several countries does not need one, because countries are handled with feed labels inside one account. Merchant Center for Agencies became generally available worldwide on 11 May 2026 and is the right structure if you do manage multiple clients.
Why did my Performance Max campaign stop showing products?
The most common cause after the migration is a feed label mismatch. The campaign references a label that no longer exists on any Merchant Center data source, so there are no products to serve. Check the feed label in campaign settings against the label on your data source, including case.
How do I check if my product feed is still working?
Three things, in this order: the last fetch time on every data source should be within 24 hours, the active item count should be close to your real catalogue size, and the feed label on each data source should match the label in your Shopping and Performance Max campaigns exactly.
When exactly did the Content API for Shopping shut down?
18 August 2026. Beta users lost access earlier, on 28 February 2026.
I upload a CSV by hand every week. Do I need to do anything?
No. Manual upload, scheduled fetch and Google Sheets are separate upload methods and are not the Content API.
How do I know if my Shopify or WooCommerce app migrated?
Update it to the current version, then check that your data source in Merchant Center has fetched within the last 24 hours and that your active item count matches your catalogue. If both are true, it migrated.
My campaigns stopped serving in August. Can I recover the lost performance?
The spend is gone, but the learning is not permanently lost. Fix the feed label, confirm products are active, and let the campaigns re-stabilise. Expect a settling period rather than an instant return to previous levels, particularly on Performance Max.
Should I switch from an API connection to a scheduled file fetch to avoid this in future?
Usually not. API connections update faster, and refresh speed matters more now that price and availability accuracy affects both Shopping and AI shopping surfaces. The lesson is to keep connectors updated, not to downgrade the connection.
Do I need a developer for this?
Only if you have a custom integration. If you use a platform app or a feed tool, updating the app and re-checking your feed labels covers it.
Next steps
Run the four steps above today, even if performance looks normal. A feed label mismatch on one of several campaigns is easy to miss when the account total still looks healthy.
If you would rather have someone check it properly, we audit Merchant Center and Google Ads together so the feed side and campaign side are verified against each other. See our Google Shopping ads agency page, or work through our Merchant Center audit template yourself.
Related reading: what changed in the current Merchant Center interface, Performance Max and feed optimisation, the Performance Max checklist, Google Ads optimisation checklist, and Google product data specification 2026.
Summarise this article with:
