Tag: product taxonomy

  • Faceted Navigation: How Product Taxonomy Powers Your Filter System

    Faceted Navigation: How Product Taxonomy Powers Your Filter System

    Faceted Navigation: How Product Taxonomy Powers Your Filter System

    Faceted navigation is the filter sidebar on your category pages. It is one of the highest-impact conversion tools in ecommerce — when it works. When it does not work, customers face unusable filter options, incomplete results, and irrelevant products. The difference between a working and a broken faceted navigation system almost always comes down to the quality of the product taxonomy underneath it.

    What Is Faceted Navigation?

    Faceted navigation is a multi-dimensional filtering system that allows customers to narrow a product set by applying multiple attribute filters simultaneously. Each filter dimension — colour, size, brand, material, price range — is a “facet”.

    When a customer lands on a “Women’s Running Shoes” category page and uses the filters to select: Size = 8, Colour = Black, Brand = Asics — faceted navigation returns only the products matching all three criteria simultaneously. This is fundamentally different from traditional category browsing where customers can only drill down one level at a time.

    Faceted navigation significantly increases the probability that a customer with specific requirements finds what they are looking for — which directly increases conversion rate on category pages. But it only works if the attribute data powering the filters is structured, consistent, and complete.

    The Taxonomy-Navigation Connection

    The filter options available on any category page come directly from the attribute values assigned to products in that category. Your product taxonomy determines:

    • Which attributes exist as filters — only attributes defined in your taxonomy attribute set for that subcategory can become filters
    • Which values appear in each filter — only the distinct values present in your product data for that attribute appear as filter options
    • How many products each filter returns — if 30% of products are missing an attribute, filtering by that attribute returns an incomplete set

    This means a product taxonomy decision — what attributes to assign to a subcategory, what values to allow for each attribute — directly determines what filters customers see and how useful those filters are. For the foundation on building taxonomy correctly, see What Is Product Taxonomy and How to Build a Product Taxonomy From Scratch.

    Why Flat Taxonomy Breaks Faceted Navigation

    A flat taxonomy — one level of categories with no subcategories — forces all products in a top-level category to share the same filter set. In a home goods store with a flat structure, the “Furniture” category contains sofas, dining tables, bed frames, and desk lamps. The filter panel must serve all of them simultaneously.

    The result: a filter panel that includes Number of Seats (relevant to sofas only), Bed Size (relevant to beds only), Bulb Type (relevant to lamps only), and Seating Capacity (relevant to dining tables only) — all visible at once, none relevant to all products. Customers see a confusing, cluttered filter panel and abandon filtering entirely.

    Hierarchical taxonomy solves this by enabling category-specific filter sets. Sofas get their own filter panel with Number of Seats, Configuration, and Fabric. Lighting gets its own panel with Fitting Type, Dimmable, and IP Rating. Each subcategory shows only the filters relevant to it. The Flat vs Hierarchical Taxonomy guide covers when each approach is appropriate.

    The 4 Attribute Rules for Effective Faceted Navigation

    Rule 1: Normalise attribute values

    Every attribute that becomes a filter must use controlled, consistent values. Colour cannot have 40 variations of blue — it must have one “Blue” value (plus specific shades as a secondary attribute if needed). Size cannot have “S”, “Small”, “SM”, “size S”, and “SMALL” — it must have one normalised “S” value. Unnormalised values create filter option lists that customers cannot navigate.

    Rule 2: Ensure completeness for filter attributes

    A filter attribute that is missing from 40% of products returns a result set that excludes 40% of matching products. If a customer filters by Colour = Blue and 40% of your blue products are missing the colour attribute, the filter is hiding products the customer would buy. Run completeness checks on every filter attribute — any attribute below 90% coverage is undermining your conversion rate.

    Rule 3: Define filter attributes per subcategory, not globally

    Different subcategories need different filters. Do not apply a global attribute set across all categories. Define which attributes become filters for each subcategory — this is a taxonomy design decision, not a platform configuration decision. The attribute set in your taxonomy is what drives the filter panel.

    Rule 4: Keep facet option counts manageable

    5–15 options per filter facet is the usable range for most attributes. A colour filter with 40 options is unusable. A brand filter with 200 options needs a search-within-filter feature. Use controlled attribute value lists to prevent facet option counts from growing beyond the usable range as your catalog expands.

    Common Faceted Navigation Failures and Their Taxonomy Root Causes

    SymptomRoot CauseFix
    Filter returns zero results despite products existingProducts missing the filter attributeAttribute completeness audit + bulk fill
    Colour filter has 40+ optionsUnnormalised colour valuesColour normalisation — map to controlled value list
    Filter returns wrong product typesProducts miscategorised in wrong subcategoryReclassify affected products
    Same filter appears on every category regardless of relevanceFlat taxonomy — no subcategory-specific attribute setsMigrate to hierarchical taxonomy with per-subcategory attribute definitions
    Filter option counts are highly inconsistentAttribute values assigned inconsistently across catalogControlled vocabulary enforcement + bulk standardisation

    The root cause of most faceted navigation failures is not a platform problem — it is a product data problem. The Completeness Checker identifies which attribute gaps are most significant across your catalog. The PIM Readiness Score gives you a full picture of where your taxonomy and attribute governance has gaps affecting both faceted navigation and channel performance. Also see How Bad Taxonomy Kills Your Site Search for the broader impact beyond filters.

    Frequently Asked Questions

    What is faceted navigation in ecommerce?

    Faceted navigation is a filtering system that allows customers to narrow a product set by applying multiple attribute filters simultaneously — for example, filtering shoes by Size = 8, Colour = Black, Brand = Nike, and Style = Running to show only matching products. Each filter dimension is a “facet” derived from structured product attributes in your taxonomy.

    Why does product taxonomy affect faceted navigation?

    Because the filters on any category page come directly from the attribute sets assigned to that category in your taxonomy. If your taxonomy assigns different attributes to different products in the same category, or uses inconsistent attribute values, the filter options become incomplete or unusable. The taxonomy is the data layer that faceted navigation is built on.

    What is the difference between faceted navigation and site search?

    Site search retrieves products matching a keyword query. Faceted navigation filters an existing product set by attribute values. They work together — a customer searches “running shoes” (site search), then uses facets to filter by size and colour (faceted navigation). Both depend on the same underlying product data quality, which means taxonomy problems typically affect both simultaneously.

    How many filter options should each facet display?

    5–15 options per facet is the usable range. Fewer than 5 suggests the attribute is not differentiated enough to warrant a filter. More than 15–20 options on a single facet is typically unusable — customers cannot scan that many options efficiently. Use controlled attribute value lists and normalisation to keep facet option counts manageable as your catalog grows.

  • Free Product Taxonomy Template: Download for 5 Industries (2026)

    Free Product Taxonomy Template: Download for 5 Industries (2026)

    Free Product Taxonomy Template: Download for 5 Industries (2026)

    Building a product taxonomy from scratch takes days. Validating that it maps correctly to Google’s taxonomy, includes the right attribute sets per subcategory, and uses normalised attribute values takes longer. This template gives you a pre-built, working starting point for five industries — so you spend your time adapting rather than building from zero.

    The template is free. No email required for the preview version. The full editable template is available via LynkPIM’s free plan.

    What’s in the Template

    The template is a structured Google Sheets file with five tabs — one per industry. Each tab contains:

    • Category hierarchy (Levels 1–4) — pre-built category structure from department level down to product type, based on real ecommerce catalog patterns for each industry
    • Required attribute sets per subcategory — the specific attributes that must be filled for a product in that subcategory to be considered complete (e.g. Colour, Size, Material, Gender for fashion; Processor, RAM, Storage for electronics)
    • Recommended attribute sets — additional attributes that improve search, filtering, and channel performance without being strictly required
    • Normalised attribute value lists — controlled vocabulary for colour, size, material, and other attributes that require consistency across the catalog
    • Google product category ID mapping — the correct leaf-node GPC ID for every subcategory, ready to use directly in your feed

    Tab 1: Fashion and Apparel Template

    The fashion tab covers: Women’s Clothing, Men’s Clothing, Kids’ Clothing, Footwear, Accessories, Swimwear, and Lingerie & Nightwear — down to Level 4 (Midi Dresses, Rain Jackets, Running Shoes etc.).

    Attribute sets include the full apparel requirements for Google Shopping (gender, age_group, color, size, size_system, item_group_id) plus apparel-specific attributes like neckline, length, occasion, and sleeve length. The colour normalisation table maps 200+ common fashion colour names to their normalised values for filters and feeds.

    Full details on fashion taxonomy requirements in the Fashion Taxonomy guide.

    Tab 2: Electronics Template

    The electronics tab covers: Computers & Laptops, Smartphones & Wearables, Audio, TV & Home Cinema, Cameras & Photography, Gaming, Components & Storage, and Cables & Accessories.

    Attribute sets go deep on technical specifications — processor family, RAM, storage type, screen size, connectivity standards for laptops; driver size, noise cancellation type, codec support for headphones; IP rating, connectivity, battery capacity for smartphones. Compatibility attribute fields are included for all accessory subcategories.

    Full details in the Electronics Taxonomy guide.

    Tab 3: Home Goods and Furniture Template

    The home goods tab covers: Furniture, Lighting, Bedding & Textiles, Kitchen & Dining, Storage & Organisation, Home Decor, and Outdoor.

    Attribute sets include the dimension fields critical for furniture (Width, Height, Depth, Weight, Assembly Required, Flat Pack), material normalisation mapping 150+ home goods material names to controlled values, and the two-field approach to style attributes (marketing name vs normalised filter value).

    Full details in the Home Goods Taxonomy guide.

    Tab 4: Food and Beverage Template

    The food & beverage tab covers: Fresh & Chilled, Ambient Grocery, Beverages, Frozen, Health & Nutrition, Snacks & Confectionery, Bakery, and Alcohol.

    This tab includes the full 14-allergen attribute set (with Contains / May Contain / Free From value options), dietary attribute fields (Vegan, Vegetarian, Gluten-Free, Halal, Kosher, Organic), shelf life and storage type fields, and the nutritional attribute set required by UK FIC regulations.

    Full details in the Food & Beverage Taxonomy guide.

    Tab 5: B2B Industrial Template

    The B2B industrial tab covers: Fasteners & Fixings, Pneumatics & Hydraulics, Electrical Components, Safety Equipment, Tools & Machinery, MRO Supplies, and Pipe & Tube.

    Attribute sets include the technical specification fields critical for industrial products (thread standard, material grade, pressure rating, IP rating, temperature range), compliance certification attributes (CE marking, ATEX, RoHS, REACH), and the UNSPSC classification mapping for each subcategory.

    Full details in the B2B Industrial Taxonomy guide.

    How to Adapt the Template to Your Catalog

    1. Copy the template to your Google Drive (File → Make a Copy)
    2. Delete subcategories you do not carry — if you do not sell footwear, delete the footwear rows from the fashion tab
    3. Add subcategories specific to your range — if you sell a product type not covered, add a row and fill in the attribute set manually using the existing rows as a format guide
    4. Update attribute value lists — customise the normalised colour, size, and material lists to match your actual product data
    5. Verify Google product category IDs — cross-check any subcategories you have modified against Google’s current taxonomy file to confirm the GPC ID is still the most specific available match

    Before building on top of this template, take the PIM Readiness Score to understand where your current product data governance has gaps — the template tells you what your taxonomy should look like, the readiness score tells you how far your current data is from that standard.

    Download the full editable template: lynkpim.app/pricing — available on the free plan, no credit card required.

    Frequently Asked Questions

    What is included in the free product taxonomy template?

    Five industry tabs (Fashion & Apparel, Electronics, Home Goods & Furniture, Food & Beverage, B2B Industrial), each with: full category hierarchy (Levels 1–4), required and recommended attribute sets per subcategory, normalised attribute value lists, and Google product category ID mapping for every subcategory.

    What format is the template in?

    Google Sheets with five tabs — one per industry. It can be downloaded as an Excel file or used directly in Google Sheets. Each tab is a working reference document designed to be adapted, not just read.

    Can I use the template for a mixed catalog across multiple industries?

    Yes. Take the relevant tabs from each industry and merge them into your own taxonomy document. The Google product category mapping in each tab is self-contained and works independently. If you sell both electronics and home goods, combine those two tabs into a single working taxonomy.

    How do I customise the template for my specific catalog?

    Copy to your Google Drive, then: delete subcategories you do not carry, add subcategories specific to your range using existing rows as a format guide, update attribute value lists to match your actual product data, and verify GPC IDs against Google’s current taxonomy file for any subcategories you modify or add.

  • How Bad Product Taxonomy Kills Your Site Search (and What to Fix First)

    How Bad Product Taxonomy Kills Your Site Search (and What to Fix First)

    How Bad Product Taxonomy Kills Your Site Search (and What to Fix First)

    Site search is where buyers with high purchase intent go. A customer using your site search already knows they want something — they are not browsing, they are trying to buy. When that search fails, returns irrelevant results, or shows broken filters, that customer is gone. And bad product taxonomy is the reason it fails more often than any other factor.

    This article covers the exact ways taxonomy problems break site search, how to identify which ones are costing you the most, and what to fix first for the fastest conversion impact.

    The 5 Ways Bad Taxonomy Destroys Site Search

    1. Zero-result searches for products that exist

    A customer searches for “navy waterproof jacket”. You have three of them in stock. But they do not appear in the results because the colour attribute is stored as “Storm Blue” in one product and “Dark Navy” in another — neither matches “navy”. The filter engine cannot retrieve products it cannot match.

    This is the most costly taxonomy failure because it is invisible. Your product catalog tells you nothing is wrong. Your search results tell the customer nothing exists. They leave and buy elsewhere.

    2. Broken filters from inconsistent attribute values

    Filters are only as good as the consistency of the attribute data they draw from. If your colour attribute has values like “Navy”, “Dark Navy”, “Midnight Navy”, “Navy Blue”, “Storm Blue”, “Deep Blue”, and “Steel Blue” — your colour filter becomes a list of 40+ options that customers cannot navigate. They give up on filtering and resort to keyword search, which then fails for the reason above.

    The same problem affects size (S, Small, SM, Sm, size S), material (Cotton, 100% Cotton, Pure Cotton, Cotton Rich), and almost every attribute that is entered manually without controlled values.

    3. Wrong products in search results

    A product placed in the wrong category surfaces in the wrong filter context. A customer filtering “Women’s Shoes” should not see men’s boots that were miscategorised. This damages trust immediately — if your search returns obviously wrong products, customers lose confidence in the entire catalog.

    4. Missing attributes creating empty filter panels

    If 30% of your sofa products are missing the “Number of Seats” attribute, your seating filter only covers 70% of your sofas. A customer filtering for 3-seater sofas gets an incomplete result set and may conclude you do not stock what they need — when you do, it is just missing the attribute that would surface it.

    5. Flat taxonomy making all filters identical

    A flat taxonomy with no subcategories means all products in a top-level category share the same filter panel. A home goods store with a flat structure shows size, colour, and material filters for sofas, ceiling lights, and kitchen knives simultaneously — none of the filters are relevant to all products, so none of them are useful to anyone.

    Hierarchical taxonomy enables category-specific filter sets — sofas show Number of Seats, Fabric, and Configuration; lighting shows Fitting Type, Bulb Included, and Dimmable. The difference in filter usability is dramatic. See Flat vs Hierarchical Taxonomy for when each applies.

    How to Find Which Taxonomy Problems Are Hurting You Most

    Before fixing anything, identify where the problem is largest. Three data sources tell you this:

    1. Site search zero-results report

    Extract your zero-result search queries from your analytics platform. Every query that returned zero results is a potential taxonomy failure. Match these queries against your product catalog — if the product exists but did not surface, the cause is almost always a missing or inconsistent attribute value.

    2. High-exit filter paths

    Look at which filter combinations have the highest bounce or exit rates. If customers who filter by “Blue” then immediately leave, the blue filter results are irrelevant or incomplete. This points to a colour normalisation problem.

    3. Attribute completeness audit

    Run an attribute completeness check across every subcategory. What percentage of products in each subcategory have the Size attribute? The Colour attribute? The Material attribute? Any subcategory below 80% completeness on its required attributes has broken filters. Use the Completeness Checker to run this across your full catalog.

    What to Fix First — Priority Order

    1. Colour normalisation (fastest impact, lowest effort) — create a controlled colour value list (Blue, Red, Green, Black, White, Grey, Yellow, Pink, Purple, Brown, Orange, Beige) and remap all existing colour values to it. This immediately fixes colour filters across all affected products.
    2. Fill missing required attributes (high impact, medium effort) — identify which attributes are missing at scale using your completeness checker, then bulk-fill them. Start with the subcategories that have the most products and the lowest completeness scores.
    3. Reclassify miscategorised products (medium impact, low effort per product) — use your zero-results report to identify which searches are failing and cross-reference against product records to find miscategorised items. Fix them in batches by subcategory.
    4. Restructure flat to hierarchical (highest long-term impact, highest effort) — this is the right fix if your underlying structure is flat. It takes longer but compounds — every future product benefits from the correct structure without manual intervention. See How to Build a Product Taxonomy From Scratch for the build process.

    The PIM Readiness Score identifies exactly where your current taxonomy and attribute data governance has gaps — and gives you a prioritised action list to work from. Free, takes 5 minutes. Start there before deciding which of the four fixes to tackle first.

    Frequently Asked Questions

    How does bad product taxonomy affect site search?

    Bad taxonomy causes zero-result searches (products exist but are miscategorised or missing attributes), broken filters (attributes not consistently assigned), and irrelevant search results (products from wrong categories surface). Customers see these as a broken site — they do not know the cause is data quality.

    What is the fastest taxonomy fix for improving site search conversion?

    Colour normalisation delivers the fastest visible impact. If your colour attribute has 40+ inconsistent values instead of a controlled list of 8–12 normalised values, your colour filter is broken for every customer who uses it. Normalising to a controlled list immediately fixes colour-based filtering across all affected products without changing your catalog structure.

    How do I find which taxonomy problems are hurting my site search most?

    Extract your zero-result search queries from your analytics platform — every query that returned nothing for a product that exists is a taxonomy failure. Cross-reference against your product catalog to identify the specific attribute gaps. Also run an attribute completeness audit by subcategory to find where required attributes are most frequently missing.

    Can site search work well with a flat taxonomy?

    Only for very small catalogs under ~200 products. Once the catalog grows, a flat taxonomy forces all products in a top-level category to share the same filter panel regardless of product type — making filters irrelevant and unusable. Customers abandon filtered search and rely on keyword search, which then fails due to inconsistent attribute values.

  • Google Product Category vs Your Internal Taxonomy: What’s the Difference?

    Google Product Category vs Your Internal Taxonomy: What’s the Difference?

    Google Product Category vs Your Internal Taxonomy: What’s the Difference?

    Two taxonomies. One product. This is the reality of modern ecommerce — every product needs to live somewhere in your internal catalog structure, and simultaneously needs to be classified in Google’s own taxonomy for Shopping performance. These two systems serve completely different purposes and should never be confused for each other.

    Your Internal Taxonomy — What It’s For

    Your internal product taxonomy is the classification system you design for your own business. It reflects how your team organises products, how your customers browse your site, and how your buying and merchandising teams think about the catalog.

    It uses your naming conventions. “Outerwear” might be at Level 2 in your taxonomy. “Men’s Rain Jackets” might be your Level 3 subcategory. These names work for your team because they reflect how you buy, stock, and sell these products.

    Your internal taxonomy also drives your site navigation, search filters, and internal reporting. It is designed for humans — your buyers, your customers, and your ecommerce team. For a full guide on building it correctly, see What Is Product Taxonomy and How to Build a Product Taxonomy From Scratch.

    Google’s Product Category Taxonomy — What It’s For

    Google’s product category taxonomy is a fixed, hierarchical classification system that Google uses to understand what your product is. It has over 6,000 categories across up to 7 levels, maintained by Google and updated periodically.

    It is designed for Google’s matching algorithm — not for humans. When you assign a product to “Apparel & Accessories > Clothing > Outerwear > Coats & Jackets” (ID: 212), you are telling Google’s algorithm which auction pool this product belongs in, which additional attribute requirements apply, and how to match it to buyer search queries.

    You do not modify it. You map your products to it. The full taxonomy ID list is available publicly and should be used as a reference, not a foundation for your own catalog structure. Full details in the Google Product Category Taxonomy guide.

    The Key Differences

    Internal TaxonomyGoogle Product Category
    Who designs itYouGoogle
    Who it servesYour team and customersGoogle’s matching algorithm
    Naming conventionYour own namingGoogle’s fixed naming
    How deep3–4 levels typicalUp to 7 levels, 6,000+ nodes
    Where it livesYour PIM / platform / spreadsheetThe google_product_category feed field
    What it powersNavigation, filters, internal ops, reportingShopping auction relevance, attribute requirements, tax rules
    How often it changesWhen your catalog evolves1–2 times per year by Google
    Can you modify itYes — it’s yoursNo — you only map to it

    Why You Need Both — and Why They’re Different

    A common mistake is trying to build an internal taxonomy that mirrors Google’s. This creates several problems:

    • Google’s naming doesn’t match customer language — “Coats & Jackets” is fine for an algorithm but might not reflect how your buyers describe products on your site
    • Google’s structure doesn’t match your business — your business may organise products by season, by brand, by collection, or by customer segment in ways that don’t correspond to Google’s classification
    • Google updates break your internal structure — if your navigation and filters are built on Google’s taxonomy, every Google taxonomy update requires changes to your site

    Your internal taxonomy should be built for your customers and your team. Google’s taxonomy should be mapped to from your internal taxonomy — a separate, maintained mapping document that connects your subcategories to the correct Google category IDs.

    How to Build the Mapping Document

    The mapping document is a simple table: your internal subcategory name on the left, the corresponding Google category ID on the right. This is the only connection you need between your taxonomy and Google’s.

    1. List every subcategory in your internal taxonomy
    2. For each subcategory, search Google’s taxonomy file for the most specific matching leaf node
    3. Record the numeric ID — not the text path string
    4. Apply the ID to all products in that subcategory programmatically — not product by product
    5. Review annually when Google publishes taxonomy updates

    This approach means a taxonomy change on Google’s side only requires updating the mapping document, not restructuring your internal taxonomy, your site navigation, or your product records.

    The product_type Field — the Third Layer

    Google Shopping feeds support a third category-related field: product_type. Unlike google_product_category, this is a free-form field you control completely.

    Use product_type to include your internal taxonomy path in the feed — for example, “Outerwear > Men’s Outerwear > Rain Jackets”. This value does not affect Google’s matching algorithm but it does appear as a segmentation option in Google Ads, letting you create Shopping campaigns and bid strategies based on your own category structure rather than Google’s.

    This means you can have all three in your feed simultaneously:

    • google_product_category: 212 (tells Google what the product is)
    • product_type: Outerwear > Men’s Outerwear > Rain Jackets (your internal naming for campaign segmentation)
    • Internal taxonomy: stored in your PIM, driving your site and your team’s workflow

    Check the Flat vs Hierarchical Taxonomy guide to ensure your internal structure is appropriately deep before building your mapping document. Take the PIM Readiness Score to see how well your current product data governance supports this dual-taxonomy approach.

    Frequently Asked Questions

    Do I need both an internal taxonomy and Google product categories?

    Yes. Your internal taxonomy serves your team and customers using your naming conventions. Google’s taxonomy serves their matching algorithm using their naming conventions. You need both, connected by a mapping document that translates your subcategory names to Google category IDs.

    Should I build my internal taxonomy to match Google’s?

    No. Build your internal taxonomy for how your team and customers think about your products. Keep the mapping to Google’s taxonomy in a separate document. If you build your internal structure to mirror Google’s, you tie your site navigation and team workflows to a taxonomy you don’t control — and every Google update risks breaking something in your catalog.

    What is the product_type field and how does it relate to my internal taxonomy?

    The product_type field is a free-form field in your Google Shopping feed where you include your own internal category path. It does not affect Google matching but enables campaign segmentation in Google Ads based on your own taxonomy naming. It is the bridge between your internal taxonomy and your Google Shopping campaigns.

    How often does Google’s taxonomy change and how does that affect my internal taxonomy?

    Google updates its taxonomy 1–2 times per year. These changes do not affect your internal taxonomy at all — they only affect the mapping document. Using numeric IDs in your feed (not text path strings) means most updates have zero impact on your feed, since IDs remain valid even when Google renames a category path.

  • Google Product Category Taxonomy: The Complete 2026 Guide

    Google Product Category Taxonomy: The Complete 2026 Guide

    Google Product Category Taxonomy: The Complete 2026 Guide

    Google’s product category taxonomy is one of the most impactful — and most misused — attributes in Google Shopping feeds. Every product in your feed needs a google_product_category value. Get it right and your products appear in the correct auctions for relevant searches. Get it wrong and you are competing for irrelevant traffic at the wrong price.

    This guide covers how Google’s taxonomy works, how to find the right category for any product, and the most common mapping mistakes costing stores auction performance.

    What Is Google’s Product Category Taxonomy?

    Google’s product taxonomy is a hierarchical classification system with over 6,000 categories across up to 7 levels of depth. Every product sold through Google Shopping must be classified within this taxonomy using the google_product_category feed attribute.

    Unlike your own internal product taxonomy — which you design for your team and customers — Google’s taxonomy is fixed. You do not modify it. You map your products to it. The full taxonomy file is publicly available and updated periodically. Understanding how it relates to your own internal category structure is covered in detail in the Google Product Category vs Internal Taxonomy guide.

    How google_product_category Affects Shopping Performance

    The category value you assign determines which auction pool your product enters. Google uses it to:

    • Match products to relevant search queries — a product in the correct leaf-node category is matched to more specific searches
    • Set category-specific requirements — some categories (apparel, alcohol, healthcare) have additional required attributes that only apply once Google knows your product’s category
    • Power Shopping filters — the filter options available to buyers on Shopping results pages are partly driven by the category the product is in
    • Determine tax and shipping rules — in some markets, tax treatment is category-dependent

    The difference between a parent category and a leaf node is significant. A product mapped to “Apparel & Accessories” (ID: 166) enters a much broader auction pool than the same product mapped to “Apparel & Accessories > Clothing > Outerwear > Coats & Jackets” (ID: 212). The leaf-node product appears for more specific queries at lower CPCs and with higher relevance scores.

    The taxonomy Attribute: ID vs Text String

    Google accepts google_product_category in two formats:

    • Numeric ID: 212 — the unique identifier for that category node. Stable across taxonomy updates.
    • Full path string: Apparel & Accessories > Clothing > Outerwear > Coats & Jackets — human-readable but can break if Google renames any node in the path.

    Use the numeric ID. If Google restructures a category path or renames a node, the numeric ID continues to resolve correctly. The text path string will return an error or be ignored if the exact wording changes.

    How to Find the Right Category ID

    1. Download the official taxonomy file from google.com/basepages/producttype/taxonomy-with-ids.en-GB.txt
    2. Open it in a spreadsheet or text editor. Each row shows: ID - Full Path
    3. Search (Ctrl+F) for the most specific term describing your product — e.g. “Rain Jacket”, “Sofa”, “NVMe SSD”
    4. Review all matching rows and select the most specific leaf node that accurately describes your product
    5. Record both the ID and the full path — use the ID in your feed, keep the path in your mapping document for human reference

    Most Common google_product_category Mistakes

    MistakeImpactFix
    Using a parent category instead of leaf nodeReduced relevance, wrong auction poolAlways map to the deepest available level
    Using text path instead of numeric IDBreaks when Google renames categoriesSwitch to numeric IDs in your feed
    One category for all productsAll products compete in wrong auctionsMap per subcategory, not per store
    Mapping manually per productInconsistency, errors at scaleMap subcategory → GPC once, apply programmatically
    Never updating after taxonomy changesStale mappings, possible errorsReview taxonomy file annually

    Category Mapping by Industry — Quick Reference

    Product TypeGoogle Category IDFull Path
    Women’s running jacket5598Apparel & Accessories > Clothing > Activewear > Track Jackets & Hoodies
    Men’s leather Oxford shoes187Apparel & Accessories > Shoes > Men’s Shoes > Oxfords
    Gaming laptop328Electronics > Computers > Laptops
    True wireless earbuds3989Electronics > Audio > Headphones > In-Ear Headphones
    3-seater sofa443Furniture > Sofas & Sectionals
    King duvet set569Home & Garden > Linens & Bedding > Duvet Covers
    Ground coffee5775Food, Beverages & Tobacco > Beverages > Coffee
    NVMe SSD1723Electronics > Computers > Computer Components > Hard Drives & Storage > Solid State Drives

    product_type vs google_product_category — What’s the Difference?

    These two attributes are frequently confused. They serve completely different purposes:

    • google_product_category — uses Google’s fixed taxonomy. Affects auction relevance, Shopping matching, and category-specific attribute requirements. Required.
    • product_type — a free-form field you define using your own category naming. Does not affect Google matching. Can be used for campaign segmentation in Google Ads (similar to custom labels). Optional but recommended.

    Both can coexist in the same feed. Use google_product_category to tell Google what your product is. Use product_type to reflect your own internal category naming for campaign management purposes.

    For how to build and maintain your internal taxonomy alongside Google’s, see What Is Product Taxonomy and How to Build a Product Taxonomy From Scratch. To generate a correctly structured feed with category mapping applied, use the Google Shopping Feed Generator.

    Frequently Asked Questions

    Is google_product_category required in Google Shopping feeds?

    Yes, it is required for all products. Products submitted without it may still appear but Google auto-assigns a category — almost always a broad parent level that will underperform compared to the correct leaf-node mapping.

    Should I use the numeric ID or the text string?

    Use the numeric ID. It is stable across taxonomy updates — if Google renames or restructures a category path, the ID continues to resolve correctly. The text path string can break silently if Google changes the exact wording of any node.

    What happens if I use the wrong google_product_category?

    Wrong or overly broad categories reduce Shopping relevance — your products appear for fewer relevant queries and compete in incorrect auction pools. A jacket in “Apparel & Accessories” (parent) is in a completely different and far broader auction than the same jacket in “Apparel & Accessories > Clothing > Outerwear > Coats & Jackets” (leaf node).

    How often does Google update its product taxonomy?

    Typically 1–2 times per year. Numeric IDs remain valid across updates but text path strings may become outdated. Review the taxonomy file annually and after major Google Merchant Center announcements.

    What is the difference between google_product_category and product_type?

    google_product_category uses Google’s fixed taxonomy and directly affects auction relevance and matching. product_type is a free-form field you define using your own naming — it does not affect Google matching but can be used for campaign segmentation in Google Ads similar to custom labels.

  • Product Taxonomy for Food and Beverage Ecommerce: Full Setup Guide

    Product Taxonomy for Food and Beverage Ecommerce: Full Setup Guide

    Product Taxonomy for Food and Beverage Ecommerce: Full Setup Guide

    Food and beverage ecommerce has a taxonomy challenge that no other category faces at the same level: regulatory compliance. Allergen data, nutritional information, country of origin, and storage requirements are not optional attributes — they are legal requirements in most markets. A food taxonomy that gets the category hierarchy right but misses the compliance attribute layer is both incomplete and a legal liability.

    This guide covers how to build a food and beverage taxonomy that works for customers, for Google Shopping, and for regulatory compliance simultaneously.

    Why Food Taxonomy Needs a Compliance Layer

    Food ecommerce has obligations that other ecommerce categories do not. In UK and EU markets, the Food Information for Consumers Regulation (FIC) requires that 14 major allergens are clearly identified on all pre-packaged food products sold online. Nutritional information per 100g is also required for most food products.

    This means your product taxonomy must support a compliance attribute layer — not just a category hierarchy. Every food product record needs structured allergen fields, nutritional values, and country of origin. These cannot be buried in free-text descriptions — they must be structured attributes that can be displayed, filtered, and audited.

    For the foundational taxonomy structure applicable to all industries before adding food-specific requirements, see How to Build a Product Taxonomy From Scratch.

    Recommended Top-Level Structure for Food and Beverage

    Level 1Level 2 ExamplesLevel 3 Examples
    Fresh & ChilledDairy, Meat & Poultry, Fruit & Vegetables, Ready Meals, DeliMilk, Cheese, Yogurt, Butter & Spreads
    Ambient GroceryPasta & Rice, Tinned Goods, Sauces & Condiments, Oils & VinegarsDried Pasta, Tinned Tomatoes, Pasta Sauces
    BeveragesCoffee, Tea, Soft Drinks, Juices, Water, Hot ChocolateGround Coffee, Whole Bean, Coffee Pods
    FrozenFrozen Meals, Frozen Meat, Ice Cream, Frozen Vegetables, Frozen BakeryFrozen Pizza, Frozen Fish Fillets
    Health & NutritionProtein Supplements, Vitamins, Sports Nutrition, SuperfoodsWhey Protein, Plant Protein, BCAA
    Snacks & ConfectioneryCrisps, Nuts, Chocolate, Sweets, Cereal Bars, BiscuitsDark Chocolate, Milk Chocolate, Vegan Chocolate
    BakeryBread, Pastries, Cakes, Gluten-Free BakerySourdough, White Sliced, Seeded Loaves
    AlcoholWine, Beer & Cider, Spirits, Low & No AlcoholRed Wine, White Wine, Champagne & Sparkling

    The 14 Mandatory Allergen Attributes

    Each of the 14 major allergens must be a separate structured attribute on every food product record with three possible values:

    • Contains — the allergen is a declared ingredient
    • May Contain — manufactured in a facility that also processes this allergen (cross-contamination risk)
    • Free From — the product does not contain and is not cross-contamination risk for this allergen

    The 14 allergens are: Gluten, Crustaceans, Eggs, Fish, Peanuts, Soybeans, Milk, Nuts, Celery, Mustard, Sesame, Sulphur Dioxide & Sulphites, Lupin, Molluscs.

    Structured allergen attributes enable allergen-specific filtering (customers can filter “Nut-Free” or “Gluten-Free”) and allow your compliance team to audit allergen data across the full catalog efficiently. Free-text allergen data in descriptions cannot be audited or filtered.

    Dietary Attribute Set

    Beyond the mandatory allergen layer, structured dietary attributes drive high-value customer filtering. These are among the most-used filters on food ecommerce sites:

    • Vegan — contains no animal products or by-products
    • Vegetarian — contains no meat or fish
    • Gluten-Free — certified gluten-free (below 20ppm threshold)
    • Dairy-Free — contains no milk or dairy derivatives
    • Nut-Free — contains no nuts and produced in a nut-free facility
    • Halal — certified Halal
    • Kosher — certified Kosher
    • Organic — certified organic (specify certification body)
    • No Added Sugar
    • Low Calorie (define threshold — e.g. <100kcal per serving)

    Shelf Life and Storage Attributes

    Storage and shelf life attributes serve both customer information and operational fulfilment routing. Products with different storage requirements (ambient, chilled, frozen) need to be identifiable programmatically — your fulfilment system needs to know which warehouse zone and which delivery service applies to each product.

    • storage_type: ambient / chilled (2-8°C) / frozen (-18°C)
    • shelf_life_days: total shelf life from production date
    • minimum_remaining_life_on_despatch: minimum days remaining when shipped (e.g. 60% of total shelf life)
    • best_before_guidance: “Best Before”, “Use By”, “Display Until” — the label type

    Nutritional Attributes (Required for UK/EU Markets)

    Under UK FIC regulations, the following nutritional values are required per 100g/100ml on food product pages:

    • Energy (kJ and kcal)
    • Total Fat (g)
    • Saturated Fat (g)
    • Carbohydrates (g)
    • Sugars (g)
    • Protein (g)
    • Salt (g)

    These must be structured attributes in your product data — not embedded in label images. Structured data can be indexed by search engines, displayed dynamically, and audited for completeness. Image-embedded nutritional data cannot.

    Google Product Category Mapping for Food

    ProductCorrect Google Category
    Ground coffeeFood, Beverages & Tobacco > Beverages > Coffee
    Whey protein powderHealth & Beauty > Health Care > Fitness Nutrition > Protein Supplements
    Gluten-free pastaFood, Beverages & Tobacco > Food Items > Grains, Rice & Pasta
    Red wineFood, Beverages & Tobacco > Beverages > Alcoholic Beverages > Wine
    Vegan chocolate barFood, Beverages & Tobacco > Food Items > Sweets & Snacks > Candy & Chocolate

    Managing allergen data, nutritional values, and shelf life attributes at scale across a large food catalog requires a system that enforces attribute completeness before products are published. The PIM Readiness Score identifies exactly where your current data governance has gaps. Download the free Taxonomy Template at lynkpim.app — the Food & Beverage tab includes the full category hierarchy and compliance attribute set.

    For context on how food taxonomy compares structurally to another attribute-heavy category, see the Home Goods Taxonomy guide.

    Frequently Asked Questions

    Are allergen attributes legally required for food ecommerce in the UK?

    Yes. Under the UK Food Information for Consumers Regulation (FIC), all 14 major allergens must be clearly indicated on pre-packaged food products sold online. Structured allergen attributes ensure these are displayed accurately, consistently, and can be audited across the full catalog. Free-text allergen data in descriptions does not meet this standard reliably.

    How should dietary attributes like Vegan and Gluten-Free be structured?

    Dietary attributes should be structured boolean or controlled-value attributes on every food product — not free-text descriptions. Structured dietary attributes enable accurate site filtering, prevent manual errors when products are updated, and allow your compliance team to audit attribute accuracy across the full catalog at any time.

    Should food categories be organised by cuisine type or by food category?

    Organise by food type (Dairy, Bakery, Beverages) rather than cuisine (Italian, Asian, Mexican) for the primary taxonomy structure. Cuisine and origin work well as filterable attributes. Type-based categories map directly to Google’s taxonomy and match how customers search for food online — “gluten-free pasta” not “Italian gluten-free”.

    What shelf life attributes should food products have?

    Include storage_type (ambient / chilled / frozen), shelf_life_days (total from production), minimum_remaining_life_on_despatch (days remaining when shipped to customer), and best_before_guidance (Best Before / Use By / Display Until). These drive fulfilment routing, customer-facing freshness communication, and return rate management.

    Does Google Shopping allow food and beverage products?

    Yes, food and beverage products are allowed in Google Shopping with some exceptions. Alcohol requires age verification compliance and may be restricted by country targeting. Supplements and health food products must comply with local regulations. Most ambient grocery, beverages, and specialty food products can be advertised without restrictions — verify your specific product types in Google Merchant Center’s product data specification.

  • Product Taxonomy for B2B Industrial Products: The Complete Guide

    Product Taxonomy for B2B Industrial Products: The Complete Guide

    Product Taxonomy for B2B Industrial Products: The Complete Guide

    B2B industrial product taxonomy is the most technically demanding category structure in ecommerce. Industrial buyers know exactly what they need — often down to a part number, material grade, and certification standard. A taxonomy that cannot surface products by technical specification loses B2B buyers immediately, because they will not browse to find the right hydraulic fitting. They will go somewhere that lets them specify it.

    This guide covers how to build an industrial taxonomy that works for procurement buyers, engineers, and maintenance teams — not just for general consumers.

    Why B2B Industrial Taxonomy Differs from B2C

    • Part number is the primary identifier: B2B buyers often search by manufacturer part number (MPN) or internal reference code. Your taxonomy must support this lookup path, not just category browsing.
    • Technical specifications are purchase criteria: An industrial buyer does not choose a bolt by colour. They specify thread standard (M6, M8, M10), material grade (Grade 8.8, 304 stainless, A4 marine grade), head type (hex, socket cap, button head), and length in millimetres.
    • Compliance is non-negotiable: Many industrial products require specific certifications (CE, ATEX, RoHS, REACH, IP ratings) and buyers will not purchase without visible certification data.
    • Volume and price structures: B2B products often have quantity-break pricing and minimum order quantities — these need to be attributes, not ad hoc product descriptions.

    For the foundational taxonomy build process before B2B-specific requirements, see How to Build a Product Taxonomy From Scratch.

    Start With a Standard Classification System

    Unlike B2C categories where you build from customer search behaviour, B2B industrial taxonomy should be anchored to an established classification standard. Do not build from scratch.

    • UNSPSC (United Nations Standard Products and Services Code) — widely used in procurement and public sector. Free to access at unspsc.org. Four-level hierarchy: Segment → Family → Class → Commodity.
    • eCl@ss — European standard, widely used in manufacturing and industrial supply chains. More granular than UNSPSC for technical components.
    • GS1 GPC (Global Product Classification) — used in retail and wholesale supply chains. Better for MRO and maintenance products than for pure manufacturing components.

    You do not need to expose these classification codes to buyers. Use them as the structural backbone of your internal taxonomy, then create buyer-friendly category names as a display layer on top.

    Recommended Top-Level Structure for Industrial

    Level 1Level 2 ExamplesLevel 3 Examples
    Fasteners & FixingsBolts, Nuts, Washers, Anchors, Rivets, ScrewsHex Bolts, Socket Cap Screws, Coach Bolts
    Pneumatics & HydraulicsFittings, Valves, Cylinders, Hoses, PumpsPush-fit Fittings, Compression Fittings
    Electrical ComponentsConnectors, Cable Management, Switches, RelaysDIN Rail Connectors, Terminal Blocks
    Safety EquipmentPPE, Eye Protection, Respiratory, Fall ProtectionSafety Helmets, Hi-Vis Jackets
    Tools & MachineryHand Tools, Power Tools, Measuring, CuttingTorque Wrenches, Digital Callipers
    MRO SuppliesLubricants, Cleaning, Sealing, AdhesivesBearing Grease, Thread Sealant
    Pipe & TubeSteel Pipe, Copper Tube, Plastic Pipe, FittingsStainless Steel Tube, HDPE Pipe

    Technical Specification Attributes

    Fasteners (Bolts, Nuts, Screws)

    • Required: Thread standard (M4, M6, M8, M10 etc.), Material grade (Grade 8.8, Grade 10.9, A2 stainless, A4 marine), Head type, Length (mm), Finish (zinc plated, hot dip galvanised, plain)
    • Recommended: Tensile strength (MPa), Hardness (HRC), Drive type, Standards compliance (DIN, ISO, BS, ANSI), Minimum order quantity, Pack size

    Pneumatic Fittings

    • Required: Connection type (push-fit, compression, threaded), Port size (BSP, NPT, metric), Tube OD (mm), Material (brass, stainless, nylon), Max pressure (bar), Temperature range (°C)
    • Recommended: Flow rate (l/min), Seal material (NBR, EPDM, PTFE), ATEX rated (yes/no), IP rating

    Safety Equipment (PPE)

    • Required: CE marking (yes/no), Standard compliance (EN 397, EN 388, EN 166 etc.), Protection class, Size/Fit range, Material
    • Recommended: EN standard version year, Shelf life, Cleaning instructions, Compatible with other PPE items

    Compliance and Certification Attributes

    Compliance data is what separates a functional industrial taxonomy from an inadequate one. B2B buyers in regulated industries (construction, oil and gas, food processing, pharmaceuticals) cannot purchase without verified compliance data.

    • CE marking: Yes / No — mandatory for products sold in EU/UK regulated categories
    • ATEX certification: Zone rating — for equipment used in explosive atmospheres
    • RoHS compliance: Yes / No — restriction of hazardous substances in electrical equipment
    • REACH compliance: SVHC declaration — substances of very high concern disclosure
    • IP rating: IP54, IP65, IP67 etc. — ingress protection for electrical and electronic products
    • Industry standards: DIN, ISO, BS, ANSI, ASTM — the specific standard and version the product is manufactured to

    Part Number Structure as Taxonomy Signal

    In B2B industrial catalogs, the part number (MPN — Manufacturer Part Number) is often the most important search term. Procurement buyers copy part numbers from approved vendor lists and search for exact matches. Your product records must include manufacturer part numbers, and your site search must index them.

    Beyond search, consider encoding category information into your internal part number format. A part number structure like CAT-MFR-SPEC-VARIANT means any product ID immediately signals its category, manufacturer, and variant — making catalog management programmatic rather than dependent on correct manual categorisation.

    The PIM Readiness Score identifies where your current B2B catalog data governance has gaps — particularly around technical specification completeness and compliance attribute coverage. The free Taxonomy Template at lynkpim.app includes the B2B Industrial tab with a pre-built category structure and attribute set.

    For a comparison of how B2B industrial taxonomy differs structurally from consumer categories, see the Home Goods Taxonomy guide as a contrast point.

    Frequently Asked Questions

    What classification standard should I use for B2B industrial taxonomy?

    UNSPSC is the most widely adopted standard for industrial and procurement catalogs globally. eCl@ss is preferred in European manufacturing and engineering contexts. Use the standard most common in your target buyer’s procurement system — many enterprise procurement platforms require UNSPSC codes on purchase orders and will not process invoices without them.

    How important is part number (MPN) in B2B industrial taxonomy?

    Extremely important. B2B buyers frequently search by exact manufacturer part number copied from an approved vendor list or Bill of Materials. Your site search must index MPNs and your product records must include both your internal part number and the manufacturer’s part number. Missing MPN data means losing buyers who search by part number — which is a significant share of B2B industrial search volume.

    What compliance attributes should industrial products have?

    At minimum: CE marking status, relevant EN/ISO/DIN/ANSI standards compliance, RoHS status for electrical products, and IP rating where applicable. ATEX certification is mandatory for products used in potentially explosive atmospheres. REACH SVHC declarations are required for products containing substances of very high concern sold in EU/UK markets.

    How do you handle quantity pricing in a B2B product taxonomy?

    Quantity break pricing and minimum order quantities should be structured product attributes, not free-text in descriptions. Store them as structured fields: min_order_qty, pack_size, and pricing tiers with corresponding quantity thresholds. This enables filter by minimum order, automated price calculation, and correct price display in Shopping feeds.

    Should B2B industrial products use the same Google Shopping feed structure?

    Yes, the same Merchant Center feed structure applies. B2B industrial products benefit significantly from detailed technical specifications in the product description (which Google indexes), and from the deepest available google_product_category value. Many B2B industrial searches are long-tail and highly specific — title construction should include thread standard, material grade, and key certifications where character limits allow.

  • Product Taxonomy for Home Goods and Furniture: The Complete Guide

    Product Taxonomy for Home Goods and Furniture: The Complete Guide

    Product Taxonomy for Home Goods and Furniture: The Complete Guide

    Home goods and furniture present a taxonomy challenge that is distinct from fashion or electronics. Products are large, physical, and often customisable. Customers search by room, by style, by material, and by dimension — sometimes all at once. A sofa is not just a sofa: it is a 3-seater, right-hand-facing, grey velvet, Scandi-style corner sofa with a specific width that must fit through a standard doorframe.

    This guide covers how to build a home goods taxonomy that handles all of those dimensions without becoming unmanageable.

    Room-Based vs Type-Based Hierarchy: Which to Choose

    The first decision in home goods taxonomy is whether to organise by room or by product type at the top level. Both approaches appear in the market. Both have genuine pros and cons.

    Room-Based (Living Room, Bedroom, Kitchen)Type-Based (Sofas, Beds, Tables)
    Customer navigationIntuitive for browsing by project (“doing up my bedroom”)Intuitive for specific product search (“I need a sofa”)
    Cross-room productsProblem — a side table works in bedroom AND living roomNo problem — side tables are just side tables
    Google Shopping mappingDifficult — Google organises by type, not roomEasy — maps directly to Google taxonomy
    SEORoom keywords have high volume but low commercial intentType + material + size keywords have high commercial intent
    VerdictWorks for editorial/inspiration contentBetter for ecommerce catalog and feed performance

    The recommended approach: use type-based categories as your primary taxonomy structure and add room as a filterable attribute on each product. This gives customers both navigation paths without creating structural problems for products that belong in multiple rooms. For a full comparison of hierarchy approaches, see Flat vs Hierarchical Taxonomy.

    Recommended Top-Level Structure for Home Goods

    Level 1Level 2 ExamplesLevel 3 Examples
    FurnitureSofas, Beds, Tables, Storage, Chairs, WardrobesCorner Sofas, 2-Seater Sofas, Sofa Beds
    LightingCeiling Lights, Floor Lamps, Table Lamps, Wall LightsPendant Lights, Chandeliers, Spotlights
    Bedding & TextilesDuvet Sets, Pillowcases, Throws, Curtains, RugsKing Duvet Sets, Blackout Curtains
    Kitchen & DiningCookware, Tableware, Kitchen Storage, AppliancesNon-stick Pans, Dinner Sets, Knife Blocks
    Storage & OrganisationShelving, Boxes & Baskets, Hooks, Drawer OrganisersFloating Shelves, Wicker Storage Baskets
    Home DecorMirrors, Vases, Picture Frames, Candles, ArtworkWall Mirrors, Full-Length Mirrors
    OutdoorGarden Furniture, Outdoor Lighting, Planters, BBQsGarden Dining Sets, Garden Sofas

    Attribute Sets for Home Goods

    Furniture (Sofas, Tables, Chairs, Beds)

    • Required: Brand, Colour, Material (primary), Dimensions (W × H × D in cm), Weight (kg), Assembly required (yes/no)
    • Recommended: Frame material, Leg material, Interior style, Room (Living Room / Bedroom / etc.), Maximum load (kg), Flat pack (yes/no), Number of seats (sofas/chairs)
    • Google category: Furniture → [specific type] e.g. Furniture > Sofas & Sectionals

    Lighting

    • Required: Brand, Colour/Finish, Fitting type (E27, B22, GU10 etc.), IP rating (for outdoor/bathroom), Material
    • Recommended: Bulb included (yes/no), Bulb type, Max wattage, Dimmable (yes/no), Height (cm), Shade diameter (cm), Interior style
    • Google category: Furniture > Lamps & Lighting > [specific type]

    Bedding & Textiles

    • Required: Brand, Colour, Size (Single / Double / King / Super King), Material composition, Care instructions
    • Recommended: Thread count (sheets), Tog rating (duvets), Pattern, Weave type, Hypoallergenic (yes/no)
    • Google category: Home & Garden > Linens & Bedding > [specific type]

    Dimension Attributes — Non-Negotiable for Furniture

    Dimension data is the most common missing attribute in home goods feeds, and it is the attribute customers are most likely to abandon without when making a buying decision. Furniture customers need to know if a sofa fits their space before they buy. A sofa listing without dimensions loses that sale before it begins.

    • Width, Height, Depth: In centimetres. Required for all furniture and large home goods.
    • Seat height: For chairs and sofas — critical for accessibility and ergonomics.
    • Weight: In kilograms. Important for customer planning and delivery expectations.
    • Assembly required: Yes / No — customers plan their time around this.
    • Flat pack: Yes / No — relevant for customers with size-restricted access (e.g. lifts, narrow staircases).

    Material Management in Home Goods

    Material naming in home goods has the same problem as colour naming in fashion. Marketing names (“Smoked Oak”, “Brushed Concrete Effect”, “Warm Walnut”) are meaningful to buyers but problematic for site filters and Google Shopping.

    Use a two-field approach: store the marketing material name for product copy and an additional normalised material value for filtering and feed submission:

    • Smoked Oak → Oak
    • Brushed Concrete Effect → Concrete / MDF
    • Warm Walnut Veneer → Walnut
    • Hammered Antique Brass → Brass

    Without normalised material values, your filter “Shop by Material” becomes unusable — customers cannot find all oak products because they appear under fifteen different marketing material names.

    Style as a Filterable Attribute

    Interior style — Modern, Scandinavian, Industrial, Traditional, Coastal, Maximalist — is a genuine purchase driver for home goods customers. But style should be a filterable attribute, not a category. Here is why:

    • A product can have multiple applicable styles — a rattan sofa is both Coastal and Boho
    • Style trends change — “Cottagecore” did not exist as a search term five years ago; you cannot build permanent category structure on trends
    • Style categories create structural debt — “Industrial Living Room Furniture” and “Scandinavian Living Room Furniture” as subcategories double your category maintenance without adding navigational value

    Assign style values as multi-value attributes and surface them as filters. A product can carry two or three style tags and appear in all relevant filter results without duplicating the product record.

    Google Product Category Mapping for Home Goods

    ProductCorrect Google Category
    3-seater sofaFurniture > Sofas & Sectionals
    King size bed frameFurniture > Beds & Bed Frames
    Pendant ceiling lightFurniture > Lamps & Lighting > Ceiling Lights & Fans
    King duvet setHome & Garden > Linens & Bedding > Duvet Covers
    Non-stick frying panKitchen & Dining > Cookware > Frying Pans & Skillets
    Floating shelfFurniture > Shelving > Wall Shelves & Ledges

    Once your home goods taxonomy is structured, managing dimension attributes and material values at scale benefits significantly from a PIM that enforces attribute completeness before products are published. Take the PIM Readiness Score to identify your current gaps, or download the free Taxonomy Template — including the Home Goods & Furniture tab — at lynkpim.app.

    For a broader framework applicable across all industries before diving into home-specific requirements, see How to Build a Product Taxonomy From Scratch.

    Frequently Asked Questions

    Should a home goods taxonomy be room-based or product-type-based?

    Product-type-based is recommended for the primary taxonomy structure. Room should be a filterable attribute on each product, not a top-level category. This avoids the structural problem of cross-room products and maps far more cleanly to Google’s product taxonomy — which organises by type, not by room.

    What dimension attributes are required for furniture?

    Width, Height, and Depth in centimetres are required for all furniture and large home goods. Additionally include Weight (kg), Assembly Required (yes/no), and Flat Pack (yes/no). Seat height is strongly recommended for chairs and sofas as it is a key purchase decision factor.

    How should interior style be handled in a home goods taxonomy?

    Style should be a multi-value filterable attribute, not a permanent category. One product can carry multiple style tags — Coastal and Boho, for example — and appear in all relevant filter results without duplicating the product record. Creating style-named categories creates structural debt that becomes difficult to manage when interior trends shift.

    What Google product category should I use for sofas?

    Use the leaf-node: Furniture > Sofas & Sectionals. Avoid parent categories like “Furniture” alone. The more specific your Google product category, the better your Shopping feed relevance and the more accurately Google matches your products to buyer queries.

    How should material be managed in a home goods taxonomy?

    Use a two-field approach: marketing material name (Smoked Oak, Warm Walnut Veneer) for customer-facing copy, and a normalised material value (Oak, Walnut) for feed attributes and site filters. Without normalised values, your “Shop by Material” filter becomes a list of marketing names rather than a useful browsing tool.

  • Flat vs Hierarchical Product Taxonomy: Which Is Right for Your Catalog?

    Flat vs Hierarchical Product Taxonomy: Which Is Right for Your Catalog?

    Flat vs Hierarchical Product Taxonomy: Which Is Right for Your Catalog?

    The structure of your product taxonomy determines how your catalog scales, how your site filters work, and how well your products map to Google Shopping categories. Flat and hierarchical are the two fundamental structural approaches — and choosing the wrong one for your catalog size and complexity creates problems that get harder to fix the longer they go unaddressed.

    What Is a Flat Taxonomy?

    A flat taxonomy has a single level of categories. Products sit directly under a top-level category with no subcategories beneath it. The entire catalog structure is one layer deep.

    Example: A small accessories store with a flat taxonomy might have: Bags, Scarves, Hats, Belts, Sunglasses, Jewellery. Every product sits directly under one of those six categories. There are no subcategories — “Bags” is not further divided into Handbags, Crossbody Bags, Clutches, Tote Bags.

    Flat taxonomies are easy to set up and easy to understand at a glance. They work well when the catalog is small and products within each category are genuinely similar enough that no further subdivision adds value.

    What Is a Hierarchical Taxonomy?

    A hierarchical taxonomy has multiple nested levels. Categories contain subcategories, which may contain further subcategories, down to the most specific product type level.

    Example: The same accessories store with a hierarchical taxonomy: Bags > Handbags > Leather Handbags. Or Bags > Crossbody Bags. Each level adds specificity — and with it, the ability to filter, map to Google’s taxonomy precisely, and manage products by type without the entire “Bags” category becoming unnavigable.

    Head-to-Head Comparison

    Flat TaxonomyHierarchical Taxonomy
    StructureOne level — all categories at the same depthMultiple levels — categories contain subcategories
    Best forCatalogs under ~200 products, narrow rangeAny catalog with 200+ products or multiple product types
    NavigationSimple — works when categories are few and clearMore complex but enables breadcrumb navigation and drill-down filtering
    Filter accuracyLimited — attributes apply across entire categoryHigh — attributes defined per subcategory, filters are specific
    Google category mappingImprecise — top-level categories rarely match Google leaf nodesPrecise — subcategories map directly to Google taxonomy leaf nodes
    ScalabilityPoor — adding products creates category bloatHigh — hierarchy absorbs new product types without structural change
    MaintenanceLow initially, high as catalog growsHigher upfront, lower long-term
    Channel mappingDifficult — manual per-product mapping often requiredSystematic — subcategory maps once to each channel

    When Flat Taxonomy Works

    Flat taxonomies are appropriate in a small number of specific situations:

    • Catalog under 200 SKUs with a genuinely narrow product range where subcategories would be redundant
    • Single-category specialty stores — a store that sells only coffee beans, only yoga mats, or only one type of product doesn’t need a hierarchy
    • Early-stage stores planning to restructure as the catalog grows — a flat structure is a valid starting point if you know it will be replaced

    In all other cases, the limitations of flat taxonomy become apparent quickly as the catalog grows. The most damaging limitation is Google Shopping performance — flat taxonomy categories rarely correspond to Google’s taxonomy leaf nodes, resulting in products being assigned to broad parent categories that hurt auction relevance.

    When Hierarchical Taxonomy Is Required

    Hierarchical taxonomy becomes necessary when any of these conditions are true:

    • Your catalog has more than 200 products
    • You sell across multiple product types that require different attribute sets
    • You need accurate Google Shopping category mapping below the parent level
    • Your site needs faceted filtering (filter by colour, size, material etc.)
    • You sell across multiple channels that each have their own taxonomy
    • Your team needs to manage products by type for buying, merchandising, or reporting

    For most ecommerce stores, the answer is hierarchical. The question is not whether to use hierarchical taxonomy but how many levels and how specifically to define subcategories. For the full build process, see How to Build a Product Taxonomy From Scratch.

    The Google Shopping Argument for Hierarchical Taxonomy

    Google’s product taxonomy has over 6,000 categories. It goes 5–7 levels deep in most categories. A flat internal taxonomy maps to Google’s parent-level categories at best — “Clothing” instead of “Apparel & Accessories > Clothing > Activewear > Track Jackets & Hoodies”.

    The difference in Shopping performance between a product mapped to a parent category and one mapped to the correct leaf node can be significant — better relevance matching means your products appear for more specific search queries at lower CPCs. If Google Shopping is a meaningful channel for you, hierarchical taxonomy is not optional.

    Migrating from Flat to Hierarchical

    If your catalog currently has a flat structure and you are outgrowing it, migration is straightforward in principle — though it requires careful execution to avoid breaking navigation and losing indexed URLs.

    1. Design the new hierarchical structure before touching anything live
    2. Remap every product to its new subcategory in a staging environment
    3. Set up 301 redirects from old category URLs to new subcategory URLs
    4. Update your feed’s google_product_category values to the new leaf-node mapping
    5. Update your sitemap and request GSC re-indexing after going live

    Rankings may dip briefly after migration as Google recrawls the new structure. This is normal and temporary — the long-term gains in navigation, filtering, and channel performance outweigh the short-term disruption.

    For industry-specific guidance on what a hierarchical structure should look like in practice, see the fashion taxonomy guide and electronics taxonomy guide. Take the PIM Readiness Score to identify where your current taxonomy structure has gaps.

    Frequently Asked Questions

    What is a flat product taxonomy?

    A flat taxonomy has a single level of categories with no subcategories. Every product sits directly under a top-level category. Simple to set up but breaks down as catalog size grows — filters become unwieldy, Google category mapping becomes imprecise, and category pages become unmanageable.

    What is a hierarchical product taxonomy?

    A hierarchical taxonomy has multiple nested levels — typically Department > Category > Subcategory > Product Type. Products sit at the most specific level. This structure scales to any catalog size and enables precise Google category mapping and deep attribute-based filtering.

    When should you use a flat taxonomy?

    Flat taxonomies work for small catalogs under 200 products with a genuinely narrow product range where subcategories would be redundant. Specialty retailers with a single product type can use a flat structure effectively. For most ecommerce stores with varied product ranges, hierarchical is the right choice.

    Can you migrate from flat to hierarchical taxonomy?

    Yes. The process requires designing the new hierarchy, remapping products to new subcategories, setting up 301 redirects from old category URLs, updating feed category mapping, and requesting GSC re-indexing. Rankings may dip briefly during migration but recover as Google processes the new structure — and long-term performance gains are significant.

  • What Is Product Taxonomy? Definition, Examples and Why It Matters

    What Is Product Taxonomy? Definition, Examples and Why It Matters

    What Is Product Taxonomy? Definition, Examples and Why It Matters

    Product taxonomy is the classification system that organises your products into a structured hierarchy. It determines how products are grouped, named, and navigated — on your website, inside your catalog management system, and across every sales channel you use.

    Get it right and customers find products faster, your Google Shopping feed performs better, and your team can manage thousands of SKUs without chaos. Get it wrong and you end up with inconsistent categories, broken filters, and channel mapping errors that cost you sales daily.

    Product Taxonomy Definition

    A product taxonomy is a hierarchical system for classifying products into groups based on shared characteristics. The word comes from the Greek taxis (arrangement) and nomos (law or method) — it is, literally, the rules by which products are arranged.

    In practical ecommerce terms, a product taxonomy answers three questions for every product in your catalog:

    1. What type of product is this? (Product Type / Subcategory)
    2. What category does it belong to? (Category)
    3. What department does that category sit under? (Department)

    Those three questions map to the three levels every functional taxonomy needs: Department → Category → Subcategory.

    A Simple Product Taxonomy Example

    LevelNameExample
    Level 1 — DepartmentClothingClothing, Footwear, Accessories
    Level 2 — CategoryMen’s ClothingMen’s, Women’s, Kids’
    Level 3 — SubcategoryMen’s JacketsJackets, Trousers, Shirts, Knitwear
    Level 4 — Product TypeMen’s Rain JacketsRain Jackets, Leather Jackets, Puffer Jackets

    Every product in the catalog sits at the most specific level — Level 3 or Level 4 — not at the top. A product is never just “Clothing”. It is always “Men’s Rain Jackets” or “Women’s Running Shoes”.

    Taxonomy vs Categories vs Attributes — What’s the Difference?

    These three terms are often used interchangeably but they are distinct concepts.

    • Taxonomy — the overall classification system and its rules. The framework.
    • Categories — the individual nodes within the taxonomy. Men’s Jackets is a category.
    • Attributes — the properties of a product within its category. Colour, Size, Material, Brand are attributes of a product in Men’s Jackets.

    Taxonomy tells you where the product lives. Attributes describe what the product is. Both are necessary. A product without a taxonomy position cannot be found by browsing. A product without attributes cannot be filtered or matched to specific search queries.

    Why Product Taxonomy Matters for Ecommerce

    1. Site navigation and search

    Your taxonomy is the structure your site navigation and filters are built on. If your taxonomy is flat or inconsistent, your filters do not work. Customers searching for “blue running shoes women size 7” cannot filter to that result if Colour, Activity, Gender, and Size are not structured attributes on products in the correct subcategory.

    2. Google Shopping performance

    Google Shopping requires a google_product_category value for every product. This value must map to Google’s own taxonomy at the most specific level available. A jacket submitted as “Apparel & Accessories” instead of “Apparel & Accessories > Clothing > Outerwear > Coats & Jackets” loses relevance in every Shopping auction it enters. Your taxonomy must map to Google’s.

    3. Channel feed mapping

    Every major channel — Google Shopping, Amazon, Facebook Catalogue, retail marketplaces — has its own category taxonomy. Your internal taxonomy needs to translate cleanly to each one. A well-structured internal taxonomy makes this mapping straightforward. A chaotic one makes it a manual monthly project.

    4. Internal catalog management

    A consistent taxonomy means your team can find, update, and report on products by category without ambiguity. Without it, “running shoes” might live under “Athletic Footwear”, “Sports”, “Men’s Sports”, and “Women’s Running” in the same catalog — making bulk updates, seasonal campaigns, and channel exports all harder than they need to be.

    Flat vs Hierarchical Taxonomy

    Two structural approaches exist for product taxonomy. For most ecommerce stores with more than a few hundred products, the difference matters significantly. The full comparison is covered in the Flat vs Hierarchical Taxonomy guide, but the key distinction is:

    • Flat taxonomy: One level of categories, no subcategories. Simple but breaks down above ~200 products. Filters become unwieldy and Google category mapping becomes imprecise.
    • Hierarchical taxonomy: Multiple nested levels. Scales to any catalog size. Enables precise Google category mapping and deep attribute-based filtering.

    Product Taxonomy in Practice — Real Examples

    Across industries the hierarchy principle stays the same but the depth and attribute requirements differ significantly. A fashion taxonomy needs colour normalisation, size system declarations, and seasonal attribute management. An electronics taxonomy needs technical specification attributes and compatibility data. A home goods taxonomy needs dimension attributes and material normalisation. Each industry guide is linked below.

    How to Build Your Product Taxonomy

    The full step-by-step build process is covered in How to Build a Product Taxonomy From Scratch — from auditing your products through to Google category mapping and documentation. The short version:

    1. Define what your taxonomy needs to do — navigation, channel mapping, or both
    2. Audit your existing products before designing any categories
    3. Design 5–12 top-level departments
    4. Build at minimum three levels of hierarchy
    5. Define attribute sets per subcategory
    6. Map every subcategory to a Google product category leaf node
    7. Document the rules

    Before building, take the PIM Readiness Score to identify where your current product data governance has gaps. The free Taxonomy Template at lynkpim.app gives you a pre-built starting point for 5 industries.

    Frequently Asked Questions

    What is product taxonomy in ecommerce?

    Product taxonomy is the hierarchical classification system used to organise products into categories, subcategories, and product types. It defines the structure that powers site navigation, search filters, channel feeds, and internal catalog management.

    What is the difference between product taxonomy and product attributes?

    Taxonomy defines where a product sits in the hierarchy — Men’s Clothing > Jackets. Attributes define the properties of that product within its category — Colour: Navy, Size: L, Material: Nylon. Taxonomy organises the catalog structure; attributes describe individual products within it.

    Why does product taxonomy matter for Google Shopping?

    Google Shopping requires a google_product_category value for every product in your feed, mapped to Google’s own taxonomy at the most specific leaf-node level. Broad or incorrect category values reduce relevance matching and hurt Shopping auction performance — your products appear for fewer relevant queries and at lower positions.

    How many levels should a product taxonomy have?

    A minimum of three levels: Department (Level 1), Category (Level 2), and Subcategory (Level 3). Larger catalogs benefit from a fourth level (Product Type). More than four levels rarely adds value and increases maintenance complexity without meaningful benefit to navigation or channel mapping.

    What is the difference between a flat and hierarchical product taxonomy?

    A flat taxonomy has one level of categories with no subcategories — simple but breaks down above ~200 products. A hierarchical taxonomy has multiple nested levels that scale to any catalog size, enable precise Google category mapping, and support deep attribute-based filtering. For the full comparison see Flat vs Hierarchical Taxonomy.