Shopping taxonomy

Google product category: how the taxonomy works and how to map a catalog to it.

Google publishes one taxonomy for every merchant in the world, which means your categories will never match it exactly. Mapping is the job, and it is a mapping problem with a right answer, not a naming exercise.

Map categories in Nexodo See the feed specification

One taxonomy

Google publishes a single hierarchy for all merchants.

Two fields

google_product_category and product_type do different jobs.

Mapped, not renamed

Your categories stay yours. The mapping is an attribute.

Structure

A single hierarchy, referenced by numeric id or by full path.

The Google product taxonomy is a published hierarchy of several thousand categories, each with a numeric id and a full path written with the greater-than separator. You can send either the id or the path. The id is safer, because Google occasionally renames a category and a stored path then stops matching while an id keeps working.

Send the most specific category that is genuinely correct. A category that is too broad reduces how well a product is understood; a category that is wrong is worse than one that is broad. Where no specific category fits, a correct parent is the right answer.

Field	What it is	Who defines the values
google_product_category	A category from the published Google taxonomy	Google
product_type	Your own category path for the item	You
Value form	Numeric id or full path with greater-than separators	Google, id preferred
Cardinality	One category value per product	Google

Top level

The twenty-one top-level categories.

Every category in the taxonomy descends from one of twenty-one top-level entries. Picking the right top level first is the same discipline that makes UNSPSC classification tractable: it removes most of the taxonomy before you start searching.

Industrial and trade catalogs usually live under Business and Industrial or Hardware, and those two branches are deeper than most merchants expect. Search inside the branch rather than across the whole taxonomy.

Animals and Pet Supplies
Apparel and Accessories
Arts and Entertainment
Baby and Toddler
Business and Industrial
Cameras and Optics
Electronics
Food, Beverages and Tobacco
Furniture
Hardware
Health and Beauty
Home and Garden
Luggage and Bags
Mature
Media
Office Supplies
Religious and Ceremonial
Software
Sporting Goods
Toys and Games
Vehicles and Parts

Category and type

Do not use product_type as a second attempt at the category.

The two fields answer different questions. The Google category tells Google what kind of thing this is, using Google's words. The product type tells Google what you call it, using yours, and it is what campaign structures and reporting group on. Copying the Google category into product type throws away the field that would have made your reporting usable.

Send your own category path in product type, exactly as it appears in your catalog, and keep the mapped Google category in its own field. Both are cheap to produce from a PIM once the mapping exists as an attribute on the category rather than on each product.

Google category mapped from your category, stored once per category
Product type carrying your own path for reporting and bidding
Numeric category ids preferred over stored path strings
One mapping to maintain, not one per product

Maintenance

The taxonomy changes, so store the mapping where you can re-run it.

Google republishes the taxonomy periodically and categories are added, renamed and occasionally removed. A mapping baked into an export script is invisible when that happens. A mapping stored as an attribute on your own category tree can be reviewed, diffed and re-approved when the taxonomy moves.

In Nexodo the Google category sits on the category record as a governed value, so every product inherits it and a single review updates a whole branch. That also makes it visible in completeness checks: a category with no Google mapping is a publishing blocker you can see before the feed is rejected.

Map at the category level and let products inherit
Review the mapping when Google republishes the taxonomy
Treat an unmapped category as a completeness failure
Keep a record of which taxonomy release the mapping was made against

Frequently asked questions

Clear answers before you evaluate a PIM.

Is google_product_category required?

It is not required for every product, but Google uses it to understand and place your items, and some categories and policies depend on it. Treat it as required in practice for a catalog you care about, and confirm the current requirement in the Merchant Center product data specification.

Should I send the id or the full path?

The numeric id. Paths are human readable but they break when Google renames a level, and a broken path is silently ignored while a wrong category is not.

What if nothing in the taxonomy fits my product?

Use the most specific correct ancestor. A correct broad category is better than a specific wrong one, and Google treats an incorrect category as a data quality problem rather than a near miss.

Can one product have two categories?

No. The field takes a single value. If a product genuinely belongs in two places in your own merchandising, that is what your own category tree and the product type field are for.

Continue your product data research

Feed specification

Test Nexodo with a supplier file your team already uses.

Tell us how your supplier files arrive and what your channels reject, and we will tell you whether this workflow fits.

Talk to us See what Nexodo does

A person replies, normally within one business day
Use a representative product sample
We will say plainly if Nexodo is the wrong fit

Google product category: how the taxonomy works and how to map a catalog to it.

A single hierarchy, referenced by numeric id or by full path.

The twenty-one top-level categories.

Do not use product_type as a second attempt at the category.

The taxonomy changes, so store the mapping where you can re-run it.

Clear answers before you evaluate a PIM.

Continue your product data research

Google Shopping feed specification: what is required, what is conditional, and what breaks.

Build channel output from approved product data, not another spreadsheet.

Product taxonomy that makes a changing catalog easier to navigate.

The Shopify product CSV, column by column, including the rows that confuse everyone.

Test Nexodo with a supplier file your team already uses.