Google Shopping Disapproved? Merchant Center Approval Guide
Before you change anything, establish which problem you actually have. A product issue affects named items. An account issue affects the account. They live in different places in Merchant Center, they have different fixes, and the wrong correction wastes days.
Start here: product issue or account issue?
In Merchant Center, items needing action are surfaced under Products > Needs attention. Issues affecting the account as a whole are surfaced separately, in the view for account setup and policy issues. Google describes product issues as affecting individual products, and account issues as broader in scope. Google: find and fix product and account issues.
Match the correction to the reason Google actually names. Rewriting titles when the flagged issue is a landing page mismatch does not address the named mismatch.
Approval timing is not a promise. Google states that an initial review for Shopping ads can take 3 to 5 business days, that other programmes can take longer, and that making changes may delay a review. Nothing you do guarantees a fast approval, and approval itself is separate from whether an item then wins impressions.
Status, first action, and where the evidence lives
| What you see | First action | Evidence and source |
|---|---|---|
| Pending / under review | Leave it alone and let the review finish. Avoid repeated edits while it is in review. | Products > Needs attention shows the item state; Google notes initial Shopping ads review can take 3-5 business days and other programmes longer. Merchant Center: find and fix product issues |
| Disapproved (single item or small group) | Read the specific issue named against those items and correct that attribute or page. | Product issues are shown against the individual products affected. Merchant Center: find and fix product issues |
| Disapproved across a whole category or feed | Look for a shared data or policy cause, such as a mapping or export rule; investigate the issue Google names. | Attribute requirements vary by product, country and programme in Google's product data specification. Product data specification |
| Missing identifiers flagged | Supply the real identifier where one exists. Only set identifier_exists to no where identifiers genuinely are not assigned under the category rules. | Google documents identifier_exists and the unique product identifier rules separately. identifier_exists |
| Account-level issue or suspension | Work the account setup and policy issues view and follow the issue-specific instructions shown there. | Account issues are broader than a single product and appear in the account issues view. Merchant Center: account issues |
Diagnosing product issues
Product issues are named against specific items, so read them literally. Two attribute areas cause a disproportionate share of avoidable confusion, and both are conditional rather than universal:
Required is not the same as universal
Google's product data specification marks attributes as required, optional or conditional, and the condition depends on the product, the country you target and the programme. For example, google_product_category is generally optional, while condition and variant attributes such as colour or size are conditional on what you sell and where. Check your own categories rather than copying a generic list. Product data specification.
Identifiers: supply them, don't switch them off
identifier_exists set to no is for products where unique identifiers genuinely are not assigned under the category rules. It is not a shortcut for data you have not collected, and handmade products are not automatically exempt. identifier_exists and unique product identifiers.
One item or a pattern?
Count the affected items before you act. For a few affected items, inspect their individual data and pages. For a whole category, investigate shared mappings, templates and export rules, as well as the named policy reason. A shared upstream cause can recur if only individual rows are edited.
Diagnosing account issues
Account issues sit in the account setup and policy issues view. They are broader than one attribute: they concern the account, the site behind it, or programme requirements. Each issue Google raises comes with its own instructions, including what to correct and how a review is requested for that issue. Work that flow rather than a generic appeals routine.
Misrepresentation, the account-level reason that alarms people most, is broader than a price mismatch. Google's policy covers business identity, misleading or unavailable offers, and material omissions, so check the whole site experience, not only the price attribute.
If your account is also affected by wider terms or programme changes, read them alongside the issue itself: Google Merchant Center June 2026 update: terms, emails and what to check.
Review timing, and what a resubmission does not buy you
Google's guidance on initial review is 3 to 5 business days for Shopping ads, with other programmes taking longer and changes potentially delaying the review. Not every resubmission restarts a queue, and there is no fixed technical waiting period we can honestly quote before requesting a review. The dependable sequence is: identify the named reason, correct the cause at source, let corrected data process, then use the review path Merchant Center shows for that issue.
When you do request a review, follow Google's issue-specific path: some issues offer a fix or disagree route with prerequisites to complete first, reviews can take up to 7 business days, and a cooldown can disable the request button with its end date shown. Further unsuccessful reviews can extend that cooldown.
Keep eligibility and performance separate. Getting an item approved makes it eligible to serve. Whether it earns impressions and profitable sales is a campaign, bidding and margin question, not an approval question.
Approved, but the products get no impressions
This is a different investigation from a disapproval, and it belongs on the campaign side as often as the feed side. Start by reading the item's status per destination and per country in Merchant Center rather than assuming a single overall state. Google: product status. Then work down in this order:
- Destination and country. An item can be eligible for one destination or country and not another. Check the status for the destination and country you are actually advertising in.
- Account link. Confirm the Merchant Center account is linked to the Google Ads account running the campaign, and that the link is active rather than pending.
- A campaign that includes the item. Confirm an enabled campaign covers it, and that the listing group or product group actually includes it rather than excluding it or leaving it in an unbid-on branch.
- Stock, location and billing. Out-of-stock availability, targeting that excludes the item's shipping location, and an account with a billing problem all stop serving without a product disapproval.
- Targets, budget and demand. An item can be perfectly eligible and still lose every auction because the target is too strict, the budget is exhausted early, or there is little search demand for that product at all. Google's guidance on low traffic on your ads covers the common campaign-side causes.
Work down the list before changing anything. Raising the budget is not the default answer to zero impressions, and it will not move an item that is ineligible in the country you are targeting or excluded by the listing group.
Price and availability mismatch: where to look
A price or availability mismatch is a disagreement between what your data says and what the page shows. Google's product data specification sets out how price, currency and availability must be submitted and that they must match the landing page. Google: product data specification. Gather the evidence in one place before editing anything, for two or three affected items:
| Where to look | What to record |
|---|---|
| Source feed or platform export | The price, sale price, currency and availability leaving your system for that item. |
| Processed item in Merchant Center | The values after feed rules and supplemental feeds have been applied, per country. |
| Landing page for the exact variant and country | The displayed price, currency and stock state on the variant the item links to, in that country's context, not the parent product. |
| Structured data on the page | Whether the marked-up price, currency and availability agree with what the page shows a shopper. |
| Checkout | The price a shopper reaches at basket and checkout, including anything applied later that changes it. |
Where they disagree tells you which step introduced the difference: a source value, a feed rule, a country or currency setting, a variant-level page problem, or a checkout behaviour. Correct it at that step rather than overriding the value downstream, let the corrected data process, then re-check the same items.
Our operational checklist
Use this operational checklist to investigate a disapproval. It is practical guidance, not a Google document.
- Record the exact issue name, the number of items affected, and the date, before changing anything.
- Classify it: product issue, or account issue. Do not start work until that is settled.
- Open two or three affected items and compare feed values with the live product page for the same country and currency.
- Decide whether the cause is a value, a rule, or a page. Fix it where it is generated, not in a manual override, unless the override is the deliberate long-term answer.
- Re-check the specification for the specific attribute and country involved before adding or removing anything.
- Let the corrected data process and confirm the underlying issue is fixed, then follow the review path Merchant Center shows. Some issues remain flagged pending review even after the fix has processed.
- Re-check the same issue a week later. A recurring count means the upstream cause is still live.
Worked example (hypothetical)
Illustrative only, not a client account
A retailer sees 1,400 items flagged with a single issue name. Two hundred are in one category, the rest are spread across everything else. Working item by item, they would edit 1,400 rows.
Classified first, the picture changes: the 200 share an export template that drops a conditional attribute for that category, and the remaining items share a currency setting applied to a second country feed. Two upstream corrections, not 1,400 edits. Fixing the upstream causes reduces repeated manual edits; approval and the number of reviews remain uncertain.
Pending, disapproved, suspended: the questions we get asked
My products are pending. What should I do?
Pending means the item is still in review, not that something is wrong. Google states that an initial review for Shopping ads can take 3-5 business days, and that other programmes can take longer. Making changes during review can delay it further. Confirm the item is genuinely pending rather than disapproved, then wait rather than resubmitting repeatedly.
My products are disapproved. Where do I find the reason?
Open Products and then Needs attention in Merchant Center. Product issues are listed against the individual items affected, with the attribute or policy that triggered them. Fix the specific reason shown for those items rather than applying a general feed clean-up and hoping it clears.
My account is suspended. Is that the same problem?
No. Account-level issues appear in the account setup and policy issues view, not against individual products. They usually concern the account, the website or programme requirements rather than one attribute in the feed. Follow the issue-specific instructions Google shows for that issue, which include how and when to request a review.
Are the requirements the same for every product?
No. Google's product data specification marks some attributes as required, some as optional and some as conditional, depending on the product, the country you sell in and the programme you are using. Check the specification for your own categories and destinations before assuming an attribute is mandatory.
When should I request a review?
After the underlying cause is actually corrected and the corrected data has been processed. Merchant Center shows the review path that applies to each issue. There is no universal waiting period we can promise, and approval is never guaranteed by a resubmission.
Does approval mean my products will get traffic?
No. Approval means an item is eligible to serve. Whether it actually serves, and how often, depends on your campaigns, bids, budgets, competition and the query. Eligibility and performance are separate problems and should be diagnosed separately.
Sources
Related Reading
Stuck on a Merchant Center issue you cannot place?
We manage product feeds and Merchant Center as part of retained Google Ads work. If you would rather talk it through first, a conversation is a conversation: we cannot promise approval, and no one can diagnose a whole account in half an hour.
Next step
Is your feed telling Google what the business needs it to know?
Margin, stock and product role belong in the feed. Most feeds carry none of them.