Blog

  • 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.

  • How to Automate Your Google Shopping Feed Updates (2026 Guide)

    How to Automate Your Google Shopping Feed Updates (2026 Guide)

    How to Automate Your Google Shopping Feed Updates (2026 Guide)

    Manual Google Shopping feed management is one of the highest-risk activities in ecommerce operations. Every time a price changes, a product goes out of stock, or a promotion goes live — and the feed is not updated within 24 hours — you risk price mismatch disapprovals that remove products from Shopping entirely. Full automation eliminates this risk.

    This guide covers every automation method available in 2026, when to use each, and how to set them up correctly.

    Why Manual Feed Updates Fail

    Manual feed management fails not because teams are careless but because the speed of change in ecommerce catalogs outpaces human update cycles. Prices change for flash sales. Stock depletes. New products launch. Promotions end. Any one of these events — if not reflected in the feed within 24 hours — creates a price mismatch or availability mismatch that Merchant Center catches during its next crawl.

    The solution is not faster manual processes. It is removing humans from the update loop entirely for routine data changes. For the context on how feeds connect to your product data source, see the PIM to Google Shopping Integration guide.

    Method 1: Scheduled URL Fetch (Recommended for Most Stores)

    Your system generates a feed file at a stable URL. Google Merchant Center fetches that URL on a schedule you configure — daily, twice daily, or more frequently. Every fetch pulls a fresh copy of your full product data.

    How to set it up

    1. In Merchant Center, go to Products → Feeds → [your primary feed] → Settings
    2. Under Fetch Schedule, set the frequency to Daily at minimum
    3. Set the fetch time to a low-traffic period — typically 2:00–4:00 AM in your primary market timezone
    4. For stores with frequent promotions or high stock turnover, set to Twice daily
    5. Save and trigger a manual fetch to confirm the URL is accessible and the feed processes without errors

    Best for: Most ecommerce stores. Works with any platform that can generate a feed file at a stable URL — Shopify, WooCommerce, Magento, custom platforms.

    Limitation: The whole feed updates at once on a schedule. If a product goes out of stock at 10am and your next fetch is at 2am, the product will show as in stock in Shopping for 16 hours. For stores with fast-moving inventory, this window creates availability mismatch risk.

    Method 2: Google Content API (Real-Time Updates)

    The Content API allows your system to push product updates to Merchant Center immediately when a product changes — no waiting for a scheduled fetch. A price change in your platform can trigger an API call that updates the product in Merchant Center within minutes.

    When to use the Content API

    • Catalogs over 50,000 products where full-feed fetches become slow or resource-heavy
    • Stores with real-time pricing (dynamic pricing, live stock-based pricing)
    • High-velocity inventory where products sell out within hours
    • Stores running multiple daily promotions that change prices frequently

    Content API setup requirements

    The Content API requires developer resource to implement — it is not a no-code option. Your platform needs to be configured to send API calls to Merchant Center when product data changes. Google’s Content API documentation is the reference for implementation. The Feed Generator handles API delivery without custom development for most store configurations.

    Method 3: Feed Management Tool (No-Code Automation)

    Feed management tools sit between your product data source and Merchant Center. They pull product data from your platform or PIM, apply transformation rules (title construction, category mapping, attribute normalisation), generate the feed file, and deliver it to Merchant Center on schedule — with no manual steps after initial setup.

    Best for: Teams without developer resource, stores managing feeds across multiple channels (Google + Amazon + Facebook), and catalogs where feed transformation logic is complex enough that maintaining it manually is impractical.

    Separating Price/Availability from Content Updates

    Not all feed data needs to update at the same frequency. Treating your feed as a single monolithic file that updates everything at once is inefficient and sometimes counterproductive.

    Data TypeUpdate FrequencyDelivery Method
    Price, sale_price, availabilityDaily minimum — twice daily for promotionsPrimary feed or price-only supplemental feed
    New productsSame day as launchSupplemental feed or Content API push
    Titles, descriptionsWeeklyPrimary feed
    ImagesOn changePrimary feed
    Custom labelsWeekly or monthlyCustom label supplemental feed

    Using a supplemental feed for price and availability updates is a practical option for stores whose primary feed platform cannot be updated on a daily schedule. See the Supplemental Feeds guide for setup details.

    Setting Up Merchant Center Alerts

    Automation without monitoring is incomplete. Feed automation can fail — URLs become inaccessible, file formats break, authentication tokens expire. Set up Merchant Center email alerts so processing failures are caught within hours, not days.

    1. In Merchant Center, go to Settings → Email Preferences
    2. Enable alerts for: Feed processing errors, Product disapprovals (daily digest), Account warnings
    3. Add a shared team email address (not just a personal one) so alerts are seen even when you are out of office

    For full automation of feed generation, delivery, and monitoring from one place — including price validation before submission — the Google Shopping Feed Generator handles all three without custom development. Start with the LynkPIM free plan.

    Frequently Asked Questions

    How often should Google Shopping feeds update?

    Price and availability fields should update at minimum daily. Stores with frequent promotions or fast-moving inventory should update twice daily. Product content fields (titles, descriptions, images) can update weekly — these change infrequently and do not cause disapprovals if slightly delayed. The critical rule: your feed price must match your landing page price at all times.

    What is the difference between Scheduled URL Fetch and the Content API?

    Scheduled URL Fetch pulls a complete feed file from a hosted URL on a schedule — best for catalogs under 50,000 products with predictable update patterns. The Content API allows your system to push individual product updates to Merchant Center in real time as products change — better for large catalogs, real-time prices, or stores with unpredictable inventory movements.

    What happens if my Google Shopping feed fails to update?

    If your feed fails to fetch for more than 30 days, Google may deactivate it and your products stop appearing in Shopping. Shorter delays cause price mismatch disapprovals when your site prices change but your feed does not update. Set up Merchant Center email alerts for feed processing errors so failures are caught within hours, not days.

  • How Product Data Quality Affects Your Google Shopping ROAS

    How Product Data Quality Affects Your Google Shopping ROAS

    How Product Data Quality Affects Your Google Shopping ROAS

    Most Google Shopping ROAS discussions focus on bids, bidding strategies, and campaign structure. These matter. But for stores with data quality problems, no bidding strategy can overcome a feed where products are disapproved, titles are vague, categories are wrong, or GTINs are invalid. Product data quality affects ROAS before a single auction is entered.

    This article covers the six data quality factors with the biggest direct ROAS impact, ranked by how much they cost you and how quickly they can be fixed.

    How Product Data Affects ROAS — The Mechanism

    Product data quality affects ROAS through three distinct mechanisms. Understanding which applies to which data problem helps you prioritise fixes correctly.

    • Auction eligibility: Disapproved products do not enter any auctions. Products with “Limited performance” warnings enter fewer auctions and at lower positions. GTIN errors and policy violations cause this.
    • Auction relevance: Your title and google_product_category determine which search queries your products are matched to. Vague titles and broad categories match your products to irrelevant queries — you spend budget on traffic that does not convert.
    • Click-to-conversion rate: Image quality, title specificity, and price competitiveness all affect whether a click becomes a purchase. This is the layer that most data quality guides ignore but where significant ROAS gains are available.

    Factor 1: Product Titles — The Highest-Impact Fix

    Google uses your product title as the primary signal for matching your product to search queries. A vague title matches fewer queries. A specific, well-structured title matches more relevant queries at higher relevance scores — meaning better positions at lower CPCs.

    The ROAS impact of title quality is larger than most stores expect because it affects both sides of the equation: the cost of each click (auction position) and the value of each click (title specificity means higher buyer intent).

    Title TypeQueries MatchedTypical CTRTypical Conversion Rate
    “Men’s Jacket”Broad, low-intent0.8–1.2%Low — wrong intent mix
    “Columbia Rain Jacket Men Navy L”Specific, high-intent3.5–5.2%High — buyer knows what they want

    Title formula: Brand + Gender/Age + Material + Product Type + Colour + Size for apparel. Brand + Key Spec + Product Type + Model for electronics. Check every title against this formula using the Feed Audit Checklist.

    Factor 2: GTINs — The Eligibility Gate

    Products without valid GTINs receive a “Limited performance” status in Google Merchant Center. This is not a warning you can safely ignore. Limited performance means:

    • Reduced auction eligibility — the product enters fewer auctions than it would with a valid GTIN
    • Lower relevance scores — Google cannot cross-reference the product against its product knowledge graph
    • No eligibility for Shopping promotions or special ad formats that require GTIN verification

    For branded products, fixing invalid GTINs directly restores auction eligibility. For custom or handmade products that genuinely have no manufacturer GTIN, set identifier_exists = FALSE — this removes the warning without fabricating a GTIN.

    Factor 3: Google Product Category — The Auction Pool Problem

    An incorrect or overly broad google_product_category puts your product in the wrong auction pool. A running jacket in “Apparel & Accessories” competes against handbags, sunglasses, and children’s clothing — all irrelevant to your buyer. Your bids are wasted on impressions that will not convert because the query intent does not match.

    Fixing category mapping to leaf-node IDs is a one-time task per subcategory. Once mapped correctly in your feed, it applies to all products in that subcategory automatically. Full guide at Google Product Category Taxonomy.

    Factor 4: Image Quality — The CTR Multiplier

    In Google Shopping, the product image is the first thing a buyer sees. It is the primary visual decision trigger before the title or price are read. Image quality directly affects CTR, and CTR directly affects ROAS.

    • White background images consistently outperform lifestyle images for CTR in Shopping results for most product categories
    • Higher resolution images (800×800px+) render better in Shopping and reduce the pixelation that signals low-quality product listings
    • Multiple images via additional_image_link (up to 10) improve performance — Google can show different angles in different contexts
    • Colour-specific images for variants — a buyer filtering for navy gets shown the navy product, not a different colour from the same style

    Factor 5: Price and Availability Freshness

    A price mismatch disapproval removes a product from Shopping entirely — zero impressions, zero clicks, zero revenue until fixed. For stores that run frequent promotions or have fast-moving stock, stale feed data is a constant ROAS drain because it creates disapprovals that take 24–48 hours to resolve.

    The fix is structural: daily minimum feed updates, twice-daily during promotion periods, and using sale_price + sale_price_effective_date for promotions rather than changing the base price field. This prevents price mismatch disapprovals at the source.

    Factor 6: Attribute Completeness — The Long Tail Opportunity

    Products with complete optional attributes — colour, size, material, pattern, age_group, gender — match against more specific long-tail search queries. A buyer searching “navy size 12 waterproof running jacket women” only finds your product if all five of those attributes are present in your feed.

    Long-tail queries typically convert at higher rates than broad queries because they indicate more specific buying intent. Every missing optional attribute is a set of high-intent queries your product is invisible for. Run an attribute completeness audit using the Completeness Checker to identify which products are missing which attributes at scale.

    Priority Order — Where to Start

    1. Fix disapprovals first — any disapproved product is earning zero. Check Merchant Center Diagnostics before anything else. See the Fix Disapprovals guide.
    2. Optimise titles — highest impact on relevant traffic. Apply the title formula to your top 20% of products by revenue first.
    3. Validate GTINs — restore “Limited performance” products to full auction eligibility.
    4. Fix category mapping — move all products from parent categories to leaf nodes.
    5. Set up daily feed refresh — prevent price mismatch disapprovals from recurring.
    6. Complete optional attributes — unlock long-tail query matching for all products.

    Use the Catalog Health Score to benchmark your current data quality across all six factors and get a prioritised fix list specific to your catalog. For ongoing feed management that prevents these issues at source, explore the LynkPIM free plan.

    Frequently Asked Questions

    Does product data quality affect Google Shopping ROAS?

    Yes, directly — through three mechanisms: auction eligibility (disapproved products don’t appear at all), auction relevance (vague titles and broad categories match wrong queries), and click-to-conversion rate (image quality and title specificity determine whether clicks convert). All three affect ROAS before any bidding decision is made.

    Which product data fix has the biggest impact on Google Shopping ROAS?

    Title optimisation typically delivers the biggest immediate ROAS improvement for most stores. A specific, well-structured title matches more relevant search queries, improves auction relevance, increases CTR, and attracts higher-intent buyers. Apply the formula: Brand + Gender/Age + Material + Product Type + Colour + Size for apparel; Brand + Key Spec + Product Type for electronics.

    How does a missing GTIN affect Google Shopping performance?

    Products without valid GTINs receive “Limited performance” status — reduced auction eligibility, fewer impressions, and lower positions than identical products with valid GTINs. For branded products, fixing invalid GTINs directly restores full auction eligibility. For custom products with no manufacturer GTIN, set identifier_exists = FALSE to remove the warning.

  • 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 Shopping Feed Audit Checklist: 25 Points to Check Before You Submit

    Google Shopping Feed Audit Checklist: 25 Points to Check Before You Submit

    Google Shopping Feed Audit Checklist: 25 Points to Check Before You Submit

    A Google Shopping feed with errors is not just underperforming — disapproved products are completely invisible in Shopping results regardless of your bid. This 25-point checklist covers every attribute and compliance check you need to run before submitting your feed to Google Merchant Center. Work through each section before every new feed submission.

    Section 1: Required Attributes (5 checks)

    • id — unique per product/variant, consistent across feed updates, no spaces or special characters
    • title — follows formula: Brand + Key Attribute + Product Type + Detail. Minimum 30 characters, maximum 150. No promotional text (“Free shipping”, “Buy now”).
    • description — minimum 150 characters recommended. No HTML tags. Includes key product attributes (material, size, use case). Not a duplicate of the title.
    • google_product_category — uses the deepest applicable leaf-node ID from Google’s taxonomy, not a parent category. See the GPC Taxonomy Guide for correct mapping.
    • brand — present for all branded products. Not “N/A”, “Unknown”, or your store name for manufacturer brands.

    Section 2: Product Identifiers (5 checks)

    • gtin — present for all products with a manufacturer-assigned GTIN. Correct format (EAN-13, UPC-12, ISBN-13 etc.). Valid check digit — use the GTIN Validator to verify in bulk.
    • identifier_exists — set to FALSE for any product with no manufacturer GTIN (custom, handmade, or private label without a barcode). Do not leave GTIN blank without this field.
    • mpn (Manufacturer Part Number) — present for products without GTIN where the MPN is the primary product identifier (common in B2B, electronics, automotive parts).
    • No placeholder GTINs — check for test values like 0000000000000, 1234567890123, or repeated digits. These cause immediate disapprovals.
    • Variant GTINs — each size/colour/material variant has its own unique GTIN, not the same GTIN as the parent style.

    Section 3: Titles and Descriptions (5 checks)

    • Title formula — Brand + Gender/Age + Material + Product Type + Key Attribute. For apparel: Brand + Gender + Material + Product Type + Colour + Size. Titles should match what buyers search for.
    • No promotional language in titles — “Free shipping”, “On sale”, “Best price”, “Limited time” all violate Google’s title policies and will cause disapprovals.
    • No HTML in descriptions — strip all <p>, <br>, <strong> tags. Feed descriptions must be plain text only.
    • Description length — 150–5,000 characters. Descriptions under 150 characters significantly underperform. Descriptions over 5,000 characters are truncated.
    • No keyword stuffing — descriptions that repeat the same keyword 10+ times violate policy and reduce quality score. Write for the buyer, include key attributes naturally.

    Section 4: Images (5 checks)

    • Image dimensions — minimum 100×100px (non-apparel) or 250×250px (apparel). Recommended 800×800px or larger. Google rejects images under minimum dimensions.
    • No watermarks or overlays — no promotional text, no brand watermarks, no “Sale” badges, no borders. White or light neutral background preferred for Shopping ads.
    • Image URL returns 200 — test 10–20 image URLs to confirm they load correctly. 404 image URLs cause product disapprovals.
    • No placeholder images — white squares, question mark boxes, “image coming soon” graphics are all disapproval triggers.
    • Colour-variant images — for apparel products with multiple colours, each colour variant uses an image showing that specific colour. Do not reuse one image across all colour variants.

    Section 5: Pricing, Availability, and Landing Pages (5 checks)

    • Price matches landing page — spot-check 10–20 products by comparing feed price against the live product page price. Even a 1p discrepancy triggers a price mismatch disapproval.
    • Availability matches landing page — if feed says “in stock” but the product page shows “out of stock” or “sold out”, you will get an availability mismatch disapproval.
    • Price format — formatted as 29.99 GBP (number + space + ISO currency code). Not “£29.99”, not “29.99 pounds”, not “29,99”.
    • Sale prices use sale_price field — do not change the price field during promotions. Use sale_price + sale_price_effective_date so prices revert automatically when the promotion ends.
    • Landing page returns 200 — confirm link URLs return 200, load on mobile, and show the correct product (not a category page or 404).

    Section 6: Apparel-Specific Checks (5 checks)

    Skip this section if you do not sell clothing, footwear, or accessories. For apparel, these checks are mandatory — see the full Apparel Feed Requirements guide.

    • item_group_id — all variants of the same style share the same item_group_id. Verify no variant is missing this field.
    • color — human-readable values (Navy, Coral, Charcoal), not hex codes or internal codes. Up to 3 values separated by “/”.
    • size — present for every apparel variant. Matches the labelled size on the product.
    • gender — male, female, or unisex. Present for every apparel product.
    • age_group — adult, kids, newborn, infant, or toddler. Present for every apparel product.

    After the Audit — Before You Submit

    • Run all GTINs through the GTIN Validator
    • Run your full feed through the Completeness Checker to catch missing required fields
    • Set up Merchant Center email alerts (Settings → Notifications) so feed processing errors notify you immediately
    • After submitting, check Merchant Center Diagnostics within 24 hours for any new disapprovals or warnings

    For stores managing large catalogs where manual auditing is impractical, the Google Shopping Feed Generator builds feeds with validation built in — catching common errors before the feed reaches Merchant Center.

    Frequently Asked Questions

    How often should I audit my Google Shopping feed?

    Run a full audit before any new feed submission and after major catalog changes. Monitor Merchant Center Diagnostics weekly for ongoing issues. A full audit quarterly is a good rhythm for most stores — more frequently during peak trading periods when prices and stock change rapidly.

    What is the most common reason for Google Shopping feed disapprovals?

    Price mismatch — where the price in the feed does not match the price on the landing page — is the most common data-related disapproval cause. Invalid or missing GTINs are the second most common. Both are caught by this checklist before submission.

    Do I need to audit my feed if I use an automated feed tool?

    Yes. Automated tools can generate incorrect attribute values, fail to update on schedule, or apply wrong category mappings without alerting you. Merchant Center Diagnostics should be reviewed weekly regardless of how your feed is generated — automated does not mean error-free.

  • 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.