What is probably happening
Product data does not match the landing page
Price, availability, currency, variant, title, image or shipping values can differ between the feed and the product page, especially with sales, bundles, dynamic pricing or Shopify Markets.
Policy or restricted-product issue
Some disapprovals are tied to product categories, claims, images, regulated goods, destination quality or missing business information. Editing bids will not fix a policy mismatch.
Feed fields are missing or malformed
GTIN, MPN, brand, condition, age group, color, size, shipping, tax, product type, images or item group IDs may be missing, invalid or inconsistent across variants.
The website blocks or changes what Google sees
Popups, geo redirects, blocked crawlers, unavailable products, checkout restrictions, slow pages or JavaScript-rendered data can make Google's review see a different product than users do.
Automatic feed sync keeps reintroducing the error
Manual fixes inside Merchant Center can be overwritten by Shopify, WooCommerce, a feed app, supplemental feed rules or scheduled uploads.
How to check it without breaking anything
Export affected products and group them by exact issue type, not just by campaign impact.
Open several product examples and compare feed values with the live landing page.
Check account-level diagnostics separately from item-level disapprovals.
Verify identifiers, variants, images, price, availability, shipping and destination eligibility.
Inspect whether the feed source, supplemental feed or ecommerce connector overwrites your changes.
Review the policy explanation before appealing; do not submit a weak appeal if the root cause is still present.
How I would solve it step by step
Fix the source of truth
Correct the ecommerce platform, feed app, supplemental feed or feed rule that produces the product data. Do not rely on one-off manual edits if the next sync will erase them.
Separate policy from data quality
For data-quality issues, repair fields and request reprocessing. For policy issues, repair the product, website or business information before any appeal.
Validate before scaling campaigns
Once products are approved again, check whether Shopping or Performance Max receives impressions and whether product groups, bids, budgets and conversion goals are still aligned.
Document the fix
Keep screenshots, issue IDs, product IDs, feed changes and dates. If the issue returns, this history makes the second diagnosis much faster.
If it gets technical
You can follow this path yourself. If the diagnosis reveals a strange data mismatch, a delicate tracking setup, a risky bidding decision or a blocker that needs account access, Lia keeps this context and brings it to CreatikLab so you do not start from zero.
Take this context to LiaWhat I would not do
Appealing before fixing the product or website.
Fixing products one by one while the feed source keeps recreating the error.
Treating account-level warnings as item-level disapprovals.
Ignoring price, availability or shipping mismatches because products look correct to logged-in users.
Restarting campaigns before product eligibility and tracking are stable.
Frequently asked questions
Should I appeal every disapproved product?
No. Appeal only when the product, website and feed data are actually compliant. Many disapprovals are better fixed through feed or landing-page corrections first.
Can disapproved products affect Performance Max?
Yes. If PMax depends on Shopping inventory, product disapprovals can reduce eligible inventory and push spend toward other channels or stop delivery for affected products.
Why do products get disapproved again after I fix them?
Usually because the original feed source, ecommerce connector or scheduled upload overwrites the correction. Fix the upstream source, not only the Merchant Center interface.
