1. Read Diagnostics before touching anything
Open Merchant Center, then Products, then Diagnostics. You will see two lists: item issues and account issues. Item issues name specific products and attributes; account issues affect the whole feed. Work the item list first – it is concrete, countable, and usually the bulk of lost visibility.
Export the worst offenders. For each, note the exact error text. Google's error messages are terse but precise; "Missing value [gtin]" means exactly that, and the fix is data, not settings.
2. Check identifiers first
GTIN, MPN, and brand are the most common silent killers. Typical patterns: GTINs that are actually internal SKUs, placeholder values like "1234567890123", or brand names that differ between the feed and the landing page. Google cross-checks these; mismatches read as untrustworthy data.
Rule of thumb: if the identifier would not scan at a checkout counter, do not put it in the feed. For genuinely GTIN-less products, the correct move is declaring that properly – not inventing numbers.
3. Compare price and availability against the landing page
Google crawls your product pages and compares. If the feed says $49 and the page says $59, or the feed says in stock while the page says otherwise, expect disapprovals. This drift usually comes from caching, scheduled feed generation, or currency and tax handling – fix the pipeline, not just the values.
4. Separate data problems from policy problems
This distinction saves the most time. Data problems (attributes, identifiers, formatting) are fixable and worth fixing. Policy problems (restricted categories, misleading claims, landing-page experience) are Google's rules – no amount of feed editing overrides them. If you are hitting a policy wall, the honest answer is to change the offer or the page, not to keep resubmitting.
5. Fix feed delivery last
Fetch errors, expired credentials on scheduled fetches, and malformed files sit underneath everything else. Verify the feed actually uploads cleanly and on schedule before treating content errors as the whole story – a feed that has not refreshed in three weeks makes every other diagnostic meaningless.
What to do after the fix
Re-run diagnostics after one full feed cycle, not five minutes after saving. Merchant Center needs time to reprocess. Track disapproved-item counts weekly for a month; if they creep back up, the cause is upstream – usually whoever or whatever writes the product data.
Want a professional diagnostic?
We run structured Merchant Center feed diagnostics: audit, root-cause mapping, remediation, and verification.
Related: Catalog Cleanup & Migration · Cleaning & migrating catalogs