Updated: July 10, 2026
On July 7, Google updated its merchant listing documentation to explain how product category structured data can carry both merchant-defined text and Google-defined category codes. The clarification matters because it gives ecommerce operators, SEO leads, and product-data teams a more precise way to compare visible product language, on-page markup, and Merchant Center data. It is implementation guidance—not a promise of rankings, rich results, or product approval.
What Is Changing in the Market
Google’s Search Central documentation update log now notes two related changes to merchant listing guidance. One explains that the Product.category property can accept plain Text values as well as CategoryCode objects. The other explains how merchants can express the effective dates of sale prices. For this article, the category clarification is the important development.
In the updated merchant listing documentation, Google describes plain text as a way to represent a merchant’s own product category, similar to the product_type attribute in Merchant Center. A CategoryCode can represent a category from Google’s product taxonomy. The documentation also allows multiple category values, which means custom grouping and a predefined taxonomy can be expressed without treating them as the same thing.
That distinction reflects how ecommerce teams already work. A store may use an internal hierarchy that fits its navigation and reporting, while a marketplace or search platform uses a separate standardized taxonomy. Clearer documentation makes it easier to map those systems deliberately instead of assuming one label serves every purpose.
Google’s Merchant Center guidance reinforces the distinction. The product_type attribute uses a merchant’s own categorization system. The google_product_category attribute uses Google’s predefined taxonomy and may be used to correct automatic categorization in specified situations. Neither should be treated as promotional copy.
Why This Matters for Nicotine-Free Botanical Aroma Products
Niche product categories often need more careful language than broad retail categories. A product name, storefront category, structured-data value, and Merchant Center field may be maintained in different systems. If those systems describe the same item in materially different ways, the result can be confusing for shoppers and difficult for an ecommerce team to audit.
For nicotine-free and tobacco-free botanical aroma products, category wording should stay factual and restrained. It can describe product format, merchandising group, or catalog organization, but it should not become a place for outcome claims. Structured data is machine-readable product information; it is not an appropriate channel for adding promises that are absent from the visible page.
A shopper browsing botanical aroma options in the Honppo shop should encounter product names and descriptions that make the format understandable. Behind the page, category values should support that same basic understanding. The role of the data is consistency, not persuasion.
This also creates a useful review boundary. The July update does not mean every store should immediately change its markup. It means teams now have clearer official documentation to compare against their current implementation. A small, documented audit is more responsible than a sitewide schema change made without checking the existing product feed, visible copy, and plugin output.
Consumer Search Intent Behind This Topic
Consumers rarely search for structured-data properties by name. Their intent appears in practical questions: What kind of product is this? How is one format different from another? What aroma options are available? Does the product contain nicotine or tobacco? Clear visible product education answers those questions directly.
Product category structured data serves a different audience: search and commerce systems interpreting the page. The best result is alignment between those two layers. A category value should not contradict the product title, description, availability, price, or storefront navigation that a person can see.
For brand-side readers, the search intent is operational. They want to know whether the new guidance requires an immediate change, how merchant-defined categories differ from Google’s taxonomy, and how to avoid introducing inconsistent data. The answer starts with an inventory of what is already published, not with a new label chosen in isolation.
What Brands Should Communicate Carefully
First, brands should avoid presenting category markup as proof that Google endorses a product or its positioning. Google’s documentation explains supported data formats. It does not certify the product, guarantee placement, or confirm advertising eligibility.
Second, a custom product type and a Google product category should not be blended casually. Merchant Center describes product_type as the merchant’s own categorization and google_product_category as a predefined Google value. Teams should record which system owns each value and why it was selected.
Third, category values should remain consistent with visible facts. If a structured-data value makes the product sound materially different from the page a shopper reads, the right response is to investigate the mismatch. Adding more markup does not resolve unclear product communication.
Finally, implementation should be tested in a limited scope. Google recommends validating structured data with its Rich Results Test and reviewing how deployed pages are seen through Search Console tools. That is a technical quality check, not a guarantee that a search feature will appear. Brands using a WordPress plugin or ecommerce platform should also identify whether the markup is generated automatically before making manual changes.
Takeaway
Google’s July 7 update gives ecommerce teams clearer language for expressing merchant-defined and Google-defined categories in product markup. The practical value is not a new promotional tactic. It is a better framework for checking whether visible product information, structured data, and Merchant Center fields describe the same item coherently.
For botanical aroma ecommerce, the lowest-risk next step is a review: identify current category values, compare them with the visible product page and feed, document any mismatch, and validate a small sample before considering broader implementation. Keep category language factual, avoid unsupported implications, and treat search appearance as an outcome that no markup can guarantee.
FAQ: Product Category Structured Data
What is the difference between a custom product type and a Google product category?
A custom product type follows the merchant’s own catalog organization. A Google product category uses Google’s predefined taxonomy. The updated documentation explains how both concepts can be represented in merchant listing markup without treating them as interchangeable.
Does adding a category guarantee a rich result?
No. Google states that structured-data features are not guaranteed to appear. Category data should be accurate and consistent because it helps describe the product, not because it promises a particular search display.
What should a niche ecommerce brand review first?
Start with the visible product title and description, current structured data, storefront grouping, and Merchant Center fields. Record any inconsistency before changing a plugin, feed, or schema output.
