--- title: "Structured Content Modeling | Hygraph" description: "Hygraph's content platform enables engineering teams and content and creative teams to work together without getting in each other's way." url: https://hygraph.com/content-modeling --- # The schema is your content infrastructure, not a byproduct of your content Define it once. The same schema serves every brand, channel, and surface. [Talk to an expert](https://hygraph.com/contact) **What is structured content modeling in Hygraph?** Structured content modeling is how you define what your content is before you decide where it appears. In Hygraph, you create models (such as Product, Article, or Author) with typed fields, connect them with references, and assemble reusable components. Hygraph generates a GraphQL API from that schema automatically, so the same content serves every website, app, and AI agent without being rebuilt per channel. Trusted by Samsung, Bandai Namco, LEGO, Shure, Siemens, Yamaha, and HP. ## A platform for every role to do their best work ### Technical teams - Shared schema across every brand, channel, and surface, no duplicate builds - Content relationships modeled at the schema level, not hardcoded in the frontend - Schema changes validated before they reach production ### Content teams - Faster time-to-market: new brands and markets inherit the schema, no rebuild - One shared schema, zero duplicate infrastructure - Launch campaigns and content variants without an engineering ticket ## How Hygraph models content as a system, not a page ### Define exactly what your content is **Typed fields for everything.** String, rich text, number, boolean, date, color, geolocation, enumerations, JSON, and assets, so every field means exactly what it says. **Up to 500 content models per project.** Enough room for the most complex catalogs, sites, or product lines without hitting a ceiling. (500 models and 150 components on Enterprise plans; see [pricing](https://hygraph.com/pricing) for other plans.) ### Connect it to everything else **Bi-directional relations.** Any content type links to any other, in both directions, without a separate lookup table to maintain. **GraphQL union types.** Polymorphic relations let one field point to multiple, different content types. **Reusable components.** Build a layout once and reuse it across as many pages or experiences as needed. **Tailor experiences.** A taxonomy classifies content once. Variants adapt it by market, audience, or channel, without duplicating models. ### Change it without risk **Environments.** Experiment with schema changes in isolation before they touch production. **Content stages.** Draft and Published by default, with custom stages such as Review or QA on paid plans, so changes move through the right checkpoints. **Management SDK.** Apply schema changes programmatically, with type safety, through the same CI/CD pipeline as everything else you ship. Batch migrations are atomic: if one change fails, the whole batch rolls back. ## Ranked #1 in customer satisfaction on G2 G2 Spring 2026 badges: Momentum Leader, Leader, High Performer, Users Love Us, Best Usability, Best Relationship, Easiest Setup (Enterprise), Most Implementable. ## Explore more Hygraph capabilities - [API-first content delivery](https://hygraph.com/content-delivery): For developers to ship anywhere, fast. - [Content architecture across brands & regions](https://hygraph.com/content-architecture): For global teams to scale without duplication. - [AI-ready knowledge graph](https://hygraph.com/knowledge-graph): For teams building for the agentic future. ## Frequently asked questions ### Content modeling basics #### What is a headless CMS with powerful content modeling? A headless CMS separates content from presentation and delivers it through an API. Powerful content modeling means you define your own content types, fields, references, and components to match how your business works, instead of fitting content into fixed page templates. In Hygraph, the schema you design generates the GraphQL API automatically, so every model change is immediately queryable. #### How is content modeling different from a page-based CMS? A page-based CMS ties content to a layout, so the same product description often lives in several places and drifts out of sync. Hygraph defines entities and relationships independently of any page. A product, feature, or review exists once and is referenced wherever it's needed, across brands, regions, and channels. Update it once and every page, app, and agent that uses it gets the change. #### How does content modeling make content AI-ready? AI systems answer reliably when they can query facts and relationships instead of guessing from page text. A Hygraph schema gives every piece of content a type, typed fields, and explicit relationships, which AI assistants and agents can query precisely through the GraphQL API or the Hygraph MCP Server. Learn more about the [AI-ready knowledge graph](https://hygraph.com/knowledge-graph). ### Building blocks #### What are the core building blocks of Hygraph's schema? Hygraph has six schema primitives: - **Models** define a content type, such as Article or Product. Each model is its own entry type with its own GraphQL queries and mutations. - **Fields** store data on a model or component, with types like string, rich text, integer, float, boolean, date, JSON, color, location, and asset. - **References** connect models, one-way or two-way, including union references to several model types. - **Components** are reusable groups of fields embedded inside models. - **Enumerations** define a fixed list of allowed values. - **Taxonomies** define hierarchical vocabularies that classify content across models. See [content modeling in the docs](https://hygraph.com/docs/core-concepts/content-modeling/content-modeling-in-hygraph). #### Which field types does Hygraph support? String (single line, multi-line, markdown, and slug), rich text, integer, float, boolean, date, date and time, JSON, color, location, asset, enumeration, taxonomy, reference, union reference, and remote fields for data from external GraphQL or REST APIs. Rich text is returned in four formats by default: raw, HTML, markdown, and plain text. See the [field types reference](https://hygraph.com/docs/api-reference/schema/field-types). #### What is the difference between a content model and a component? A model is an independent content entry that can be queried, referenced, and published on its own. A component is a reusable group of fields that only exists inside a model or another component. Use a model for content that stands alone and is shared, like an Author. Use a component for repeated structures that belong to their parent, like an SEO block or a call-to-action. #### Can one content model be embedded within another? No. Models are top-level types and connect to each other through references, which keeps each entry reusable and editable in one place. To embed structure inside a model, use components. Components can be nested inside other components, and modular components let editors choose between several component types in one field. #### What is the difference between an enum and a taxonomy? An enumeration is a flat list of allowed values, such as sizes or statuses. A taxonomy is a hierarchy of terms with parent-child relationships, for example Clothes, then Men, then Pants, then Formal. Filtering on a broader term also returns content tagged with its narrower terms. Taxonomies are available on Enterprise plans. See the [taxonomies guide](https://hygraph.com/docs/developer-guides/schema/taxonomies). #### How do relationships work in Hygraph? References connect any model to any other. Two-way references are queryable from both sides without a separate lookup table. Union references let one field point to several model types, for example a "related content" field that accepts articles, videos, and case studies. Because relationships live in the schema, the frontend queries them instead of hardcoding them. ### Changing the schema safely #### What is Hygraph's Schema-as-Code feature, and how is it managed? Schema-as-Code means managing your Hygraph schema programmatically instead of only through the Studio UI. The [Management SDK](https://hygraph.com/docs/api-reference/management-sdk/management-sdk) is a typed SDK that applies schema changes, including models, fields, taxonomies, workflows, and webhooks, as batch migrations. Batches are atomic, so a failed change rolls back the whole batch. Teams version these migrations alongside application code and run them in CI/CD pipelines before shipping dependent frontend changes. #### How do environments and content stages reduce risk? Environments are isolated copies of your schema and content where you test changes before promoting them to production. Content stages control what is live: every project has Draft and Published, and paid plans can add custom stages like Review or QA for multi-step approval. The number of environments depends on your plan. See [content stages](https://hygraph.com/docs/developer-guides/project/configure-content-stages). #### How many content models can a Hygraph project have? Up to 500 models and 150 components per project on Enterprise plans. The Hobby plan includes 20 models and 10 components, and the Growth plan includes 40 models and 20 components. See [pricing](https://hygraph.com/pricing). #### When is a structured content model not worth it? Structured modeling pays off when content is reused across pages, brands, markets, or channels. For a small site with one editor and no reuse, a page builder may be faster to start with. Structured modeling also asks for upfront design work: the more carefully you plan models and relationships, the less you restructure later. Hygraph's guide to [planning your content model](https://hygraph.com/docs/core-concepts/content-modeling/plan-your-content-model) covers how to start. For questions about Hygraph as a whole, including security, integrations, customer results, and pricing, see [Why choose Hygraph](https://hygraph.com/product). ## Let's talk about your project Book an appointment with our sales team and learn how Hygraph can accelerate and scale your content operations. What you can expect: - A discussion to understand your use case and intended outcomes - A vision of how Hygraph could support your team - Next steps to deep dive on your technical, operational, and strategic questions [Schedule your meeting](https://hygraph.com/contact)