AI agent for Google Merchant Center: feed health and product fixes
Feed work is unglamorous and expensive to get wrong: a disapproved product earns nothing, and a price that disagrees with your landing page is a policy violation rather than a typo. The agent reads the feed, groups rejections by cause, ranks them by what they cost you, and drafts the corrections.
What the agent does with Merchant Center
- Reads products, product issues and data sources, with date-ranged Shopping performance.
- Groups disapprovals by cause rather than listing them — a hundred rejections is usually four problems.
- Ranks fixes by impressions lost, so the order follows money rather than row count.
- Inserts and removes products, and creates, fetches or deletes data sources — each approval-gated.
- Lists sub-accounts on advanced (multi-client) accounts.
- Joins Shopping performance to Google Ads spend in the same task.
The fence follows what a shopper sees
Shopping writes are not one risk level, and the tiers deliberately do not follow the verb. A price or availability change is Auto-pilot only, because a mismatch between feed and landing page is a policy violation. A title or image fix is an ordinary approval-gated write.
Deleting a data source is never unattended: it removes a feed and every offer it supplied, so the agent reads the source first and requires its display name echoed back — the id is a long number and one digit is a different live feed.
Two failures that look like permissions and are not
- An advanced (multi-client) account returns 403 on product and issue queries while a plain account lookup succeeds. Re-authorizing cannot fix it; the sub-accounts to call instead are named in the refusal.
- Merchant API refuses every call from an unregistered Google Cloud project, including the call whose own job is to report an existing registration. That one-time registration blocks everything until it is done.
Frequently asked questions
- Can an AI agent fix disapproved products in Merchant Center?
- It reads the disapprovals, groups them by cause, ranks them by lost impressions and drafts the corrections. The writes pause for approval, and price or availability edits sit behind the strictest tier.
- Why does my Merchant Center account return 403?
- Usually because it is a multi-client parent account, which refuses product and issue queries — those belong to sub-accounts. It is not a permissions problem and re-authorizing will not help. A missing one-time Cloud project registration causes the same symptom.
- Is a nightly product push safe to re-run?
- Yes — the writes use upsert semantics, so re-running updates rather than duplicating.
- Can it link Shopping performance to ad spend?
- Yes, Google Ads connects natively too, so feed quality and Shopping performance can be read in the same task rather than compared across two exports.