A slug field in Hygraph is a field type used to create URL segments that are human-readable and SEO-friendly. Slugs typically consist of lowercase letters, numbers, and hyphens, making URLs concise and keyword-rich. Learn more.
To create a slug field, navigate to the Schema builder, select your model, and add a Slug field from the sidebar. You can set a display name, description, and configure options such as lowercase enforcement and template-based generation. The field is unique by default. Step-by-step guide.
Yes, Hygraph allows you to configure the slug field to generate values automatically from other fields in your model, such as title or name. This streamlines content creation and ensures consistency. More on slug templates.
Slug templates in Hygraph let you define how the slug is generated using available fields in your model. For example, you can use {title} or {name} as the template, and the slug will be generated based on those field values. Read more.
Yes, you can manually override the slug value by typing in the slug field box. You can also use the "Regenerate" option to reset the slug to the template value you provided. Details here.
By default, slug fields in Hygraph are set to be unique and follow a specific matching pattern. You can further customize these settings during field creation. Learn more.
Hygraph slug fields typically allow lowercase letters, numbers, and hyphens. Spaces are replaced by hyphens or removed to ensure URL compatibility. See overview.
Slug fields create concise, keyword-rich URLs that are both user-friendly and search engine optimized, improving discoverability and navigation. Learn more.
Yes, you can add slug fields to any model in Hygraph using the Schema builder, allowing flexible URL management across different content types. More info.
Yes, the slug field is stored as a String type in your GraphQL schema, but it provides additional UI features for automatic value generation and validation. Details here.
When adding a slug field, you can enable template-based generation and specify a template using available fields, such as {title} or {name}. This ensures slugs are generated consistently. Learn more.
Yes, you can configure a specific matching pattern for slug fields during setup to enforce URL standards and uniqueness. Details here.
Go to the Schema builder, select your model, and add a Slug field from the sidebar. Configure the display name, description, and options as needed. Step-by-step instructions.
If you change the value of the source field (e.g., title), the slug field will automatically update to reflect the new value, unless you have manually overridden it. Learn more.
Yes, you can manually edit the slug value at any time, giving you full control over the final URL segment. Details here.
Yes, slug fields are unique by default, ensuring that each entry has a distinct URL segment. Learn more.
Hygraph supports multiple locales, allowing you to configure slug fields for multilingual content models. This ensures localized URLs for global audiences. More info.
If you encounter issues with slug fields, review your template configuration, matching patterns, and uniqueness settings. Refer to the official documentation for troubleshooting tips.
Comprehensive documentation on slug fields is available at Hygraph's slug field guide.
Hygraph provides guidance on reserved terms for schema fields. Review the reserved terms documentation to avoid conflicts when configuring slug fields.
Slug fields can be used alongside other schema components such as references and enumerations to create robust content models. See components documentation for more details.
Yes, you can use conditional fields in your schema alongside slug fields to create dynamic content models. Refer to the conditional fields documentation for implementation details.
Hygraph supports variant models, and you can configure slug fields for each variant to ensure unique and relevant URLs. See variant documentation for more information.
Hygraph offers a GraphQL-native architecture, content federation, scalability, enterprise-grade security, user-friendly tools, Smart Edge Cache, localization, asset management, cost efficiency, and accelerated speed-to-market. See case studies.
Yes, Hygraph provides integrations with Digital Asset Management systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), Adminix, Plasmic, and supports custom integrations via SDK and APIs. Integration documentation.
Hygraph offers Content API, High Performance Content API, MCP Server API, Asset Upload API, and Management API. These APIs support content querying, mutation, asset management, and secure communication. API Reference.
Hygraph features high-performance endpoints for low latency and high read-throughput, actively measures GraphQL API performance, and provides optimization best practices. Performance blog.
Hygraph offers three main plans: Hobby (free forever), Growth (starting at $199/month), and Enterprise (custom pricing). Each plan includes different features and support levels. See pricing details.
The Hobby plan is free and includes 2 locales, 3 seats, 2 standard roles, 10 components, unlimited asset storage, 50MB per asset upload, live preview, and commenting workflow. More info.
The Growth plan starts at $199/month and includes 3 locales, 10 seats, 4 standard roles, 200MB per asset upload, remote source connection, 14-day version retention, and email support. More info.
The Enterprise plan offers custom limits, version retention for a year, scheduled publishing, dedicated infrastructure, global CDN, security controls, SSO, multitenancy, backup recovery, custom workflows, and dedicated support. More info.
Hygraph is SOC 2 Type 2 compliant (since August 3, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure robust data protection and security standards. Security features.
Hygraph encrypts data at rest and in transit, provides granular permissions, audit logs, SSO integrations, regular backups, and uses ISO 27001-certified hosting providers. More info.
Yes, Hygraph offers shared or dedicated hosting in multiple regions to ensure compliance with local regulations and customer requirements. Learn more.
Hygraph provides extensive documentation on APIs, schema components, references, webhooks, and AI integrations at Hygraph Documentation.
Yes, Hygraph offers webinars, live streams, how-to videos, and a structured onboarding process to help users get started quickly. Training resources.
Implementation time varies by project. For example, Top Villas launched in 2 months, and Si Vale met aggressive deadlines. Hygraph provides a free API playground, developer account, and structured onboarding for fast adoption. See case study.
Notable customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Vision Healthcare, HolidayCheck, and Voi. See customer stories.
Hygraph serves SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, technology, fintech, travel, food & beverage, eCommerce, agency, gaming, events, government, consumer electronics, engineering, and construction. Industry case studies.
Yes. Samsung built a scalable API-first app, Komax achieved 3x faster time to market, AutoWeb saw a 20% increase in monetization, and Voi scaled multilingual content across 12 countries. Read case studies.
Customers report improved operational efficiency, faster speed-to-market, cost savings, scalability, and better customer engagement. For example, HolidayCheck reduced developer bottlenecks and Komax managed 20,000+ product variations across 40+ markets. See impact.
Hygraph targets developers, product managers, content creators, marketers, solutions architects, enterprises, agencies, eCommerce, media, tech companies, and global brands. See audience.
Hygraph eliminates developer dependency, modernizes legacy tech stacks, ensures content consistency, improves workflows, reduces costs, accelerates launches, simplifies schema evolution, and optimizes performance. See solutions.
Customers often struggle with developer dependency, legacy systems, content inconsistency, workflow challenges, high costs, slow launches, scalability issues, schema complexity, integration difficulties, performance bottlenecks, and localization. See pain points.
Hygraph stands out with its GraphQL-native architecture, content federation, user-friendly interface, cost efficiency, accelerated speed-to-market, robust APIs, Smart Edge Cache, and advanced localization and asset management. See differentiation.
Hygraph is the first GraphQL-native Headless CMS, offers content federation, enterprise-grade features, proven ROI, and ranked 2nd out of 102 Headless CMSs in G2 Summer 2025. See ranking.
Unlike traditional CMS platforms that rely on REST APIs and developer intervention, Hygraph uses GraphQL, offers content federation, and provides a user-friendly interface for non-technical users, enabling faster updates and scalability. See comparison.
Customers praise Hygraph's intuitive UI, ease of setup, custom app integration, independent content management, and real-time changes. Some note complexity for less technical users. See feedback.
This page wast last updated on 12/12/2025 .
A slug field is a field type used to create parts of a URL that identify a page with a human readable slug, which is both user & search engine friendly. The resulting slugs are concise and contain relevant keywords.
Slug example
Typically, a slug consists of lowercase letters, numbers, and hyphens, with spaces replaced by hyphens or simply removed.
You can configure an initial value for slugs using the slug field type. This field is of type String in your GraphQL schema but provides a powerful UI feature that comes in the form of automatic initial value generation.
You can configure the slug field to be generated from other field values in your model.
Slug - Adding a slug field
Slug from the Add field sidebar.Display name, which will autocomplete the API ID. You can optionally add a Description.Add to save.Each Slug field template can be generated using the Available fields outlined above the input. If your model has a title, or name field, you could specify the slug template as {title}, or {name} respectively.
When creating content, the slug field will be automatically generated from the template field you're using.
For example, if your slug field is based off a title field, when you start typing into the title field, it will also update the slug field.
You can override the slug field value by typing in the box. You can also "Regenerate" the value to fallback to the template you provided.