Localisation report

Eucalyptus

Digital healthcare

eucalyptus.health

Product: Eucalyptus is a global telehealth provider operating digital healthcare clinics. Its clinics connect patients with certified practitioners, treatments, and ongoing care, with a focus on preventative and chronic healthcare.

Brand voice: Patient-first, trustworthy, accessible, care-focused

Localisation score

41/100

Poor

Significant localisation gaps are affecting the experience.

This score uses an earlier scoring method. Run the audit again to compare it with current reports.

73Technical Audit
77Linguistic Audit
N/AContextual Audit
76Visual Audit

Audited: Aug 25, 2026Scope: Public smart sample · technical, linguistic, contextual, and visual creditsConfidence: Indicative health check from sampled pages — not a full site crawl.

Sampled 15 pages across technical, linguistic, contextual, and visual localisation credits. How we score localisation audits

How you compare

Rank #22 of 22 public audits

Public average: 71/100

See the full leaderboard

Fix first

1
high
Missing language declaration
15 sampled pages do not set html lang, so browsers and assistive tech cannot identify the locale.
See details
2
medium
Only one locale signal detected
The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).
See details
3
medium
No localized terminology set is present
The evidence contains no locale pages, so consistency of translated terminology across locales cannot be verified.
See details

Audit criteria

3 passed · 7 to watch · 6 to fix · 19 not applicable

Needs attention (6)

Locale detection
Fail40technicalWeight 3
Pages should declare a correct html lang that matches the URL and content locale.
- hightechnical · 95% confidence
  Missing language declaration
  15 sampled pages do not set html lang, so browsers and assistive tech cannot identify the locale.
  Found here
  Document head · <html lang>
  https://www.eucalyptus.health/
  What we saw
  html lang is missing on 15 pages, e.g. https://www.eucalyptus.health/, https://www.eucalyptus.health/?41ebd6b8_page=1, https://www.eucalyptus.health/?41ebd6b8_page=2
  How to fix it
  Set html lang to a BCP 47 language tag for each page locale, such as en, fr-FR, or es-419.
Locale routing
Fail72technicalWeight 3
Localized pages should use a consistent URL structure and resolve successfully.
- mediumtechnical · 90% confidence
  Only one locale signal detected
  The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).
  Found here
  Sampled pages · document
  https://www.eucalyptus.health/
  What we saw
  Detected locale signals: none
  How to fix it
  Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.
Structured data
Fail52technicalWeight 1
JSON-LD inLanguage should match the page locale when structured data is present.
- lowtechnical · 95% confidence
  Structured data omits inLanguage
  JSON-LD is present but does not declare inLanguage on sampled pages.
  Found here
  JSON-LD · <script type="application/ld+json">
  https://www.eucalyptus.health/
  What we saw
  MedicalOrganization is present but inLanguage is missing
  How to fix it
  Set JSON-LD inLanguage to match each page locale.
Terminology consistency
Fail55linguisticWeight 2
Important concepts should not be translated differently across pages.
- mediumlinguistic · 85% confidence
  No localized terminology set is present
  The evidence contains no locale pages, so consistency of translated terminology across locales cannot be verified.
  Found here
  https://www.eucalyptus.health/
  What we saw
  "locales":[]
  How to fix it
  Provide the localized page set and compare recurring concepts such as “Mission,” “Patient Safety,” and “Open Roles” across every locale.
Translation accuracy
Fail50linguisticWeight 3
Target copy should preserve the source meaning, numbers, and product actions.
- mediumlinguistic · 88% confidence
  Source-to-target accuracy cannot be assessed
  Only English copy is provided and no translated target pages or source/target pairs are available for comparison.
  Found here
  https://www.eucalyptus.health/
  What we saw
  "locales":[]; "title":"Eucalyptus | Digital Healthcare That Puts Patients First"
  How to fix it
  Supply the localized versions and compare headings, body copy, calls to action, and any numeric content against the source.
Visual hierarchy
Fail55visualWeight 1
Localization should not make headings or CTAs lose scanability.
- lowvisual · 80% confidence
  Heading is excessively long
  A localized heading may crowd the visual hierarchy. Affects 22 sampled pages.
  Found here
  Page body · heading
  https://www.eucalyptus.health/
  What we saw
  As a global telehealth provider, we're building a safe, effective and accessible future for medicine. Seen on 6 pages, e.g. https://www.eucalyptus.health/, https://www.eucalyptus.health/?41ebd6b8_page=1, https://www.eucalyptus.health/?41ebd6b8_page=2
  How to fix it
  Shorten the heading so it does not crowd the visual hierarchy.

Worth a look (7)

Fluency
Watch88linguisticWeight 2
Copy should sound natural, without grammar issues or machine-translation artifacts.
Brand voice
Watch86linguisticWeight 1
Localized copy should preserve the intended tone of the source.
Grammar and style
Watch84linguisticWeight 2
Locale-specific capitalization, punctuation, formality, and agreement should be correct.
Localized images and assets
Watch88visualWeight 1
Language-specific images and alt text should match the page locale.
Text overflow
Watch78visualWeight 3
Measured in the rendered page: localized buttons, links, labels, and headings should not clip their text more than the source page does.
- infovisual · 45% confidence
  Overflow cannot be confirmed from text-only evidence
  The extracted page text does not include visual bounds or screenshots, so clipping and overflow cannot be directly verified.
  Found here
  https://www.eucalyptus.health/
  What we saw
  The evidence provides page text and headings but no screenshots or layout measurements.
  How to fix it
  Check navigation, headings, buttons, and long localized strings at the supported viewport widths for clipping or unwanted truncation.
Layout breakage
Watch80visualWeight 3
Measured at desktop width: localized pages should not push content past the viewport when the source page does not.
- infovisual · 42% confidence
  Layout integrity cannot be confirmed
  The evidence contains no visual screenshots or computed layout data, so overlap, grid breakage, and modal overflow cannot be assessed directly.
  Found here
  https://www.eucalyptus.health/
  What we saw
  The supplied page records include status, headings, buttons, and text, but no visual layout evidence.
  How to fix it
  Run visual checks for overlapping elements, broken grids, and overflowing dialogs on each localized page.
Responsive localisation
Watch78visualWeight 2
Measured at mobile width: localized pages should not scroll sideways or clip labels when the source page does not.
- infovisual · 40% confidence
  Responsive behavior is unverified
  No viewport-specific screenshots or measurements are provided, and no localized pages are listed, so responsive localization cannot be confirmed.
  Found here
  https://www.eucalyptus.health/
  What we saw
  "locales":[]; the page evidence contains no viewport or responsive-layout data.
  How to fix it
  Test every locale at mobile, tablet, and desktop widths, including navigation, headings, cards, and calls to action.

Passed audits (3)

Not applicable (19)

Detected locales

We did not find any language versions on the sampled pages.

Pages sampled

Next step

Critical gaps showed up. Claim this domain to track fixes in a workspace, or book a review with our team.

Book an audit review

Send this to your team

We'll email a short summary — score, top fixes, and a link back to this report — so it's easy to forward.