Ads agent
Would Google Shopping ads accept your product pages?
This agent checks the things Google's Merchant Center is documented to disapprove products for, before Google does: whether your robots.txt names AdsBot in a block list, whether your product pages state the same price and availability as your own product data, and whether your shipping and returns are stated in a form Google reads rather than estimates.
AdsBot plays by its own rule: it ignores a blanket 'block all bots' line and obeys only a rule that names it. So blocking AI crawlers never touches your ads, and this agent only flags a robots.txt that switched off ad verification by name, which is usually a copy-pasted list nobody meant.
Everything here is measured from your own store's public pages and your own product data. We never claim to know what Google will decide, and connecting your actual Merchant Center verdicts is a separate, optional step that does not exist yet.
Every check this agent runs
Read from the checklist the scan executes, not written for this page. A check added to the agent appears here with no marketing edit.
| Check | Reads | Category | Severity |
|---|---|---|---|
| adsbot_access Your robots.txt switches off Shopping ads by nameAdsBot is the crawler Google uses to check the pages your ads point at, and it plays by its own rule: it ignores a blanket 'block everything' line and obeys only a rule that names it. So a store that blocked 'all bots' has not blocked AdsBot and is fine here. This flag fires only when your robots.txt names AdsBot-Google in a Disallow, which is usually a copy-pasted blocklist, and it means Google cannot verify your landing pages: ads get disapproved for reasons that look like a mystery. | Your storefront | Ad eligibility | high |
| product_page_parity A product page disagrees with its own product dataPrice and availability mismatches are the two most common reasons Merchant Center disapproves a product: Google compares the page it fetches against the data it was given, and a disagreement reads as unreliable. We probe a small sample of your product pages and compare each page's own structured data against your product record. A page whose offer states a different price, or no availability at all, is what this flag names. We only ever compare a page against your own data, and a page we could not read or parse is reported as unknown, never as wrong. | Your storefront | Ad eligibility | high |
| ads_policy_markup Google estimates your shipping and returns instead of reading themThe same MerchantReturnPolicy and OfferShippingDetails markup the AEO agent checks has a second, separately documented consumer: Google's shopping surfaces use it to show shipping cost and return windows on ads and free listings. Without it, Google falls back to account-level settings in Merchant Center, or estimates, and an estimate that disagrees with your checkout is a disapproval risk. This is the one place structured data has a documented commercial effect, which is why two agents check it: AEO for answers, this one for ads. Fixing it once satisfies both. | Your storefront | Ad eligibility | medium |
We measure your store, not the assistants. We do not claim to know what ChatGPT or Gemini will recommend, and we will not sell you a number we cannot take.
See where your store stands.
Read-only, public pages only, about 2 minutes. One free audit per store, so we ask for an email and keep it with your result.
Already convinced? Install Agentible on your store