Google Merchant Center Next: What Changed and What Sellers Must Redo

If you learned Google Merchant Center before 2023, most of the menus you remember are gone. Google rebuilt the product as Merchant Center Next, moved every account onto it, and in July 2026 removed the "Next" from the name. The product you log into today is simply called Google Merchant Center, but it is the Next version under the hood.

That matters because a lot of tutorials, agency SOPs and app docs still describe the classic interface. This guide explains what changed, where things live now, what was removed or put behind add-ons, and the checks every seller should run to make sure nothing was lost in the move.

Timeline: from classic to Next to plain Merchant Center

So when someone says "Merchant Center Next" today, they mean the current Merchant Center. There is no classic version to switch back to.

The new interface: where things moved

The biggest adjustment for experienced sellers is finding things. Configuration moved into the Settings (gear) menu, and product problems moved into the Products area. The renames that trip people up most:

Reporting was also consolidated into a Performance area, with product, free listings and pricing insights in one place. New tools arrived alongside it, including Product Studio for AI image and text help and the Store quality report, which scores shipping, returns, browsing and purchase experience.

Product sources: how data gets in now

In the classic version, you created a feed and uploaded products. The current Merchant Center treats every way of getting product data in as a "data source", and it adds a source classic never had: your website.

• Products found on your website. Google can detect products from your site's pages and structured data and add them automatically. Merchant Center also uses crawled data to fill gaps in products you submit.
• E-commerce platform apps. Shopify's Google & YouTube app, Google for WooCommerce and similar integrations push products through the API.
• Files. A CSV, TSV or XML file uploaded manually, fetched on a schedule from a URL, or delivered by SFTP.
• Google Sheets. A spreadsheet linked as a source, refreshed on a schedule.
• API. Custom integrations using the Merchant API.
• Manual entry. Adding and editing single products directly in the interface, which classic barely supported.

Every source is either a primary source (it can create products) or a supplemental source (it only adds or overrides attributes for products that already exist in a primary source). The concept is the same as classic feeds, but you now reach them under Settings > Data sources, with tabs for each type.

If your Shopify store syncs through the Google & YouTube app, one related change: products sold in overlapping Shopify markets are now split into separate country data sources. Google notes that this resets performance history for those products and that existing attribute rules and campaigns may need manual updates. Our guide to Google Shopping feeds on Shopify covers that setup in detail.

What was removed or works differently

Most classic features survived in some form, but several now behave differently or sit behind switches you have to turn on.

Supplemental sources and attribute rules need an add-on

In classic, supplemental feeds and feed rules were always available. Now you enable the Advanced data source management add-on under Settings > Add-ons before they appear. If you relied on them, confirm the add-on is on and your rules still exist and run in the right order.

Diagnostics is simpler and shallower

The detailed Diagnostics tab with its long history became Needs attention, which focuses on current issues grouped by type. Historical charts exist but are harder to find (look for the history view inside Needs attention), and some long-range trend data is more limited than it was.

Direct edits can conflict with your source

You can now edit a product's title, price or description directly in Merchant Center. That edit is stored as its own input. If the product also comes from an app or feed, the two can conflict, and a later sync may overwrite your change. For anything that should stick, fix it at the source.

Website data fills gaps automatically

Because Google reads your site, it may fill missing attributes or add products you never submitted. That is helpful for a small store, and confusing for a store that uses a curated feed and sees products it deliberately left out. Review what the website source is contributing.

The Content API is gone

Older custom scripts and plugins used the Content API for Shopping. Google set its sunset for August 18, 2026, with service degrading from September 1, 2026. Anything still calling it stops working reliably. Google's own apps for Shopify and WooCommerce are maintained by Google, but custom middleware and older third-party connectors need checking.

Setting up attribute rules in the new interface

Attribute rules are where most experienced sellers lose time after the move, because the menus are new even though the logic is the same. To create one:

1. Go to Settings > Add-ons and add Advanced data source management if it is not already on.
2. Go to Settings > Data sources and open the primary source you want to change.
3. Open the attribute rules tab for that source and choose the attribute to modify, for example title or product_type.
4. Pick the operation: set to a value or another attribute, extract part of a value, find and replace, prepend, append or calculate.
5. Add conditions if the rule should apply only to some products, for example brand equals a specific value.
6. Use the preview to compare the draft value with the current value on a few products.
7. Save. Rules run in order, and the change applies once the data source is processed again.

A typical use is adding the brand to the start of titles that lack it, or copying a collection name into product_type. Rules are best for patterns. If you find yourself writing a rule for a single product, fix that product in your store instead.

Shopify and WooCommerce stores: what the change means

If you sell through Shopify or WooCommerce, most of the migration happened for you. Google's own integrations (the Google & YouTube app for Shopify and Google for WooCommerce) moved to the new data source model and the Merchant API. You see them as an API data source in Settings > Data sources, and you should not edit or delete that source by hand.

Two things are worth checking. First, if you added a separate feed app on top of Google's integration at some point, you may now have two primary sources for the same products, which causes duplicates and conflicting prices. Keep one. Second, if you run older third-party feed plugins, confirm they have moved to the Merchant API, since the Content API they may have used is being shut down. For the Shopify side of the setup, see Google Merchant Center for Shopify.

What sellers should check or redo

Google migrated account settings, products and most rules automatically. Still, things slip through, especially on accounts that were set up years ago. Run through this list once:

1. Check your data sources. Open Settings > Data sources and confirm there is exactly one primary source per product set. Remove old test feeds and look for duplicate products from the website source and your main feed.
2. Turn on the add-on if you used supplemental feeds or feed rules. Then confirm each supplemental source is linked to the right primary source and feed label, and that attribute rules produce the values you expect in the preview.
3. Re-verify business info. Business name, address, customer service contact details and logo live under Business info. Missing or outdated contact details are a common trigger for misrepresentation reviews.
4. Re-enter shipping and returns. Check Settings > Shipping and returns. Add handling and transit times so delivery estimates show, and add your return policy (window and cost). Both also count toward Store quality.
5. Confirm marketing methods. Make sure free listings and any other methods you want are active, and that Google Ads is linked under the account's connections settings if you run Shopping or Performance Max campaigns.
6. Audit integrations. List every tool that writes to Merchant Center (feed apps, repricers, inventory tools, custom scripts). Confirm each one has moved to the Merchant API.
7. Review users and access. Old agency users and former staff often carried over. Remove anyone who no longer needs access.
8. Update your own docs. Replace screenshots and menu paths in SOPs and training material so new staff are not hunting for "Diagnostics" or "Feeds".

What stayed the same

The things that decide if your products get approved did not change with the interface:

• The product data specification: the same attributes (id, title, description, link, image_link, price, availability, gtin, brand and so on) with the same rules.
• The Shopping policies, including misrepresentation, which remains the most common reason for account suspensions. See how to fix a misrepresentation suspension.
• Website requirements: working checkout, clear refund and shipping policies, visible contact information and accurate prices.
• Free listings and Shopping ads, which still draw on the same product data.

In other words, an account that had data quality or policy problems in classic still has them now. The redesign made the problems easier to see, not easier to ignore.

Working in the current Merchant Center day to day

A practical weekly routine in the new interface looks like this:

1. Start on the Overview page for account-level warnings, which appear before product-level ones.
2. Open Products > Needs attention and fix the issue affecting the most products first. Click into an issue to see which attribute and which data source is responsible.
3. Fix at the source: in Shopify or WooCommerce for app-synced products, in your feed or sheet for file sources, or with an attribute rule when the source cannot produce the right value.
4. Check the Performance area for free listings and pricing insights on your top products.
5. Glance at Store quality monthly and pick one area to improve.

If you are brand new to the platform, start with what Google Merchant Center is and how it works. If your product issues trace back to store data (missing GTINs or brands, thin descriptions, missing policy pages or contact details), the AM Jarvis GMC Scanner and Fixer scans a connected Shopify or WooCommerce store for those problems and pushes the fixes back to the store in batches, so the data Merchant Center reads is correct at the source.