Merchant Center Request Review Is Unavailable: What to Check

A greyed-out Request review button does not identify the cause. Check the issue details, outstanding tasks, and review history before changing the account. The correct next action depends on the state shown in Merchant Center.

Google's review guidance describes prerequisites such as requested identity verification and a non-empty product data source. It also describes cooldowns that disable the button. Completing one prerequisite does not prove all the others are complete.

Identify what blocks the review

Use this decision table as our suggested triage method. A screenshot of the disabled button is useful, but the surrounding issue text matters more.

Evidence in the account	Next action
A review is already pending.	Keep its receipt and monitor that review's status.
An identity task remains open.	Complete the requested task through the official flow.
The product data source is empty.	Check why products are missing and restore accurate product data.
A cooldown expiry appears.	Record the expiry and use the interval to complete the audit.
The notice says appeals are exhausted.	Save the exact restriction and check the remaining options shown.
No reason appears.	Gather the issue details and contact support for clarification.

Check the correct account and issue

An agency or store platform can expose several account identifiers. Confirm which Merchant Center account received the restriction. Record the product ID if the problem affects an item. Also record the country and marketing method named in the issue.

Google's issue guidance separates product problems from account problems. A product correction and an account suspension therefore need separate status checks. Our Merchant Center suspension guide explains that distinction.

Build a short chronology before asking for help. Include the original issue, website changes, review dates, and decision emails. Keep the original language of each decision. Replacing several different messages with “still suspended” hides useful information.

Complete real prerequisites

For an identity task, compare its current state with the submission receipt. Uploading a file is not the same as receiving a completed status. For missing product data, inspect the latest source processing result and the store platform connection.

Google's review instructions say an empty source needs at least one product before review eligibility can be prompted. Add a genuine, accurate product through the supported process. Do not create a dummy item solely to activate a button.

Use the remaining time to inspect the actual customer journey. Compare an advertised item with its page, checkout, delivery terms, and returns information. Our misrepresentation checklist provides a structured website review.

Assign each finding an owner and completion date. Record whether the fix is published, still being developed, or awaiting confirmation from another system. That distinction helps you decide when another review is justified.

Fictional worked example: verification complete, button still disabled

This invented example concerns Cedar Pantry, an online kitchenware shop. The owner completes an identity task but cannot request another account review. They initially assume verification failed.

Check	Finding	Evidence or action
Identity task	The account shows completed.	Save the status and completion email.
Product source	Current products appear with recent processing.	Record the source name and processing timestamp.
Issue details	A cooldown expiry follows an unsuccessful review.	Save the exact notice and expiry.
Website audit	The delivery page contradicts the checkout estimate.	Correct the estimate and capture both pages.

The owner does not repeat identity verification. They check a second product and confirm the revised delivery statement matches the checkout. The evidence folder now contains the cooldown notice, task status, and correction record. Their next action is to check review availability after the stated expiry. No review result is assumed.

Handle cooldowns and exhausted appeals carefully

Google says support cannot shorten or bypass a cooldown. The account's notice determines when to check again. Do not treat a temporary cooldown as proof that all future review options have ended.

An explicit exhausted-appeals notice needs a different response. Preserve it and read any support or redress options it supplies. Ask a specific question about that restriction if clarification remains available. There is no basis for promising a hidden escalation route or a universal number of reviews.

Our Merchant Center recovery service starts by assessing the issue and available process. Include any finality or cooldown wording in your diagnosis request so the scope can be assessed accurately.