Merchant Center health check: what healthy actually means

Confirm how many current products Merchant Center processed and how many are healthy, limited, disapproved, or pending. Then identify account-level issues and any destinations or countries with broader restrictions. A score can summarize this picture, but the underlying evidence should remain visible.

Ten affected products are not automatically more important than one. A single disapproved offer that recently received clicks may deserve earlier investigation than a large set of unused warnings. Clicks and impressions provide prioritization context only; they do not measure lost revenue.

Traffic context is safe only where a Merchant performance row maps one-to-one to the processed product. Ambiguous rows should stay unmatched rather than being guessed into an issue total.

Review when each source last updated and whether the account reflects recent store changes. Sample price, availability, images, identifiers, variants, and landing pages. Check structured data as supporting evidence, but do not assume it alone determines Merchant eligibility.

A current snapshot can miss operational risk. Track when issues first appear, when their affected set expands, and when Google reports resolution. A resolved state is more useful than simply sending the first alert and forgetting the problem.

• New issues that were absent in the prior complete sync
• Expanded affected-product sets
• Impact changes on deterministically matched traffic
• Resolved issues and recovered product status
• Repeated sync or OAuth failures that require action

CommerceVigil can inspect connected Merchant data, classify direct Google issues, monitor lifecycle changes, and prioritize supported performance evidence. It cannot see every Google auction, prove a causal revenue loss, change your feed, or guarantee that a correction will restore delivery.