Ecommerce SEO · July 2026
Small online shops should treat product categories as customer-navigation pages first and structured data second. Google’s July 2026 update clarifies how Product.category can express both a shop’s own category and a recognised category code. The practical opportunity is cleaner product information—not a shortcut to rankings.
Reviewed by Trend Transformers · Practical website and SEO guidance for small businesses
What changed in July 2026?
Google updated its Merchant listing documentation to explain that the category property on a Product can use either plain text or a CategoryCode. That aligns webpage markup with the category fields merchants already encounter in product feeds. The change is most relevant to shops with a manageable catalogue, a clear product taxonomy and a reason to keep site and feed data consistent.
The important limitation is equally useful: schema is a description of the page, not a replacement for a well-organised catalogue. Google can choose whether and how to show enhanced search features. Start with pages that genuinely represent one purchasable product and already include price, availability, images and a clear description.
Where product category data belongs
Single product pages
Best starting point. The product, its category and the customer decision are all specific enough to describe accurately.
Product feeds
Keep merchant-defined product types and any Google category mapping consistent with the page where possible.
Navigation pages
Use useful copy, filters and internal links. Do not pretend a multi-product category page is one Product.
A practical implementation checklist
- Fix the shop taxonomy first. Use names customers understand, such as “waterproof work boots” rather than an internal stock code. Give every product one sensible primary path.
- Choose the source of truth. For WooCommerce, decide whether the product editor, feed plugin or ERP supplies category data. Two systems silently disagreeing is worse than a smaller, accurate rollout.
- Check the visible page. The product name, category context, price, availability, delivery information and return policy should be easy for a human to find.
- Add only supported, truthful markup. Use the current Google Search documentation update and the relevant product structured-data documentation as the implementation reference.
- Validate a sample. Test representative products: a simple item, a variable product and an out-of-stock product. Then inspect the rendered HTML, not only the plugin settings.
- Measure business signals. Watch impressions, product-page clicks, feed disapprovals and checkout behaviour. A prettier report is not the goal; clearer discovery and qualified visits are.
| Situation | Useful action | Avoid |
|---|---|---|
| Ten to fifty products | Manually review the core product template and top-selling pages. | Adding categories that are not visible anywhere on the page. |
| Large or changing catalogue | Map fields in the catalogue/feed system and run a scheduled sample audit. | Maintaining conflicting category names in several plugins. |
| Service business with a few shop items | Prioritise high-intent products and the service pages that explain the offer. | Turning every service page into a Product page. |
Text category or category code?
Text is usually the right first choice for a small-business website because it can reflect the words shoppers use. A category code can be valuable when a feed, marketplace or merchandising process already relies on a recognised classification. The decision is operational: use the format your source data can maintain accurately. Do not invent codes manually just to make markup look more technical.
How this fits a wider website plan
Product information works best when the rest of the website is dependable. A small-business website foundation should make pages fast to maintain, easy to navigate and readable on mobile. An SEO and GEO review can then check whether category pages, product pages, internal links and evidence on the site help the right customers make decisions.
For a small catalogue, begin with the pages that already receive enquiries or sales. For a larger catalogue, document the data flow before changing markup. That sequence avoids the familiar problem of polished schema describing stale prices, retired products or ambiguous categories.
FAQ
Will Product.category guarantee rich results?
No. Structured data helps Google understand eligible information, but Google decides how search features appear. Accurate product pages, policy pages and feed data remain more important than any single property.
Should a category archive use Product schema?
Usually no. A category archive represents a collection. Use it to help shoppers browse and link to individual products; mark up a product page when the page is about one specific purchasable product.
Can a WordPress plugin add this automatically?
Often, but automation still needs checking. Confirm that the category comes from the correct field, is present in rendered output and stays aligned with your product feed after updates.
What should a small shop do first?
Review five high-value product pages, their category wording, availability, images, delivery and return information. Fix the source data before expanding the rollout.
Sources
- Google Search Central: latest documentation updates
- Google Search Central: product structured data
- Schema.org: Product
Trend Transformers can help you prioritise product pages, information architecture and technical SEO without turning a manageable website into a maintenance burden.