WooCommerce Google Product Feed: Setup and Troubleshooting Checklist for Google Merchant Center

Preparing a WooCommerce Google product feed is not limited to connecting a store with Google Merchant Center. Before synchronization, product data must be complete, identifiers must be mapped accurately, category-specific attributes may need additional configuration, and each product must be eligible for inclusion. After submission, the product can still be processed, limited, excluded or not approved.

This checklist separates the stages that are often confused: preparing product data in WooCommerce, including products in the feed, processing the submitted information, and checking approval and visibility in Merchant Center. Requirements can vary according to the product category, target country, Google program and feed solution. The checklist therefore supports an audit and troubleshooting process, but it does not guarantee approval, visibility or a fixed publication time.

What This WooCommerce-to-Google Product Feed Checklist Covers

A reliable preparation process starts with the product record in WooCommerce and ends with item-level diagnostics in Google Merchant Center. The first question is whether the product has the basic information needed to be included in the feed. The next is whether identifiers and additional attributes accurately describe the product. Only then should you investigate status and visibility.

Synchronization is not the same as approval

A product may be present in the feed but still be under review or processing. It may also be approved in one context while having limited visibility or a separate issue that affects where it appears. Conversely, a product may never reach Google because it is not synchronized or has been excluded in WooCommerce.

WooCommerce and Merchant Center also use different status vocabularies. Pending, Expiring and Disapproved are labels documented for the WooCommerce Google for WooCommerce interface. Merchant Center separately uses statuses such as Under review, Processing, Approved, Limited and Not approved. Check which interface displays a status before deciding what action is appropriate.

Pre-Sync WooCommerce Product Data Audit

For the Google for WooCommerce workflow, WooCommerce identifies the product title, product description, product ID, product link and product image as basic fields that should be present before synchronization. These fields are the starting point, not a universal list that guarantees approval for every product or market.

Next, check the information that can create inconsistencies between the store and the submitted data. The product price and availability should correspond with the information shown on the product page and during the purchase process. Also inspect the destination link and confirm that it leads to the relevant product rather than to a different item or an unavailable page.

Products with variations require an additional review of how the selected feed solution represents products and variations. Do not assume that one parent product record describes every variation correctly. Review the submitted data for a representative product and, where applicable, its variations before applying a configuration to the complete catalog.

Basic fields and landing-page consistency

Use this order for a single-product audit:

1. Confirm that the title, description, product ID, product link and image are present.
2. Compare the submitted price and availability with the product page and checkout information.
3. Check that the landing page is available and represents the submitted product.
4. Review identifiers and category-specific attributes after the basic data is complete.

Basic WooCommerce fields alone do not automatically mean that a product will be approved.

GTIN, Brand, MPN and identifier_exists Mapping

Google uses unique product identifiers to help describe products accurately. Relevant attributes include GTIN, MPN and brand. The most important mapping rule is straightforward: when a manufacturer has assigned a valid GTIN, map that value to the Google gtin attribute. A store’s internal WooCommerce SKU is not a substitute for a manufacturer-assigned GTIN.

Google recognizes GTIN forms including UPC, EAN, JAN, ISBN and ITF-14. The value must be valid for the product. Do not invent, guess or reuse a number simply to remove a missing-field warning. Incorrect identifiers can cause warnings, limited visibility or product disapproval.

If no manufacturer-assigned GTIN exists, check whether the product has appropriate brand and MPN information. MPN values should be manufacturer-assigned, unless the seller is the manufacturer and has no assigned identifier. These fields should describe the actual product and should not be generated as arbitrary replacements for missing data.

For a product that genuinely has no assigned unique product identifiers, Google allows the seller to indicate this with identifier_exists set to no or false, depending on the supported feed format. This setting is not a general workaround for incomplete catalog data.

A practical identifier decision path

1. Establish whether the product has a manufacturer-assigned GTIN.
2. If it does, map the accurate GTIN and do not replace it with the store SKU.
3. If no GTIN exists, check the applicable brand and manufacturer-assigned MPN data.
4. Use identifier_exists=no or false only when the product genuinely has no assigned identifiers and the feed format supports that value.
5. Review the resulting item-level diagnostics instead of assuming that a mapping change resolves every issue.

Do not fabricate or guess GTIN, MPN or brand values.

Category-Specific Attributes and Custom WooCommerce Fields

Basic fields and identifiers may not be enough for every catalog. WooCommerce documentation identifies additional category-specific data for areas including apparel, media, books and electronics. The appropriate attributes depend on the product and the applicable Google requirements.

Examples of attributes that may apply in relevant categories include size, color, gender, age group or ISBN. Use them only when they accurately describe the product and are relevant to the category or program. A field should not be populated with an invented value merely because a mapping interface offers it.

WooCommerce also notes that custom global attributes are not synchronized by default in Google for WooCommerce and may require the Attribute Mapping tool. Before mapping, confirm that the WooCommerce attribute contains consistent values and that its meaning corresponds to the Google attribute. Category, target country and program rules should be checked before applying one mapping across the catalog.

Why one mapping cannot fit every catalog

A clothing catalog, book catalog and electronics catalog do not necessarily require the same product data. Separate the audit into two layers: the basic fields that describe the product generally, and the attributes that depend on its category. This prevents an irrelevant attribute from being treated as universally required.

When a custom field is mapped, test a controlled set of products first. Check the actual submitted value and its relationship to the product page. A successful mapping means that data was transferred; it does not by itself confirm approval or visibility.

Feed Inclusion, Channel Visibility and Excluded Products

If a product is absent from the Google feed, begin in WooCommerce rather than immediately changing attribute mappings. In Google for WooCommerce, review the Product Feed area, including the Account Issues and Product Issues tabs. These locations can reveal whether the problem concerns the account, product data or eligibility.

Products marked Not synced may be queued, ineligible or excluded from the product feed. Check the product’s channel visibility setting as well. WooCommerce documents Sync and Show as eligible for Google visibility, while Don’t Sync and Show excludes the product. A product can therefore be complete but absent because it is not enabled for synchronization.

After checking WooCommerce, compare the result with Merchant Center. Review the product’s source, visibility, status and item-level issues. This comparison helps distinguish three different situations: the product was never included, it was submitted but has a data problem, or it was processed but is not currently visible.

WooCommerce documentation states that channel-visibility changes may synchronize automatically within one to two days for that documented solution. Treat this as solution-specific information, not as a universal timing promise for every feed method.

WooCommerce-side exclusion checks

1. Open the Product Feed area and review Account Issues and Product Issues.
2. Find products marked Not synced and determine whether they are queued, ineligible or excluded.
3. Check whether Channel Visibility is set to Sync and Show or Don’t Sync and Show.
4. Record the current setting and issue before changing the configuration.
5. Compare the WooCommerce result with the source and diagnostics shown for the item in Merchant Center.

Do not assume that a missing product is necessarily affected by an attribute-mapping error.

Status-Based Troubleshooting: Pending, Expiring, Disapproved and Not approved

Status interpretation depends on the interface. In WooCommerce’s Google for WooCommerce documentation, Pending means that Google is still processing the product. Expiring means that the product is expected to become inactive within three days. Disapproved means that the product is inactive and not shown in Google Listings.

Merchant Center uses a separate model: Under review, Processing, Approved, Limited and Not approved. Needs Update is a separate indicator rather than a replacement for the main status. This distinction matters because a product can have approved data and still not be visible in a particular context.

When the status indicates processing or review, inspect the available details without treating the status as confirmation of success. When the product is Disapproved or Not approved, open the item-level reason and address the blocking data or policy issue. Warnings may leave products visible with limited performance, while disapprovals stop affected products from showing across Google until the issue is resolved.

Price, availability and landing-page discrepancies should receive particular attention because the submitted information needs to correspond with the store experience. After correcting data, review the resulting diagnostics rather than assuming that the product will automatically become approved.

A status-first diagnostic order

1. Identify whether the status is shown in WooCommerce or Merchant Center.
2. Read the detailed product-level issue, not only the summary label.
3. Separate processing or review from an actual data correction requirement.
4. Prioritize Disapproved or Not approved products before warnings and limited visibility.
5. Check Needs Update separately and compare the submitted data with the current product page.

WooCommerce status labels should not be treated as a complete replacement for Merchant Center’s current status model. Google controls approval and visibility, so no fixed review time or automatic approval should be promised.

Final Validation Before and After Feed Synchronization

Before changing a mapping or visibility rule across a large catalog, use a small, representative product group. This is especially important when the store contains many products or variations. A controlled test makes it easier to see whether the new rule transfers the intended values and whether it changes which products are included.

For each tested product, recheck the title, description, ID, link, image, price, availability, identifiers and relevant category attributes. Then compare the WooCommerce inclusion setting with the source, visibility, status and item-level diagnostics in Merchant Center. Save the previous mapping and record the result so that further troubleshooting has a clear reference point.

The final preflight checklist

• Basic product data is complete and the landing page matches the submitted item.
• GTIN, brand and MPN values are accurate where applicable.
• identifier_exists is used only when the product genuinely lacks assigned identifiers.
• Category-specific attributes are mapped only when relevant.
• Channel visibility allows synchronization when the product should be included.
• WooCommerce and Merchant Center diagnostics have been checked separately.

Approval of submitted data is not the same as guaranteed product visibility.

The most dependable WooCommerce Google product feed workflow is sequential: complete the basic product record, verify price and availability, map genuine manufacturer identifiers, add relevant category attributes, confirm feed inclusion, and then inspect status, visibility and item-level diagnostics in Merchant Center. WooCommerce documentation and Google documentation describe different layers of this process, so their labels should not be merged into one status system. Requirements may also vary by catalog, category, country, program and feed solution. Use a controlled product subset when changing mappings, never fabricate identifiers, and treat approval or visibility as outcomes controlled by Google rather than guaranteed results. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.