Google released a useful update to its e-commerce SEO documentation on July 7, 2026. It’s the kind of change that matters more than another round of decorative schema work.

According to Google’s Search documentation updates, Google added guidance for using the Product.category property in merchant listing structured data. The property now supports both Text and CategoryCode values.

For ecommerce businesses with large or complicated catalogs, this creates a clearer way to communicate product classifications to Google Search and Shopping.

What the New Product.category Guidance Covers

Google’s updated merchant listing structured data documentation connects Product.category with two familiar Merchant Center attributes:

• product_type
• google_product_category

A plain Text value represents the merchant’s custom product category. It works similarly to the product_type attribute in a Merchant Center feed.

For example, a retailer might use an internal category path such as:

Home & Garden > Outdoor Living > Patio Furniture

Google recommends keeping custom product types under 750 characters.

A CategoryCode value represents a category from Google’s official Product Taxonomy. It works similarly to the google_product_category feed attribute.

When using CategoryCode, the markup should include:

• @type set to CategoryCode
• inCodeSet pointing to a Google Product Taxonomy URL
• codeValue containing the category ID or complete category path

Google accepts either a numeric taxonomy ID or a full category path. When using a path, separate each level with a greater-than symbol.

You Can Include More Than One Category Value

The Product.category property can accept an array of values. That array can combine custom text with a Google Product Category.

This means a merchant can provide its internal classification and Google’s standardized classification within the same product markup.

For example:

"category": [
  "Women’s Clothing > Dresses > Formal Dresses",
  {
    "@type": "CategoryCode",
    "inCodeSet": "https://www.google.com/basepages/producttype/taxonomy-with-ids.en-US.txt",
    "codeValue": "2271"
  }
]

That flexibility is useful for stores whose internal catalog structure doesn’t perfectly match Google’s taxonomy.

Clean the Taxonomy Before Updating the Markup

The mistake to avoid is treating this like a copy-and-paste schema project.

If feed categories are vague, inconsistent, or outdated, adding them to structured data won’t fix the underlying catalog. It’ll simply reproduce the same problems in another format.

Before implementing Product.category, review:

• Internal category names
• Merchant Center product_type values
• Google Product Category assignments
• Product page breadcrumbs
• Collection and category page names
• Product feed rules
• Structured data templates

The same product shouldn’t sit in one category on the website, another in the product feed, and an unrelated one in its structured data.

That doesn’t mean every label must be identical. Internal merchandising categories and Google’s taxonomy serve different purposes. However, they should describe the same product accurately.

Start With High-Value Product Groups

Stores with thousands of products shouldn’t update the entire catalog without testing the implementation.

Start with a controlled group of important products. Prioritize categories that generate meaningful revenue, contain many variants, or have known feed-quality issues.

Then:

1. Map each internal category to the appropriate Google Product Category.
2. Update the product feed and structured data rules.
3. Test the markup with Google’s Rich Results Test.
4. Inspect several live URLs in Google Search Console.
5. Monitor Merchant listings reports for new errors or warnings.
6. Compare the structured data with the visible product information.

Once the test group is accurate, apply the same process to additional categories.

Don’t Confuse Better Data With a Guaranteed Ranking Boost

Google says the update helps merchants provide merchant-defined and Google-defined category information in their markup. That can enhance the product information Google receives for Search and Shopping.

However, Google hasn’t said that adding Product.category creates a direct ranking boost. Structured data can help Google understand a page and make products eligible for certain search experiences, but it doesn’t guarantee enhanced visibility.

The value comes from providing accurate and consistent product information, not adding schema properties simply because they’re available.

Better Classification Supports a Better Ecommerce Foundation

Stores with deep catalogs, extensive product variants, or years of taxonomy drift have the most cleanup work. They may also have the most to gain from creating a more consistent product-data system.

The goal isn’t to add another property that nobody maintains after launch. It’s to align product classifications across the catalog, Merchant Center feeds, page templates, and structured data.

Boring classification work often beats clever SEO theater. If your product data has become a spaghetti bowl of conflicting categories and feed rules, getting outside technical SEO help may be faster than trying to untangle it by guesswork.