How Google Merchant Center works
Merchant Center is where a shop’s product data lives inside Google. You send it a feed — an uploaded file, a scheduled fetch, an app on your ecommerce platform, or a direct connection — carrying one row per sellable item with its title, description, price, availability, images, identifiers and link. Google checks each row against its policies and against its own understanding of the product, then makes the approved items available to Shopping ads and to free product listings.
Two things sit behind that. The account holds settings that apply to everything you sell: verified ownership of the website, delivery rates, returns policy, tax where it applies, and the countries you sell into. And Google visits your product pages to confirm that the price and availability in the feed match what a customer would actually see. Disagreement between the two is the most common reason items stop showing.
Why Merchant Center matters
Shopping campaigns and the retail side of Performance Max have no ads to write in the usual sense; they assemble what a shopper sees out of the feed. Titles, images and prices are the creative, so feed quality is campaign quality, and a disapproved item is simply not for sale on Google no matter what the campaign is doing.
Free product listings matter too. Approved items can appear on shopping surfaces without any spend, which is worth having for a smaller shop that cannot fund continuous advertising.
Where Merchant Center goes wrong
Item disapprovals accumulate quietly. A missing identifier, an image with promotional text across it, a price that differs from the landing page by a rounding or a currency, a product a policy restricts, or a page a crawler cannot reach — each removes items without removing the campaign, so spend concentrates on whatever is left standing.
Account-level suspension is the serious version, and it usually follows something structural: a website with no contact details, no refund or delivery terms, a checkout that cannot be completed, or unverified ownership of the domain. Fixing that is far slower than preventing it. The other recurring problem is a feed that refreshes too rarely, so a sold-out item stays advertised and the mismatch is discovered by a customer.
How to act on it
Treat the diagnostics screen as a weekly job rather than a launch task, and work through disapprovals by reason rather than item by item, because one cause usually explains many rows. Keep price and availability synchronised often enough that the feed and the site never contradict each other, and let your platform’s own connection handle that if it offers one.
Beyond compliance, the work that pays is in the product titles and attributes: a title that reads like something a person would search for rather than an internal product name, correct GTINs, brand, condition, and the fields that let Google understand what the item is. That ongoing feed work moves shopping performance more reliably than bid changes do.
