Content API sunset: who feeds your Merchant Center?

Your storefront can look fine and still stop updating products in Merchant Center. Merchant Center is Google's product catalog: it powers Shopping ads, free listings, and related surfaces that do not rely on your site HTML alone.

Google has set dates for sunsetting Content API for Shopping — the classic API many integrations used to push catalogs into Merchant Center. The replacement is Merchant API. For LatAm B2B ecommerce, the operational question is not "is Google down?" — it is: who feeds Merchant Center in your stack?

In plain words, per Google's official deprecation and sunset guide:

• Official sunset: August 18, 2026. Content API for Shopping is no longer the supported path; migrate to Merchant API.
• From September 1, 2026: without an active extension, Content API requests begin failing intermittently with HTTP 410 Gone.
• Full decommissioning: expected in early 2027 (subject to revision based on ecosystem migration progress).

The Merchant API migration overview covers the technical path; Google also notes that if you use a partner/platform, they usually migrate for you, and if you have a custom API integration, you must migrate yourself.

Before you open a ticket with your agency or partner, run this one-page audit. A feed is the product data flow (title, price, stock, GTIN, and so on) that reaches Merchant Center — via API, file, or platform connector.

Path A — Partner / platform (Shopify, WooCommerce, BigCommerce, VTEX, official apps)

If the catalog reaches Merchant Center through your platform's app or connector, the partner usually migrates for you. Your job: ask in writing whether they already use Merchant API (or when), and verify in Merchant Center that products keep syncing after the key dates.

• Email the partner or check their changelog / help center on Content API → Merchant API.
• Confirm which Merchant Center account is linked and who has admin access.
• Do not assume: "we are on Shopify/VTEX" does not prove the connector already migrated on your account.

Path B — Middleware, ERP, or custom scripts calling Content API

If middleware, a custom ERP connector, an internal script, or a feed vendor calls Content API for Shopping directly, that is your operational debt. Migrating to Merchant API is on you (or the agency that owns that integration): inventory endpoints, rewrite against Merchant API, test in staging, and ship with a rollback plan.

• List which systems write products, prices, and inventory to Google.
• Identify the Google Cloud project and credentials still talking to Content API.
• Plan a test window; if you truly need more time, request an extension via Google’s official form — it does not replace early-2027 decommissioning.

Shopping ads, organic product listings, and several Google surfaces read the catalog in Merchant Center. If the feed goes stale — wrong price, ghost stock, broken attributes — the site can look fine while discovery does not. This is not ranking drama; it is product-data debt.

In LatAm B2B that hurts when the ERP is the source of truth and the web or middleware "translates" the catalog poorly. Fixing the storefront does not fix Merchant Center if nobody feeds the catalog.

For ecommerce owners and ops in LatAm B2B (Shopify, Woo, BigCommerce, VTEX, or a custom stack):

1. Name the owner: who is accountable for the Merchant Center catalog? (marketing, ops, IT, or partner).
2. Classify the path: partner/platform vs middleware/ERP/custom (audit above).
3. Open Merchant Center: review products, data sources / integrations, and recent diagnostics (feed errors, disapprovals).
4. If Path A: ask the partner for proof of Merchant API migration; schedule a check after Aug 18 / Sep 1, 2026.
5. If Path B: schedule migration with staging; do not first-test in production on the day of the 410s.
6. Document access: Merchant Center, Google Cloud, connector repos — ownership in the client's name.
7. Decide partner vs agency: partner for official connectors; agency when the feed comes from ERP/custom middleware.

What is Merchant Center?

It is where Google stores your business product catalog for Shopping ads, free listings, and related surfaces. It is not the same as your website: it is the product data Google uses beyond your HTML.

Are Content API for Shopping and Merchant API the same?

No. Content API for Shopping is the older API (now in sunset). Merchant API is the modern replacement. If your integration still calls Content API, you need to migrate.

If I use Shopify / Woo / BigCommerce / VTEX, do I have to migrate myself?

In most cases, no: the partner or official app usually migrates for you. Still verify with them and watch Merchant Center on the key dates. If you also run your own script or middleware on top, that part is yours.

Does this affect my site’s SEO rankings?

No. This is feed and Merchant Center debt (product data), not HTML or organic site rankings. If the feed fails, what degrades is the catalog in Shopping and related surfaces — not “the algorithm punished your blog.”

What if I do not migrate in time?

Without an extension, from September 1, 2026 Content API calls can fail intermittently (HTTP 410). Full shutdown is expected in early 2027. If you need more time, use Google’s official extension form; it buys time but does not cancel early-2027 decommissioning.

If you want people-first Search or AI Overviews, that is a different topic: see our B2B GEO / AI Search checklist. If you are on the middleware/ERP/custom path and need a Merchant API migration plan without improvising in production, Somos Gente Digital can help map the feed, test in staging, and keep ownership clear. See ecommerce that fits your business or write us via Contact.