How to request a Google Merchant Center re-review (and what actually gets products re-approved)

Not every disapproval needs a re-review. Data-quality issues (a missing GTIN, a price that does not match the product page, an image with a promotional overlay) clear on their own: fix the product, and Google re-crawls it within a few days, no request required. A re-review is for policy and account-level problems, where a human or an automated policy check has to look again. Asking for a re-review on a plain data issue just adds noise.

• Data issue: fix it in your store and wait for the next crawl. No request.
• Policy or account issue: fix the cause, then request a re-review.
• Account suspension: the account-level version of the same thing, with less room for error.

Google limits how often you can request a re-review, and repeated requests without real change can slow you down or count against you. Treat the first request as the one that matters. Go through every flagged product or policy, make the actual correction, and confirm it is live on the storefront, not just in the feed.

• Resolve every item Google flagged, not just the obvious one.
• Check the change is visible on the live product page, since Google re-crawls the page.
• Give the crawl time to pick up data fixes before you touch a policy request.

In Merchant Center, open the product or the account issue from the Diagnostics or Policy area. Item-level disapprovals show a path to fix and, where relevant, to request a review of that item. Account-level or policy suspensions show a single request button once you confirm you have addressed the problem. You submit once and then wait; there is no queue you can jump.

• Item-level: from the product issue detail.
• Account-level: from the account issues or the policy banner.
• Submit one clear request rather than several partial ones.

Keep it factual. Name the issues you were flagged for, state what you changed for each, and point to where it is now correct. Do not argue policy, do not promise anything, and do not pad it with reassurance. A reviewer wants to see that the specific problem is gone. Concrete beats persuasive.

• List each issue and the exact change you made.
• Reference the products or pages where the fix is now live.
• Avoid claims about future behaviour or guarantees of compliance.

Reviews typically take a few days, sometimes longer for account-level cases. Do not resubmit while one is pending, and do not make further large changes mid-review. If it comes back still disapproved, read the reason carefully: it is usually a different issue you missed, not a rejection of your fix. This is also where a monitor earns its keep, by keeping a record of what was wrong and what you changed, so the next request almost writes itself.