Your 'Sale' category tells Google almost nothing about the product

One pair of boots belongs to “Men”, “Walking Boots”, “New In” and “Sale”. Which category should your Google Shopping feed send?

The answer depends on the field. Your merchandising categories explain how the shop is organised; Google's taxonomy classifies what the product is. Mixing those jobs can create confusing campaign groups or inappropriate data requirements.

Two fields, two purposes

google_product_category is a value from Google's taxonomy. product_type is your own classification. A useful feed can send both, provided each describes the item accurately.

Google categorises products automatically and accepts category overrides in specified cases, including category-specific requirements, campaign targeting and alcohol. Check the current Google product category guidance. Manually mapping every category is not automatically the best use of your team's time.

The last row matters because requirements can differ by product type. Use the most specific appropriate taxonomy entry rather than a broad parent selected for convenience.

Check products with several category assignments

Our Data Feed Manager maps Magento categories to Google's taxonomy and lets unmapped categories inherit from mapped parents. A product uses the first applicable mapping found while considering its deepest assigned categories.

That makes category structure consequential. A deeply nested “Sale > Last Chance” branch can win over the descriptive category if it inherits a mapping. Leave merchandising branches unmapped where appropriate and inspect the resulting feed for products that appear in both types of branch.

Do not assume equal-depth assignments will resolve according to the category your merchandising team considers primary. Preview representative products and verify the exported value.

Map the range you actually sell

Start with a few affected categories and products whose classifications are wrong or whose campaigns depend on them. Match the item, not the audience or the promotion. Then inspect mixed categories where siblings genuinely belong to different product types.

The module's mapping is category-based and global across feeds and store views. If one Magento category needs different taxonomy choices for individual products, you need a more specific category arrangement or template logic based on a product attribute. A per-feed mapping override is not provided by the category mapping screen.

Review Google's product type guidance for your own hierarchy. Keep the path useful for campaign management and reporting rather than automatically accepting a merchandising branch just because it is deepest.

Know when automatic categorisation is enough

A small catalogue with an unambiguous product type may need little manual mapping. Check Google's assigned categories and campaign requirements first. Correct the consequential errors; do not turn an optional field into a week-long exercise without a reason.

After changes, verify the exported values and subsequent Merchant Center diagnostics. Mapping does not fix invalid identifiers, wrong prices or poor images. Those checks are in our Magento Merchant Center feed guide.

Use the Data Feed Manager mapping demo with a product assigned to several categories. That is the test most likely to reveal whether the module's selection rule fits your catalogue. Preview that exported item before mapping the rest of the tree.