Fix Google Merchant Center Disapprovals with AI: A Step-by-Step Guide

Connect Merchant Center to Claude or ChatGPT

MCP Ads connects Merchant Center to your AI client through the Merchant API. Add the MCP Ads connector to Claude, ChatGPT, Cursor or another MCP client, sign in with the Google account that has access to the Merchant Center account, and the assistant can list your accounts and sub-accounts. The Merchant Center MCP page describes what is covered and the Merchant Center docs list each action.

One setup step is Merchant API specific: if the first call fails with "GCP project not registered", the account needs a one-time developer registration, which a Merchant Center admin can run from the chat. After that, everything below works from a prompt.

Step 1: check account-level issues first

When many products are disapproved at once, the cause is usually the account, not the products. Misrepresentation, a suspended account, an unverified or unclaimed website, missing shipping settings for a country, or a missing return policy can each disapprove the whole catalogue in a destination. Editing products will not help until that is fixed.

List the account-level issues in my Merchant Center account, with severity, the countries and destinations affected, and what Google says to do about each. Then tell me whether any of them would explain products being disapproved in bulk.

• Misrepresentation: usually a site trust problem (missing contact details, unclear return or shipping policy, checkout issues). The fix is on the website, followed by a review request.
• Website not verified or claimed: the homepage needs to be verified and claimed; the assistant can check its status.
• Shipping and returns: missing settings for a target country disapprove products there. The assistant can read your current shipping settings and return policies and show what is missing.
• Some issues carry a Google action such as requesting a review. Where Google exposes that action, MCP Ads can trigger it, after you confirm.

Step 2: get the catalogue health summary

Next, ask for the totals: how many products are approved, pending, limited and disapproved, per country and per destination (Shopping ads, free listings, and so on), with the most common issues. This is the number to come back to after fixes, and it shows where to look first: an issue affecting 900 products in your main market beats one affecting 4 in a minor one.

Give me a status summary of my Merchant Center catalogue by country and destination: approved, limited, pending and disapproved counts, and the top issues with how many products each affects. Rank the issues by products affected in the US.

Step 3: group product issues by cause

Now list the disapproved products with their issues, and ask the assistant to group them. The issue code alone is not enough; the same "price mismatch" can come from a currency error on one product type and a sale price that expired on another. Grouping by issue plus a shared attribute (brand, product type, data source, image domain) is what turns a list into a to-do list.

List the disapproved products in the US, including ones that are only limited. Group them by issue, and within each issue look for what the products have in common: brand, product type, data source, or price range. For each group, explain the cause in one sentence and propose the fix.

• Price or availability mismatch: the feed disagrees with the landing page. Common causes are a caching layer serving old prices, a sale price that ended on the site but not in the feed, or a currency or tax setting.
• Missing or incorrect identifiers (GTIN, brand, MPN): usually concentrated in a few brands or in your own-brand products. Products without a manufacturer GTIN should say so rather than invent one.
• Image issues: promotional overlays, watermarks, placeholder images or images that fail to crawl. These usually come from one template or one image host.
• Landing page errors: the product link returns an error, redirects, or is blocked to Google's crawler. Often one URL pattern after a site change.
• Policy issues (restricted products, prohibited content): read the explanation carefully. Some need a product change, some a policy appeal, and some mean the product cannot be advertised in that country.

Step 4: read one product's issues in full

For each group, pick one product and ask for its issues rendered the way Merchant Center explains them, with what Google detected, which attribute is at fault, and the suggested fix. This is the step that stops you fixing the wrong thing; for example, a price mismatch might turn out to be a shipping-cost mismatch in a single country.

Show me the full issue explanation for product en~US~SKU-1042, including which attribute is wrong, the value Google found on the landing page if it says, and the fix steps. Then show me the product's current title, price, availability, link and image link.

Step 5: fix the products in the right place

Where the fix goes depends on where the product comes from, and getting this wrong is why some disapprovals come back every morning.

For the 38 products in the "missing GTIN" group from brand Acme, these are our own-brand products with no manufacturer GTIN. Create a supplemental data source called "Fixes - identifiers" if we don't have one, and plan setting identifier_exists to false for those products. Show me the diff for each product before writing anything.

• Products from a scheduled file feed (a URL Merchant Center fetches, often generated by your e-commerce platform or a feed app): an edit to the product is overwritten at the next fetch. Fix the source, or put the corrected values in a supplemental data source, which overrides the feed and survives fetches. MCP Ads refuses to write directly over a feed-owned product unless the write goes to a supplemental source or you explicitly override, so a fix is not silently lost at the next fetch.
• Products from the API or an e-commerce integration: edit the product attributes directly. Only the attributes you name are changed.
• Website problems (wrong price on the page, broken links, missing policies): fix the site. No feed change will resolve a landing page that disagrees with it.

Step 6: preview, apply, and confirm approval

Every product write in MCP Ads has a dry-run mode: the assistant first shows you each product's attributes before and after, and writes nothing. Read it, then approve. After a real write, the result reports approval per destination (approved, limited, disapproved or pending), so you see straight away whether Google accepted the change or whether it is still processing.

If you fixed the source feed rather than individual products, you do not have to wait for the next scheduled fetch: ask the assistant to fetch the file data source now. Then check the disapproved list again. Google needs time to recrawl landing pages for some issues, so a product can stay pending for a while after a correct fix; compare the summary from Step 2 a day later.

Apply the identifier changes we just reviewed. Then fetch our main product feed now, wait for processing, and show me the disapproved products in the US again with the new summary counts next to the ones from this morning.

A weekly feed-health routine

Disapprovals return whenever the site, the platform or Google's policies change, so a short weekly check beats a big quarterly clean-up. One prompt covers it:

Weekly Merchant Center check: any new account-level issues; approved/limited/disapproved counts by country compared with last week's numbers I paste below; any issue affecting more than 20 products; and the 10 disapproved products that sold best in Shopping over the last 30 days, so we fix those first.

• Prioritise by revenue, not count. A disapproved best-seller costs more than a hundred disapproved long-tail variants; MCP Ads can read Merchant Center product performance to rank them.
• Watch "limited" as well as "disapproved". A product serving in one country but not another is easy to miss.
• Check after every site change: a theme update, a new caching or currency plugin, or a URL migration are the usual causes of a sudden wave of mismatches.
• Keep the context in one chat: the same connector reads Google Ads, so you can ask which Shopping or Performance Max campaigns lost the most impressions on the affected products.

What the assistant cannot do

It cannot override Google's policy decisions, and it should not try to work around them; the fix for a policy disapproval is to change the product or website so it complies, or to appeal when Google got it wrong. It also cannot see your landing pages the way Google's crawler does, so for mismatches it relies on Google's reported values and what you tell it about the site. And it will not invent identifiers: if a product has a manufacturer GTIN, it has to come from the manufacturer or your product data.