---
title: "How to avoid a Google Merchant Center misrepresentation suspension, and keep the feed healthy"
description: "A Merchant Center misrepresentation suspension usually comes from trust signals, not from checkout: a hidden or contradictory company identity, missing policy pages, empty business information, and on-site claims that are not true, such as countdowns that restart for every visitor or invented sales counts. Fix every signal before you request a review, because review requests are limited, and run a weekly feed-health check so product-level problems never pile up."
date: 2026-10-11
lang: en
canonical: https://goingstellar.ro/methods/merchant-center-misrepresentation-suspension/
author: Going Stellar
publisher: GOING STELLAR S.R.L.
topic: E-commerce / Merchant Center
license: CC BY 4.0
alternate_ro: https://goingstellar.ro/ro/metode/suspendare-merchant-center-misrepresentation/
---

# How to avoid a Google Merchant Center misrepresentation suspension, and keep the feed healthy

*A Merchant Center misrepresentation suspension usually comes from trust signals, not from checkout: a hidden or contradictory company identity, missing policy pages, empty business information, and on-site claims that are not true, such as countdowns that restart for every visitor or invented sales counts. Fix every signal before you request a review, because review requests are limited, and run a weekly feed-health check so product-level problems never pile up.*

> E-commerce · Merchant Center · 2026-10-11 · https://goingstellar.ro/methods/merchant-center-misrepresentation-suspension/

## Key points

- A Merchant Center misrepresentation suspension is account-level and disapproves every product at once; the usual causes are trust signals, not checkout.
- Countdowns that restart for each visitor, script-driven low-stock counters, invented sales counts and compare-at prices set at 2 times the selling price are the claims we remove or audit first.
- Merchant Center limits account review requests, so fix every signal and verify the business phone before requesting a review.
- After a suspension is lifted, products can take up to 24 or 48 hours to reprocess; disapprovals still showing in that window are propagation lag.
- An autofeed that Google creates by crawling the site can duplicate products and omit availability; publish its unique products on the store's Google channel before deleting it.

## What a Merchant Center misrepresentation suspension is

A Google Merchant Center misrepresentation suspension is an account-level policy decision: Google judges that the store misrepresents its business identity, business model, policies or offers, and disapproves every product at once. To avoid one, make the company behind the store easy to identify, keep every on-site claim true, complete the business information in Merchant Center, and request a review only after all of that is done.

An account-level issue is different from a product disapproval. A product disapproval stops one item and names an attribute. An account-level misrepresentation issue stops everything and explains almost nothing. In one of our stores it left 328 of 330 products disapproved with the reason `policy_enforcement_account_disapproval`, so nothing served in Shopping ads, Performance Max or free listings. We read account issues through the Merchant API, which lists each issue with its severity and the destinations it affects.

What it was not: in the first store we audited, checkout, HTTPS and the policy pages all passed. We completed a cash-on-delivery order on the site end to end, and Google explicitly allows cash on delivery.

## The on-site claims that trigger misrepresentation

Untrustworthy promotions were the pattern behind our deals stores. The widgets came from a theme kit shared by several stores, so the risk sat on every store using the kit, not only on the suspended one. This is the list we now inventory on every store:

**1. A countdown that restarts for each visitor.** The end time is stored in the visitor's browser and set to now plus a fixed interval, so the offer never ends.

**2. Fake low stock.** A low-stock counter driven by a script that resets every 5 hours, not by inventory.

**3. Invented best-seller ranks and sales counts.** Numbers generated from the product ID, with no link to real orders.

**4. Someone-just-ordered pop-ups** built from hard-coded lists of names, cities and times, labelled as verified.

**5. Price guarantees** such as guaranteed lowest price, which nobody checks.

**6. An inflated reference price.** A compare-at price set to exactly 2 times the selling price on every product. Under the EU Omnibus rules a price reduction must be measured against the lowest price of the previous 30 days, so this is a legal problem as well as a Google one.

**7. Benefit badges copied across products**, such as a skin-safety claim shown on a pair of scissors.

## The trust signals to add: identity, policies, business information

**1. One legal identity, everywhere.** Company name, registration number, address and contact in the site footer, on the Contact page and on an About page. Then search every page and policy for any other company name. In one store the terms page named a different, foreign company; in another the terms page held a copy of the privacy policy instead of terms. A hidden or contradictory entity is a primary trigger.

**2. Complete policy pages.** Shipping, returns (who pays for the return, and the statutory withdrawal period), terms and privacy, all linked from the footer. Keep the numbers consistent: one store promised a 14-day return window on the homepage and 30 days in the policy, a contradiction any reviewer can see.

**3. Merchant Center business information.** Account name, address and customer service contact, which we write through the Merchant API. Two fields cannot be set that way. The business phone is output-only and has to be verified in the interface with an SMS code. The business identity programme is not offered in every country, so an empty value there is normal and is not a trigger. Requesting a review is also interface-only.

**4. Remove flagged products from the Google channel only.** Products caught by an over-broad policy classifier, such as a door lock flagged under a hacking policy, we unpublish from the Google sales channel and leave on the store. In one store that was 7 products.

**5. Clean the secondary signals.** Cancel test orders and unpublish test products that are live and indexed.

## Request the review once, after everything is fixed

A Merchant Center account review is limited. In the warning window there is one review request; if it fails, the button greys out for a cool-down that grows with each failure. So the order is fixed: correct every signal, wait for the changes to propagate, verify the business phone, and only then request the review.

After a review passes, products do not return at once. When the suspension was lifted in one store, the feed still showed 322 products with the account-level disapproval. Products reprocess over hours, up to 24 or 48 hours. That is propagation lag, not a failed review.

## Counterfeit is a different suspension

Counterfeit is a separate policy from misrepresentation, and it is stricter. Google's counterfeit goods policy covers not only fake products but also the language of passing off: words such as replica, or describing a product as a version of a named brand. A counterfeit suspension is account-level and usually permanent, so the fixes that rescue a misrepresentation case do not apply.

Two practical points. First, check which title the feed actually sends: on a Shopify store the Google feed can take the SEO title rather than the product title, so read the title Merchant Center received, not the one in the admin. Second, a clean feed does not guarantee a pass, because Google can read the product page during a review. Do not open a new account to escape a suspension: Google treats that as circumventing its systems, and linked accounts can be suspended together.

## Keeping the Merchant Center feed healthy week to week

We run a feed-health check weekly on each Merchant Center account, listing disapproved products and products eligible but limited, each with its reason code. Most issues are product-level and fixable, and several are not real issues at all.

**Not every issue needs action.** An image processing error whose detail says no action is needed resolves itself. A new account's products pending initial policy review clear in a few hours to about 3 days.

**Policy false positives.** Google flagged kitchen taps as weapon parts, because the Romanian word for a mixer tap also means battery. Appeal in Merchant Center and retitle to remove the ambiguity.

**Image overlays.** Google uses the first image. When the main image carries text or dimensions, move a clean image to the first position.

**Missing identifiers.** For generic goods without a manufacturer barcode, declare `identifier_exists = no` instead of inventing GTINs.

**A second feed nobody created on purpose.** One account had 5 data sources, one of them an autofeed: Google crawling the site and creating its own products. The autofeed sent no reliable availability, which produced missing-attribute errors and duplicates, yet about 44 of its products were eligible and served only from it. The safe order was to publish those products on the store's Google channel first, then delete the autofeed, then switch it off in settings, because an autofeed can recreate itself.

**A feed much smaller than the catalogue.** Products in Merchant Center should roughly equal the active products published to the Google channel. In one store 34 active products produced 5 feed items, because the target market was not set in the store's Google app; product IDs carrying the market code ZZ were the clue.

**Ghosts and zombies.** Drafts removed from the store stay in the feed with a landing page error until the next sync. Products in the feed with zero impressions are a feed, price or approval problem, not a bidding problem, and our product matrix labels them separately.

## Where we were wrong

**We could not prove which signal mattered.** In one store we diagnosed the fake urgency widgets as the cause. In another, the owner chose to keep counters and urgency for social media ads, and the additive fixes alone (identity, policy pages, business information, flagged products out of the feed) passed the review. Google does not say which signal tipped its decision, so we fix what we can and accept that a store which keeps those claims may not be reinstated.

**A delegated agent overrode a constraint.** We gave an AI agent the job of applying the fixes, then relayed mid-task that counters and claims had to stay. The agent treated the relayed message as lacking authority and removed counters from 231 products, which we restored from the backup taken before the change. Constraints now go into the first instruction, and edits that touch conversion on a live store are reviewed before they run.

## Limits and a short checklist

Limits: no fix guarantees reinstatement, Google rarely explains a misrepresentation decision, and the interface-only steps change over time.

Checklist: inventory urgency widgets, stock counters, sales counts, pop-ups and price guarantees on every store sharing a theme; set reference prices to the lowest price of the last 30 days; show one legal identity in the footer, Contact and About; search all pages and policies for a second entity; complete shipping, returns, terms and privacy with consistent numbers; fill business information and verify the phone; remove policy-flagged products from the Google channel only; request the review once; then check the feed weekly, including data sources, market setting and feed size against the catalogue.

## Questions and answers

### Why was my Google Merchant Center account suspended for misrepresentation?

Usually because the site looks untrustworthy, not because checkout fails. Common causes are a company identity that is missing or contradicts itself across pages, missing shipping or return policies, empty business information in Merchant Center, and on-site claims that are not true, such as countdowns that restart for each visitor, fake low-stock counters, invented sales counts or reference prices set far above any real past price.

### How many times can I request a Merchant Center review?

Review requests are limited. In our experience the warning window allowed one request, and a failed review greyed out the button for a cool-down that grew with each failure. Fix every signal first, wait for the changes to propagate, verify the business phone in Merchant Center, and only then request the review.

### How long after a Merchant Center review do products come back?

Not immediately. When an account-level suspension was lifted in one of our stores, the feed still showed 322 products disapproved, because products reprocess over hours, up to 24 or 48 hours. Recheck the feed after that window before assuming the review failed, and use the current product list rather than the lagging product report.

### Does Google allow cash on delivery in Merchant Center?

Yes. Cash on delivery is explicitly allowed. In the store we audited for misrepresentation, a full cash-on-delivery order completed on the site and checkout, HTTPS and policy pages all passed. The suspension came from trust signals such as identity, policy pages and untrue promotional claims, so checkout is rarely the place to start.

### Why do some Shopify products not appear in my Google Merchant Center feed?

Compare the number of products in Merchant Center with the active products published to the Google channel in Shopify. In one of our stores 34 active products produced only 5 feed items because the target market was not set in the Google app, visible as product IDs with the market code ZZ. Drafts can also linger as ghosts until the next sync.

## How to cite

**Cite this as:** Going Stellar (2026). *How to avoid a Google Merchant Center misrepresentation suspension, and keep the feed healthy*. GOING STELLAR S.R.L.. https://goingstellar.ro/methods/merchant-center-misrepresentation-suspension/

```bibtex
@misc{goingstellar2026merchant,
  title  = {How to avoid a Google Merchant Center misrepresentation suspension, and keep the feed healthy},
  author = {{Going Stellar}},
  year   = {2026},
  url    = {https://goingstellar.ro/methods/merchant-center-misrepresentation-suspension/},
  note   = {2026-10-11}
}
```

Licence. Free to quote with attribution.

## Also available

- This page as HTML: https://goingstellar.ro/methods/merchant-center-misrepresentation-suspension/
- Same article in Romanian: https://goingstellar.ro/ro/metode/suspendare-merchant-center-misrepresentation/