What does misrepresentation mean in Merchant Center?
Google’s Shopping policy addresses misleading or missing information that affects a purchase decision. Its examples include inaccurate business identity, false affiliations, unavailable offers, and concealed transaction conditions. The account notice and linked policy determine which issue you need to address.
A storefront can look polished while important facts remain unclear. Review what a customer would understand about the seller, the product, delivery, support, and returns before committing to purchase.
Identify the scope of the issue.
Check whether the problem affects an individual product, a group of products, or the merchant account. Record affected countries and destinations where shown. Fixing a product attribute does not demonstrate that an unrelated business-level concern has been addressed.
Create one issue register from the current account notices. If Google Ads also shows a restriction, track that status separately. Do not assume that a successful Merchant Center review automatically clears every other account task.
Audit the store as a customer would.
Use a sample of actual products, including different variants, prices, and delivery conditions. Follow each sample from its listing through the product page and checkout. Document where the information changes and whether that change is accurately disclosed.
| Review area | Questions to answer |
|---|---|
| Business identity | Who sells the goods, where does the business operate, and how can a customer contact it? |
| Product and availability | Does the selected variant match the listing? Can the business actually fulfill the order? |
| Price and checkout | Do the product price, currency, and required charges remain understandable through checkout? |
| Fulfillment | Where does the order ship from, and do handling and transit estimates describe the real process? |
| Returns and support | What is the return window, where do returns go, who pays, and how does the customer begin? |
Keep submitted product data aligned.
Compare the values actually submitted to Merchant Center with the live product page and checkout. Check the variant, availability, condition, price, currency, and identifiers relevant to the item. Verify that an integration has processed your correction rather than assuming that an edit in the store is already reflected in the feed.
Do not invent product identifiers or supplier records. Where an identifier is not assigned or an attribute has a specific exception, follow the product data specification. Keep the affected product IDs and a small set of dated examples so the correction can be checked.
Prepare before requesting a review.
Recheck the live store after corrections, including mobile checkout and the policy links that shoppers actually use. Maintain a change log with a URL, finding, action, and retest result for each issue. The narrative should describe what is now true rather than a list of future promises.
Google’s current review guidance places account issues under Products → Needs attention → View setup and policy issues. Use the available option that accurately describes whether you corrected a problem or disagree with it. Complete identity verification if requested before review is available.
If the review is unavailable or unsuccessful.
Google documents cooldown periods during which another review cannot be requested; unsuccessful reviews can extend the wait. Use the date and instructions displayed in your account rather than assuming a fixed interval for every merchant.
A denial is a reason to reassess the evidence and the current store. Look for unresolved findings, corrections that did not reach the product data, or contradictions between the appeal and the buying experience. Do not replace the store’s identity or fabricate transactions to create a different appearance.
Common questions.
Is adding policy pages enough?
The policies need to describe how the store actually operates, and the product and checkout experience must be consistent with them. A copied returns page does not fix inaccurate stock, unexpected charges, or an unclear seller identity.
Does every product need a GTIN?
Use the product data specification for the particular item and attribute. Do not invent identifiers or submit a value belonging to a different product. Identifier requirements and exceptions depend on the product.
Can I appeal a decision I believe is wrong?
Use the disagreement option when it is available for the issue and you can support that position. Provide the requested explanation or evidence and check any account prerequisites before submitting.
How long will a review take?
Google publishes review estimates in its help guidance, but timing can vary with the issue and complexity. Follow your account status and confirmation email. Treat an estimate as planning information, not an approval deadline.
Go to the source
Official policies & guidance.
Google’s requirements are linked below. The review steps on this page are RID Marketing’s practical guidance, not an exhaustive Google checklist. Sources checked September 24, 2026; follow any newer instructions in your account.
- Merchant Center: Misrepresentation policy (opens in a new tab)
- Merchant Center: request a review of your issues (opens in a new tab)
- Merchant Center: building trust with customers (opens in a new tab)
- Merchant Center checkout requirements (opens in a new tab)
- Merchant Center product data specification (opens in a new tab)
- Merchant Center business document verification (opens in a new tab)
- Merchant Center warnings, suspensions, and cooldowns (opens in a new tab)