Useful Patch: audit first, safe fixes first, no approval guarantees.
Account Level Enforcement

Merchant Center Account Level Enforcement: What It Is, Why It Happens, and How to Appeal

Account level enforcement restricts your entire Merchant Center account based on policy violations, not individual products. It is different from a product disapproval and different from a full account suspension. Understanding which one you have changes what needs to be fixed before you appeal.

Google decides reinstatements. The audit identifies the specific trigger and helps you build the right evidence before appealing.

Signs you have ALE rather than product disapprovals

ALE vs product disapprovals vs account suspension: what is the difference

Merchant Center applies restrictions at three levels. Knowing which one applies determines what needs to be fixed and what evidence Google wants when you appeal.

Issue type Scope Where it appears in Merchant Center Typical fix path
Product disapproval Individual products or groups of products Diagnostics tab, item-level issues section Fix the specific attribute, price, or policy issue on the affected products, then request review
Account level enforcement (ALE) Entire account, all products restricted from Shopping or other surfaces Account status section; may appear alongside product-level issues Fix the website-level or policy-level issue causing the flag, document the changes, then submit an account-level appeal
Account suspension Full account; all access to Shopping Ads and free listings removed Account status shows suspended; separate suspension notification sent by email Identify the suspension reason (often misrepresentation, policy repeat violations, or circumvention); remediate fully; submit a formal reinstatement request with evidence

The most common mistake is treating an ALE as a product disapproval and fixing individual products without addressing the account-level policy issue. This usually results in a failed review request because Google is looking for evidence that the website-level problem has been resolved, not just that specific products were edited.

The four most common triggers for account level enforcement

ALE typically follows one of these patterns. Identifying which trigger applies to your account is the most important first step.

1. Website experience policy violations

Google's crawler checks for a clear, trustworthy purchase experience. ALE is triggered when the crawler finds issues across the whole website rather than on specific products. Common triggers: no visible returns or refund policy, no accessible contact information, checkout flows that do not complete cleanly, or login walls that block the purchase path from outside the store.

What Google wants: evidence that the website now meets the shopping experience requirements, ideally with screenshots of the policy pages, contact page, and a completed checkout test.

2. Misrepresentation pattern across products

When price, availability, or product details mismatches appear across many products rather than a few, Google may escalate from individual product flags to an account-level restriction. The trigger is usually a systemic feed issue (stale prices, wrong currency, feed not updating) rather than a deliberately misleading store.

What Google wants: evidence that the feed is now accurate and updating correctly, with before and after screenshots showing the specific mismatches have been resolved.

3. Repeated policy violations after warnings

If an account has received individual product disapprovals or policy warnings and the same violations continue to appear after review, Google may apply account-level enforcement to prevent the account from continuing to serve non-compliant products. This is an escalation from item-level warnings.

What Google wants: a clear audit trail showing what was wrong, what was fixed, and why the same violations will not reappear. Process evidence carries more weight than just the fixed products.

4. Business identity or verification issues

Some ALE restrictions are triggered by inconsistencies in business identity information: the trading name on the store does not match the Merchant Center account, the business address is inconsistent, or the store appears to be operating as a different entity from what is registered in the account. This is separate from the misrepresentation policy but often appears alongside it.

What Google wants: consistent, verifiable business identity information across the store, the Merchant Center account, and any verification documents requested.

Evidence checklist for an account level enforcement appeal

Appeals for ALE require different evidence from product-level disapprovals. The following checklist covers the standard evidence set that a well-prepared appeal should include.

Website compliance evidence

  • Screenshot of the returns and refund policy page, including the URL
  • Screenshot of the contact page with phone, email, or contact form visible
  • Screenshot of the privacy policy page
  • Completed checkout test showing the full purchase flow works without login
  • Screenshot of the shipping policy or shipping information page

Feed and price accuracy evidence

  • Screenshot showing current feed last-fetched date and time
  • Before and after screenshots of specific products where prices were mismatched
  • Confirmation that automatic item updates are correctly configured or disabled
  • Feed diagnostics showing zero or minimal active warnings after fixes

If the trigger was a repeat violation

  • List of the specific products or attributes that were flagged previously
  • What was changed on each, with screenshots
  • Process description: what changed in the feed or product management to prevent recurrence
  • Confirmation that the feed update schedule is reliable going forward

Business identity evidence (if requested)

  • Consistent trading name across the store, the Merchant Center account, and any Google Ads account
  • Business address consistent with the country setting in Merchant Center
  • If Google requested identity verification: government-issued business registration document
Get the 199 GBP audit

What the Useful Patch audit does for ALE cases

The audit maps which trigger is most likely based on the evidence visible in the account, then gives you a ranked list of what to fix and what to document before submitting an appeal. For ALE cases, the audit specifically checks:

Website experience check

Review of the store's trust pages, contact information, returns policy visibility, and checkout path from the perspective of Google's crawler requirements.

Feed accuracy review

Check whether a systemic feed problem (stale prices, wrong attributes, update failure) is the root cause, and what needs to change in the feed configuration to fix it.

Appeal readiness assessment

Honest assessment of whether the account is ready to appeal, what evidence is still missing, and what the most likely objection will be in the next review. No guarantees on outcome.

Frequently asked questions

How do I know if I have ALE rather than a product disapproval?

Product disapprovals appear in the Diagnostics section and list specific items or attributes. Account level enforcement appears in the Account status section and typically says something about "account-level" issues or restricts all products from serving. If your campaigns show "limited" across all products but no individual product errors explain the scale of the drop, ALE is a likely cause.

Can I appeal ALE the same way I appeal a product disapproval?

No. Product disapproval appeals request a re-review of specific items after fixing the attribute or content issue. ALE appeals require demonstrating that the account-level policy issue has been resolved, usually with website compliance evidence and a description of what changed. Submitting a product-level fix for an account-level restriction typically fails without addressing the root cause.

Does ALE mean my account is suspended?

Not necessarily. ALE can apply to Shopping Ads surfaces while leaving other surfaces active, or it can restrict products broadly without a formal suspension notification. A full account suspension usually comes with a specific email notification and a different status message. If you are unsure, the audit can help identify which you have based on what is visible in your account.

I fixed the issues but my appeal was rejected. What now?

Rejected appeals for ALE usually mean either the fix was incomplete, the evidence submitted did not clearly demonstrate the fix, or there is an underlying issue that was not identified. The audit is useful at this point to take a second look at what might still be triggering the restriction and what evidence the next appeal needs to include.

Will the audit guarantee my account is reinstated?

No. Google decides reinstatements. The audit identifies the most likely cause and gives you the strongest fix path and evidence set based on what is visible. Whether a specific appeal succeeds depends on what you submit and Google's current enforcement stance on your account category.

Useful Patch does not fabricate compliance evidence, invent business identity documents, or guarantee Google approvals. The audit is a structured diagnostic. Google decides reinstatements.

Related help pages

Account Suspension Help

For full account suspensions with a formal suspension notification and email from Google.

Misrepresentation Flags

The misrepresentation policy is one of the most common account-level triggers. Specific misrepresentation audit.

Main Merchant Center Audit

The main audit service covering all issue types including ALE, product disapprovals, and feed errors.