Introducing Taxonomies

#Making Content Findable and Future-Proof with Taxonomies

When 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.

#Why Taxonomies Matter

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:

• Provide smarter navigation and search, based on consistent categories and hierarchies.
• Enable personalization at scale, since content can be reliably filtered and targeted.
• Reduce editorial overhead, by removing the need to manually clean up or align tags.
• Build a future-proof content model, where new product lines, markets, or channels can be added without restructuring.

#Taxonomies in Hygraph

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:

• Hierarchical structure: Define clear relationships across with the required levels of depth.
• Central governance: Maintain a single source of truth and prevent duplication or inconsistent naming.
• Reusable across models: Apply taxonomies to any content type to avoid silos.
• Advanced filtering in GraphQL: Query both the value and its full path, and use operators like descendants_of to build rich faceted navigation or personalized feeds.

Editors see the same consistent terms everywhere they work. Like in the example below:

#A Practical Example

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.

#When to Use Taxonomies

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:

• Content needs to be classified consistently across multiple models or teams.
• Multi-level filtering is required (e.g. Category → Subcategory → Topic).
• Controlled vocabularies should be centrally managed and not left to free-text tagging.
• The same categories need to be applied across projects, channels, or product lines.

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.

#Build on Solid Foundations

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.

#Getting started

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.