Open the Merchant Center Help Center in September and the policy pages look different. The two old documents are gone, replaced by a single set of Shopping policies. For merchants in restricted categories, the phrase policy consolidation usually triggers one worry first. Are the rules tightening? The official answer is unusually direct.

The announcement published on July 15 states that the Help Center update completes in September, that it is intended to simplify and clarify these policies for merchants, and that it does not introduce substantive changes to or more restrictive enforcement of the policies. Merchants should expect no additional restrictions on their product listings as a direct result of the update (official announcement, July 15, 2026). For almost every merchant, this is a documentation move. The work it asks for is cross-checking, not rewriting.

What merged

Until September, the Merchant Center Help Center ran two policy documents in parallel. One governed Shopping ads; the other governed free listings. They overlapped heavily but were not identical, so merchants running both programs had to flip between them and could easily miss a difference.

After the merge, the two documents become one set of Shopping policies. Several things stay put. In the current version of the Help Center, the policies are still organised under four areas, prohibited content, prohibited practices, restricted content and site requirements. Some policies still apply only to Shopping ads, and Google says it will clearly indicate when that is the case.

What changes is how you read, not what the rules say. Merchants who previously needed only one document will now meet clauses from the other track inside the same document, and the labels exist for exactly that situation.

Documentation changes and enforcement changes are two different things

This section is worth reading twice. A documentation move belongs to information structure. Enforcement belongs to execution. They are separate matters. The announcement says the update does not introduce substantive changes or more restrictive enforcement. The Help Center also describes enforcement actions clearly, which include disapproving individual products, temporarily capping impressions for some flagged accounts, and suspending accounts for repeat or severe violations. None of these changed with the merge (per the current version of the Help Center).

Third-party reads point the same way. Analyses describe the update as a documentation cleanup with no new rules (see iComChain in August and Miraflow in September, for reference). One of their observations is practically useful. A merchant who has only ever run free listings has never had a reason to read the ads policy document, and will now meet ads-only clauses inside the same document for the first time; check the label before assuming they apply to you (third-party reading, for reference).

Two overreactions are common. Pulling a batch of products the moment the notice lands, or pushing back a holiday launch plan, both misread a structural change as a tightening of the rules. The official wording states there are no additional restrictions, so plan to that wording.

A cross-check checklist for restricted categories

The list below uses adult products as the example; other restricted categories follow the same logic. Check clause details against the current version of the Help Center, not old screenshots or secondhand summaries.

First, locate the entry for your category. For adult content, the current Help Center lists adult merchandise such as sex toys, sexually suggestive content, and images containing exposed skin and nudity as restricted content, with limits that include not serving on Search and not serving to minors (the adult-oriented content page in the Help Center). That page currently says it applies to Shopping ads and local inventory ads; which clauses extend to the free listings side after the merge will be marked in the new document.

Second, check feed attributes and account settings. Adult products need the adult [adult] attribute per the product data specification, or account-level settings that direct them to an appropriate audience; both are the official paths. Then go market by market. The Help Center lists country-specific requirements, and a range of markets does not allow promotion of this content at all, while others such as Germany attach specific conditions.

Third, walk through your landing pages. If the page behind an ad or listing contains violating content, the fix is updating the site to meet the requirements, not only editing feed data.

Fourth, keep disapproval records and appeal materials. Disapprovals and appeals are regulars in restricted verticals, so log each round. Which warning email arrived, which products were involved, what you changed, when you appealed, and what you submitted with the appeal. The Help Center notes that most violations come with a warning email and a fix window of 7 or 28 days; appeals can run through individual review or a standard appeal; and bulk appeals come with conditions, since violating products must be removed from your data source first or the whole batch can fail outright and limit later appeal chances. Account-level reviews typically take 7 business days, longer for complex cases. Keep the records close; they save repeat trial and error.

Fifth, turn policy monitoring into a routine. Follow the Merchant Center announcements changelog and cross-check your category's clauses once a quarter. After the merge, the document structure and layout will differ, so memory or a year-old screenshot will fail you sooner or later.

The timeline before October

For the rest of September, three moves are enough. Read the merged document once when it is live, focusing on the labeled clauses. Update bookmarks, runbooks and compliance checklists that point at two documents to point at one. And for restricted categories, run the five-step cross-check above.

From October, fold the changelog review and the quarterly cross-check into routine monitoring, and stop there. Feed data needs no change from this merge, and launch schedules need no adjustment. Spending effort in the wrong place costs more than the policy itself.

What not to do

Do not treat it as a compliance notice and pull products or delay launches. The official wording says the update brings no additional restrictions.

Do not read only half. If you have only run ads, set aside time for the free listings clauses; if you have only run free listings, confirm the label before changing your settings for an ads-only clause.

Do not blur documentation change into enforcement change. The official side has issued no new statement about enforcement intensity, so work to the existing wording.

Do not mass-appeal the moment something is flagged. The Help Center warns that violating products must be cleared before a bulk appeal, and a badly prepared batch can fail outright and affect later chances.