Skip to content
aivoma
Free check

Fix guides · Cart, checkout & content

Your product data may have stopped reaching Google on 18 August

Google retired the Content API for Shopping on 18 August 2026. Integrations still calling it get HTTP 410 and stop updating — usually with no warning.

Impact: Critical We fix this in AI Visibility Setup — €790 · Updated

The symptom

  1. Merchant Center prices, stock or new products stopped changing after 18 August 2026, while the shop itself looks fine.
  2. A custom integration or an older feed plugin logs 410 Gone against shoppingcontent.googleapis.com.
  3. Products drift into *Not current* or get disapproved for price and availability mismatches, because Google is comparing your page to data it can no longer refresh.
  4. Nothing in WooCommerce is broken and nobody changed anything — which is exactly why this goes unnoticed.

Why it matters

Google retired the Content API for Shopping on 18 August 2026 and replaced it with the Merchant API. Calls to the old v2.1 endpoints now return 410 Gone. There is no grace period and no fallback.

This is an API-only cutoff. Manual file uploads, scheduled fetches and Google Sheets feeds keep working, so a shop can be half-fine: the feed it uploads is current, while the integration that used to push stock levels is silently dead.

The damage is quiet and compounding. Google keeps serving the last data it received, so listings stay up but drift out of date — wrong prices, items shown in stock that are not, and eventually disapprovals for mismatch. Ad spend keeps running against stale inventory.

It also reaches every surface fed by Merchant Center: free listings, Shopping, AI Overviews and AI Mode product results all read the same data.

How to check it yourself

  1. Merchant Center → Products → *All products*: look at Last updated. If the newest timestamp is on or before 18 August 2026, nothing has reached Google since.
  2. Change a price in WooCommerce, wait for the next sync, and see whether Merchant Center reflects it. This is the fastest conclusive test.
  3. If you use Google for WooCommerce, check the plugin version and update it — recent releases moved to the Merchant API.
  4. For a custom or agency-built integration, search the code and logs for shoppingcontent.googleapis.com or content/v2.1. Either string means it is calling a retired endpoint.
  5. Merchant Center → Diagnostics, and the announcements change log, will show account-level feed problems.

How to fix it

  1. If you use the official Google for WooCommerce extension: update it. Keeping that extension current is what carries most stores across, and it is the least work by a wide margin.
  2. If you use a third-party feed plugin: check the vendor has shipped a Merchant API release, update, then re-authorise the Merchant Center connection — the migration usually needs fresh consent rather than just new code.
  3. If you have a custom integration: it must be ported to the Merchant API. The resource names and request shapes changed; this is a rewrite of the integration layer, not a base-URL swap.
  4. As an immediate stopgap, switch to a scheduled feed fetch: publish a product feed at a stable URL and have Merchant Center pull it on a schedule. File and Sheets ingestion were unaffected by the retirement, so this restores fresh data within a day while the proper fix is arranged.
  5. Once data flows again, re-check disapprovals: items rejected during the stale period usually clear on the next successful fetch, but price-mismatch strikes can take a review.

FAQ

Straight answers to the questions store owners ask

I only upload a file or use Google Sheets. Am I affected?

No. The retirement applies to programmatic API integrations. Manual uploads, scheduled fetches and Sheets-based feeds continued working through 18 August and still do. It is worth confirming which method your shop actually uses, because plugins often set up an API connection without saying so.

How would I know this happened? Google did not email me.

Usually you would not, which is the problem. The shop keeps working, listings stay visible, and only the freshness of the data degrades. The reliable signal is the Last updated timestamp in Merchant Center — if it stopped moving in August, so did your product data.

Is this the same as the Merchant Center reporting change?

No, they are separate and happened days apart. The API retirement on 18 August stops data reaching Google. The reporting update around 24 August changed how existing traffic is classified — YouTube affiliate results were split out of organic and history was restated — which makes charts dip without any loss of real demand.

Can I just wait for my plugin to fix it?

Only if the plugin is actively maintained and you have verified a Merchant API release exists. Every day on a dead integration is another day of stale prices and stock reaching every Google surface, so set up a scheduled feed fetch in the meantime rather than waiting.

Free instant store check

See what AI assistants can read on your store — in 60 seconds

Paste your store URL. We test AI-crawler access, product schema, prices, GTINs, feeds and email security live, and show the exact gaps. No sign-up, no obligation.

Check my store free