The full Google product taxonomy used by Google Merchant Center for Shopping ads and free product listings. This dataset includes every category ID and its complete breadcrumb path, making it easy to classify products in your feed with the correct google_product_category value.
Pro tip: Import the JSON version into your product management system as a searchable lookup — staff can find the right category ID by typing keywords instead of browsing the full tree.
Select which columns to include in your download.
About the Google Product Categories Dataset
This dataset contains the complete Google product taxonomy, the official classification system used by Google Merchant Center to categorize products for Shopping ads, free product listings, and Buy on Google. Each entry provides the numeric category ID along with the full hierarchical path separated by angle brackets. The taxonomy covers thousands of product types across all major industries, from apparel and electronics to home goods and vehicles. This data is sourced from Google's published taxonomy file and kept in sync with the latest updates.
Common Use Cases
Accurate product categorization is critical for e-commerce visibility. Here are the most common applications for this dataset:
- Google Merchant Center feeds: The
google_product_categoryattribute is required or strongly recommended for Shopping feeds. Use this dataset to map your internal categories to the correct Google taxonomy IDs. - Product feed automation: Load the taxonomy into your feed management tool or CMS plugin to auto-suggest categories as you add new products, reducing manual classification errors.
- Competitive analysis: Cross-reference competitor product listings with the taxonomy to understand which categories they target and identify gaps in your catalog coverage.
- Multi-channel syndication: Use the taxonomy as a translation layer between Google Shopping and other marketplaces like Facebook Commerce, Amazon, or Bing Shopping that accept Google category IDs.
Column Reference
The dataset provides straightforward columns for direct integration into product feeds:
- category_id — The unique numeric identifier assigned by Google to each category node. This is the value you submit in the
google_product_categoryfield of your Merchant Center feed. - category_path — The full human-readable path from root to leaf, using " > " as the delimiter (e.g. "Animals & Pet Supplies > Pet Supplies > Dog Supplies > Dog Beds"). This is the alternative text-based format Google also accepts.
- parent_id — The category ID of the parent node, useful for reconstructing the full tree structure in a database or building hierarchical navigation.
- depth — The level of nesting in the tree, starting at 1 for top-level categories. Helpful for filtering to specific levels when building UI components.
How Product Taxonomy Impacts Ad Performance
Assigning the most specific category possible has a direct impact on your Shopping ad performance. Google uses the product category to determine which search queries trigger your product listing. A product classified under a broad parent category competes in a wider pool, while a product classified at the leaf level matches more specific queries and typically achieves higher click-through rates. Additionally, certain categories have specific attribute requirements — for example, products in apparel categories require size, color, and gender attributes. Using this dataset to find the deepest matching category ensures you meet all attribute requirements and maximize your listing quality score.
Working with the Taxonomy in Code
For developers building feed generation systems, the JSON export provides a ready-to-use array that can be loaded into a trie or hash map for fast category lookups. The parent_id field lets you reconstruct the full tree programmatically, enabling features like breadcrumb navigation or category pickers with expand and collapse behavior. If you use a relational database, the SQL export creates an indexed table with a self-referencing foreign key on parent_id, supporting recursive CTEs for ancestor and descendant queries. The CSV format is ideal for one-time imports into spreadsheet-based feed templates.