The Content API for Shopping is shutting down: what to check before it stops

The Content API for Shopping is the older programmatic way apps and scripts talked to Google Merchant Center: reading product statuses, pushing product data, managing accounts. Google is replacing it with the Merchant API, a rebuilt and modular version, and the old Content API is being switched off. After the cutoff, calls to the retired endpoints stop working. Anything that still depends on them, a sync job, a reporting script, a third-party feed tool, loses its connection to Merchant Center.

• Content API for Shopping (the old interface) is being retired.
• Merchant API (the modular replacement) is where everything moves.
• After the cutoff, calls to the old endpoints simply stop returning data.

Most Shopify stores connect to Merchant Center through a managed integration, Google’s own channel app or a maintained third-party app, and those providers handle the migration for you. The risk sits with anyone whose connection is not maintained by someone else: a custom-built sync, an in-house reporting script, an older or abandoned app, or a feed tool whose vendor has gone quiet. If someone on your team wrote code against Merchant Center, or you use a tool that has not shipped an update in a while, assume it needs checking.

• Lower risk: managed integrations from Google or an actively maintained app.
• Higher risk: custom scripts, in-house sync jobs, or older apps built on the Content API.
• Watch out for third-party feed tools whose vendor has stopped updating.

You do not need to read code to get a first signal. Look at how your products reach Merchant Center and who maintains that path. If it is an app from the marketplace that still receives updates, you are probably fine. If it is a bespoke integration, a script someone set up once, or a tool that has not changed in a year, that is where to look. When in doubt, ask the provider directly whether their integration already runs on the Merchant API, and get the answer in writing.

• Trace how product data actually gets to Merchant Center today.
• Check whether each app or tool in that path still ships updates.
• Ask providers plainly whether they are on the Merchant API yet, and keep the answer.

The goal is simple: every path into Merchant Center should run on the Merchant API before the old one is switched off. For managed apps, confirm the vendor has migrated. For custom code, plan the move to the Merchant API and test it against a real account, not just in theory. Do not leave it to the last week. Once the Content API stops, a broken sync means products quietly drop out of Google Shopping until someone notices the lost traffic.

• Confirm every managed integration has moved to the Merchant API.
• Migrate and test custom code well before the cutoff, against a live account.
• Have a fallback: know how to reconnect if a sync breaks on the day.

Deadlines like this are the visible part of a moving target: Google changes how Merchant Center works more often than most stores track. The way to not get caught is to watch the account itself, not the calendar. A check that reads your live product and account status through the current Merchant API tells you the moment something drops, whether it is a sunset, a policy change, or a disapproval, while it is still a small fix. Feed Guard runs on the Merchant API, so this sunset changes nothing on our side. It is an informational check, not legal or technical advice, and it does not guarantee compliance, but seeing a problem the day it appears is most of the fight.