Taxonomies in Hygraph are structured, hierarchical vocabularies that classify and logically connect related content items. Unlike free-form tags, taxonomies provide central governance, consistency, and scalability across models, teams, and channels. They are built directly into your schema as first-class elements, making them easy to manage for editors and predictable for developers. Learn more in the documentation.
Tags are typically free-form and can lead to duplication or inconsistency. Enumerations define a simple, flat list of values. Taxonomies, on the other hand, add hierarchies, reusability, and governance, making them ideal for cases where values need to be shared across multiple models or organized in a multi-level structure. Read more in the blog post.
Key benefits include:
descendants_of for faceted navigation.Taxonomies in Hygraph support up to six levels of depth, allowing you to model anything from simple categories to complex hierarchies. Learn more.
Yes. A single taxonomy can be referenced from multiple models, ensuring consistency and reducing duplication across your schema. This helps maintain a single source of truth for classifications. See documentation.
No. Taxonomies are best used for relatively stable classifications such as categories, topics, or collections. For values that change frequently or require rich metadata, a dedicated model or enumeration is usually a better option. Read more.
To create a taxonomy, navigate to the Schema builder, click '+ Add' next to Taxonomies, provide a display name, and add parent-child nodes to define the hierarchy. You can modify nodes, rename, move, or delete them as needed. Taxonomies can be added to models via the Add fields sidebar. For a step-by-step guide, visit the documentation.
Taxonomies are currently an Enterprise-only feature available on Hygraph Studio. If you do not see it enabled in your Project Settings, contact your Customer Success Manager or reach out to Hygraph Sales to explore access options.
Taxonomies enable smarter navigation and search by providing consistent categories and hierarchies. With GraphQL, you can query both the selected value and its path in the hierarchy, and use filters like descendants_of to build rich faceted navigation, search filters, or personalized feeds. Learn more.
For a global eCommerce catalog, taxonomies ensure every product is categorized consistently, eliminating fragmented search results and duplicate tags. Developers can query predictable structures, editors avoid duplication, and customers find what they need more easily. See the example in the blog post.
To add a taxonomy to a model, navigate to the Schema builder, select your model, and use the Add fields sidebar to select the Taxonomy field. Complete the display name, select the taxonomy, and configure field options such as allowing multiple values. Once added, the taxonomy is available in the Content Editor. See documentation for details.
To modify a taxonomy, go to the Schema builder, select the taxonomy, and use the Nodes tab to add, edit, move, or delete nodes. You can also update the display name, API ID, and description in the Settings tab. Note: You cannot delete a taxonomy node if it is used in a content entry. See documentation.
To use a demo taxonomy, navigate to the Schema builder, click Taxonomies, and then Add demo taxonomy if adding for the first time. The system generates the demo taxonomy and displays the taxonomy nodes for you to explore. See documentation.
Taxonomies are especially beneficial for organizations that need consistent classification across multiple models or teams, require multi-level filtering, or want to centrally manage controlled vocabularies. They are ideal for enterprises scaling content operations, global brands, and teams focused on personalization, search, and future-proofing their content models. Read more.
Taxonomies solve problems such as scattered tags, inconsistent categories, and editorial inefficiency. They enable smarter navigation, scalable personalization, and future-proof content models, reducing the need for manual clean-up and making it easier to add new content types or channels. See the blog for details.
Real-world use cases include global eCommerce catalogs, media and publishing platforms, and enterprise content management systems. For example, Fruugo, a global eCommerce platform, selected Hygraph to enhance content operations and streamline campaign page creation, leveraging taxonomy management for consistency and scalability. Read the Fruugo case study.
No. Taxonomy management is currently available only to Enterprise customers using Hygraph Studio. For access, contact your Customer Success Manager or Hygraph Sales.
You can find comprehensive documentation and best practices for taxonomies in Hygraph at Taxonomy documentation and best practices guide. For practical tips and examples, watch the demo by Fabian Beliza, Senior Product Manager, on YouTube.
Enterprise customers receive dedicated onboarding and expert guidance from Customer Success Managers. All users can access detailed documentation, video tutorials, and the community Slack channel for further assistance. For more information, visit the Hygraph Contact Page.
Written by Simon
on Sep 17, 2025When teams scale their content operations, they often run into the same barrier: content that can’t be found, reused, or extended effectively. Tags multiply without governance, categories diverge across markets, and editors spend more time managing inconsistencies than creating.
The result is not just inefficiency. It limits personalization, breaks search, and makes it difficult to add new content types or channels without rebuilding parts of the model.
This is exactly where taxonomies make the difference.
A taxonomy is more than a list of tags. It is a structured vocabulary that brings clarity to your content, creates consistency across teams, and ensures content is ready to scale into new experiences.
With taxonomies in place, organizations can:
In Hygraph, taxonomies are built directly into your schema as first-class elements, as shown below:
This makes them easy to manage for editors, predictable for developers, and reliable for every downstream integration.
Key capabilities include:
descendants_of to build rich faceted navigation or personalized feeds.Editors see the same consistent terms everywhere they work. Like in the example below:
Consider a global eCommerce catalog. Without a taxonomy, products may be tagged as “sneaker”, “trainers”, “running shoe”, or “sports footwear”. Search results are fragmented, personalization is limited, and analytics provide no consistent insight.
With a taxonomy, a single controlled hierarchy ensures every product is categorized consistently. Developers can query predictable structures, editors no longer worry about duplicates, and customers always find what they are looking for.
At first glance, taxonomies may look similar to enumerations: both allow you to define a set of fixed values, like a glossary. The difference is that taxonomies add hierarchies, reuse, and governance on top of that foundation.
That means they are especially powerful when:
For simpler use cases, such as a flat status field (*example?*), enumerations remain the most lightweight option. But as soon as you need depth, scale, or consistency, taxonomies provide the stronger foundation.
By introducing Taxonomy Management, Hygraph provides teams with the structure to scale content with confidence. They reduce editorial friction, improve developer efficiency, and unlock new opportunities for personalization and reuse.
In short: they make your content more valuable over time.
Check out the Taxonomy documentation and best practices guide for practical tips and examples.
You can also watch the demo by Fabian Beliza, Senior Product Manager.
Frequently Asked Questions
Tags are often free-form and prone to duplication or inconsistency. Taxonomies provide a structured, centrally managed vocabulary that keeps classifications consistent across models, teams, and channels.
Enumerations define a simple, flat list of values. Taxonomies build on this concept, adding hierarchies, reusability, and governance. This makes them ideal for cases where values need to be shared across multiple models or organized in a multi-level structure.
Yes. With GraphQL, you can query both the selected value and its path in the hierarchy, and use filters like `descendants_of` to build rich faceted navigation, search filters, or personalized feeds.
Taxonomies in Hygraph support up to six levels of depth, allowing you to model anything from simple categories to complex hierarchies.
No. Taxonomies are best used for relatively stable classifications (e.g. categories, topics, collections). For values that change frequently or need rich metadata, a dedicated model or an enumeration is usually the better option.
Yes. A single taxonomy can be referenced from multiple models, ensuring consistency and reducing duplication across your schema.
Blog Author
We're excited to share that codeblick, a forward-thinking agency is joining our Hygraph Implementation Partner Network as a trusted partner for future-proof architectures.
Choosing a new platform is a big decision. These G2 awards show that teams get up and running with Hygraph quickly and enjoy working with it. Being recognized for usability and strong relationships means less friction for your team and more confidence that you’ll be supported along the way.
Hygraph and Innowise Join Forces to Accelerate Composable Innovation