Google has completely overhauled the help documentation for its Merchant Center API, renaming the page from "API access to Merchant Center" to simply "Google Merchant Center API" and rewriting the content from scratch.

The change surfaced in Google's help documentation and was flagged by industry watchers tracking Google's documentation edits. It is a documentation revision, not a confirmed change to the API's underlying behavior — Google has not issued a separate statement about new API capabilities, and ranking or feed-processing effects are not in play here.

What changed in the document

The old version of the page was thin. It made no mention of older tools or the broader Merchant Center architecture, and it offered no setup or authentication instructions. Developers integrating with Merchant Center had to rely on scattered resources to figure out how to authenticate and connect.

The new version addresses both gaps directly. It lays out the specific technical options for accessing the API and adds setup and authentication instructions that the previous page lacked entirely. For developers and feed management teams, that removes a real friction point: authentication guidance previously required piecing together information from multiple sources.

The rewritten page also highlights benefits and exclusive features available through the API. Google now explicitly calls out access to Google Product Studio, its AI-powered product imagery tool, and direct account notifications. These features were not surfaced in the old document, meaning some merchants and tool builders may not have known they could reach them programmatically.

Beyond those headline items, the revision includes what observers describe as "plenty of other changes" — expanded detail throughout the page covering technical options the old version never mentioned.

Documentation change, not a product announcement

To be clear about what is confirmed versus inferred: the confirmed facts are the rename, the complete rewrite, the addition of setup and authentication instructions, and the newly highlighted features including Product Studio and account notifications. All of this comes directly from comparing the old and new versions of the help page.

What is not confirmed is whether this documentation refresh signals an imminent deprecation of the older Merchant Center tools the new page references, or a broader architectural shift in how Google wants merchants and platforms to integrate. The document now acknowledges older tools and the wider architecture — something the old page omitted — but Google has not announced any retirement timeline.

A diff of the two documents, old and new, is circulating among industry watchers, and discussion of the change is playing out on X.

Who this matters to

The audience most affected is developers and feed management platforms that build against Merchant Center — agencies running large product catalogs, e-commerce teams managing shopping feeds at scale, and SaaS tools in the shopping-feed space. For them, better authentication documentation reduces integration time, while the explicit mention of Product Studio access and direct account notifications may prompt a second look at features they had not wired up.

For merchants who manage feeds manually through the Merchant Center interface, the practical impact is minimal. This is a developer-facing change.

The timing also fits a pattern: Google has been steadily pushing merchants toward more programmatic management of product data, and cleaner API documentation lowers the barrier for smaller teams to adopt that approach.

What to watch next

Monitor Google's Merchant Center documentation and developer channels for follow-up changes — particularly any explicit deprecation notices for the older tools the new page now references, and any expansion of the exclusive features list beyond Product Studio and account notifications.