Localisation report
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
PoorSignificant localisation gaps are affecting the experience.
Sampled 15 pages across technical, linguistic, contextual, and visual localisation credits. How we score localisation audits
Rank #22 of 24 public audits
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.
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.
No localized terminology set is present
The evidence contains no locale pages, so consistency of translated terminology across locales cannot be verified.
Found here
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.
3 passed · 13 to fix · 19 not applicable
Locale detection
Fail40technicalPages should declare a correct html lang that matches the URL and content locale.
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
Fail72technicalLocalized pages should use a consistent URL structure and resolve successfully.
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
Fail52technicalJSON-LD inLanguage should match the page locale when structured data is present.
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
Fail55linguisticImportant concepts should not be translated differently across pages.
No localized terminology set is present
The evidence contains no locale pages, so consistency of translated terminology across locales cannot be verified.
Found here
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
Fail50linguisticTarget copy should preserve the source meaning, numbers, and product actions.
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
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.
Fluency
Fail88linguisticCopy should sound natural, without grammar issues or machine-translation artifacts.
Brand voice
Fail86linguisticLocalized copy should preserve the intended tone of the source.
Grammar and style
Fail84linguisticLocale-specific capitalization, punctuation, formality, and agreement should be correct.
Localized images and assets
Fail88visualLanguage-specific images and alt text should match the page locale.
Visual hierarchy
Fail55visualLocalization should not make headings or CTAs lose scanability.
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.
Text overflow
Fail78visualText should not clip, truncate unexpectedly, or overflow buttons and navigation.
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
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
Fail80visualLocalized pages should not overlap, break grids, or overflow modals.
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
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
Fail78visualLocalized layouts should hold up across mobile, tablet, and desktop widths.
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
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.
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.
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 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.
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.
No localized terminology set is present
The evidence contains no locale pages, so consistency of translated terminology across locales cannot be verified.
Found here
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.
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
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.
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
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 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
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 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
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.
Optional. Enter your work email and we will send a concise summary of this public report.
Critical gaps showed up. Create a workspace to run a deeper registered audit, or book a review with our team.
