Google Merchant Center's September 2026 Shopping Policy Consolidation: What's Actually Changing

Google Merchant Center Help published a notice on July 15, 2026 confirming that starting in September 2026, its separate Shopping ads policies and free listings policies will merge into a single, unified Shopping policy document. Google's own language is explicit that this "does not introduce substantive changes to, or more restrictive enforcement of, the policies," and that merchants "should expect no additional restrictions on their product listings as a direct result of the update." That framing is accurate, but it undersells why this update is still worth a merchant's attention, and it lands alongside two other real Merchant Center changes this year worth tracking at the same time.

This post covers exactly what's merging, why a documentation reorganization is still worth checking even when Google says nothing substantive changed, and two other concurrent 2026 Merchant Center updates, the platform's rename and a reporting overhaul, that matter more than this one for most sellers. If your Shopping and Performance Max campaigns are limited by how much creative variety you can produce for your feed, the AI Image Generator in Miraflow AI is worth knowing about while you're auditing your account anyway, since feed creative quality affects Shopping performance far more than any policy documentation change does.

What's Actually Changing in September 2026

Until now, Google Merchant Center has maintained two separate policy documents: Shopping ads policies, covering the paid product listings that appear in Shopping campaigns and Performance Max, and free listings policies, covering the unpaid product listings that appear in the Shopping tab and elsewhere. A merchant running both simultaneously, which describes most active Shopping advertisers, has had to reference and stay current on both documents independently, even though the two overlap heavily in prohibited content, prohibited practices, restricted content, and site requirements.

Starting in September 2026, those two documents become one. Google has stated that rules applying only to paid Shopping ads, and not to free listings, will be clearly labeled inside the merged document rather than simply omitted or left ambiguous. The underlying policy categories themselves, what's prohibited, what's restricted, and what site requirements apply, are not changing as part of this update. This is a documentation and organization change, not a new set of rules.

Why This Isn't Nothing, Even Though Google Says Nothing Substantive Changed

It's tempting to read "no additional restrictions" and file this under changes that don't require any action. That's mostly right, but not entirely, and the exception matters for a specific group of merchants.

A seller who has only ever run free listings, never paid Shopping ads, has historically had no reason to read the Shopping ads policy document at all. Once the two merge into one Shopping policy reference with ads-only rules labeled rather than separated into their own document, that seller is far more likely to actually encounter ads-specific policy language while reading through the merged document, even if none of it currently applies to them. That's not a new restriction, but it is a real change in what a free-listings-only merchant is likely to read and potentially misapply to their own account.

The more practical value cuts the other way. A merchant running both programs no longer has to cross-reference two documents to understand a single policy area, which reduces the real, common failure mode where a seller checks one document, assumes it covers both programs, and misses a distinction that only applied to the one they didn't read. Google's own language, that ads-only rules will be "clearly indicated when this is the case," is direct acknowledgment that the previous two-document structure created exactly this kind of confusion.

The practical move for any active Shopping seller is a one-time read-through of the merged document once it goes live in September, specifically checking for any rule labeled as applying only to the program (ads or free listings) you weren't previously required to read closely. A twenty-minute read now is cheaper than a disapproved listing discovered later because a labeled, ads-only rule turned out to apply somewhere you didn't expect.

How This Plays Out for Different Types of Sellers

A small, single-category seller running only free listings has genuinely the least to do here, but also the most to gain from actually reading the merged document once. Since this seller has never had reason to open the Shopping ads policy document, the merge is effectively the first time ads-specific language becomes visible to them at all, which is useful groundwork if they ever decide to launch paid Shopping or Performance Max campaigns later, since the policy context will already be familiar rather than a cold start.

A mid-size seller running both free listings and Shopping ads across a broad catalog benefits most directly from the consolidation itself, since cross-referencing two overlapping documents to confirm a single policy question has been a real, if minor, tax on account management. One document with clearly labeled exceptions removes that friction immediately.

A large, marketplace-scale seller managing feeds across dozens of product categories and multiple regions should treat this as an opportunity to formally update internal compliance documentation and training material that likely still references the two old, separate policy sets. Bigger operations tend to have that kind of policy knowledge baked into internal wikis or onboarding docs for new team members, and an external document restructuring is exactly the kind of change that quietly goes stale in an internal reference unless someone owns updating it.

Why Google Keeps Doing This

It's fair to ask why a company the size of Google spends engineering and documentation effort on a change it explicitly says doesn't alter anything substantive. The honest answer is support cost and trust. A merchant confused about which policy document applies to their account, or one who discovers a violation after only reading half of the relevant rules, generates support tickets, appeals, and account suspensions that are expensive for Google to process and frustrating enough for sellers that some abandon Shopping ads entirely rather than untangle the confusion. A single, clearly labeled policy document reduces that friction at scale, even if it changes nothing for any individual seller who was already reading both documents carefully. That's the same logic behind the Merchant Center Next-to-Merchant Center rename below: cutting confusion at the documentation and naming level is cheap relative to the support and trust cost of leaving it unresolved indefinitely.

The Bigger Context: Merchant Center Next Quietly Became Just "Merchant Center"

This policy merge is not happening in isolation. In July 2026, Google also announced it was dropping the "Next" branding from Merchant Center entirely, across its Help Center documentation, in-product interface, and communications. The platform previously known as Merchant Center Next is now simply referred to as Google Merchant Center. No account changes accompanied the rename; every feature continues working exactly as before. Since January 1, 2026, the old Merchant Center Classic interface has not been accessible at all, meaning every active seller has already been running exclusively on what is now just called Merchant Center, whether or not they'd noticed the rename.

Taken together with the policy merge, the pattern is a platform in active cleanup mode: consolidating two policy documents into one, and consolidating two product names (Classic and Next) down to one, both in the same year. Neither change requires action on its own, but both point toward Google treating Merchant Center as a settled, mature platform worth simplifying rather than one still actively being renamed or restructured feature by feature.

The August 24 Reporting Overhaul, the Change That Actually Affects Your Numbers

While the policy merge is mostly a documentation change, a separate Merchant Center update that took effect August 24, 2026 is worth more attention, since it directly affects the performance numbers a seller sees. Google's own announcement described this as an update to "align reporting definitions across Google platforms including Ads and YouTube," with one specific, concrete change: YouTube affiliate results are now separated out from other performance data rather than blended into a single number.

For a Shopping seller whose Performance Max campaigns run across YouTube alongside Search and Shopping inventory, this means a metric that previously represented a blended total now splits YouTube-driven affiliate results out separately. If your reported conversion numbers shifted around August 24 without any corresponding change in your actual campaigns or budgets, this reporting definition change, not a real performance shift, is the most likely explanation. It's worth pulling your own account's reporting from before and after that date specifically to confirm which of your metrics were affected before drawing any conclusions about campaign performance around that time.

Other Concurrent Changes Worth Knowing About

A few other real Merchant Center and Shopping changes from earlier in 2026 are worth having on your radar alongside the September policy merge, since together they explain a busier-than-usual year for Shopping infrastructure changes:

• Sponsored ads embedded into free listing grids (April 2026), meaning free and paid listings now appear interleaved in the Shopping tab rather than in clearly separated sections, which is part of why Google is now testing a hide-sponsored-products toggle, spotted in screenshots in July 2026 and confirmed by Google's Ads Liaison as an active test aimed at "making ad labeling more consistent across search and shopping ads," with no committed launch date yet.
• Manufacturer Center's manual entry option removed (effective July 9, 2026), requiring sellers who previously updated product data by hand in the interface to switch to either the Manufacturer Center API or scheduled file uploads. Data submitted before that date remains in the account and required no migration action, but any seller still relying on manual entry needs a new submission method going forward.
• Product ID separation requirements for online versus in-store attributes, and greyed-out, non-clickable buy buttons for out-of-stock items, both rolled out earlier in 2026 as part of the same general push toward stricter, more automated feed data quality.

None of these directly relate to the September policy merge, but they paint a consistent picture: Google has been steadily tightening feed data automation and requirements throughout 2026, of which the policy consolidation is the most visible but least consequential single piece. It's a similar pattern to what we've covered in Google's real-time policy review changes and the Local Services Ads migration into Performance Max: individually small, but cumulatively a lot for an active seller to track across a single year.

What to Actually Do Before September

1. Bookmark the merged policy document once it publishes in September and do a single read-through specifically looking for labeled ads-only or free-listings-only rules, especially if you've only ever closely followed one of the two previous documents.
2. Pull your account's reporting from before and after August 24, 2026 to identify whether the YouTube affiliate reporting separation shifted any of your key metrics, before attributing any change to campaign performance itself.
3. Confirm your product data submission method if you were previously using Manufacturer Center's manual entry interface, since that option is already gone as of July 9, 2026.
4. Don't panic-audit your listings expecting new restrictions. Google's own language is unusually direct that no new restrictions are part of this specific update, so treat the September change as a documentation cleanup to read once, not a compliance deadline to scramble around.

Common Mistakes Sellers Make With Merchant Center Policy Updates

• Assuming a policy merge always means new restrictions. Google's language here is explicit that it does not, and treating every Help Center announcement as a compliance emergency wastes time better spent on actual feed and creative quality.
• Only reading the policy document for the program you actively pay for. Once ads-only and free-listings-only rules live in one merged document, skipping the sections that don't currently apply to you means missing context that becomes relevant the moment you expand into the other program.
• Confusing the August 24 reporting change with an actual performance drop. A metric that looks different after that date may simply be reported differently, not performing differently, and conflating the two leads to unnecessary campaign changes based on a false signal.
• Still trying to manually update product data through Manufacturer Center. That option has been gone since July 9, 2026; continuing to look for it wastes time that should go toward setting up the API or scheduled file upload instead.

Where Feed Creative Quality Actually Moves the Needle

None of these documentation and reporting changes affect the single biggest lever in Shopping and Performance Max performance: the quality and variety of your product images and video. A merged policy document and a cleaner reporting dashboard don't fix a feed with only one low-resolution product photo per SKU. The AI Image Generator in Miraflow AI supports text-to-image, image-to-image editing, and inpainting, useful for generating the square, portrait, and landscape product image variants a Performance Max asset group actually needs, while the cinematic AI video generator covers matching video formats for campaigns that pull from the same feed. Our prompt guide for AI-generated Amazon FBA product images and AI UGC ad prompts for product and lifestyle content both cover the same production gap for a Shopping feed specifically. If you're building out a full Shopping and Performance Max creative workflow, our guides on Performance Max's 2026 steering and reporting controls and Google's Gemini Omni inside Asset Studio cover the campaign and creative side of the same account this policy merge sits inside.

For more on how Google's broader 2026 Search and Shopping changes fit together, our explainers on Google's local inventory ads becoming the shopping default and the AI Max migration timeline cover two of the other major September 2026 Google Ads changes happening in the same window as this policy merge. Browse more marketing guides on the Miraflow AI blog.

Frequently Asked Questions

Does the September 2026 policy merge add any new restrictions to my listings? No. Google has stated directly that this update does not introduce substantive changes or more restrictive enforcement, and merchants should not expect additional restrictions as a direct result.

Do I need to do anything before September 2026? No required action, but a one-time read of the merged policy document once it publishes is worth doing, especially if you've only closely followed one of the two previous separate documents.

What happened to Merchant Center Next? As of July 2026, Google dropped the "Next" branding entirely; the platform is now simply called Google Merchant Center. No features or account settings changed as part of the rename.

Why did my Performance Max reporting numbers change around August 24, 2026? Google updated reporting definitions to align across Ads and YouTube on that date, specifically separating YouTube affiliate results from other performance data. Check your before-and-after numbers before assuming a real performance shift occurred.

Can I still manually update products in Manufacturer Center? No. Manual entry was removed effective July 9, 2026. Product data submitted before that date remains in the account, but ongoing updates require the Manufacturer Center API or scheduled file uploads.

Is the hide-sponsored-products toggle live yet? No. As of this writing it is a confirmed test, with Google's Ads Liaison describing it as work toward more consistent ad labeling across Search and Shopping, but with no committed launch date.

Conclusion

The September 2026 Shopping policy merge is exactly what Google says it is: a documentation cleanup, not a new set of rules, and it doesn't deserve a compliance scramble. But it's worth reading once it goes live, especially if you've only ever paid attention to one of the two policy documents being merged. The changes actually worth an active seller's attention this year sit around it: the August 24 reporting realignment that can shift your numbers without a real performance change behind it, and the ongoing consolidation of Merchant Center itself into a single, simpler platform. None of those change the fact that feed creative variety, not policy documentation, remains the biggest lever for Shopping and Performance Max performance heading into the rest of 2026.

References

1. Merchant Center announcements change log, Google Merchant Center Help
2. Google merges two Shopping policy sets but adds zero merchant restrictions, ppc.land
3. Google To Merge Google Shopping Ads & Free Listing Policies To One Policy, Search Engine Roundtable
4. Google Shopping's July Reshuffle: 3 Changes for Sellers, Digital Applied