eucalyptus.health — AI Site Grade

Analysis

Eucalyptus has excellent AI-crawler access but zero structured AI onboarding — and the cold-knowledge gap reveals a regulatory blind spot the site itself never addresses

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, Applebot-Extended, anthropic-ai — receive a full 200 response with identical HTML to a browser visit. The homepage returns ~231KB of content to every bot tested. The sole exception is Bytespider (ByteDance), which gets a 403 from Cloudflare. The robots.txt is maximally permissive (User-agent: * Allow: /) with no AI-specific directives at all. No llms.txt exists (404). The site runs on Cloudflare (CDN/WAF) with Webflow as the CMS, served via AWS Lambda (x-lambda-id header). No JS-rendering risk: the homepage delivers 627 words of visible text on a plain GET.

Cold-Knowledge Gap

The LLM knows Eucalyptus as an Australian digital health company operating Pilot, Kin, Juniper, and Software clinics, with ~$60M Series C funding from BOND and backing from Blackbird/AirTree. It also recalls regulatory scrutiny over weight-loss drug advertising (Ozempic) in 2023. The site itself never mentions this regulatory episode anywhere — not on the FAQ, not on the patient-safety page, not in any blog post. The site presents a polished narrative of clinical governance, peer-reviewed research, and patient safety accreditations (ACHS EQuIP6, ISO-27001, DTAC, NICE endorsement), but the cold-knowledge model has already surfaced a reputational vulnerability that the site's own content strategy ignores.

Schema Posture

The homepage carries a single MedicalOrganization schema with name: "Eucalyptus", alternateName: "Euc", and links to Instagram and LinkedIn. That is the only schema on the entire homepage. The FAQ page has zero schema — no FAQPage markup despite containing a structured FAQ with 15+ questions and answers. Blog posts use Article schema with datePublished and dateModified. The mission, patient-safety, research, and clinical-indicators pages all have no schema at all. A FAQPage schema on /faq and MedicalWebPage or HealthTopic schema on condition-specific pages would dramatically improve how AI engines interpret the site's content.

External Signals

The site references five digital clinics (Pilot, Kin, Juniper, Software, Compound) that operate on separate domains (pilot.com.au, kinfertility.com.au, myjuniper.com, skin.software, compound.co). These sub-brands carry the actual patient-facing content and transactional flows, meaning AI crawlers hitting eucalyptus.health see a corporate parent page, not the clinical depth. The research page lists 25+ peer-reviewed publications (2024-2026) on real-world weight-loss outcomes, prescribing error rates, and patient satisfaction — a strong evidence signal that is not surfaced in any structured schema. The blog is active and substantive, covering clinical governance, patient advocacy campaigns (#WeNeedMoreLeave, BFF Movement), and global expansion into the UK, Germany, Japan, and Canada.

Findings

1. No llms.txt file for AI onboarding Medium

   The site returns a 404 for llms.txt, missing an opportunity to guide AI crawlers to key pages and context.

   What to change: Create an llms.txt file listing core pages (FAQ, research, clinical governance) and a brief site summary.

2. FAQ page lacks FAQPage schema High

   The /faq page contains 15+ questions and answers but has no FAQPage structured data, reducing AI understanding and eligibility for rich results.

   What to change: Add FAQPage schema with Question/Answer markup to the FAQ page.

3. Key content pages have no structured data Medium

   The mission, patient-safety, research, and clinical-indicators pages lack any schema markup, limiting AI interpretation of their content.

   What to change: Add MedicalWebPage, HealthTopic, or WebPage schema to these pages as appropriate.

4. Site omits known regulatory scrutiny over weight-loss advertising Medium

   LLMs recall a 2023 regulatory episode involving weight-loss drug advertising (Ozempic), but the site's FAQ, patient-safety page, and blog posts never address it, creating a gap between public knowledge and site narrative.

   What to change: Add a transparent section or blog post addressing regulatory compliance and advertising standards.

5. Bytespider (ByteDance) blocked by Cloudflare Low

   Bytespider receives a 403 error, preventing ByteDance's AI crawler from accessing the site.

   What to change: Allow Bytespider access if coverage on ByteDance platforms is desired.

6. Patient-facing clinics on separate domains dilute AI visibility Medium

   The five digital clinics (Pilot, Kin, Juniper, Software, Compound) operate on separate domains, so AI crawlers on eucalyptus.health see only corporate content, not clinical depth.

   What to change: Consider cross-linking or using schema to associate sub-brands with the parent site.

7. No HealthTopic or MedicalCondition schema on condition pages Medium

   The site does not use HealthTopic or MedicalCondition schema on pages discussing health conditions, missing opportunities for AI to understand clinical context.

   What to change: Add HealthTopic or MedicalCondition schema to relevant pages.

8. Research publications not surfaced via schema Low

   The research page lists 25+ peer-reviewed publications but uses no schema (e.g., ScholarlyArticle) to make them machine-readable.

   What to change: Add ScholarlyArticle schema to each publication entry.

What's working

• All major AI crawlers receive full access — GPTBot, ClaudeBot, PerplexityBot, and others get a 200 response with full HTML content, ensuring AI visibility.
• Robots.txt allows all crawlers without restrictions — The robots.txt is maximally permissive (Allow: /) with no AI-specific blocks, ensuring broad access.
• Homepage content is fully server-rendered — The homepage delivers 627 words of visible text on a plain GET, with no JavaScript dependency for content.
• Active blog with substantive clinical governance content — The blog covers clinical governance, patient safety, and research, providing rich content for AI indexing.
• Research page lists 25+ peer-reviewed publications — The research page aggregates real-world evidence, a strong signal for AI credibility.
• Homepage has MedicalOrganization schema — The homepage includes MedicalOrganization schema with name and alternateName, aiding entity recognition.
• Blog posts use Article schema with dates — Blog posts include Article schema with datePublished and dateModified, improving AI understanding of timeliness.
• Sitemap contains 80 URLs for comprehensive indexing — The sitemap lists 80 URLs, helping crawlers discover all pages.