Localisation report
Heidi
Healthcare AIheidihealth.com
Product: Heidi provides AI tools for clinicians across the care journey, including clinical documentation, dictation, medical evidence lookup, care gap outreach, and patient communications. Its tools aim to reduce administrative work and save clinicians time.
Brand voice: Practical, supportive, clinically focused
Localisation score
78/100
GoodThe website is generally well localised, with some issues to improve.
- 82Technical Audit
- 74Linguistic Audit
- 88Contextual Audit
- 67Visual Audit
Sampled 15 pages across technical, linguistic, contextual, and visual localisation credits. How we score localisation audits
How you compare
Rank #7 of 23 public audits
Fix first
- 1high
Untranslated call to action
A fr-ca page still uses source-language CTA copy. Affects 3 sampled pages.
See details - 2medium
Sitemap omits some published locales
Locale-prefixed pages for fr, de do not appear in sampled sitemap URLs.
See details - 3medium
Localized text is much longer than the source
A fr string is 171% the length of the source, which often causes overflow. Affects 13 sampled pages.
See details
Audit criteria
5 passed · 14 to watch · 8 to fix · 8 not applicable
Needs attention (8)
Language switcher
Fail74technicalVisitors should move between locales without losing the current page.
- mediumtechnical · 62% confidence
Current-page preservation is not demonstrated
The evidence shows locale coverage and several homepage URLs, but does not explicitly verify switching between locales while retaining a non-homepage path.
Found here
Header · <nav>
https://www.heidihealth.com/What we saw
"locales":["de-be","de-ch","de-de",...,"ja-jp"] and homepage examples such as "https://www.heidihealth.com/", "https://www.heidihealth.com/en-us", and "https://www.heidihealth.com/en-gb"
How to fix it
Test the language switcher from representative inner pages and confirm that each locale preserves the equivalent path.
Structured data
Fail0technicalJSON-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.heidihealth.com/What we saw
Organization is present but inLanguage is missing
How to fix it
Set JSON-LD inLanguage to match each page locale.
Translation completeness
Fail34linguisticLocalized pages should not leave source-language copy in place, except brand names and URLs.
- highlinguistic · 92% confidence
Untranslated call to action
A fr-ca page still uses source-language CTA copy. Affects 3 sampled pages.
Found here
Link · <a>
https://www.heidihealth.com/fr-caWhat we saw
Primary CTA: "Skip to main content" Seen on 3 pages, e.g. https://www.heidihealth.com/fr-ca, https://www.heidihealth.com/de-de, https://www.heidihealth.com/fr-fr
How to fix it
Translate leftover source-language CTAs to match the surrounding locale copy.
Translation accuracy
Fail72linguisticTarget copy should preserve the source meaning, numbers, and product actions.
Text expansion
Fail40visualLonger translations should not create obvious length pressure versus the source UI.
- mediumvisual · 88% confidence
Localized text is much longer than the source
A fr string is 171% the length of the source, which often causes overflow. Affects 13 sampled pages.
Found here
Heading · heading
https://www.heidihealth.com/fr-caWhat we saw
EN "Relief in every visit" → FR "Heidi — Your AI Care PartnerHeidi AI" (171%) Seen on 3 pages, e.g. https://www.heidihealth.com/fr-ca, https://www.heidihealth.com/fr-fr, https://www.heidihealth.com/de-de
How to fix it
Shorten the translation or give the control more room so the longer copy does not overflow.
Localized images and assets
Fail74visualLanguage-specific images and alt text should match the page locale.
Visual hierarchy
Fail58visualLocalization should not make headings or CTAs lose scanability.
- lowvisual · 80% confidence
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 4 sampled pages.
Found here
Page body · heading
https://www.heidihealth.com/de-deWhat we saw
„Seit ich Heidi benutze, kann ich mich dem Patienten besser zuwenden. Ich muss nicht mehr sofort alles stichpunktartig mitschreiben.” Seen on 2 pages, e.g. https://www.heidihealth.com/de-de, https://www.heidihealth.com/fr-fr
How to fix it
Shorten the heading so it does not crowd the visual hierarchy.
Component consistency
Fail70visualRepeated components should stay visually consistent across locales.
- lowvisual · 95% confidence
Repeated components differ across locales
Button counts differ between the source locale and fr.
Found here
Page body · <button>
https://www.heidihealth.com/fr-caWhat we saw
Source locale has 13 buttons; fr has 8.
How to fix it
Keep the same repeated controls across locales, or drop unused ones on purpose.
Worth a look (14)
Sitemap
Watch76technicalLike Lighthouse: a valid XML sitemap must be discoverable, robots.txt should reference it with an absolute Sitemap: URL, and localized URLs should appear for published locales.
- mediumtechnical · 88% confidence
Sitemap omits some published locales
Locale-prefixed pages for fr, de do not appear in sampled sitemap URLs.
Found here
Sitemap · sitemap.xml
https://www.heidihealth.com/sitemap-index.xmlWhat we saw
Sitemap locales in sample: en; missing: fr, de
How to fix it
Include URLs for every published locale prefix in the sitemap.
Accessibility localisation
Watch84technicallang, aria-label, and alt text should match the page locale.
Terminology consistency
Watch80linguisticImportant concepts should not be translated differently across pages.
Fluency
Watch86linguisticCopy should sound natural, without grammar issues or machine-translation artifacts.
Brand voice
Watch84linguisticLocalized copy should preserve the intended tone of the source.
Grammar and style
Watch86linguisticLocale-specific capitalization, punctuation, formality, and agreement should be correct.
CTA intent
Watch89contextualLocalized calls to action should communicate the intended product action.
UI context
Watch88contextualTranslations should fit the UI component: button, nav, form, modal, or error.
Product context
Watch86contextualLanguage should match product concepts such as plans, settings, and workflows.
Contextual meaning
Watch87contextualStrings should be judged in surrounding page and component context, not in isolation.
Audience context
Watch89contextualLanguage should fit the intended audience, such as consumer, enterprise, or developer.
Text overflow
Watch76visualText should not clip, truncate unexpectedly, or overflow buttons and navigation.
Layout breakage
Watch76visualLocalized pages should not overlap, break grids, or overflow modals.
Responsive localisation
Watch76visualLocalized layouts should hold up across mobile, tablet, and desktop widths.
Passed audits (5)
Not applicable (8)
Detected locales
German (Belgium)
de-be · hreflang
Swiss High German
de-ch · hreflang
German (Germany)
de-de · hreflang
German (Luxembourg)
de-lu · hreflang
English (United Arab Emirates)
en-ae · hreflang
Australian English
en-au · hreflang
Canadian English
en-ca · hreflang
British English
en-gb · hreflang
English (Hong Kong SAR China)
en-hk · hreflang
English (Ireland)
en-ie · hreflang
English (Malaysia)
en-my · hreflang
English (New Zealand)
en-nz · hreflang
English (Saudi Arabia)
en-sa · hreflang
English (Singapore)
en-sg · hreflang
American English
en-us · hreflang
English (South Africa)
en-za · hreflang
Spanish (Argentina)
es-ar · hreflang
European Spanish
es-es · hreflang
Mexican Spanish
es-mx · hreflang
French (Belgium)
fr-be · hreflang
Canadian French
fr-ca · hreflang
Swiss French
fr-ch · hreflang
French (France)
fr-fr · hreflang
French (Luxembourg)
fr-lu · hreflang
Japanese (Japan)
ja-jp · hreflang
Pages sampled
Next step
Strong localisation signals. Claim this domain to keep locales healthy as you ship, or book a deeper 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.
