Google Merchant Center: setup, diagnostics, and suspensions

Phase 3 introduced Merchant Center as a dashboard to watch. This is the operating manual: how the account should be configured, how to work the diagnostics systematically instead of whack-a-mole, and the suspension mechanics that every store hits eventually - usually at the worst time.

A healthy setup, checklist form

The foundations that prevent most future pain: website claimed and verified (proves you own the domain the feed points to), shipping settings configured accurately - including per-market - because Google compares your declared shipping against checkout reality, and mismatches are a policy issue, not a detail; return policy configured (increasingly surfaced in listings, per the schema thread from Phase 5); tax/VAT settings correct per market; and the feed source itself - the Shopify Google & YouTube app for straightforward setups, a feed tool for the multi-channel/multi-market cases from Phase 3's decision framework. One structural recommendation regardless of source: know where each attribute is coming from (which Shopify field maps to which GMC attribute), documented in one place. The hour that costs saves days across future debugging.

Working the diagnostics systematically

The Products → Diagnostics view offers item-level issues sorted by affected count - and that sort order is your triage. The method: work issue types, not items, top down. Ten thousand items with one shared issue ("missing color") is one fix in the source data or one mapping rule - not ten thousand fixes. Per issue type, the diagnostic question sequence from last lesson: is the data missing at source (fix the catalog - the durable fix), present but unmapped (fix the feed configuration), or present and mapped but rejected (read Google's actual requirement - often a format detail like size value conventions). Two issue classes deserve standing priority: anything marked disapproval (item invisible now) over warnings (item weakened), and issues on your revenue products over long-tail - the same traffic-weighted triage as Phase 2's audits.

Suspension mechanics, demystified

Account suspensions feel arbitrary; they're mostly not. The dominant cause is misrepresentation - Google's umbrella for "the buying experience doesn't match what was promised": feed/site price mismatches, unclear or missing contact info and policies, checkout problems, or business-identity signals that don't add up. Preemptive warnings arrive with a fix window; actual suspensions require a re-review request after fixing. The realistic guidance: re-reviews take days to weeks, repeated failed re-reviews extend cooldowns, and support escalation exists but is slow - which is why the only good suspension strategy is the boring one: policy hygiene as permanent hygiene (visible contact info, accurate policies, tight feed-site consistency), audited quarterly, not after the email arrives. For a store doing meaningful Shopping revenue, a two-week suspension in Q4 is a five-figure event. The hygiene is cheap insurance.