Google’s own documentation confirms the date: the Content API for Shopping “will be sunset on August 18, 2026.” Some trade coverage of that line reads it as a hard cutoff with no extensions planned. The same Google page that names the sunset date also links to a form for extended access. The date is not in question. The no-exceptions framing around it is worth checking against the source it claims to summarize.
What Google’s Migration Page Actually Says
The Content API for Shopping is the programmatic interface merchants and their tools use to send product data into Merchant Center. Google’s developer page states plainly that this API “will be sunset on August 18, 2026.” The same page carries an invitation to “apply for extended access to Content API for Shopping,” linking out to a request form.
Google calls Merchant API “a new, simplified API designed to help you manage your Merchant Center accounts and showcase your products with ease,” and names it the official replacement. Merchant API reached general availability in August 2025, per Google’s Merchant Center announcement log.
Where the “Hard Cutoff” Reading Comes From
Producthero’s January 20 breakdown of the change states that after August 18, “product data can no longer be sent to Google Merchant Center using the Content API,” and that integrations still running on it will stop working for uploads. Some coverage goes further, treating the deadline as final and extensions as off the table. That characterization comes from the trade write-ups.
Producthero’s piece also draws a distinction the shorter versions of this story tend to drop: the sunset applies to one upload path, not to product data in general. Per Producthero, “[I]f your product data is uploaded via XML feeds, scheduled fetches, or manual uploads, this change does not affect you.” The API sunset targets programmatic submission specifically. A merchant whose feed runs through a file or a dashboard upload is not the audience for this date.
Does the Content API for Shopping Sunset Affect Every Merchant?
No. The Content API for Shopping stops accepting product data submissions on August 18, 2026, affecting merchants and tools that push data programmatically through that API. Feeds sent by XML, scheduled fetch, or manual upload sit on a separate path that Producthero’s analysis describes as unaffected. Merchant API, generally available since August 2025, is Google’s named replacement, and the same migration page also links to a form to apply for extended access.
What to Verify Before the Date Arrives
The practical question for anyone running a Google product feed is not the date. It is which door the data walks through. A feed built on XML uploads or a scheduled fetch has nothing to change here, per Producthero’s read of the announcement. A feed wired to the Content API needs a status check: has it already moved to Merchant API, or is it still sending data through the interface that stops accepting it on August 18? An extension that has not been granted is a plan built on a form, not a commitment.
Google is not the only platform changing how product data reaches its systems. Our coverage of Amazon’s AI rewrites of over-limit product titles looked at a marketplace deciding what seller-submitted data ends up in its catalog. On the account side, Google’s agency tooling for multi-client Merchant Center accounts is a separate lever worth checking alongside any API migration.
Read against Google’s own Merchant API documentation and Producthero’s breakdown of the sunset, the story is not that Google reversed course. It is that the page naming the date also names a way to ask for more time.
