A product disapproval is a data diagnosis, not a reason to rewrite the whole campaign. Start with the exact affected items and issue label, then trace the value from source catalog to feed to landing page.
Locate the scope of the issue
Separate account-wide warnings from a few rejected products. Export affected item IDs, issue types and dates. Check whether the pattern follows one supplier, category, variant attribute or image source. Merchant Center status tells you whether items are approved or disapproved for eligible surfaces.
Fix the source, not just a copy
Compare the submitted title, price, availability, image, identifiers and variant details with the current product page. Google’s product data specification warns that missing or incorrect attributes and conflicting site data can cause disapprovals or limited eligibility. Correct the source system that supplies the feed; otherwise the next sync may overwrite a manual patch.
Resubmit and verify
After a correction, allow the feed to refresh or follow the applicable review process. Record the item ID, original issue, source change and new status. Then open the live landing page on mobile to check the same facts. A corrected feed is a prerequisite for campaign delivery, not evidence by itself of more sales.
Worked decision example
Illustrative diagnosis: ten variants are disapproved while the parent item remains eligible. The affected variants all lack a color value after a recent catalog import. Correct the attribute in the source catalog, confirm each landing page shows the same variation, and resync the feed. Record the old and new Merchant Center status. Changing campaign bids would not fix this data problem, and a resubmission alone would not make an incorrect value true.
Practical review checklist
- Which exact item IDs are affected?
- Where does the incorrect value originate?
- Do feed and landing page now match?
Where to go next
Google Ads service · shopping feed optimization guide · Google product data specification