3 min read
In brief
- There is no published duration by suspension type. Anyone quoting 'three to five business days' for a specific category is guessing.
- What you control is the completeness and legibility of the evidence, and whether you resubmit while the account is unchanged.
- Resubmitting during an open review, or twice in the same state, is the most reliable way to make a review take longer.
The honest answer
Merchant Center reviews are queued work performed by people against policy categories whose investigation depth varies enormously. A missing policy page can be confirmed in minutes. A misrepresentation finding across a catalogue requires sampling product pages, comparing them with the feed, checking the business details and reading the account history.
That is why no duration table is trustworthy: the same label can mean a fifteen-minute check or a multi-day investigation, and the reviewer cannot know which until they have started. What can be described — accurately — is what shifts a case in either direction.
Not a timeline, a queue position
Treat a review as a queue with an unknown service time. You cannot shorten the service time, but you can avoid being sent to the back of the queue, and you can avoid being re-queued after a rejection.
What makes it slower
- Requesting review while the finding is unresolved — the reviewer checks, finds it, and the case is closed with a rejection. The clock restarts from your next request.
- Resubmitting a second request while one is open. Two open requests do not double your chances; they add noise.
- A store that changed materially during the review, so the evidence the reviewer is looking at no longer matches what you described.
- Account history with unresolved warnings or repeated review requests. This is read as a pattern and invites the longer investigation.
- Evidence that requires the reviewer to infer a fix — 'we improved our policies' rather than a link to the page that now exists.
What shifts it the other way
- 1
Fix everything, then request once
One request against a store where every finding is demonstrably resolved is the fastest path available, and it is the only one you control.
- 2
Make the fix visible without logging in
Policy pages in the footer, business details on the contact page, prices visible in the target currency. Reviewers look at what a customer sees.
- 3
Reduce scope
If ten items caused a catalogue-wide finding, removing those ten and re-syncing is a cleaner state than a hundred partial edits.
- 4
Keep the account quiet
No theme deploys, no feed experiments, no new accounts during a review. Every change during review is a variable you have introduced.
You cannot know how long a review will take, and anyone who tells you otherwise is guessing. You can know that you requested once, against a store where every finding is fixed and every fix is visible to someone who is not logged in — which is the only lever this process gives you.
