Google Merchant Center is the gateway for your products into Google Shopping, but also into the free listings that appear in Search, Google Images and YouTube. Connecting a WooCommerce store to Merchant Center is a matter of a few settings. Getting a product feed in which no item is disapproved takes more: a properly configured account, complete data and, above all, strict consistency between the feed and the store’s pages.
What Merchant Center checks before your products
Before examining a single item, Google examines the store. Several conditions must be met.
The website must be verified, then claimed. Verification proves you control the domain; claiming associates the URL with your Merchant Center account, and each URL can be claimed by only one account. Verification is done through an HTML tag, a file upload, Google Tag Manager, Google Analytics or your e-commerce platform.
The store must inspire trust. Google requires clearly accessible contact details, at least one common payment method, a checkout that works from start to finish and clear communication of the total cost before purchase. The return policy must be easy to find on the site and entered in Merchant Center.
Shipping must be configured. In most countries, including the US, the UK and France, shipping costs are mandatory, for Shopping ads as well as free listings. Google recommends setting them in the account settings and reserving the feed’s shipping attribute for exceptions: bulky or fragile products, or items with a specific rate.
None of these points concerns the quality of the product pages, but each can block the entire catalog. Better to settle them before submitting the first product.
Connecting WooCommerce to Merchant Center
Google offers several ways to populate Merchant Center: a file, a Google Sheet, the API, an e-commerce platform integration or automatic retrieval of products from the store. For WooCommerce, three approaches dominate.
The Google for WooCommerce extension
This is the official extension, free on the WooCommerce marketplace. It creates or connects the Merchant Center account, syncs products automatically and lets you launch Performance Max campaigns if you wish. It offers attribute mapping rules to match your WooCommerce attributes to feed attributes, and it reads WooCommerce’s native GTIN field.
A product feed plugin
Feed plugins generate an XML or CSV file, regenerated at regular intervals, that Merchant Center fetches from a given URL. They offer finer control over each attribute, filters to exclude certain products and the ability to produce feeds for other channels from the same base.
Automatic retrieval from the website
Merchant Center can also add products automatically by crawling the store’s pages and their structured data. This is a fallback rather than a primary source: control over the attributes remains limited, updates depend on Google’s crawl schedule rather than yours, and anything missing from the page markup is simply missing from the listing.
Whatever the method, feed quality depends on product page quality. A feed only transports the data present in WooCommerce: an attribute left empty in the store stays empty in Merchant Center.
Feed attributes and their source in WooCommerce
Google’s product data specification distinguishes attributes required for all products from those that become required depending on the case.
| Merchant Center attribute | Usual source in WooCommerce | Rule to know |
|---|---|---|
ID [id] |
SKU or product ID | 50 characters maximum, unique and stable |
Title [title] |
Product name | 150 characters maximum, matching the page |
Description [description] |
Long or short description | 5,000 characters maximum, no links or promotional text |
Link [link] |
Product URL | Verified domain |
Image link [image_link] |
Main image | No watermark or promotional text |
Availability [availability] |
Stock status | Identical to the page |
Price [price] |
Regular price | Identical to the page, currency included |
Brand [brand] |
Brands (native since WooCommerce 9.6) or attribute | Required for new products, except movies, books and music recordings |
GTIN [gtin] |
“GTIN, UPC, EAN, or ISBN” field | Strongly recommended whenever a GTIN exists |
MPN [mpn] |
Attribute or custom field | Required when no manufacturer-assigned GTIN exists |
Condition [condition] |
Extension setting | Required for used or refurbished products |
Two cases deserve particular attention.
Variable products. The item group ID attribute [item_group_id] is required for variants in most target countries: it links the sizes and colors of the same model. Each variation keeps its own ID, its own price if needed and its own GTIN.
Apparel. For clothing and accessories sold in the US, the UK, France and several other markets, the Color [color], Size [size], Gender [gender] and Age group [age_group] attributes are required. They therefore need to exist as WooCommerce attributes, ideally global ones, so they can be passed along. Building these attributes is detailed in our article on WooCommerce attributes.
On the image side, Google has announced a minimum size of 500 x 500 pixels for all product images, enforced from January 31, 2027. A catalog illustrated with smaller thumbnails would do well to get ahead of it.
The GTIN, finally, weighs directly on visibility: a product that has one but is submitted without it risks limited distribution. Its format rules are detailed in our guide to EAN and GTIN codes.
The most predictable disapprovals
Many disapprovals stem from a gap between what the feed says and what the page shows.
Price mismatch. Googlebot regularly crawls landing pages and compares the feed price with the page price. A sale price applied in the store but absent from the feed, a cache serving an old version, incorrect structured data: any one of these is enough to trigger a disapproval. Stores that show prices with tax to some visitors and without tax to others, or that display a different price based on geolocation, are especially exposed.
Availability mismatch. A product out of stock in the store but declared in stock in the feed falls under the same mechanism. Feeds regenerated once a day on a store where stock moves by the hour will produce this error on a regular basis; a shorter regeneration interval or a direct sync is the fix.
Invalid or incorrect GTIN. Wrong check digit, internal-use code, number borrowed from a neighboring product, same GTIN on every variation.
Non-compliant images. Watermark, added logo, promotional banner or advertising overlay on the main image.
Missing information. Brand absent, shipping costs not configured, required apparel attributes left blank.
Merchant Center offers automatic item updates: when the price, sale price, availability or condition differ between the feed and the page, Google can correct the item from the page’s structured data. These updates are enabled by default, but Google specifies that they do not replace updating your data regularly. They also only work if the page markup is correct, which is the whole point of our recommendations on Product structured data.
Before submitting the feed
A quick check saves a lot of back and forth with Merchant Center:
- Website verified and claimed, contact details visible, return policy published.
- Shipping costs configured in the account.
- Brand entered for every new product.
- GTIN entered for every product and every variation that has one, brand and MPN otherwise.
- Variant and apparel attributes present as WooCommerce attributes.
- Price and availability identical across the feed, the page and the structured data.
- Main images free of added text and large enough.
Titles and descriptions deserve the same care as for the store itself, since Google requires them to match the page. The writing principles are laid out in our guide to writing a product page.
Product pages ready for the feed
A feed with no disapprovals starts with complete product pages. Fichewise writes each WooCommerce product page from verified sources and fills in, alongside the text, the attributes, the GTIN and the brand that feed Merchant Center. The license includes exports in Google Shopping and Amazon formats. Fichewise runs either on your own API keys (the cost is then limited to that of the API, around €0.25 per product page) or through the managed service with credit packs, with no key to manage; the details are on the pricing page. The Features page describes how every piece of data is sourced.