#What are Taxonomies?
Taxonomy Management is a central place to set up and reuse categories, tags, or hierarchies across your content. Instead of creating separate fields for each model, you define a taxonomy once and apply it wherever you need it.
Think of it as creating the “master list” of how your content should be classified. Whether it’s product categories, blog topics, or travel destinations, editors always work with the same set of options, and developers know the data is structured in the same way everywhere.
#Why Taxonomies?
As projects grow, classification systems tend to break down. One team creates a field for “Category,” another adds “Type,” someone else starts tagging free-text, and soon you’ve got duplicates, inconsistent naming, and content that’s hard to reuse.
That slows editors, who waste time searching or guessing which field to use. It frustrates developers, who can’t query data cleanly across models. And it makes scaling painful because every new model introduces more inconsistencies.
Taxonomy Management fixes this by giving you one shared source of truth. Editors tag with confidence. Developers get predictable data. The business avoids the cost of messy content down the line.
#Taxonomies in Action
Define a taxonomy in your schema, adding parent-child relationships if you need depth. Link it to any content model such as blog posts, products, landing pages, or more.
Editors see the same consistent terms everywhere they work. Like in the example below:
Developers query by taxonomy in GraphQL or REST to build filters, navigation, recommendations, or personalized feeds.
Because the taxonomy lives in the schema, it scales as your content grows. Adding a new market, product line, or content type doesn’t require reinventing categories - you simply just extend the existing taxonomy.
#The Impact Beyond Classifications
Taxonomy Management is about more than keeping things tidy. It creates real advantages:
- For editors: Less guesswork, faster tagging, and confidence that content will surface in the right places.
- For developers: Cleaner schema and predictable structures that make advanced use cases easy to build.
- For the business: Unlocks better discovery, smarter search, and personalized content experiences without costly cleanup projects later.
In short, it helps teams move faster and deliver better experiences as content grows more complex.
#Getting started
To try it: open your project in Hygraph Studio, go to Schema → Taxonomies, and create your first taxonomy (or start with the Demo Taxonomy). Connect it to any model, tag your content, and query it through the API right away.
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.
Blog Author