---
title: Model product taxonomies
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

## Taxonomy

In Xperience, taxonomies allow editors to organize and categorize content efficiently. Using tags, which can be structured hierarchically, editors can apply multiple taxonomy groups to a single content type, creating a flexible way to manage information.

For example, the Kbank demo site contains different taxonomy groups. The goal of _Products_ in Kbank is to show how you can use the taxonomy feature and support various scenarios.

- **Core** taxonomy: Provides semantic tags to further refine different content types into various topics and categories.
- **Currencies** taxonomy: Identifies the currency in which a financial service is available and helps global users understand their options.
- **Regional Availability** taxonomy: Specifies the countries where products or services are offered and supports the website's localization.
- **Financial Information** taxonomy: Defines attributes for financial product features, such as eligibility criteria or availability.

These examples demonstrate how you can approach modeling product-specific taxonomies in Xperience to help editors structure content while maintaining consistency and scalability.

For example, you can create dedicated content types to model relationships between different product (and other content type) categories and then group them accordingly.

![Taxonomy created with a dedicated content type item](https://docs.kentico.com/docsassets/modules/model-product-taxonomies/taxonomy-as-content-type-category-item.png "Taxonomy created with a dedicated content type item")

![Product with linked content item](https://docs.kentico.com/docsassets/modules/model-product-taxonomies/product-with-linked-content-item-as-taxonomy.png "Product with linked content item")

You’ve seen how you can break a complex financial product into a reusable content type, a composite of other content types.

![Product content type in simple graph](https://docs.kentico.com/docsassets/modules/model-product-taxonomies/graph-product-content-type-complete.png "Product content type in simple graph")

The image contains a comprehensive content model diagram for a _Product – Account_ content type. It shows how the _product_ content type comprises of taxonomies, reusable schemas, and related content types.

The _Product – Account_ content type includes core schema fields such as _title_, _short description_, _media_, _taxonomy_, and _product details_, where media fields references a standalone _Asset_ content type with fields for a _title_, _alt text_ or _media file_, and taxonomy is built through the [taxonomy](https://docs.kentico.com/documentation/developers-and-admins/configuration/taxonomies.md) feature.

_Benefits_ and _Product features_ are built through a reference to dedicated content types, where _Benefits_ store data like _description_ or _icon_, while _Product features_ contain fields for a _label_, _key_, _price_, _value_ or a _dedicated taxonomy group_ that defines availability of each feature.

It also contains multiple financial fields like _annual percentage rate_, _interest rate_ defined through reusable field schemas, and two fields that reference dedicated taxonomies – _Currencies_ and _Regional availability_.

Finally, the product contains this product's specific fields to store _minimal inflow_ requirements, and _overdraft limits_.

> **Info:** Interested in a different approach? Watch a short video about modeling a slightly different reusable Product content type.
>
> 🎬 [Video](https://www.youtube.com/embed/fX2zx2gvmqM?si=VuVnd1Qw3kn1l-Zu)