Quick answer: A Google Merchant Center product feed is a structured file (or API sync) that describes each product: ID, title, description, link, image link, price, availability, brand and other attributes. Connect a verified website, create a feed that Google can fetch on a schedule, fix disapprovals in Diagnostics, and keep price and availability in sync with your site. Most errors come from mismatched prices, missing images, policy issues or weak identifiers.
If you want products to appear in Google Shopping ads (and related Google inventory surfaces available in your country in 2018), Merchant Center is the hub and the feed is the fuel.
This guide covers practical setup and the errors that waste the most time.
What you need before the feed
- A Google Merchant Center account
- Website claimed and verified
- Accurate product pages with prices visible
- Clear refund and contact information as required by Google’s policies
- Product data you can export: SKUs, titles, descriptions, images, GTIN/MPN/brand where applicable
Ecommerce platforms often have official or third-party connectors for WooCommerce, Shopify, Magento and others. You can also upload spreadsheets or host a scheduled XML/CSV fetch.
Core attributes that must be right
Exact requirements vary by country and category, but these matter constantly:
- id – stable unique ID (do not recycle IDs for different products)
- title – clear, readable, not keyword-stuffed
- description – helpful, matches the page
- link – product landing page URL
- image_link – publicly crawlable image meeting size guidelines
- availability – in stock / out of stock / preorder values as specified
- price – matches the landing page (including currency)
- brand, gtin, mpn – strong identifiers improve free and paid performance; required in many cases
Apparel and certain categories need extra attributes (colour, size, gender, age group). Variants should be set up so Google understands the parent/child relationships correctly for your platform.
Feed formats and fetch schedule
Common approaches:
- Scheduled fetch from a URL your store generates overnight
- Direct upload for small catalogues (does not scale well)
- Content API for large or fast-changing inventories
- Platform app that pushes updates for you
Fetch at least daily for most stores. If inventory moves fast, increase frequency or use API updates for availability and price. Stale “in stock” items that 404 or show different prices earn disapprovals and frustrated shoppers.
Landing page and policy alignment
Google checks that:
- The price on the page matches the feed (watch tax and shipping display rules for your country)
- The product can be purchased in a normal flow
- Adult, unsafe or restricted products follow policy
- Your site supports HTTPS for checkout where required
- Returns and contact details meet Shopping ads requirements
A beautiful feed cannot save a checkout that breaks on mobile. Fix the store first.
Common errors and how to approach them
Price mismatch
Currency symbols, missing sale prices, or member-only prices on the page while the feed shows a different number. Align on-sale attributes (sale_price) with what guests see without logging in, unless you use features designed for member prices.
Image problems Images too small, blocked by robots.txt, watermarks that violate guidelines, or placeholders. Use clean product photos on stable URLs.
Missing GTIN / incorrect identifiers Either supply correct GTINs or use the appropriate indicator when products genuinely have none (custom goods). Fake GTINs backfire.
Availability mismatches Feed says in stock, page says sold out (or the reverse). Sync on the same inventory source your cart uses.
Adult or policy disapprovals Read the policy text in Merchant Center Diagnostics. Some products need landing page modifications; some cannot run at all.
Crawl issues Blocked resources, soft 404s, or redirect chains on product links. Related technical hygiene: crawl errors.
Duplicate listing / identical products Multiple IDs pointing to the same offer confuse the system. Clean variants and canonical product URLs.
Work the Diagnostics tab systematically. Fix high-volume errors first.
Titles and descriptions that sell without spam
Write titles the way shoppers scan: brand, product type, key attribute (size/colour/material) where useful. Avoid ALL CAPS and repetitive keyword lists. Descriptions should match the page and include practical details (pack size, compatibility, materials).
For broader ecommerce SEO beyond the feed, see Shopify SEO if you are on Shopify, or your platform’s equivalent practices on WooCommerce.
Free listings and ads
Depending on your country and Google’s current programmes, Merchant Center data may power paid Shopping campaigns in Google Ads and additional free inventory surfaces. Even when free surfaces exist, data quality still matters. Treat the feed as core merchandising infrastructure, not a one-time ads task.
Link Merchant Center to Google Ads correctly when you run Shopping campaigns, and keep conversion tracking accurate so bids have clean signals (AdWords conversion tracking).
Operational checklist
Weekly or daily depending on size:
- Open Diagnostics and clear new account issues
- Spot-check random products: feed price vs page price
- Confirm fetch times succeeded
- Review products with impressions but no clicks for title/image quality
- Remove discontinued IDs cleanly rather than leaving zombie offers
Feed optimisation beyond error-free
Once disapprovals are under control, improve click-through with better titles and images, and improve conversion with landing pages that match ad promises. Segment bestsellers for custom labels so Google Ads can bid differently. Custom labels (margin, clearance, seasonal) turn a raw catalogue into a campaign structure.
Negative keyword work still happens in Google Ads, not in Merchant Center. Keep the division of labour clear between feed quality and campaign hygiene.
Staging and launches
When you rebuild a store, plan Merchant Center carefully: new URLs need redirects, IDs should remain stable if products are the same, and a second test Merchant Center account can prevent polluting the live feed during migration. Never experiment with fake prices on the production feed.
FAQ
Can I use one feed for multiple countries?
Often you need country-specific feeds or correctly configured multi-country setups with the right currency and shipping settings. Do not point a UK pound feed at a US account without the proper structure.
Should I include out-of-stock items?
Follow Google’s guidance and your strategy. Out-of-stock can remain with correct availability values in some cases, but outdated URLs should not linger.
Do I need a developer?
Small catalogues can start from spreadsheet exports. Larger catalogues usually need an automated feed from the store database or a maintained connector.
Clean data wins Shopping
Google Merchant Center product feeds succeed when attributes are complete, prices and availability match the site, and Diagnostics is part of weekly store ops. Fix the feed at the source, not with one-off spreadsheet patches that drift again tomorrow.
If you need help getting Shopping feeds clean and keeping them aligned with your catalogue, our Turn visitors into customers ecommerce work includes Merchant Center setup, error cleanup and the store-side data fixes behind them.
