Skip to main content
Zhihe Growth 中文
Platform updates · Google Shopping

Google Supports Product.category: Aligning Product Classification with Website Schema

Google's July 7, 2026 merchant-listing update documented Product.category with Text and CategoryCode values. The field can connect merchant-defined categories, Google's taxonomy and website product entities, but does not automatically earn search display.

Author: Zhihe Growth Research Center Original publication: Date of event/observation: Sources checked: 2026-07-22

Key Takeaway

Treat Product.category as governed product data, not a keyword field. Establish internal categories, verified Google Product Taxonomy mappings, market scope and variant relationships, then align visible categories, Merchant Center feeds and JSON-LD. Do not guess taxonomy codes.

What's the official change?

Google Search Central's July 7, 2026 update described Product.category support for Text and CategoryCode, aligned with Merchant Center's product_type and google_product_category attributes. This permits merchant-defined and Google-defined category information in markup.

Text can express an internal hierarchy, such as 'Industrial vision inspection equipment > Surface defect inspection'. CategoryCode expresses a code in a defined taxonomy. Neither is a place for unrelated popular keywords. Conflicts among content, breadcrumbs, navigation, product entities and feeds increase ambiguity.

Documentation update 2026-07-07
Documented property Product.category
Supported types Text or CategoryCode

Implications for International Brands

Consistent classification helps explain what products are, what they can be compared with and which tasks they serve. Chinese ERP categories, English website terms, dealer catalogs and Merchant Center fields often diverge for the same SKU. A governed mapping lets product, collection, feed and knowledge records share stable terminology.

B2B products may be organized by industry, application, process or installation method. Product.category does not replace model, sku, brand, manufacturer, material, audience or application details. Explain complex classification choices and limitations in visible content.

Keep standard CategoryCode values stable across languages and control translated Text values through a glossary to avoid inconsistent category translations across English, Spanish and Chinese sites. Product entities on corresponding hreflang pages should use the same @id or a traceable mapping, not conflicting names or identifiers.

Zhihe Growth's Assessment

Zhihe Growth recommends incorporating category into the page-level source of truth before generating schema. Define ownership, change rules, source systems and Google-facing fields; unmanaged markup quickly falls behind ERP and feed data.

Consistent categories can connect product facts with selection guides, FAQs, evidence and applications. Product pages identify the category; guides explain choices; FAQs state boundaries; evidence pages support claims with tests or certification. This supplies mutually consistent sources without guaranteeing retrieval or citations.

Implementation Checklist

  1. 1. Inventory website, ERP, PIM and Merchant Center categories and build a field mapping.
  2. 2. Assign each core product a verified merchant-defined product_type and Google taxonomy mapping; record versions and owners.
  3. 3. Use terms consistent with schema in visible breadcrumbs and category descriptions.
  4. 4. Place Product.category on the correct Product node; do not mark a collection page as one product.
  5. 5. Sample language and variant pages for consistent category, brand, SKU and canonical relationships.
  6. 6. Check syntax in Rich Results Test and Merchant Center diagnostics, then verify facts separately.

Limitations

Property support does not guarantee merchant-listing display or give CategoryCode greater ranking weight than Text. Markup must match visible content and satisfy the feature's full eligibility rules.

Taxonomies and internal categories evolve. Choose a category that represents the sold entity and explain additional applications in content rather than stacking conflicting codes.

Official sources