GuideUpdated 2026-07-06

Google Merchant Center pending review: what it means and how long it takes

What "pending review" means in Google Merchant Center, normal review times, what actually speeds it up, and when a stuck pending state is a real problem.

Plain-English summary

Pending means Google is still deciding: the product isn't serving yet, but nothing is wrong. Most items clear within 3 business days; new accounts can take longer because the whole account is in a review queue. There is nothing you can click to speed it up, but there is plenty you can do to avoid resetting the clock, and a clear line for when pending has become a problem worth acting on.

What pending review actually means

When a product shows pending (or "under review") in Merchant Center, Google has received it but hasn't decided whether it can serve. It isn't approved, it isn't disapproved; it's in a queue. No reason string exists because there's no decision to explain yet.

This trips merchants up because pending looks like a problem: the item isn't showing on Google, and Diagnostics lists it alongside genuine errors. But pending is the normal state for every product at three predictable moments:

  • First submission: every new item is reviewed before it serves.
  • After a significant edit: changing price, title, image or landing page URL can send an approved item back through review.
  • After a fix: a disapproved item you've corrected re-enters the queue before it comes back as approved.

If you want the full map of the states between approved and disapproved, the disapproval taxonomy covers pending alongside preemptive disapproval and serving-with-warnings.

Normal review times

Situation Typical time to clear
New item, established account 24–72 hours
Edited item re-entering review A few hours to 3 days
Fixed item after disapproval 1–3 days (data), up to 7 days (policy re-review)
First feed on a brand-new account 3–7 business days
Policy-sensitive categories (health, adult, restricted) Up to 7+ business days

Two things worth internalising from that table. First, 72 hours is the working baseline: don't start troubleshooting an established account before then. Second, new accounts are slower for a structural reason: the review isn't just per-product, it's per-account, and the account queue runs first.

What actually speeds it up: nothing you can click

There is no expedite button. Resubmitting the feed doesn't help; support can't jump the queue; upgrading your spend doesn't change it. Worse, some things merchants do while waiting actively hurt:

  • Editing pending items resets their review. Each meaningful change puts the item back at the start of the queue. Submit, then leave it alone.
  • Resubmitting the whole feed re-fetches everything, and materially-changed items re-enter review.
  • Requesting a review while pending does nothing useful: the request-review flow exists for policy disapprovals, not queue position.

The lever you do control is first-pass quality. An item that arrives with a valid GTIN, a compliant image, an accurate price and a reachable landing page clears review once and stays approved. An item that fails review comes back disapproved, needs a fix, and queues again, so the real cost of dirty data isn't the disapproval, it's the doubled queue time. Validating the feed before Google sees it is how you make "pending" a state you pass through once.

When pending becomes a problem

Pending is only benign while it's moving. Escalate when:

  1. Established account, items pending beyond 7 business days. Check Diagnostics for an account-level issue first: an account under review or suspension holds every item in limbo. See the taxonomy guide for why account issues always come first.
  2. New account pending beyond ~2 weeks. The account review may have silently stalled on something verifiable: missing returns policy, unverified website, incomplete business details. Fix the trust signals, then contact support.
  3. A batch of previously-approved items flips to pending together. That's not a queue, that's a trigger: usually a feed change, a site change, or a policy re-evaluation. Trace what changed and when; a step change in item states after a deploy or import is exactly what change monitoring is built to catch.
  4. Items oscillate pending → approved → pending. Almost always caused by a feed that rewrites attributes on every fetch (regenerated IDs, timestamps in titles), making every product look "edited" daily. Stabilise the feed output.

If items come back disapproved rather than approved, switch to the fix workflow; pending was never your problem, the data was.

Deep dive New-account review queues, and why the first fortnight sets your ceiling

A brand-new Merchant Center account isn't just slower; it's reviewed differently. Before any product serves, Google evaluates the account: is the website live and complete, does checkout work end-to-end, are contact details, returns and refund policies findable, does the business name match the domain, is payment processing real. Products sit pending until that account-level pass completes, which is why a perfect feed on a day-old account still shows 100% pending.

What this means in practice:

  • Don't submit a feed before the site is finished. A placeholder returns page or a checkout that errors during the account review doesn't just delay you; it risks a misrepresentation suspension, which is a far deeper hole than a slow queue. See misrepresentation and account suspension.
  • Submit a representative first batch, not the whole catalogue. The first review sets Google's baseline trust in your data. A clean 500-product first submission that passes at 99% establishes better standing than 20,000 items arriving with 15% failures. You can scale the feed up the week after.
  • The first fortnight compounds. Accounts that clear review cleanly see subsequent item reviews run faster; accounts that generate early disapproval waves get looked at harder. First-pass quality on day one is the cheapest trust you'll ever buy.
  • Verify and claim the website before the feed goes in. An unclaimed website URL is the most common silent blocker in new-account reviews, and everything sits pending and nothing tells you why.

The pattern that works: finish the site, verify the domain, run your feed through validation so identifiers, images and prices are right before submission, send a clean representative batch, and touch nothing for 72 hours. Merchants who do this mostly never think about pending again; merchants who submit-edit-resubmit through week one often spend a month in the queue they were trying to skip.

Pending vs the states that need action

State Serving? Action needed
Pending / under review No None; wait, don't edit
Disapproved No Fix the named reason, resync, see the fix workflow
Approved with warning Yes, reduced reach Work the warning, see limited performance warnings
Expiring Yes, briefly Refresh the feed; items lapse ~30 days after last fetch

The discipline that matters: check which state you're actually in before doing anything. Half of "my products are stuck in review" cases are really a feed that stopped fetching, or an account-level issue holding everything, both of which have fixes, neither of which is a queue.

Frequently asked questions

How long does Google Merchant Center pending review take?

For an established account, most items clear within 24–72 hours of submission. Brand-new accounts routinely take 3–7 business days for the first batch because the account itself is being reviewed, not just the products. Policy-sensitive categories can take longer still.

Can I speed up a pending review?

No. There is no button, support request, or resubmission trick that shortens the queue. Resubmitting the feed or editing pending items can actually restart the review clock. The only real lever is submitting clean data the first time so items pass on the first look.

Is pending the same as disapproved?

No. Disapproved means Google made a decision against the item and recorded a reason you can fix. Pending means no decision exists yet. Neither state serves ads, but only disapproval needs action from you.

Why is my whole new account stuck in pending?

New Merchant Center accounts go through an account-level review covering your website, contact details, returns policy and checkout before any product serves. Until that clears, every item shows pending regardless of how clean the feed is.

My products have been pending for two weeks. Is that normal?

No. Anything beyond 7 business days for an established account, or beyond about 2 weeks for a new one, is worth escalating: check for an account-level issue first, then contact Merchant Center support with your account ID.

Put this into practice. /tools rebuilds messy product data into Merchant Center-ready feeds. Connect a store and see your Feed Health Score in minutes.
Try /tools →