Merchant Center Drops 'Next': What Actually Changes for Sellers

Google Merchant Center dropped the "Next" from its name on July 9, 2026 — the platform every Shopping seller logs into is now simply called Google Merchant Center again. Google's announcement is explicit that this is branding only: no account changes, no feed changes, no campaign changes, no new login flow. So why write a full guide about a name?

Because the rename lands in a busy season for Merchant Center operators, and it is surrounded by changes that do carry deadlines. Sellers searching "Merchant Center changes 2026" will find the cosmetic rename, a genuinely breaking API shutdown on August 18, and an active phishing campaign that impersonates the Merchant Center login — three unrelated things that generic coverage tends to blur into one.

This guide separates them cleanly: what Google actually announced, the full 2023-to-2026 arc that the rename closes, the one deadline that requires real work, why the rename window is a phishing risk worth briefing your team on, and a short checklist of what — if anything — to do.

The announcement itself is short. Via an official Merchant Center Help update on July 9, 2026, Google said: "The platform you use today will simply be referred to as Google Merchant Center." The rollout is gradual rather than a hard cutover — per Google, "You'll begin to notice the 'Next' branding removed from our Help Center articles, email communications, and the Merchant Center interface," with the scrub continuing across branding, help documents, and communications in the coming weeks.

Barry Schwartz at Search Engine Roundtable broke the story the same morning, and as of this writing the rename is the most recent entry in Google's official Merchant Center announcements changelog — no further branding changes have been announced since.

Notably absent from the announcement: any mention of changed URLs, API endpoints, or account IDs. On a direct read of Google's help page, this is a UI and copy-string change, not an infrastructure change. If your agency has runbooks that reference merchants.google.com, nothing in the announcement suggests those links break.

Google front-loaded the reassurance, and it is worth quoting precisely because rename announcements are where vague coverage invents obligations that don't exist. The official line: "No action is required. This name change doesn't affect your account." Google then itemized three specific guarantees, each of which maps to a thing sellers would otherwise worry about.

The practical consequence for advertisers: campaigns that consume Merchant Center data are equally untouched. If you run Performance Max campaigns that pull from Merchant Center feeds, nothing in the feed-to-campaign pipeline changes — the same products, attributes, and disapproval rules apply the day after the rename as the day before. The only visible difference will be copy strings in the interface and in Google's emails as the "Next" scrub rolls out.

Where the rename does create work is in your own material, not Google's. Agency decks, client onboarding docs, internal SOPs, and training videos that say "Merchant Center Next" are now dated — harmless, but the kind of staleness that erodes client confidence in a pitch. That cleanup is the one legitimate to-do the rename generates, and it is covered in the checklist below.

Most coverage treats the rename as a standalone one-liner. It reads differently as the closing step of a migration Google has been running for roughly three years. Merchant Center Next was unveiled at Google Marketing Live in May 2023 — worth pinning down, because even trade coverage has been internally inconsistent about the origin month. The original pitch: instead of requiring a manually built product feed, the new interface auto-detects product information — pricing, imagery, descriptions — from a merchant's website, with sellers able to edit what gets pulled or switch the feature off entirely. Google's message to bigger sellers at the time: "While we're simplifying, the features that larger retailers rely on aren't going anywhere."

In August 2024 Google announced the mass-migration timeline — "By September, all retailers will be upgraded to Merchant Center Next, which includes new insights reports, generative AI imagery tools and a more intuitive interface" — and by September 2024 the migration was complete for all merchants, with classic Merchant Center documentation phased out of the Help Center. Trade coverage suggests the classic interface itself was fully retired by early 2026, though Google never pinned that to a dated announcement of its own; what is verifiable is that Google's old "transition to Merchant Center Next" FAQ page now returns a 404, consistent with the transition period being over. The table below assembles the full arc — with an explicit action-required column, because that distinction is exactly what generic coverage keeps blurring.

Read as a sequence, the rename makes obvious sense. "Next" was transitional branding — useful only while two interfaces coexisted and Google needed a way to distinguish the new one from the classic one it was replacing. Once every merchant was on the new platform and the classic documentation was gone, the qualifier stopped carrying information. Google dropping it is the naming equivalent of striking scaffolding after the build: a signal that the company considers the migration genuinely, permanently done.

Here is the conflation risk this post exists to prevent. Forty days after the rename announcement — and 38 days after this post publishes — Google shuts down the legacy Content API for Shopping on August 18, 2026. Any merchant still pushing product data programmatically through that API must migrate to the newer Merchant API before then or their feed pipeline breaks. That is a real, breaking, dated change — and it has nothing to do with the rename. The two were announced independently and affect entirely different things.

Who is actually exposed? A narrower group than the deadline's urgency suggests. Merchants using scheduled fetch (a server file Google pulls), manual file uploads, or Google Sheets feeds are unaffected — those ingestion paths are not the Content API. The deadline bites only where product data is pushed programmatically: custom feed middleware, some ERP and PIM connectors, and in-house scripts written against the old API. A first wave of this migration already happened — Merchant API beta users had to complete their move off the Content API by February 28, 2026 — so August 18 is the final call for everyone else.

The five-minute audit: ask whoever owns your feed integration one question — "does anything we run call the Content API for Shopping?" If the answer is scheduled fetch, manual uploads, or Sheets, you are done. If the answer involves custom code or a third-party connector, get a written confirmation from the vendor that it is Merchant API-ready before August. Feed plumbing is invisible until it breaks, and a broken feed takes every Shopping and Performance Max campaign downstream of it down too.

"Watch for phishing" reads like boilerplate until you know the threat is already live. In February 2026 — five months before the rename — PPC News Feed reported a campaign of malicious search ads that closely imitate the official Merchant Center login page, surfacing when users search "GMC" on Google and designed to capture credentials. The reported tell worth training staff on: two-factor authentication prompts sometimes appear to originate from outside the US, most often Brazil. The standing advice from that report is unglamorous and correct — verify the URL before entering login details, and enable two-factor authentication.

The broader climate makes the rename timing worse. AdExchanger has reported an ongoing pattern of sophisticated Google ads account-takeover scams in which attackers lock out legitimate users, erase campaign and reporting data, and spend stolen budget on further phishing ads — with some agency executives reporting significant losses and no refunds. None of that is rename-specific. But a rebrand is exactly the moment such operations exploit: a fake "your account must be updated for the new Google Merchant Center" email is dramatically more plausible in the weeks after a real, publicized name change — especially when Google itself has told users to expect its emails to start looking different as the "Next" branding is removed from communications.

For agencies managing client accounts at scale, this belongs in the client communication plan, not just the internal one. Clients see the same fake emails your team does, and a client who enters credentials on a spoofed page compromises the account you manage. A two-line note to clients — rename is real, action emails are fake — costs five minutes and closes the most likely attack path. It is the same account-hygiene discipline that protects paid media programs generally: the ad budget is only as safe as the weakest login with access to it.

Four items, honestly prioritized. Note what leads: the only time-critical item is the API audit, and the account itself needs nothing at all.

If you are touching your feed setup anyway while auditing for API calls, it is a reasonable moment for routine feed hygiene — the kind that pays off regardless of renames. Product data quality is a cross-marketplace discipline: keeping product-page data feed-ready improves what Merchant Center auto-pulls from your site, and the same structured-attribute rigor carries from Amazon's Featured Offer ranking to Google Shopping. And if your feed pipeline, API migration, or Shopping campaign structure needs more than a checklist, our ecommerce services cover exactly this territory — feed architecture, marketplace integration, and the campaign layer on top.

Looking forward, expect a lag economy around the old name. Google will finish its scrub within weeks, but third-party tools, courses, agency templates, and years of blog posts will say "Merchant Center Next" for a long time. That is mostly harmless — the product is the same — but it means documentation age is now easy to spot at a glance, and it gives scammers a second angle ("your tools still say Next, click here to upgrade"). The stable heuristic for the next year: treat the two names as synonyms, and treat anyone claiming the name change itself demands action as either confused or malicious.