Hygraph | Website Analysis by Allsite Studio

SEO

Homepage Leads with a 2,000-Word Hidden FAQ Block Before Any Visible Content

Score

38

Severity

High

Finding

The raw HTML of the Hygraph homepage begins with an enormous structured FAQ section — approximately 2,000 words of Q&A content covering AI features, pricing plans, technical integrations, security certifications, use cases, and competitive comparisons — before any of the visible hero content (H1, CTA, logo strip). This FAQ is rendered as the first DOM content but appears to be visually hidden (not displayed to standard visitors). The block includes a footer line: 'When was this page last updated? This page wast last updated on 12/12/2025.' — notably with a typo ('wast' instead of 'was'). This is a deliberate LLM/GEO (Generative Engine Optimisation) strategy — injecting structured FAQ content so that AI assistants like ChatGPT, Perplexity, and Claude cite Hygraph when answering questions about headless CMS. It is a sophisticated SEO tactic but contains a critical typo in the attribution line.

Recommendation

The GEO FAQ block is a smart strategy — structured, detailed, and comprehensive. Two fixes are needed: (1) fix the typo in the metadata line: 'This page wast last updated' → 'This page was last updated'; (2) ensure the FAQ content is updated at least quarterly to reflect new products, pricing changes, and competitive positioning — the 'last updated' date of 12/12/2025 is now 3+ months stale. Additionally, verify the FAQ's Schema.org FAQPage markup is correctly implemented so that Google surfaces Hygraph's FAQ answers in rich results for headless CMS queries — this is the secondary benefit of the GEO approach and requires proper structured data to activate.

SEO

Homepage Leads with a 2,000-Word Hidden FAQ Block Before Any Visible Content

Score

38

Severity

High

Finding

The raw HTML of the Hygraph homepage begins with an enormous structured FAQ section — approximately 2,000 words of Q&A content covering AI features, pricing plans, technical integrations, security certifications, use cases, and competitive comparisons — before any of the visible hero content (H1, CTA, logo strip). This FAQ is rendered as the first DOM content but appears to be visually hidden (not displayed to standard visitors). The block includes a footer line: 'When was this page last updated? This page wast last updated on 12/12/2025.' — notably with a typo ('wast' instead of 'was'). This is a deliberate LLM/GEO (Generative Engine Optimisation) strategy — injecting structured FAQ content so that AI assistants like ChatGPT, Perplexity, and Claude cite Hygraph when answering questions about headless CMS. It is a sophisticated SEO tactic but contains a critical typo in the attribution line.

Recommendation

The GEO FAQ block is a smart strategy — structured, detailed, and comprehensive. Two fixes are needed: (1) fix the typo in the metadata line: 'This page wast last updated' → 'This page was last updated'; (2) ensure the FAQ content is updated at least quarterly to reflect new products, pricing changes, and competitive positioning — the 'last updated' date of 12/12/2025 is now 3+ months stale. Additionally, verify the FAQ's Schema.org FAQPage markup is correctly implemented so that Google surfaces Hygraph's FAQ answers in rich results for headless CMS queries — this is the secondary benefit of the GEO approach and requires proper structured data to activate.

SEO

Homepage Leads with a 2,000-Word Hidden FAQ Block Before Any Visible Content

Score

38

Severity

High

Finding

The raw HTML of the Hygraph homepage begins with an enormous structured FAQ section — approximately 2,000 words of Q&A content covering AI features, pricing plans, technical integrations, security certifications, use cases, and competitive comparisons — before any of the visible hero content (H1, CTA, logo strip). This FAQ is rendered as the first DOM content but appears to be visually hidden (not displayed to standard visitors). The block includes a footer line: 'When was this page last updated? This page wast last updated on 12/12/2025.' — notably with a typo ('wast' instead of 'was'). This is a deliberate LLM/GEO (Generative Engine Optimisation) strategy — injecting structured FAQ content so that AI assistants like ChatGPT, Perplexity, and Claude cite Hygraph when answering questions about headless CMS. It is a sophisticated SEO tactic but contains a critical typo in the attribution line.

Recommendation

The GEO FAQ block is a smart strategy — structured, detailed, and comprehensive. Two fixes are needed: (1) fix the typo in the metadata line: 'This page wast last updated' → 'This page was last updated'; (2) ensure the FAQ content is updated at least quarterly to reflect new products, pricing changes, and competitive positioning — the 'last updated' date of 12/12/2025 is now 3+ months stale. Additionally, verify the FAQ's Schema.org FAQPage markup is correctly implemented so that Google surfaces Hygraph's FAQ answers in rich results for headless CMS queries — this is the secondary benefit of the GEO approach and requires proper structured data to activate.

Copy

Hero H1 'Structure changes everything' — Abstract Brand Claim With No Product Category

Score

44

Severity

High

Finding

The homepage H1 is 'Structure changes everything.' This is a punchy, confident brand line — but it provides zero product category information. A developer or VP of Engineering who lands on hygraph.com without prior context cannot determine from the H1 alone whether this is a database product, a CMS, a design tool, or a content infrastructure platform. The sub-headline helps: 'Model and govern structured, relational content for the apps and sites that power brands, commerce, portals, and AI systems.' — but it requires reading 20 words before 'content' appears as a category signal. Competitors position more explicitly in their H1s: Contentful's 'The Content Platform'; Sanity's 'The Composable Content Cloud'; Storyblok's 'The Headless CMS for Content-Driven Experiences'. Hygraph's H1 is the most abstract of the category.

Recommendation

Either: (a) add a category micro-label above the H1 — 'Headless CMS for Enterprise Teams' in small caps before 'Structure changes everything' — so the category is anchored before the brand line lands; or (b) restructure the H1 to do both jobs: 'The headless CMS where structure changes everything.' This approach preserves the brand idea while front-loading the category. Option (a) is preferable because it keeps the H1's rhythm intact while adding the visitor-orienting context. The sub-headline's mention of 'AI systems' is currently the strongest differentiation signal on the page — consider pulling it up: 'Structure your content for the apps, sites, and AI systems your brand runs on.'

Copy

Hero H1 'Structure changes everything' — Abstract Brand Claim With No Product Category

Score

44

Severity

High

Finding

The homepage H1 is 'Structure changes everything.' This is a punchy, confident brand line — but it provides zero product category information. A developer or VP of Engineering who lands on hygraph.com without prior context cannot determine from the H1 alone whether this is a database product, a CMS, a design tool, or a content infrastructure platform. The sub-headline helps: 'Model and govern structured, relational content for the apps and sites that power brands, commerce, portals, and AI systems.' — but it requires reading 20 words before 'content' appears as a category signal. Competitors position more explicitly in their H1s: Contentful's 'The Content Platform'; Sanity's 'The Composable Content Cloud'; Storyblok's 'The Headless CMS for Content-Driven Experiences'. Hygraph's H1 is the most abstract of the category.

Recommendation

Either: (a) add a category micro-label above the H1 — 'Headless CMS for Enterprise Teams' in small caps before 'Structure changes everything' — so the category is anchored before the brand line lands; or (b) restructure the H1 to do both jobs: 'The headless CMS where structure changes everything.' This approach preserves the brand idea while front-loading the category. Option (a) is preferable because it keeps the H1's rhythm intact while adding the visitor-orienting context. The sub-headline's mention of 'AI systems' is currently the strongest differentiation signal on the page — consider pulling it up: 'Structure your content for the apps, sites, and AI systems your brand runs on.'

Copy

Hero H1 'Structure changes everything' — Abstract Brand Claim With No Product Category

Score

44

Severity

High

Finding

The homepage H1 is 'Structure changes everything.' This is a punchy, confident brand line — but it provides zero product category information. A developer or VP of Engineering who lands on hygraph.com without prior context cannot determine from the H1 alone whether this is a database product, a CMS, a design tool, or a content infrastructure platform. The sub-headline helps: 'Model and govern structured, relational content for the apps and sites that power brands, commerce, portals, and AI systems.' — but it requires reading 20 words before 'content' appears as a category signal. Competitors position more explicitly in their H1s: Contentful's 'The Content Platform'; Sanity's 'The Composable Content Cloud'; Storyblok's 'The Headless CMS for Content-Driven Experiences'. Hygraph's H1 is the most abstract of the category.

Recommendation

Either: (a) add a category micro-label above the H1 — 'Headless CMS for Enterprise Teams' in small caps before 'Structure changes everything' — so the category is anchored before the brand line lands; or (b) restructure the H1 to do both jobs: 'The headless CMS where structure changes everything.' This approach preserves the brand idea while front-loading the category. Option (a) is preferable because it keeps the H1's rhythm intact while adding the visitor-orienting context. The sub-headline's mention of 'AI systems' is currently the strongest differentiation signal on the page — consider pulling it up: 'Structure your content for the apps, sites, and AI systems your brand runs on.'

Brand

G2 Summer 2025 — '#2 Headless CMS' — Not on Homepage

Score

43

Severity

Medium

Finding

Sub-page content (from the Directus comparison blog) references that Hygraph is 'ranked 2nd out of 102 Headless CMSs in G2 Summer 2025.' A G2 category ranking of #2 out of 102 products is a strong, specific, third-party validation that directly addresses the primary evaluation question every prospective customer asks: 'Is this product well-regarded?'. Yet the homepage does not display the G2 badge, the ranking, or any G2-sourced proof point. The homepage testimonials section shows three quotes from Vision Healthcare, Dr. Oetker, and Lindex Group — strong names — but no analyst or review platform badges. For a developer-facing product evaluated on platforms like G2 and Capterra, a top-3 ranking is a credibility signal that belongs in the hero trust strip.

Recommendation

Add the G2 Summer 2025 badge to the homepage hero sub-section or trust strip: '#2 Headless CMS — G2 Summer 2025 (out of 102 products)'. If the G2 Fall or Winter 2025 badges are available, use the most recent. The G2 ranking is particularly credible to the developer and technical buyer audience that Hygraph targets — they use G2 more than analyst reports. Pair it with the ISO 27001 and SOC 2 certifications in a compact trust bar: '#2 on G2 · ISO 27001 · SOC 2 Type 2 · GDPR'. This bar answers the three evaluation questions (quality ranking, security, compliance) in a single scannable line.

Brand

G2 Summer 2025 — '#2 Headless CMS' — Not on Homepage

Score

43

Severity

Medium

Finding

Sub-page content (from the Directus comparison blog) references that Hygraph is 'ranked 2nd out of 102 Headless CMSs in G2 Summer 2025.' A G2 category ranking of #2 out of 102 products is a strong, specific, third-party validation that directly addresses the primary evaluation question every prospective customer asks: 'Is this product well-regarded?'. Yet the homepage does not display the G2 badge, the ranking, or any G2-sourced proof point. The homepage testimonials section shows three quotes from Vision Healthcare, Dr. Oetker, and Lindex Group — strong names — but no analyst or review platform badges. For a developer-facing product evaluated on platforms like G2 and Capterra, a top-3 ranking is a credibility signal that belongs in the hero trust strip.

Recommendation

Add the G2 Summer 2025 badge to the homepage hero sub-section or trust strip: '#2 Headless CMS — G2 Summer 2025 (out of 102 products)'. If the G2 Fall or Winter 2025 badges are available, use the most recent. The G2 ranking is particularly credible to the developer and technical buyer audience that Hygraph targets — they use G2 more than analyst reports. Pair it with the ISO 27001 and SOC 2 certifications in a compact trust bar: '#2 on G2 · ISO 27001 · SOC 2 Type 2 · GDPR'. This bar answers the three evaluation questions (quality ranking, security, compliance) in a single scannable line.

Brand

G2 Summer 2025 — '#2 Headless CMS' — Not on Homepage

Score

43

Severity

Medium

Finding

Sub-page content (from the Directus comparison blog) references that Hygraph is 'ranked 2nd out of 102 Headless CMSs in G2 Summer 2025.' A G2 category ranking of #2 out of 102 products is a strong, specific, third-party validation that directly addresses the primary evaluation question every prospective customer asks: 'Is this product well-regarded?'. Yet the homepage does not display the G2 badge, the ranking, or any G2-sourced proof point. The homepage testimonials section shows three quotes from Vision Healthcare, Dr. Oetker, and Lindex Group — strong names — but no analyst or review platform badges. For a developer-facing product evaluated on platforms like G2 and Capterra, a top-3 ranking is a credibility signal that belongs in the hero trust strip.

Recommendation

Add the G2 Summer 2025 badge to the homepage hero sub-section or trust strip: '#2 Headless CMS — G2 Summer 2025 (out of 102 products)'. If the G2 Fall or Winter 2025 badges are available, use the most recent. The G2 ranking is particularly credible to the developer and technical buyer audience that Hygraph targets — they use G2 more than analyst reports. Pair it with the ISO 27001 and SOC 2 certifications in a compact trust bar: '#2 on G2 · ISO 27001 · SOC 2 Type 2 · GDPR'. This bar answers the three evaluation questions (quality ranking, security, compliance) in a single scannable line.

Copy

Testimonial Section Has Only Three Quotes — All from Developers, None From Content/Marketing Buyers

Score

48

Severity

Medium

Finding

The homepage testimonials section shows three attributed quotes: Luigi van der Pal (Senior Software Engineer, Vision Healthcare) — praises GraphQL-native approach; Maximilian Steudel (MarTech & Digital Engagement Lead, Dr. Oetker) — praises market launch speed; Patrik Thituson (Software Developer, Lindex Group) — praises removed blockers. Two of three quotes are from software engineers/developers. Hygraph explicitly positions for both developers AND content teams ('Hygraph for Content Teams' in the nav), with the FAQ noting 'marketers can independently create and manage diverse content types.' Yet the homepage testimonial section is developer-heavy — a content editor or marketing manager evaluating the platform sees developer satisfaction signals, not content workflow satisfaction signals.

Recommendation

Add at least one content editor or marketing persona testimonial to the homepage — the case study library likely contains editor-perspective quotes. The Dr. Oetker quote is borderline (a MarTech lead, not a developer) but uses technical language ('replicating environments'). A quote like Reprieve's finance director from iplicit's series — showing a non-technical user's experience — would diversify the signal. Ideal format for the Hygraph context: '[Quote from a content editor or content ops manager about publishing speed, editing workflow, or non-developer autonomy]' from a named company. The 'I was able to publish with minimal support from the technical team. What used to take forever now only takes about two weeks.' quote seen in the search snippet is exactly this type — surface it on the homepage if it's from a real, named customer.

Copy

Testimonial Section Has Only Three Quotes — All from Developers, None From Content/Marketing Buyers

Score

48

Severity

Medium

Finding

The homepage testimonials section shows three attributed quotes: Luigi van der Pal (Senior Software Engineer, Vision Healthcare) — praises GraphQL-native approach; Maximilian Steudel (MarTech & Digital Engagement Lead, Dr. Oetker) — praises market launch speed; Patrik Thituson (Software Developer, Lindex Group) — praises removed blockers. Two of three quotes are from software engineers/developers. Hygraph explicitly positions for both developers AND content teams ('Hygraph for Content Teams' in the nav), with the FAQ noting 'marketers can independently create and manage diverse content types.' Yet the homepage testimonial section is developer-heavy — a content editor or marketing manager evaluating the platform sees developer satisfaction signals, not content workflow satisfaction signals.

Recommendation

Add at least one content editor or marketing persona testimonial to the homepage — the case study library likely contains editor-perspective quotes. The Dr. Oetker quote is borderline (a MarTech lead, not a developer) but uses technical language ('replicating environments'). A quote like Reprieve's finance director from iplicit's series — showing a non-technical user's experience — would diversify the signal. Ideal format for the Hygraph context: '[Quote from a content editor or content ops manager about publishing speed, editing workflow, or non-developer autonomy]' from a named company. The 'I was able to publish with minimal support from the technical team. What used to take forever now only takes about two weeks.' quote seen in the search snippet is exactly this type — surface it on the homepage if it's from a real, named customer.

Copy

Testimonial Section Has Only Three Quotes — All from Developers, None From Content/Marketing Buyers

Score

48

Severity

Medium

Finding

The homepage testimonials section shows three attributed quotes: Luigi van der Pal (Senior Software Engineer, Vision Healthcare) — praises GraphQL-native approach; Maximilian Steudel (MarTech & Digital Engagement Lead, Dr. Oetker) — praises market launch speed; Patrik Thituson (Software Developer, Lindex Group) — praises removed blockers. Two of three quotes are from software engineers/developers. Hygraph explicitly positions for both developers AND content teams ('Hygraph for Content Teams' in the nav), with the FAQ noting 'marketers can independently create and manage diverse content types.' Yet the homepage testimonial section is developer-heavy — a content editor or marketing manager evaluating the platform sees developer satisfaction signals, not content workflow satisfaction signals.

Recommendation

Add at least one content editor or marketing persona testimonial to the homepage — the case study library likely contains editor-perspective quotes. The Dr. Oetker quote is borderline (a MarTech lead, not a developer) but uses technical language ('replicating environments'). A quote like Reprieve's finance director from iplicit's series — showing a non-technical user's experience — would diversify the signal. Ideal format for the Hygraph context: '[Quote from a content editor or content ops manager about publishing speed, editing workflow, or non-developer autonomy]' from a named company. The 'I was able to publish with minimal support from the technical team. What used to take forever now only takes about two weeks.' quote seen in the search snippet is exactly this type — surface it on the homepage if it's from a real, named customer.

Performance

Hero Image Loaded at 3840px Width — Next.js Image Optimisation Not Applied at Hero

Score

40

Severity

Medium

Finding

The homepage hero image is loaded via Next.js's `_next/image` optimisation pipeline: `https://hygraph.com/_next/image?url=...&w=3840&q=100`. The `w=3840` parameter requests a 3840-pixel-wide image at 100% quality. For a hero image on a standard 1440px desktop viewport, serving a 3840px image at q=100 means delivering approximately 4-6x more pixels than needed, at maximum quality. While Next.js's image component handles responsive sizing, the `q=100` parameter bypasses the default compression that would reduce file size significantly (Next.js default quality is 75). This pattern — w=3840, q=100 — is a common Hygraph customer-site misconfiguration, and it appearing on Hygraph's own homepage is particularly notable for a CMS that serves content assets via its own CDN.

Recommendation

Change the hero image Next.js parameters to a more appropriate quality and width: `w=1920&q=85` for desktop, with proper `sizes` attribute for responsive breakpoints. The Next.js Image component's `priority` attribute should be set on the hero image (it likely is, given LCP importance), but the quality reduction from 100 to 75-85 will dramatically reduce file size without visible quality degradation on screens below 2K. As the company behind a content platform with its own CDN (graphassets.com), Hygraph is in a position to model best practices for image optimisation — the hero image configuration is a visible signal of that care, or lack of it.

Performance

Hero Image Loaded at 3840px Width — Next.js Image Optimisation Not Applied at Hero

Score

40

Severity

Medium

Finding

The homepage hero image is loaded via Next.js's `_next/image` optimisation pipeline: `https://hygraph.com/_next/image?url=...&w=3840&q=100`. The `w=3840` parameter requests a 3840-pixel-wide image at 100% quality. For a hero image on a standard 1440px desktop viewport, serving a 3840px image at q=100 means delivering approximately 4-6x more pixels than needed, at maximum quality. While Next.js's image component handles responsive sizing, the `q=100` parameter bypasses the default compression that would reduce file size significantly (Next.js default quality is 75). This pattern — w=3840, q=100 — is a common Hygraph customer-site misconfiguration, and it appearing on Hygraph's own homepage is particularly notable for a CMS that serves content assets via its own CDN.

Recommendation

Change the hero image Next.js parameters to a more appropriate quality and width: `w=1920&q=85` for desktop, with proper `sizes` attribute for responsive breakpoints. The Next.js Image component's `priority` attribute should be set on the hero image (it likely is, given LCP importance), but the quality reduction from 100 to 75-85 will dramatically reduce file size without visible quality degradation on screens below 2K. As the company behind a content platform with its own CDN (graphassets.com), Hygraph is in a position to model best practices for image optimisation — the hero image configuration is a visible signal of that care, or lack of it.

Performance

Hero Image Loaded at 3840px Width — Next.js Image Optimisation Not Applied at Hero

Score

40

Severity

Medium

Finding

The homepage hero image is loaded via Next.js's `_next/image` optimisation pipeline: `https://hygraph.com/_next/image?url=...&w=3840&q=100`. The `w=3840` parameter requests a 3840-pixel-wide image at 100% quality. For a hero image on a standard 1440px desktop viewport, serving a 3840px image at q=100 means delivering approximately 4-6x more pixels than needed, at maximum quality. While Next.js's image component handles responsive sizing, the `q=100` parameter bypasses the default compression that would reduce file size significantly (Next.js default quality is 75). This pattern — w=3840, q=100 — is a common Hygraph customer-site misconfiguration, and it appearing on Hygraph's own homepage is particularly notable for a CMS that serves content assets via its own CDN.

Recommendation

Change the hero image Next.js parameters to a more appropriate quality and width: `w=1920&q=85` for desktop, with proper `sizes` attribute for responsive breakpoints. The Next.js Image component's `priority` attribute should be set on the hero image (it likely is, given LCP importance), but the quality reduction from 100 to 75-85 will dramatically reduce file size without visible quality degradation on screens below 2K. As the company behind a content platform with its own CDN (graphassets.com), Hygraph is in a position to model best practices for image optimisation — the hero image configuration is a visible signal of that care, or lack of it.

Navigation

Primary Nav Items (Product, Solutions, Resources, Developers, Partners) Have No Visible Labels in DOM

Score

50

Severity

Medium

Finding

The homepage navigation renders five primary menu items as non-linking text labels: 'Product', 'Solutions', 'Resources', 'Developers', 'Partners'. None of these appear as anchor tags in the fetched HTML — they function as dropdown triggers with no href. This means: (1) these nav items are not crawlable by search engines as individual pages; (2) there are no direct URLs for 'Product', 'Solutions', 'Resources', 'Developers' or 'Partners' overview pages that could accumulate link equity; (3) a visitor who wants to deep-link or share any of these nav sections has no URL to reference. Compare to Hygraph's own sub-pages — /product, /solutions, /for-developers, /for-marketing — which do have URLs but are not the nav items. Only 'Pricing' has a direct href in the primary nav.

Recommendation

Convert each primary nav item to a linked anchor tag pointing to a canonical overview page: Product → /product, Solutions → /use-cases, Resources → /resources, Developers → /for-developers, Partners → /partners. This gives each nav section a crawlable URL, enables link equity accumulation on important category pages, and allows users to share or bookmark specific sections. Hygraph's content-heavy sub-page architecture (dozens of comparison pages, use-case pages, framework pages) benefits enormously from having well-linked category hub pages. The current non-linking nav labels are a common Next.js dropdown pattern that inadvertently sacrifices SEO hierarchy.

Navigation

Primary Nav Items (Product, Solutions, Resources, Developers, Partners) Have No Visible Labels in DOM

Score

50

Severity

Medium

Finding

The homepage navigation renders five primary menu items as non-linking text labels: 'Product', 'Solutions', 'Resources', 'Developers', 'Partners'. None of these appear as anchor tags in the fetched HTML — they function as dropdown triggers with no href. This means: (1) these nav items are not crawlable by search engines as individual pages; (2) there are no direct URLs for 'Product', 'Solutions', 'Resources', 'Developers' or 'Partners' overview pages that could accumulate link equity; (3) a visitor who wants to deep-link or share any of these nav sections has no URL to reference. Compare to Hygraph's own sub-pages — /product, /solutions, /for-developers, /for-marketing — which do have URLs but are not the nav items. Only 'Pricing' has a direct href in the primary nav.

Recommendation

Convert each primary nav item to a linked anchor tag pointing to a canonical overview page: Product → /product, Solutions → /use-cases, Resources → /resources, Developers → /for-developers, Partners → /partners. This gives each nav section a crawlable URL, enables link equity accumulation on important category pages, and allows users to share or bookmark specific sections. Hygraph's content-heavy sub-page architecture (dozens of comparison pages, use-case pages, framework pages) benefits enormously from having well-linked category hub pages. The current non-linking nav labels are a common Next.js dropdown pattern that inadvertently sacrifices SEO hierarchy.

Navigation

Primary Nav Items (Product, Solutions, Resources, Developers, Partners) Have No Visible Labels in DOM

Score

50

Severity

Medium

Finding

The homepage navigation renders five primary menu items as non-linking text labels: 'Product', 'Solutions', 'Resources', 'Developers', 'Partners'. None of these appear as anchor tags in the fetched HTML — they function as dropdown triggers with no href. This means: (1) these nav items are not crawlable by search engines as individual pages; (2) there are no direct URLs for 'Product', 'Solutions', 'Resources', 'Developers' or 'Partners' overview pages that could accumulate link equity; (3) a visitor who wants to deep-link or share any of these nav sections has no URL to reference. Compare to Hygraph's own sub-pages — /product, /solutions, /for-developers, /for-marketing — which do have URLs but are not the nav items. Only 'Pricing' has a direct href in the primary nav.

Recommendation

Convert each primary nav item to a linked anchor tag pointing to a canonical overview page: Product → /product, Solutions → /use-cases, Resources → /resources, Developers → /for-developers, Partners → /partners. This gives each nav section a crawlable URL, enables link equity accumulation on important category pages, and allows users to share or bookmark specific sections. Hygraph's content-heavy sub-page architecture (dozens of comparison pages, use-case pages, framework pages) benefits enormously from having well-linked category hub pages. The current non-linking nav labels are a common Next.js dropdown pattern that inadvertently sacrifices SEO hierarchy.

Copy

Hygraph AI / hygraph.ai — Parallel Product Presence Not Explained on Main Homepage

Score

46

Severity

Medium

Finding

The homepage FAQ block extensively references 'hygraph.ai' as a separate URL ('Source: hygraph.ai' appears 18+ times in the FAQ answers). The footer links to 'Talk to our AI agent' and 'AI and Automation' feature page. The banner at the top of the page promotes 'Visual editing now available! Introducing Click to Edit.' Yet there is no section on the main homepage explaining what the Hygraph AI / Agentic Content Platform is, how it relates to the main product, or how to access it. The FAQ describes an 'Agentic Content Platform' with Developer Copilot, Editor Copilot, Workflow Copilot, and Hygraph Anywhere — substantial new capabilities — but a homepage visitor who doesn't read the hidden FAQ block has no idea this AI layer exists. The visible homepage copy mentions 'AI systems' once in the sub-head and once in the feature list, but never names or links to the AI product.

Recommendation

Add a dedicated 'Hygraph AI' section to the homepage, between the enterprise complexity block and the testimonials: 'Introducing Hygraph AI — from content management to content automation.' Describe the three-layer value: Developer Copilot (schema design from natural language), Editor Copilot (AI-assisted content entry), Workflow Copilot (automated publishing). Link to hygraph.ai or /ai-and-automation for the full detail. The banner promoting 'Click to Edit' visual editing is good — the AI layer deserves equal or greater homepage prominence as the single most differentiated Hygraph capability in 2026. Competitors like Contentful and Sanity are also building AI features; Hygraph should lead with its AI story, not bury it in a hidden FAQ.

Copy

Hygraph AI / hygraph.ai — Parallel Product Presence Not Explained on Main Homepage

Score

46

Severity

Medium

Finding

The homepage FAQ block extensively references 'hygraph.ai' as a separate URL ('Source: hygraph.ai' appears 18+ times in the FAQ answers). The footer links to 'Talk to our AI agent' and 'AI and Automation' feature page. The banner at the top of the page promotes 'Visual editing now available! Introducing Click to Edit.' Yet there is no section on the main homepage explaining what the Hygraph AI / Agentic Content Platform is, how it relates to the main product, or how to access it. The FAQ describes an 'Agentic Content Platform' with Developer Copilot, Editor Copilot, Workflow Copilot, and Hygraph Anywhere — substantial new capabilities — but a homepage visitor who doesn't read the hidden FAQ block has no idea this AI layer exists. The visible homepage copy mentions 'AI systems' once in the sub-head and once in the feature list, but never names or links to the AI product.

Recommendation

Add a dedicated 'Hygraph AI' section to the homepage, between the enterprise complexity block and the testimonials: 'Introducing Hygraph AI — from content management to content automation.' Describe the three-layer value: Developer Copilot (schema design from natural language), Editor Copilot (AI-assisted content entry), Workflow Copilot (automated publishing). Link to hygraph.ai or /ai-and-automation for the full detail. The banner promoting 'Click to Edit' visual editing is good — the AI layer deserves equal or greater homepage prominence as the single most differentiated Hygraph capability in 2026. Competitors like Contentful and Sanity are also building AI features; Hygraph should lead with its AI story, not bury it in a hidden FAQ.

Copy

Hygraph AI / hygraph.ai — Parallel Product Presence Not Explained on Main Homepage

Score

46

Severity

Medium

Finding

The homepage FAQ block extensively references 'hygraph.ai' as a separate URL ('Source: hygraph.ai' appears 18+ times in the FAQ answers). The footer links to 'Talk to our AI agent' and 'AI and Automation' feature page. The banner at the top of the page promotes 'Visual editing now available! Introducing Click to Edit.' Yet there is no section on the main homepage explaining what the Hygraph AI / Agentic Content Platform is, how it relates to the main product, or how to access it. The FAQ describes an 'Agentic Content Platform' with Developer Copilot, Editor Copilot, Workflow Copilot, and Hygraph Anywhere — substantial new capabilities — but a homepage visitor who doesn't read the hidden FAQ block has no idea this AI layer exists. The visible homepage copy mentions 'AI systems' once in the sub-head and once in the feature list, but never names or links to the AI product.

Recommendation

Add a dedicated 'Hygraph AI' section to the homepage, between the enterprise complexity block and the testimonials: 'Introducing Hygraph AI — from content management to content automation.' Describe the three-layer value: Developer Copilot (schema design from natural language), Editor Copilot (AI-assisted content entry), Workflow Copilot (automated publishing). Link to hygraph.ai or /ai-and-automation for the full detail. The banner promoting 'Click to Edit' visual editing is good — the AI layer deserves equal or greater homepage prominence as the single most differentiated Hygraph capability in 2026. Competitors like Contentful and Sanity are also building AI features; Hygraph should lead with its AI story, not bury it in a hidden FAQ.

Social Proof

Customer Count ('30,000 teams') from Seed Round Press Release — Not on Homepage or Verified

Score

45

Severity

Low

Finding

The 2018-era seed round press release (repurposed as a blog post) states 'Hygraph is trusted by over 30,000 teams of all sizes.' This figure appears in the seed round announcement context — meaning it may reflect the early free tier user base rather than paid customers. The current homepage shows no customer count figure anywhere — not '30,000 teams', not 'X enterprise customers', not a DAU/MAU figure. The customer logo strip is strong (Samsung, LEGO, Paramount, TED, Bandai Namco, Discovery) but without a count, a developer evaluating Hygraph vs. Contentful (which claims 30%+ of Fortune 500 use Contentful) has no scale signal from the homepage. The FAQ notes '3X faster time-to-market and 15% improved engagement' as customer outcomes but without named attribution on the homepage.

Recommendation

If the '30,000 teams' figure is current and verified (including free tier), add it to the homepage hero trust strip: 'Trusted by 30,000+ teams — from startups to Samsung.' If the figure is outdated or applies only to the free tier, calculate and publish a more specific enterprise customer count: 'X enterprise customers across 60+ industries.' The case studies page lists named enterprise customers across Samsung, Dr. Oetker, LEGO, Paramount, TED, Discovery — count these and surface the number on the homepage. Even 'Used by 200+ enterprise brands' is more persuasive than no count when competing against Contentful and Sanity for mid-market deals.

Social Proof

Customer Count ('30,000 teams') from Seed Round Press Release — Not on Homepage or Verified

Score

45

Severity

Low

Finding

The 2018-era seed round press release (repurposed as a blog post) states 'Hygraph is trusted by over 30,000 teams of all sizes.' This figure appears in the seed round announcement context — meaning it may reflect the early free tier user base rather than paid customers. The current homepage shows no customer count figure anywhere — not '30,000 teams', not 'X enterprise customers', not a DAU/MAU figure. The customer logo strip is strong (Samsung, LEGO, Paramount, TED, Bandai Namco, Discovery) but without a count, a developer evaluating Hygraph vs. Contentful (which claims 30%+ of Fortune 500 use Contentful) has no scale signal from the homepage. The FAQ notes '3X faster time-to-market and 15% improved engagement' as customer outcomes but without named attribution on the homepage.

Recommendation

If the '30,000 teams' figure is current and verified (including free tier), add it to the homepage hero trust strip: 'Trusted by 30,000+ teams — from startups to Samsung.' If the figure is outdated or applies only to the free tier, calculate and publish a more specific enterprise customer count: 'X enterprise customers across 60+ industries.' The case studies page lists named enterprise customers across Samsung, Dr. Oetker, LEGO, Paramount, TED, Discovery — count these and surface the number on the homepage. Even 'Used by 200+ enterprise brands' is more persuasive than no count when competing against Contentful and Sanity for mid-market deals.

Social Proof

Customer Count ('30,000 teams') from Seed Round Press Release — Not on Homepage or Verified

Score

45

Severity

Low

Finding

The 2018-era seed round press release (repurposed as a blog post) states 'Hygraph is trusted by over 30,000 teams of all sizes.' This figure appears in the seed round announcement context — meaning it may reflect the early free tier user base rather than paid customers. The current homepage shows no customer count figure anywhere — not '30,000 teams', not 'X enterprise customers', not a DAU/MAU figure. The customer logo strip is strong (Samsung, LEGO, Paramount, TED, Bandai Namco, Discovery) but without a count, a developer evaluating Hygraph vs. Contentful (which claims 30%+ of Fortune 500 use Contentful) has no scale signal from the homepage. The FAQ notes '3X faster time-to-market and 15% improved engagement' as customer outcomes but without named attribution on the homepage.

Recommendation

If the '30,000 teams' figure is current and verified (including free tier), add it to the homepage hero trust strip: 'Trusted by 30,000+ teams — from startups to Samsung.' If the figure is outdated or applies only to the free tier, calculate and publish a more specific enterprise customer count: 'X enterprise customers across 60+ industries.' The case studies page lists named enterprise customers across Samsung, Dr. Oetker, LEGO, Paramount, TED, Discovery — count these and surface the number on the homepage. Even 'Used by 200+ enterprise brands' is more persuasive than no count when competing against Contentful and Sanity for mid-market deals.

Copy

Section Heading 'Are you ready for the AI era?' — Closing CTA Is Weaker Than the Hero

Score

52

Severity

Low

Finding

The page closes with a CTA section headed: 'Are you ready for the AI era? Start the conversation about your content architecture.' with 'Contact Sales' and 'Get Started for Free' buttons. The 'Are you ready for the AI era?' heading is a rhetorical question that a developer visiting a technical product page will find slightly marketing-register-heavy. More critically, the closing CTA repeats the exact same two buttons as the hero — Contact Sales and Get Started for Free — with no additional value proposition, no urgency, and no social proof specific to the AI era claim. A visitor who scrolled to the bottom without converting hasn't been given a new reason to act.

Recommendation

Replace the generic closing CTA with one that provides a new incentive or urgency to act: 'Join Samsung, LEGO, and Dr. Oetker — model your content architecture for the AI era. Start free or talk to our team.' This version: names marquee customers (new information vs. the hero logo strip), connects the AI era framing to a concrete action, and offers the same dual CTA paths. Alternatively, use the closing section to surface the free tier or a specific offer: 'Start free — no credit card required. Upgrade when you need enterprise features.' This directly addresses the last-mile hesitation of a developer who is interested but hasn't committed.

Copy

Section Heading 'Are you ready for the AI era?' — Closing CTA Is Weaker Than the Hero

Score

52

Severity

Low

Finding

The page closes with a CTA section headed: 'Are you ready for the AI era? Start the conversation about your content architecture.' with 'Contact Sales' and 'Get Started for Free' buttons. The 'Are you ready for the AI era?' heading is a rhetorical question that a developer visiting a technical product page will find slightly marketing-register-heavy. More critically, the closing CTA repeats the exact same two buttons as the hero — Contact Sales and Get Started for Free — with no additional value proposition, no urgency, and no social proof specific to the AI era claim. A visitor who scrolled to the bottom without converting hasn't been given a new reason to act.

Recommendation

Replace the generic closing CTA with one that provides a new incentive or urgency to act: 'Join Samsung, LEGO, and Dr. Oetker — model your content architecture for the AI era. Start free or talk to our team.' This version: names marquee customers (new information vs. the hero logo strip), connects the AI era framing to a concrete action, and offers the same dual CTA paths. Alternatively, use the closing section to surface the free tier or a specific offer: 'Start free — no credit card required. Upgrade when you need enterprise features.' This directly addresses the last-mile hesitation of a developer who is interested but hasn't committed.

Copy

Section Heading 'Are you ready for the AI era?' — Closing CTA Is Weaker Than the Hero

Score

52

Severity

Low

Finding

The page closes with a CTA section headed: 'Are you ready for the AI era? Start the conversation about your content architecture.' with 'Contact Sales' and 'Get Started for Free' buttons. The 'Are you ready for the AI era?' heading is a rhetorical question that a developer visiting a technical product page will find slightly marketing-register-heavy. More critically, the closing CTA repeats the exact same two buttons as the hero — Contact Sales and Get Started for Free — with no additional value proposition, no urgency, and no social proof specific to the AI era claim. A visitor who scrolled to the bottom without converting hasn't been given a new reason to act.

Recommendation

Replace the generic closing CTA with one that provides a new incentive or urgency to act: 'Join Samsung, LEGO, and Dr. Oetker — model your content architecture for the AI era. Start free or talk to our team.' This version: names marquee customers (new information vs. the hero logo strip), connects the AI era framing to a concrete action, and offers the same dual CTA paths. Alternatively, use the closing section to surface the free tier or a specific offer: 'Start free — no credit card required. Upgrade when you need enterprise features.' This directly addresses the last-mile hesitation of a developer who is interested but hasn't committed.

SEO

Series B (March 2023) — No Homepage Visibility or Press Section

Score

55

Severity

Low

Finding

Hygraph raised a Series B in March 2023 (amount undisclosed, investors including Paua Ventures, Peak, and OpenOcean — total disclosed funding $43.7M). The homepage has no mention of funding, investors, or financial backing. For enterprise buyers evaluating long-term vendor stability, knowing that a headless CMS is Series B-backed with $43M raised is a vendor risk signal. The 'About Hygraph' footer link presumably covers this, but the homepage itself gives no financial stability signal. Competitors in the enterprise segment (Contentful — $300M+ raised; Sanity — $9.5M seed pre-2025, then $87M Series B April 2025) are more visibly funded. Sanity's April 2025 Series B would be actively discussed in competitive evaluations, and Hygraph's homepage currently has no counter-narrative.

Recommendation

Add a minimal investor/funding reference to the About section or footer: 'Series B-backed · Investors include Paua Ventures, Peak Capital, and OpenOcean.' For enterprise procurement, this signals vendor maturity and financial backing. Consider adding a Trust section to the homepage or footer that consolidates: funding tier, ISO/SOC certifications, GDPR status, and enterprise SLA availability. This is increasingly standard for enterprise CMS products and addresses the 'will this company be around in 3 years?' question that every enterprise buyer's legal/procurement team raises. The funding should have been prominently featured after the March 2023 announcement; if it was, ensure it hasn't been removed in subsequent site redesigns.

SEO

Series B (March 2023) — No Homepage Visibility or Press Section

Score

55

Severity

Low

Finding

Hygraph raised a Series B in March 2023 (amount undisclosed, investors including Paua Ventures, Peak, and OpenOcean — total disclosed funding $43.7M). The homepage has no mention of funding, investors, or financial backing. For enterprise buyers evaluating long-term vendor stability, knowing that a headless CMS is Series B-backed with $43M raised is a vendor risk signal. The 'About Hygraph' footer link presumably covers this, but the homepage itself gives no financial stability signal. Competitors in the enterprise segment (Contentful — $300M+ raised; Sanity — $9.5M seed pre-2025, then $87M Series B April 2025) are more visibly funded. Sanity's April 2025 Series B would be actively discussed in competitive evaluations, and Hygraph's homepage currently has no counter-narrative.

Recommendation

Add a minimal investor/funding reference to the About section or footer: 'Series B-backed · Investors include Paua Ventures, Peak Capital, and OpenOcean.' For enterprise procurement, this signals vendor maturity and financial backing. Consider adding a Trust section to the homepage or footer that consolidates: funding tier, ISO/SOC certifications, GDPR status, and enterprise SLA availability. This is increasingly standard for enterprise CMS products and addresses the 'will this company be around in 3 years?' question that every enterprise buyer's legal/procurement team raises. The funding should have been prominently featured after the March 2023 announcement; if it was, ensure it hasn't been removed in subsequent site redesigns.

SEO

Series B (March 2023) — No Homepage Visibility or Press Section

Score

55

Severity

Low

Finding

Hygraph raised a Series B in March 2023 (amount undisclosed, investors including Paua Ventures, Peak, and OpenOcean — total disclosed funding $43.7M). The homepage has no mention of funding, investors, or financial backing. For enterprise buyers evaluating long-term vendor stability, knowing that a headless CMS is Series B-backed with $43M raised is a vendor risk signal. The 'About Hygraph' footer link presumably covers this, but the homepage itself gives no financial stability signal. Competitors in the enterprise segment (Contentful — $300M+ raised; Sanity — $9.5M seed pre-2025, then $87M Series B April 2025) are more visibly funded. Sanity's April 2025 Series B would be actively discussed in competitive evaluations, and Hygraph's homepage currently has no counter-narrative.

Recommendation

Add a minimal investor/funding reference to the About section or footer: 'Series B-backed · Investors include Paua Ventures, Peak Capital, and OpenOcean.' For enterprise procurement, this signals vendor maturity and financial backing. Consider adding a Trust section to the homepage or footer that consolidates: funding tier, ISO/SOC certifications, GDPR status, and enterprise SLA availability. This is increasingly standard for enterprise CMS products and addresses the 'will this company be around in 3 years?' question that every enterprise buyer's legal/procurement team raises. The funding should have been prominently featured after the March 2023 announcement; if it was, ensure it hasn't been removed in subsequent site redesigns.