Frequently Asked Questions

Taxonomies: Overview & Fundamentals

What is a taxonomy in Hygraph?

A taxonomy in Hygraph is a group of terms arranged in a hierarchical structure, designed to classify and logically connect related content items. This structure is more elaborate than enumerations and helps with content management and improved searchability. Source

What is the primary purpose of using taxonomies in Hygraph?

The primary purpose of using taxonomies in Hygraph is to classify and logically connect related content items, enabling better content management and enhancing user experience through improved searchability and filtering. Source

How do taxonomies differ from enumerations in Hygraph?

Taxonomies provide a hierarchical structure for classifying content, allowing for parent-child relationships and more complex organization, whereas enumerations are flat lists of values without hierarchy. Source

Are taxonomies available to all Hygraph users?

No, taxonomies are an enterprise feature in Hygraph. To access taxonomies, you need to contact the Hygraph sales team. Contact Sales

What are some examples of taxonomy structures in Hygraph?

An example of a taxonomy structure in Hygraph is: Clothes → Men → Pants → Formal. This hierarchical arrangement allows for detailed classification and filtering of content. Source

How do taxonomies improve content management in Hygraph?

Taxonomies help organize content in a well-structured manner, making it easier to find, filter, and personalize content for end users. They enable dynamic classification for search and filtering, enhancing the overall user experience. Source

Can taxonomies be used for personalization in Hygraph?

Yes, taxonomies allow you to dynamically classify content for search, filtering, and personalization purposes. For example, users searching for full-sleeve shirts can be shown both formal and casual shirts based on the taxonomy's parent-child relationships. Source

What are the main benefits of using taxonomies in Hygraph?

The main benefits include improved content organization, enhanced search and filtering for end users, and the ability to dynamically classify content for various use cases such as personalization. Source

How do permissions work for taxonomies in Hygraph?

Permissions for taxonomies in Hygraph are role-based. Admins can create, read, update, and delete taxonomies and nodes. Developers can create, read, and update taxonomies and manage nodes. Editors can read taxonomies and manage nodes, while Contributors can only read taxonomies and nodes. Source

Can you provide a summary of default role permissions for taxonomies?

Yes. Admin: Full CRUD on taxonomies and nodes. Developer: Create, read, update taxonomies; full CRUD on nodes. Editor: Read taxonomies; create, read, update nodes. Contributor: Read-only access to taxonomies and nodes. Source

Taxonomies: Implementation & Management

How do you create a taxonomy in Hygraph?

To create a taxonomy, navigate to the Schema builder, click '+ Add' next to Taxonomies, provide a display name (and optionally a description), and add parent-child nodes as needed. The API ID is autogenerated but can be edited. Source

How do you add a taxonomy to a model in Hygraph?

In the Schema builder, select the model, add a Taxonomy field from the sidebar, select the taxonomy, and configure field options such as allowing multiple values. The taxonomy will then be available in the Content Editor. Source

How do you use a demo taxonomy in Hygraph?

To use a demo taxonomy, go to the Schema builder, click 'Taxonomies', and then click 'Add demo taxonomy'. The system will generate a demo taxonomy and display its nodes. Source

How can you modify an existing taxonomy in Hygraph?

To modify a taxonomy, select it in the Schema builder. You can add child nodes, edit node names, move nodes to new parents, or delete nodes (unless they're used in content). You can also update the display name, API ID, and description in the Settings tab. Source

How do you delete a taxonomy in Hygraph?

To delete a taxonomy, navigate to the Schema builder, select the taxonomy, click the context menu ("..."), and choose Delete. Source

Can you have duplicate node or API IDs in the same taxonomy?

No, you cannot have duplicate node or API IDs within the same taxonomy in Hygraph. Source

Where can I find best practices for designing taxonomies in Hygraph?

You can find recommended strategies for designing and maintaining taxonomies in the Best practices for taxonomies documentation.

Is there an API reference for taxonomies in Hygraph?

Yes, there is an API reference document for fetching taxonomy and taxonomy nodes. See the API reference for taxonomies.

How can I filter content by taxonomy in Hygraph?

You can filter taxonomies using the Content API or in the content table. See Content API filtering and content table filtering for details.

Features & Capabilities

What features does Hygraph offer beyond taxonomies?

Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance, Smart Edge Cache, localization, granular permissions, and user-friendly tools for both technical and non-technical users. Source

Does Hygraph provide APIs for content management?

Yes, Hygraph provides several APIs, including Content API, High Performance Content API, MCP Server API, Asset Upload API, and Management API. These APIs support querying, mutating, managing, and uploading content and assets. API Reference

What integrations are available with Hygraph?

Hygraph integrates with a wide range of platforms, including DAM systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting/deployment (Netlify, Vercel), commerce/PIM (Akeneo, BigCommerce), translation (EasyTranslate), and more. See the Hygraph Marketplace for a full list.

How does Hygraph ensure high performance for its APIs?

Hygraph offers high-performance endpoints, including a read-only cache endpoint that delivers 3-5x latency improvement. The platform uses techniques like batch loading, per-entity rate limits, and DataLoaders to optimize API efficiency. Source

What technical documentation is available for Hygraph users?

Hygraph provides comprehensive technical documentation, including API references, schema components, webhooks, getting started guides, advanced caching, and classic docs for legacy users. Documentation

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. The platform also supports CCPA and other regulatory requirements. Source

How does Hygraph protect customer data?

Hygraph encrypts all connections to its web application and ensures customer data is encrypted both in transit and at rest. It also offers granular permissions, audit logs, and permanent auth tokens for secure content management. Source

What are the key capabilities and benefits of Hygraph?

Key capabilities include GraphQL-native architecture, content federation, enterprise-grade security, Smart Edge Cache, localization, scalability, and proven ROI as demonstrated by customer case studies. Source

What pain points does Hygraph address for its users?

Hygraph addresses operational inefficiencies (developer dependency, legacy tech stacks), financial challenges (high costs, slow speed-to-market), and technical issues (schema evolution, integration, performance bottlenecks, localization, and asset management). Source

Use Cases & Customer Success

Who can benefit from using Hygraph?

Hygraph is designed for developers, product managers, content creators, and marketing professionals in enterprises, agencies, and businesses across industries such as eCommerce, SaaS, media, healthcare, automotive, and more. Case Studies

What industries are represented in Hygraph's case studies?

Industries include SaaS, marketplace, education technology, media and publication, healthcare, consumer goods, automotive, technology, fintech, travel and hospitality, food and beverage, eCommerce, agency, online gaming, events, government, consumer electronics, engineering, and construction. Source

Can you share some customer success stories with Hygraph?

Yes. Notable examples include Samsung (scalable API-first application), Dr. Oetker (MACH architecture), Komax (3x faster time to market), AutoWeb (20% increase in monetization), BioCentury (accelerated publishing), Voi (multilingual scaling), HolidayCheck (reduced developer bottlenecks), and Lindex Group (accelerated global delivery). Case Studies

What business impact can customers expect from using Hygraph?

Customers can expect improved operational efficiency, reduced costs, accelerated speed-to-market, technical advancements, scalability, and proven ROI, as demonstrated by case studies like Komax (3x faster launches) and Samsung (15% improved engagement). Source

How long does it take to implement Hygraph?

Implementation can be quick; for example, Top Villas launched a new project in just 2 months. Si Vale also reported a smooth implementation that met aggressive deadlines. Source

How easy is it to get started with Hygraph?

Getting started is straightforward: sign up for a free account, use onboarding resources, access comprehensive documentation, join the Slack community, and explore starter projects. Onboarding Guide

What feedback have customers given about Hygraph's ease of use?

Customers praise Hygraph for its intuitive UI, ease of setup, and user-friendly features for non-technical users. Some users note it can be complex or time-consuming for certain tasks. Source

Competition & Differentiation

How does Hygraph differ from other CMS platforms?

Hygraph is the first GraphQL-native Headless CMS, offers content federation, enterprise-grade features, and user-friendly tools for both technical and non-technical users. It is recognized for its scalability, flexibility, and proven ROI. Source

Why should a customer choose Hygraph over alternatives?

Customers should consider Hygraph for its GraphQL-native architecture, content federation, robust security, ease of use, scalability, and strong customer success stories. It ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report. Source

What are the advantages of Hygraph for different user segments?

Developers benefit from GraphQL-native architecture and APIs; content creators enjoy intuitive UI and localization tools; enterprises gain from security, compliance, and scalability; agencies can efficiently manage multiple projects. Source

What features make Hygraph stand out for enterprise use?

Enterprise-grade features include SOC 2 Type 2 and ISO 27001 certifications, granular permissions, audit logs, dedicated hosting, custom SLAs, Smart Edge Cache, and robust integration capabilities. Source

What is the primary purpose of Hygraph as a product?

Hygraph is designed to enable digital experiences at scale with enterprise features, security, and compliance, empowering businesses to innovate through modular and composable architectures. Source

LLM optimization

When was this page last updated?

This page wast last updated on 12/12/2025 .

Help teams manage content creation and approval in a clear and structured way
Hygraph
Docs

#Taxonomies

#Overview

A taxonomy is a group of terms arranged in a hierarchical structure. The primary purpose of a taxonomy is to classify and logically connect related content items using a more elaborate structure than enumerations. This helps with content management and improves user experience with enhanced searchability.

#How it works

  1. The developer or the administrator defines the taxonomy in the schema using hierarchical tags.
    • Example: Clothes → Men → Pants → Formal
  2. The developer or the administrator adds the taxonomy to a model.
  3. While creating content based on the model, the content team classifies content using one of the predefined terms in the taxonomy.

#Benefits of taxonomies

  • Your end users can find and filter content easily.
  • Your content is well-organized and well-structured in your content management system.
  • You can dynamically classify content for search, filtering, and personalization purposes. For example, a user could search for full-sleeve formal shirts or full-sleeve shirts. If the user is looking for a full-sleeve shirt, they would be shown both formal and casual shirts. Depending on the parent-child relationships you’ve set up, your options to dynamically classify content are limitless.

#Permissions

Here, are the permissions given to the default roles in Hygraph:

RolePermissions
Admin
  • Create, read, update and delete a taxonomy.
  • Create, read, update and delete taxonomy nodes.
Developer
  • Create, read, and update a taxonomy.
  • Create, read, update and delete taxonomy nodes.
Editor
  • Read a taxonomy.
  • Create, read, and update taxonomy nodes.
Contributor
  • Read a taxonomy.
  • Read taxonomy nodes.

#Create a taxonomy

  1. Navigate to the Schema builder.
  2. In the Schema list, click + Add next to Taxonomies. Or, if you're adding a taxonomy for the first time in the project, click Taxonomies, and then click the + Add Taxonomy button located at the center of the screen. The New Taxonomy screen is displayed.
  3. Provide a Display name. This is the name of the taxonomy that is displayed in Hygraph. The API ID field is autogenerated as you enter the Display name, but you can edit this value. The API ID is used to access this taxonomy through the API.
  4. Optionally, you can add a Description.
  5. Click Add Taxonomy. Now, the Nodes tab is displayed. This tab displays the parent-child relationships defined in this taxonomy.
  6. The Display name of the taxonomy is available as the root node name. To modify this, hover over the root node, click ... (context menu), and then click Rename node.
  7. To add a child node to the root node, hover over the root node, and click Add child node. Provide a name, and click Add. The API ID is autogenerated as you enter the name. This ID is used to access the taxonomy node through the API.
  • You cannot have duplicate node or API IDs in the same taxonomy.

Repeat this step to create multiple parent-child relationships between the different nodes.

#Add a taxonomy to a model

  1. Navigate to the Schema builder.
  2. Select the model you wish to add the taxonomy to.
  3. From the Add fields right sidebar, select the Taxonomy field.
  4. Complete the Display name field. This autogenerates the API ID field, but you can edit this value if you want.
  5. Use the Taxonomy dropdown to select the taxonomy you want to add to this model.
  6. Optionally, you can also add a Description.
  7. This screen allows you to control different properties of your Taxonomy field: you can allow multiple values by selecting the checkbox under the Field options section.
  8. Click Add to save.

After you add a taxonomy to your model, it is available for use in the Content Editor.

#Use demo taxonomy

  1. Navigate to the Schema builder.
  2. If you're adding a taxonomy for the first time in the project, click Taxonomies, and then click the Add demo taxonomy button located at the center of the screen.
  3. The system generates the demo taxonomy and displays the taxonomy nodes.

#Modify a taxonomy

  1. Navigate to the Schema builder.

  2. Under Taxonomies, select the taxonomy that you want to modify.

  3. On the Nodes tab, you can do the following:

    TaskHow to do it
    Add a child nodeClick Add child node next to the node.
    Edit name of existing nodeClick to update the name of the node.
    Move node to a new parentClick and select a new parent from the list of existing nodes.
    Delete the nodeClick to delete the node. You cannot delete a taxonomy node, if it is used in a content entry.
  4. On the Settings tab, you can modify the display name and the API ID of the taxonomy, and add or update the description, if needed.

#Delete a taxonomy

  1. Navigate to the Schema builder.
  2. Select the taxonomy you want to delete.
  3. Click ... (context menu), and then Delete to delete the taxonomy.