Merchant Center · Practical guide
Merchant Center misrepresentation review rejected: what to check next
Before another review request, check what changed, what is live and what the evidence still cannot establish.
If Google rejected your misrepresentation review after you made changes, check the published website against your Merchant Center settings and product data before submitting again. A failed review does not tell you which problem remains.
Before you submit again
- Save the result: the exact notice, affected market and previous review date.
- Check your review options: distinguish a rejection, a pending review, a cooldown and a notice saying no further reviews are available.
- Compare the same facts: seller identity, return terms, delivery charges, prices and availability across the website and account.
- Verify the corrections: repeat the checks on the live site and updated account information. Record anything still unresolved.
The sections below explain how to do this, with a real recovery case and a worked example you can adapt.
Check what Merchant Center actually says
Open the issue details and record the wording, affected country, review result and any next-review date. Save the changes made before the rejected review and any other action requested in the account.
Review not approved
- What to do next
- Reassess the changes and identify what has not been checked.
Under review
- What to do next
- Check the existing request's status; it is not a fresh rejection.
Cooldown or a future review date
- What to do next
- Record that date and use the interval to complete the investigation.
Verification or another required action
- What to do next
- Follow the instructions shown in the account.
No further reviews available
- What to do next
- Save the exact notice and support response. Do not assume waiting will restore the review option.
Google explains that cooldowns disable the review button and that actions such as identity verification can affect review availability. Follow the instructions for your account. Google's review guidance.
Also distinguish an account suspension from a product disapproval. One item's price error should not automatically be treated as the explanation for an account-level Misrepresentation issue.
Compare the website with the account and feed
Adding a returns page is only part of the job. Its terms must agree with the product promise, Merchant Center settings and the service the business actually provides.
Likewise, uploading a feed does not prove that Merchant Center has processed the new values. Check the current product record as well as the source file.
Use these illustrative checks to organise your investigation. They are not confirmed causes of your suspension.
Seller identity
- Compare
- About, Contact and policy pages against Merchant Center business information
- What to investigate
- Outdated or conflicting seller details; addresses used for different purposes
- Who needs to act
- Business owner confirms the real seller and address purposes; website and account owners correct inaccuracies
- How to verify
- Reopen each published location and compare it with current account details
Returns and delivery
- Compare
- Product promises and written policies against the applicable account settings
- What to investigate
- Different charges, eligibility, delivery conditions or return windows
- Who needs to act
- Retailer confirms the real terms; website and account owners update them
- How to verify
- Compare the same destination and order conditions, including exceptions
Price and availability
- Compare
- Exact product variant and currency against the matching feed item and Merchant Center record
- What to investigate
- Stale values or a comparison using different variants or markets
- Who needs to act
- Feed owner and developer correct the source of the difference
- How to verify
- Recheck the same item after processing; extend checks if a pattern appears
Checkout
- Compare
- Product offer against cart totals, delivery charges and the checkout summary
- What to investigate
- Costs or conditions that change unexpectedly along the journey
- Who needs to act
- Retailer confirms the terms; developer corrects the presentation or calculation
- How to verify
- Test the relevant basket and destination up to payment, without placing an order
Product claims
- Compare
- Product pages, banners and images against submitted titles and descriptions
- What to investigate
- Unsupported claims or different versions of the same offer
- Who needs to act
- Retailer supplies support for the claim or revises it wherever reused
- How to verify
- Recheck the live wording, images and submitted product information
These comparisons follow Google's emphasis on accurate business information, clear policies and consistent product data. Google's building-trust guidance.
Do not alter truthful business details merely to make every field identical. Establish what each address or entity represents and correct the inaccurate presentation. Record the products, variants and markets checked: a small sample cannot establish that the whole catalogue is correct.
A real case: conflicting return terms before a successful review
An anonymised Semstar audit found that a product page promised a full refund and free returns or collection, while the written policy limited the offer by geography and eligibility.
The site's structured return information also linked to a broken policy URL and included a fee that was unclear against the visible terms. Warranty and insurance wording needed clarification and accessible full terms.
The first audit covered the public website. A later re-audit included live Merchant Center settings and representative product records. It recorded aligned return terms, linked warranty terms and consistent sampled product information.
The recommendation to request review remained subject to confirming the evidence behind promotional claims. Google subsequently confirmed removal of the Misrepresentation issue from the same account.
This supports the outcome, without establishing Google's precise reason or approval of every product.
Record the fix and how you checked it
“Shipping fixed” is difficult for someone else to verify. A useful change log records the original problem, the correction, who owns it and the checks completed.
Here is one illustrative example, not a finding about a client:
Example: a free-delivery threshold
- Problem
- The homepage promised free delivery, but checkout charged below a minimum order value.
- Correction
- State the genuine threshold wherever the offer appears and align the relevant delivery settings.
- Owner
- Retailer confirms the terms; developer updates the website; account manager updates the settings.
- Check
- Test baskets below and above the threshold for the affected destination. Save dated observations and settings screenshots.
- Still open
- Another delivery market has not been tested. Record the completion date when that check is finished.
This is a practical handoff format, not a Google-required document. Do not mark the whole account ready because one correction is complete.
Gather what a website scan cannot show
A public website scan cannot inspect private Merchant Center settings, the full submitted feed or the review history. For a diagnostic, gather:
- The current suspension notice and review result.
- Current business, shipping and returns settings screenshots.
- A recent product-feed export and representative product URLs, including the relevant variants.
- Review dates and a record of previous changes.
Date the files. An old screenshot cannot verify a recent correction. Share account evidence privately and remove customer information or documents the reviewer does not need.
An agency can supply these materials without granting account access. Anything the specialist cannot establish from them should remain marked as unverified.
Decide whether another review is appropriate
Separate the findings into three groups:
- Checked and corrected: the change is live and the comparison has been repeated.
- Still unresolved: a discrepancy remains or the work is incomplete.
- Not verified: the necessary screenshots, records or other supporting information are missing.
Confirm that the checks address the issue and market in the notice. Assign the remaining work and check the available review route before submitting again.
If you disagree with the decision, explain why with supporting information. If you have corrected the issue, use the appropriate fixed-issue route shown in Merchant Center. Google recommends a thorough audit before requesting review. Google's review guidance.
Questions after a rejected review
How long should I wait before requesting another review?
Google says a one-week cooldown may begin if the issue remains unresolved after a second review attempt. Later unsuccessful reviews may lead to longer cooldowns, and support cannot shorten them. Check the date shown in your account and use the time to verify the corrections; the end of a cooldown does not establish that your store is ready. Google's review guidance.
Do three rejected reviews mean a permanent ban?
Google's public guidance does not state a universal allowance of three reviews or an automatic ban after the third rejection. It also does not promise unlimited attempts. The option to disagree with an issue may itself be limited.
Treat an explicit notice of no further reviews seriously. That is different from a temporary cooldown. Check any options listed in the notice and the support correspondence; do not assume support can reopen the internal review route. Google's review guidance.
Why did the review fail after I fixed everything?
Check what “everything” covered. Were the account settings and processed product data checked, or only the website? Were all relevant variants and markets included?
Google can consider listings, websites, accounts and third-party information. Your checks can identify gaps, but cannot reveal Google's internal assessment. Google's Misrepresentation policy.
Will correcting the findings guarantee approval?
No. A diagnostic can identify inconsistencies and help you verify changes; Google makes the review decision.
Get help with the next investigation
For agencies: get a white-label diagnostic using the website and supplied account/feed information. Your agency receives an agency-branded report, keeps the client relationship, implements changes and submits review requests. Follow-up is limited to the agreed scope.
Discuss your client's suspension
For retailers: discuss whether Semstar's recovery support is suitable for your store. Scope and pricing are agreed before paid work begins. An enquiry starts a personal conversation, not an automatic order or invoice.
Request a suspension assessment
Want to see the report structure? Get the free redacted audit example after entering your email. It illustrates broader recovery work; the agency diagnostic covers findings and a focused check, with implementation handled by your agency.