Introduction
If you've been managing a Google Merchant Center account for several years, you've certainly noticed the change: the old interface, with its separate tabs for feed management and distribution, has given way to Merchant Center Next. This isn't a simple facelift — it's a redesign of how Google organizes your product data, your ad distribution, and your compliance diagnostics.
Our article on Google Merchant Center 2026 updates covered all of the year's changes, including the fact that the shift to Merchant Center Next is now universal across all accounts. This guide focuses specifically on Merchant Center Next: what it is, why Google made this choice, what structurally changes, and — most importantly — what an e-commerce merchant concretely needs in order to migrate or consolidate their migration without losing compliance along the way.
If you're discovering Google Merchant Center for the first time, start instead with our complete guide to how Merchant Center works, which lays the groundwork before diving into the details of Next.
Table of Contents
- What Is Merchant Center Next?
- Why Google Launched Merchant Center Next
- Merchant Center Classic vs Merchant Center Next: the Structural Differences
- The Migration Timeline: What Merchants Need to Know
- Migrating to Merchant Center Next: the Practical Steps
- Common Pitfalls During Migration
- What Doesn't Change: Product Compliance Rules
- Merchant Center Next Migration Checklist
- FAQ
What Is Merchant Center Next?
Merchant Center Next is the next-generation Google Merchant Center interface, designed by Google to progressively replace the older interface, now retroactively referred to as "Merchant Center Classic." It isn't a separate product: it's the same back-office platform that hosts your product data and manages its distribution to Google Shopping, Performance Max, and free listings — but reorganized around a different logic.
The most visible change for a user accustomed to the old interface concerns how distribution is presented. Rather than navigating between siloed sections (feeds, diagnostics, promotions, loyalty programs...), Merchant Center Next groups configuration and monitoring around distribution destinations — referred to as "programs" in Google's documentation — such as Shopping ads, free product listings, or selling directly on Google. Each program has its own eligibility requirements, but shares the same underlying product database.
In practice, if you log into a Merchant Center account today, this is the interface you see — the old one is no longer available, as detailed in the timeline section below.
Why Google Launched Merchant Center Next
Google communicates three broad justifications for this redesign, consistent with the wider evolution of its advertising ecosystem.
Simplifying the merchant experience
The old interface had been built in successive layers over more than a decade, with features added over the years without an overall reorganization. The result: fragmented navigation, where the same information (a product's status, for example) could be found in several different places with slightly inconsistent presentations. Merchant Center Next aims for a more linear experience, centered on the tasks merchants actually perform — checking what's working, fixing what's blocked, configuring distribution.
Unifying accounts and multi-market structures
Merchants operating across multiple countries or with multiple sales channels (website, marketplace, physical store) historically had to juggle more complex account configurations. Merchant Center Next seeks to reduce this friction by further centralizing the management of business information and shared settings (shipping, returns, legal contact details), while still allowing distribution to be broken down by market.
Tighter integration with Performance Max and AI-driven campaigns
This is probably the most strategic motivation for Google. Performance Max relies directly on Merchant Center feed data as a training signal for its automated distribution algorithms — the closer the link between product data and the advertising layer, the faster Google's AI can react to a change in stock, price, or availability. Merchant Center Next was designed from the outset to remove friction between these two layers, rather than as a simple display layer bolted onto the old system. For more on this, our 2026 updates article details how much ground Performance Max has taken in current accounts.
Merchant Center Classic vs Merchant Center Next: the Structural Differences
Here's a summary comparison of the main structural changes, as documented by Google and observed by merchants who went through the transition.
| Aspect | Merchant Center Classic | Merchant Center Next |
|---|---|---|
| Distribution organization | Separate tabs per feature (Shopping, free listings, promotions...) managed independently | Organized by distribution "programs," with a shared product base |
| Feed management | One or more feeds managed separately, no consolidated view | Consolidated view of all feeds (primary, supplemental, local inventory) |
| Compliance diagnostics | Diagnostic reports scattered across different features | More centralized diagnostics view, designed to prioritize corrective actions |
| Business information | Sometimes duplicated configuration across linked accounts | More centralized business information at the account level |
| Campaign integration | Link with Google Ads existed, but performance tracking was separate | More direct connection between product data and ad performance |
| Access and permissions | User management close to the old Google Ads console | Permissions model aligned with current Google account standards |
Two points deserve further detail, as they're the ones that most disorient teams used to the old interface.
Organization by programs rather than siloed tabs
In the old interface, the same product could be "approved" for Google Shopping while being invisible for free listings, without this being clearly visible in one place. Merchant Center Next aims to display these statuses more legibly per distribution destination, to avoid a merchant discovering after the fact that an entire program was never activated due to missing configuration.
A more consolidated feed view
Feed management remains conceptually identical — you still submit a structured file (XML, CSV/TXT, or via the Content API) listing your products and their attributes. What changes is the readability of that management when you use several feeds in parallel: primary feed, promotional feed, local inventory feed. For the required attributes themselves — which don't depend on the interface used — see our complete Merchant Center guide.
The Migration Timeline: What Merchants Need to Know
Google rolled out this transition gradually rather than through a single abrupt switch for every account at once. New accounts opened in recent years were created directly on Merchant Center Next, while older accounts were migrated in successive waves, with notifications sent directly within the interface and by email to account administrators.
As we detailed in our article on Google Merchant Center 2026 updates, this rollout is now complete: the old Merchant Center Classic interface is no longer accessible, and every active account now runs on Merchant Center Next. In other words, this is no longer a choice to make, but a state of fact for any account currently in service.
What this means concretely depending on your situation:
You manage an account that's existed for several years If your account was migrated automatically, the essentials — product history, approval statuses, configured feeds, links to Google Ads — were normally preserved without any action on your part. The migration concerns the interface and information organization, not a reset of your data.
You're opening a new account today You start directly on Merchant Center Next, without ever having known the old interface. Older guides and screenshots you might find online, including some content published before Next became universal, may no longer exactly match what you see.
You manage several linked accounts (Multi-Client Account structure) Accounts attached to a Multi-Client Account generally follow the same migration timeline as individual accounts, but it's worth checking account by account that the switch was actually applied, particularly for accounts that are less active or rarely reviewed.
Migrating to Merchant Center Next: the Practical Steps
For the vast majority of merchants today, the technical migration itself has already happened automatically — there's no "migrate" button to click yourself. What remains your responsibility is mostly verification that nothing was lost in the transition, and adaptation of your internal habits and tools to the new organization.
First: verify the integrity of your data
Log back into your account and go through the following:
- Your products' status — compare, if you've kept earlier snapshots or exports, the number of active, disapproved, and pending products before/after the migration.
- Your configured feeds — check that all your feeds (primary, promotional, local inventory) appear correctly and sync normally.
- The link with your Google Ads account — make sure the connection between Merchant Center and Google Ads is still active, a requirement for your Shopping and Performance Max campaigns to run.
- Users and permissions — check that your team members still have appropriate access; since the permissions model has evolved, some roles may have been reassigned differently.
Adapting your internal processes
Alerts and notifications If you had configured email alerts or automated reports in the old interface, check that they're still active. Some configurations tied to the old interface haven't always carried over automatically.
Internal documentation and procedures If your team works from written procedures (internal guides, training screenshots), update them. Since the navigation logic has changed, a procedure describing precisely where to click in the old interface risks misleading your team.
Connected third-party tools If you use third-party feed management tools (agencies, feed platforms, custom scripts using the Content API for Shopping), check with your providers that their integration remains fully compatible and that no functionality has been affected by the interface reorganization.
After migration: consolidate
Once initial verification is done, the most useful next step is resuming your regular monitoring habits — catalog health, disapproved products, feed consistency — but now within the new Merchant Center Next framework. It's also a good moment to run a full compliance review, since you're already going back through your entire configuration.
Common Pitfalls During Migration
Feedback from merchants who went through this transition highlights a few recurring mistakes.
Confusing an interface change with a rules change The most common pitfall is assuming that an approval issue that appeared after migration is caused by Merchant Center Next itself. In the vast majority of cases, a product disapproved after the migration was already at fault for a compliance reason unrelated to the interface — an invalid GTIN, a price inconsistency, a missing legal page. See the next section on what doesn't change.
Not finding a feature simply because of its new location A feature that existed in the old interface generally still exists in Merchant Center Next, but may be accessible via a different path. Before concluding a feature has disappeared, it's worth checking Google's official help resources to see if it was simply relocated.
Neglecting to check secondary or low-activity accounts In a multi-account structure, it's easy to carefully verify the main account while forgetting secondary accounts (a specific market, a secondary brand, an old test account) that keep running in the background without supervision.
Letting an untrained team discover the interface in production An interface change, even a well-designed one, temporarily slows down teams used to the old navigation. Planning a minimum amount of familiarization time avoids handling errors during a period when compliance vigilance needs to stay intact.
Forgetting to re-check feeds configured via old scripts or automations If your feed submission relies on a custom script written several years ago, make sure it still points to the correct account identifiers and that nothing has become incompatible due to changes in the underlying API.
What Doesn't Change: Product Compliance Rules
This is the most important point to remember, and probably the one most prone to confusion: Merchant Center Next is a change of interface and organization, not a change to the underlying rules.
Google Merchant Center policies — price consistency between the feed and your site, accuracy of product information, image quality and compliance, presence of required legal pages (legal notice, terms and conditions, return policy, contact details), absence of misleading commercial practices — apply exactly the same way whether you're navigating Merchant Center Next or remember the old interface. A product that violated a compliance rule before the migration continues to violate it afterward, and conversely, a fully compliant feed before the migration remains compliant after — the interface switch alone triggers neither approval nor disapproval.
This distinction has an important practical implication: if you notice an increase in disapprovals after your migration, the most likely cause isn't the interface itself, but either a coincidental overlap with other policy changes (see our 2026 updates article), or a configuration issue that already existed and simply becomes more visible in the new diagnostics view.
This is precisely why an interface-independent compliance audit remains the best way to know where you actually stand. Our 47-point checklist to check before launching campaigns covers the same underlying compliance criteria, whether reviewed from Merchant Center Classic — for those who still remember it — or from Merchant Center Next.
Merchant Center Next Migration Checklist
- Confirm the account has moved to Merchant Center Next and that access works normally for all users
- Compare the number of active, disapproved, and pending products before/after the migration
- Check that all feeds (primary, promotional, local inventory) are still present and syncing
- Verify that the link with the Google Ads account is still active
- Review permissions and roles for team members
- Reconfigure email alerts and automated reports if needed
- Update internal documentation and team procedures
- Confirm with third-party providers (agencies, feed tools) that their integrations remain functional
- Check secondary or low-activity accounts within a Multi-Client Account structure
- Run a full catalog compliance audit to separate interface-related issues from underlying ones
- Plan minimal training time for teams unfamiliar with the new navigation
FAQ
Is Merchant Center Next mandatory? Yes, today. The old Merchant Center Classic interface is no longer accessible: every active account now runs on Merchant Center Next. It's no longer an option but the only available interface.
Are my existing feeds preserved after the migration? Yes. The migration to Merchant Center Next concerns the interface and information organization, not a reset of your data. Your configured feeds, product history, and approval statuses are normally preserved. It's still recommended to verify these elements after a migration, as detailed in the practical steps section above.
Does Merchant Center Next change product approval rules? No. Google Merchant Center compliance policies (price consistency, data accuracy, legal pages, image quality...) are independent of the interface used. A change in approval status after a migration almost always has an underlying compliance cause, not a direct link to the switch to Next.
Do I need to reconfigure my product feed after the migration? In principle, no — the feed continues working as configured. It's still recommended to check that syncing works normally and that your format (XML, CSV/TXT, or Content API) remains fully supported.
Are my Google Ads Shopping and Performance Max campaigns affected by the migration? The link between Merchant Center and Google Ads is preserved during migration, but it's recommended to verify it explicitly after the switch, along with product data flowing correctly into your active campaigns.
Where can I get help if a feature I used seems to have disappeared? Most features from the old interface still exist in Merchant Center Next, but may be accessible from a different location. Google's official Merchant Center help center remains the most reliable source for locating a relocated feature.
Does Merchant Center Next affect my eligibility for free listings or Performance Max? Not directly. Eligibility for these programs depends on the compliance and quality of your product data, not on the interface used to manage it.
Move to Merchant Center Next Without Losing Compliance
An interface change is the ideal moment to review your entire product compliance — since you're already checking your configuration, you might as well make sure no violation slipped into your catalog during the transition.
MyGoogle scans your product pages in 30 seconds and automatically checks price consistency, legal pages, images, and structured data — regardless of which Merchant Center interface you use.
Launch the free audit — no installation required, immediate results.