Google Merchant Center Next Migration: 2026 Ecommerce Guide

If you're still hunting for the old classic Merchant Center interface, bad news: it's gone. By multiple reports, the classic Merchant Center interface stopped being accessible in early 2026, and every account now runs exclusively on Merchant Center Next. This isn't a "should I migrate" question — it's "you've already been migrated, will you use it right" reality.

For ecommerce sellers, the biggest change in Next isn't a fresh coat of UI — it's that it treats your website as the primary source of product data by default, auto-extracting titles, descriptions, prices and images to generate or fill in products. Genuinely convenient, and genuinely full of traps. This piece lays out the changes, risks and required actions based on what's publicly known as of 2026. For the setup process itself, see Google Shopping and Merchant Center setup.

What actually happened

Google began rolling out Merchant Center Next back in 2023, migrating merchants in waves. By 2026 the transition has largely wrapped: the classic interface retired, Next became the only entry point. Running in parallel is a separate timeline that's easy to confuse — the Content API for Shopping is, by reports, being sunset around mid-August 2026, replaced by the new Merchant API. These are not the same thing:

• Merchant Center Next = the interface / dashboard you log into got a new look.
• Merchant API migration = the developer / third-party tool interface for pushing data got replaced.

If you connect to Google via Shopify, a storefront plugin, or a third-party feed tool, the second item is the one your developer or vendor should verify for exact timing and migration status — confirm the precise sunset date in Google's official docs, since sources vary slightly.

Classic vs Next: what actually changed

In one line: Next traded classic's manual control and flexibility for automation and simplicity. For a small, just-starting store with no polished feed, that's a net win; for a mature store running fine-grained feed rules, you may feel like some of your control was taken away.

Auto-crawl from the website: the biggest convenience, the biggest risk

Next crawls product titles, descriptions, prices and images straight from your site. For sellers who can't maintain a structured feed, that lowers the barrier. But by multiple accounts, auto-crawl carries clear risks:

• Wrong data / generic titles. The system may grab an imprecise field on the page as the title, or generate an overly generic description.
• Silent errors in big catalogs. The more categories and messier the SKUs, the more likely a batch of products is scraped wrong and nobody notices — big catalogs can quietly leak money without you knowing.
• Price / stock out of sync. If your site's structured data (schema) isn't clean, crawled price and availability may not match reality, which can trigger disapprovals. For troubleshooting disapproved products, see Google Shopping disapproved product fix.

So "Next handles the feed automatically" deserves an asterisk: it can get you started, but to get it right and keep it stable you still need your own clean, controlled product data source. Treat the system's auto content as a fallback, not the main act.

What sellers must do now: a migration checklist

Whether you're a legacy account that got switched over or a brand-new account, run this list:

1. Log into Next and reconcile product status. See how many products are approved / pending / disapproved — don't assume everything carried over unchanged.
2. Review auto-crawled content. Spot-check a batch of titles, descriptions, prices and images to confirm the system didn't rewrite them into generic or wrong content.
3. Confirm your primary data source. If you have a real feed (uploaded file / API / platform connection), make sure it's still active and takes priority over auto-crawl — let the source you control be primary.
4. Clean up website structured data. Price, stock, GTIN, brand and other schema fields need to be accurate, because Next uses them as input.
5. Relocate the advanced settings you depend on. Feed rules, supplemental sources and attribute mappings you used in classic have moved or been de-emphasized in Next; confirm the replacement path for each.
6. Verify API migration status (if you connect via third-party / plugin). Have your developer confirm the move from Content API to Merchant API and watch the officially published sunset date.
7. Verify the Google Ads to Merchant Center link. Google also adjusted automatic account linking in 2026 — confirm your ads account and merchant account are still correctly connected and data is flowing.
8. Establish a regular audit cadence. Make "spot-check product data + check disapprovals + reconcile price/stock" a weekly routine, not something you only do after a fire.

Don't overlook: feed optimization matters MORE in the Next era, not less

Some assume that once Next auto-crawls, they can stop caring about the feed. The opposite is true. Because both Shopping and Performance Max pull product data directly to dynamically generate Shopping ads and match long-tail searches, your data quality directly decides impressions and conversions. Whether the front of the title carries the right product type and core terms, whether attributes are complete, whether images are compliant — these are still what win or lose. The system's auto content usually can't reach that level of precision. For systematic optimization, see Google Shopping feed optimization.

Also worth a line is the downstream campaign shift: Smart Shopping was long ago replaced by Performance Max, so if you still have legacy campaigns unmigrated, handle them too — see Smart Shopping deprecated, migrate to PMax.

Frequently asked

Can I still use classic Merchant Center?

By multiple reports, the classic interface has been inaccessible since early 2026, and all accounts run on Merchant Center Next. There's no "opt out of migrating."

Does Merchant Center Next auto-generate a feed from my website?

Yes. Next treats the website as the primary data source by default, auto-crawling titles, descriptions, prices and images. But crawling can be wrong or overly generic, so you should still maintain your own clean, controlled data source as the main act.

Is this the same as the August 2026 Merchant API migration?

No. Merchant Center Next is an interface / dashboard refresh; the Merchant API migration is a new interface for developers and third-party tools (the old Content API is reported to sunset around mid-August 2026). Verify the exact date in Google's official docs.

Will I lose my feed rules and advanced settings after moving to Next?

Not all of them, but some advanced settings have moved or been de-emphasized in Next and are harder to find. Confirm a replacement path for each feature you rely on rather than assuming it's in the same place.

Do I need to make technical changes for the migration?

The interface migration is done automatically on Google's side; your main job is reconciling data and cleaning up website structured data. If you connect via a third-party / plugin, have your developer confirm the move to the Merchant API.

Why is some product data in my big catalog wrong?

Likely the auto-crawl grabbed an imprecise field on your site, or your site schema isn't clean. Big catalogs are especially prone to silent errors, so spot-check regularly and let a real feed take priority over auto-crawl.

Want to manage product data, disapprovals and unit economics together after migrating? Use our free tools to nail down the true return on each order before you talk about scaling.