Localisation report

Heidi

Healthcare AI

heidihealth.com

Product: Heidi is an AI care partner for clinicians, supporting clinical documentation, note-taking, coding, evidence-based decisions, care gap outreach, and patient communications. It is designed to reduce administrative work across the care journey.

Brand voice: Reassuring, practical, clinician-focused

Localisation score

63/100

Needs improvement

Users may encounter noticeable localisation problems.

77Technical Audit
42Linguistic Audit
73Contextual Audit
61Visual Audit

Audited: 8/17/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 #16 of 22 public audits

Top 32% of audited domainsPublic average: 68/100

See the full leaderboard

Fix first

highlinguistic · 92% confidence
Untranslated call to action
A fr-ca page still uses source-language CTA copy. Affects 5 sampled pages.
Found here
Primary action · <button>
https://www.heidihealth.com/fr-ca
What we saw
Primary CTA: "Solutions" Seen on 5 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.
mediumtechnical · 88% confidence
Sitemap omits some published locales
Locale-prefixed pages for fr, de, es, it do not appear in sampled sitemap URLs.
Found here
Sitemap · sitemap.xml
https://www.heidihealth.com/sitemap-index.xml
What we saw
Sitemap locales in sample: en; missing: fr, de, es, it
How to fix it
Include URLs for every published locale prefix in the sitemap.
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 27 sampled pages.
Found here
Heading · heading
https://www.heidihealth.com/fr-ca
What we saw
EN "Relief in every visit" → FR "Heidi — Your AI Care PartnerHeidi AI" (171%) Seen on 5 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.

Audit criteria

5 passed · 22 to fix · 8 not applicable

Needs attention (22)

Language switcher
Fail55technical
Visitors should move between locales without losing the current page.
- mediumtechnical · 70% confidence
  Current-page preservation is not demonstrated
  The evidence lists many locale variants but only shows homepage URLs, so it does not verify that switching locales preserves a non-homepage path.
  Found here
  Header · language switcher
  https://www.heidihealth.com/en-us
  What we saw
  "locales":["de-be","de-ch","de-de",...,"ja-jp"] and the shown page URLs include "https://www.heidihealth.com/en-us" and "https://www.heidihealth.com/en-gb".
  How to fix it
  Test the switcher from several non-homepage URLs and confirm that each locale links to the equivalent localized path.
Sitemap
Fail70technical
Like 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, es, it do not appear in sampled sitemap URLs.
  Found here
  Sitemap · sitemap.xml
  https://www.heidihealth.com/sitemap-index.xml
  What we saw
  Sitemap locales in sample: en; missing: fr, de, es, it
  How to fix it
  Include URLs for every published locale prefix in the sitemap.
Structured data
Fail0technical
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.heidihealth.com/en-us
  What we saw
  Organization is present but inLanguage is missing
  How to fix it
  Set JSON-LD inLanguage to match each page locale.
Accessibility localisation
Fail72technical
lang, aria-label, and alt text should match the page locale.
- infotechnical · 82% confidence
  Locale metadata is explicit for the sampled English pages
  The sampled pages expose locale-specific htmlLang values, but the evidence does not expose aria-label or alt attributes for verification.
  Found here
  Document · <html>
  https://www.heidihealth.com/en-us
  What we saw
  "htmlLang":"en-us" and "htmlLang":"en-gb"
  How to fix it
  Audit aria-label and alt attributes across every locale and ensure their values are translated or otherwise appropriate for the page locale.
Translation completeness
Fail0linguistic
Localized 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 5 sampled pages.
  Found here
  Primary action · <button>
  https://www.heidihealth.com/fr-ca
  What we saw
  Primary CTA: "Solutions" Seen on 5 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.
Terminology consistency
Fail50linguistic
Important concepts should not be translated differently across pages.
- infolinguistic · 95% confidence
  Cross-locale terminology cannot be assessed
  The supplied content shows only English page copy, so consistency of important concepts across translated locales is unverified.
  Found here
  https://www.heidihealth.com/en-us
  What we saw
  The sampled page text includes English terms such as "Platform", "Solutions", "Research", and "Get Heidi free"; no translated counterpart is shown.
  How to fix it
  Compare repeated product terms across the German, Spanish, French, Italian, and Japanese pages and standardize their translations.
Translation accuracy
Fail50linguistic
Target copy should preserve the source meaning, numbers, and product actions.
- infolinguistic · 95% confidence
  Translation accuracy cannot be assessed
  No target-language copy or source-to-target comparison is provided in the evidence.
  Found here
  https://www.heidihealth.com/en-us
  What we saw
  The shown titles, headings, buttons, and page text are English, including "The AI Care Partner for clinicians" and "Book a demo".
  How to fix it
  Provide paired source and localized strings for review, including all product actions and any numbers or other locale-sensitive content.
Fluency
Fail50linguistic
Copy should sound natural, without grammar issues or machine-translation artifacts.
- infolinguistic · 95% confidence
  Localized fluency cannot be assessed
  The evidence contains English copy only and does not show any translated text to evaluate for naturalness or machine-translation artifacts.
  Found here
  https://www.heidihealth.com/en-us
  What we saw
  "Relief in every visit The AI Care Partner for clinicians"
  How to fix it
  Review rendered copy in each target locale with a native-language reviewer.
Brand voice
Fail50linguistic
Localized copy should preserve the intended tone of the source.
- infolinguistic · 95% confidence
  Localized brand voice cannot be assessed
  The English source demonstrates a concise, reassuring tone, but no localized copy is available to determine whether that tone is preserved.
  Found here
  Hero · <h1>
  https://www.heidihealth.com/en-us
  What we saw
  "Relief in every visit" and "The AI Care Partner for clinicians"
  How to fix it
  Evaluate each localized hero, CTA, and supporting message against the source tone and revise wording that becomes overly formal, technical, or promotional.
Grammar and style
Fail50linguistic
Locale-specific capitalization, punctuation, formality, and agreement should be correct.
- infolinguistic · 95% confidence
  Locale-specific grammar and style cannot be assessed
  Only English page strings are shown, so capitalization, punctuation, formality, and agreement in other locales remain unverified.
  Found here
  https://www.heidihealth.com/en-us
  What we saw
  The evidence shows English strings such as "Contact us", "Log in", and "Get Heidi free".
  How to fix it
  Proofread each locale for its own capitalization, punctuation, formality, and grammatical agreement conventions.
CTA intent
Fail72contextual
Localized calls to action should communicate the intended product action.
- infocontextual · 82% confidence
  English CTA intent is clear in the sampled page
  The sampled English page exposes distinct acquisition and sales actions, but localized CTA intent is not shown for comparison.
  Found here
  Hero · CTA buttons
  https://www.heidihealth.com/en-us
  What we saw
  "Get Heidi free" and "Book a demo"
  How to fix it
  Verify that every locale preserves the distinction between starting access and requesting a sales demonstration.
UI context
Fail72contextual
Translations should fit the UI component: button, nav, form, modal, or error.
- infocontextual · 82% confidence
  English UI contexts are identifiable
  The evidence identifies navigation controls, search-related controls, and CTAs in English, but provides no translated UI strings for review.
  Found here
  Header · <nav>
  https://www.heidihealth.com/en-us
  What we saw
  "Platform", "Solutions", "Resources", "⌘K", "Look up", and "Research"
  How to fix it
  Review each translated string in its actual button, navigation, search, or form component and adjust wording to fit the control.
Product context
Fail72contextual
Language should match product concepts such as plans, settings, and workflows.
- infocontextual · 82% confidence
  Product context is clear in the sampled English copy
  The page consistently presents Heidi as an AI care partner for clinicians, but translated product terminology is not provided.
  Found here
  Hero · <h1>
  https://www.heidihealth.com/en-us
  What we saw
  "Heidi | Your AI Care Partner for Modern Clinical Practice" and "The AI Care Partner for clinicians"
  How to fix it
  Preserve the clinician-focused product meaning and established product terms in every localized workflow and CTA.
Contextual meaning
Fail72contextual
Strings should be judged in surrounding page and component context, not in isolation.
- infocontextual · 82% confidence
  English strings have visible page context
  The evidence places the sampled copy in navigation, hero, and CTA contexts, but does not provide target-language renderings for contextual review.
  Found here
  Hero · <h1>
  https://www.heidihealth.com/en-us
  What we saw
  "Relief in every visit", "Get Heidi free", and "Book a demo" appear together in the sampled page text.
  How to fix it
  Review localized strings in their surrounding sections and components rather than approving them as isolated translation units.
Audience context
Fail78contextual
Language should fit the intended audience, such as consumer, enterprise, or developer.
- infocontextual · 88% confidence
  The sampled page clearly targets clinicians
  The English title and hero explicitly frame the product for clinical practice and clinicians; localized audience fit is not shown.
  Found here
  Hero · <h1>
  https://www.heidihealth.com/en-us
  What we saw
  "Your AI Care Partner for Modern Clinical Practice" and "The AI Care Partner for clinicians"
  How to fix it
  Keep clinician-facing terminology and professional positioning consistent across all target locales.
Text expansion
Fail40visual
Longer 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 27 sampled pages.
  Found here
  Heading · heading
  https://www.heidihealth.com/fr-ca
  What we saw
  EN "Relief in every visit" → FR "Heidi — Your AI Care PartnerHeidi AI" (171%) Seen on 5 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
Fail50visual
Language-specific images and alt text should match the page locale.
- infovisual · 65% confidence
  Localized assets cannot be verified
  The supplied preview does not include image markup, asset names, or alt text, so locale-specific imagery and accessibility text remain unverified.
  Found here
  https://www.heidihealth.com/en-us
  How to fix it
  Inspect image elements and asset variants on each locale page, including their alt attributes, for language and cultural appropriateness.
Visual hierarchy
Fail55visual
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 5 sampled pages.
  Found here
  Page body · heading
  https://www.heidihealth.com/de-de
  What we saw
  „Seit ich Heidi benutze, kann ich mich dem Patienten besser zuwenden. Ich muss nicht mehr sofort alles stichpunktartig mitschreiben.” Seen on 3 pages, e.g. https://www.heidihealth.com/de-de, https://www.heidihealth.com/fr-fr, https://www.heidihealth.com/it-it
  How to fix it
  Shorten the heading so it does not crowd the visual hierarchy.
Component consistency
Fail70visual
Repeated 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-ca
  What we saw
  Source locale has 14 buttons; fr has 8.
  How to fix it
  Keep the same repeated controls across locales, or drop unused ones on purpose.
Text overflow
Fail70visual
Text should not clip, truncate unexpectedly, or overflow buttons and navigation.
Layout breakage
Fail70visual
Localized pages should not overlap, break grids, or overflow modals.
Responsive localisation
Fail70visual
Localized layouts should hold up across mobile, tablet, and desktop widths.

Passed audits (5)

Not applicable (8)

Detected locales

de-be (hreflang)de-ch (hreflang)de-de (hreflang)de-lu (hreflang)en-au (hreflang)en-ca (hreflang)en-gb (hreflang)en-hk (hreflang)en-ie (hreflang)en-my (hreflang)en-nz (hreflang)en-sg (hreflang)en-us (html_lang)en-za (hreflang)es-ar (hreflang)es-es (hreflang)es-mx (hreflang)fr-be (hreflang)fr-ca (hreflang)fr-ch (hreflang)fr-fr (hreflang)fr-lu (hreflang)it-it (hreflang)ja-jp (hreflang)

Full findings

mediumtechnical · 88% confidence
Sitemap omits some published locales
Locale-prefixed pages for fr, de, es, it do not appear in sampled sitemap URLs.
Found here
Sitemap · sitemap.xml
https://www.heidihealth.com/sitemap-index.xml
What we saw
Sitemap locales in sample: en; missing: fr, de, es, it
How to fix it
Include URLs for every published locale prefix in the sitemap.
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/en-us
What we saw
Organization is present but inLanguage is missing
How to fix it
Set JSON-LD inLanguage to match each page locale.
highlinguistic · 92% confidence
Untranslated call to action
A fr-ca page still uses source-language CTA copy. Affects 5 sampled pages.
Found here
Primary action · <button>
https://www.heidihealth.com/fr-ca
What we saw
Primary CTA: "Solutions" Seen on 5 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.
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 27 sampled pages.
Found here
Heading · heading
https://www.heidihealth.com/fr-ca
What we saw
EN "Relief in every visit" → FR "Heidi — Your AI Care PartnerHeidi AI" (171%) Seen on 5 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.
lowvisual · 80% confidence
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 5 sampled pages.
Found here
Page body · heading
https://www.heidihealth.com/de-de
What we saw
„Seit ich Heidi benutze, kann ich mich dem Patienten besser zuwenden. Ich muss nicht mehr sofort alles stichpunktartig mitschreiben.” Seen on 3 pages, e.g. https://www.heidihealth.com/de-de, https://www.heidihealth.com/fr-fr, https://www.heidihealth.com/it-it
How to fix it
Shorten the heading so it does not crowd the visual hierarchy.
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-ca
What we saw
Source locale has 14 buttons; fr has 8.
How to fix it
Keep the same repeated controls across locales, or drop unused ones on purpose.
mediumtechnical · 70% confidence
Current-page preservation is not demonstrated
The evidence lists many locale variants but only shows homepage URLs, so it does not verify that switching locales preserves a non-homepage path.
Found here
Header · language switcher
https://www.heidihealth.com/en-us
What we saw
"locales":["de-be","de-ch","de-de",...,"ja-jp"] and the shown page URLs include "https://www.heidihealth.com/en-us" and "https://www.heidihealth.com/en-gb".
How to fix it
Test the switcher from several non-homepage URLs and confirm that each locale links to the equivalent localized path.
infotechnical · 82% confidence
Locale metadata is explicit for the sampled English pages
The sampled pages expose locale-specific htmlLang values, but the evidence does not expose aria-label or alt attributes for verification.
Found here
Document · <html>
https://www.heidihealth.com/en-us
What we saw
"htmlLang":"en-us" and "htmlLang":"en-gb"
How to fix it
Audit aria-label and alt attributes across every locale and ensure their values are translated or otherwise appropriate for the page locale.
infolinguistic · 95% confidence
Cross-locale terminology cannot be assessed
The supplied content shows only English page copy, so consistency of important concepts across translated locales is unverified.
Found here
https://www.heidihealth.com/en-us
What we saw
The sampled page text includes English terms such as "Platform", "Solutions", "Research", and "Get Heidi free"; no translated counterpart is shown.
How to fix it
Compare repeated product terms across the German, Spanish, French, Italian, and Japanese pages and standardize their translations.
infolinguistic · 95% confidence
Translation accuracy cannot be assessed
No target-language copy or source-to-target comparison is provided in the evidence.
Found here
https://www.heidihealth.com/en-us
What we saw
The shown titles, headings, buttons, and page text are English, including "The AI Care Partner for clinicians" and "Book a demo".
How to fix it
Provide paired source and localized strings for review, including all product actions and any numbers or other locale-sensitive content.
infolinguistic · 95% confidence
Localized fluency cannot be assessed
The evidence contains English copy only and does not show any translated text to evaluate for naturalness or machine-translation artifacts.
Found here
https://www.heidihealth.com/en-us
What we saw
"Relief in every visit The AI Care Partner for clinicians"
How to fix it
Review rendered copy in each target locale with a native-language reviewer.
infolinguistic · 95% confidence
Localized brand voice cannot be assessed
The English source demonstrates a concise, reassuring tone, but no localized copy is available to determine whether that tone is preserved.
Found here
Hero · <h1>
https://www.heidihealth.com/en-us
What we saw
"Relief in every visit" and "The AI Care Partner for clinicians"
How to fix it
Evaluate each localized hero, CTA, and supporting message against the source tone and revise wording that becomes overly formal, technical, or promotional.
infolinguistic · 95% confidence
Locale-specific grammar and style cannot be assessed
Only English page strings are shown, so capitalization, punctuation, formality, and agreement in other locales remain unverified.
Found here
https://www.heidihealth.com/en-us
What we saw
The evidence shows English strings such as "Contact us", "Log in", and "Get Heidi free".
How to fix it
Proofread each locale for its own capitalization, punctuation, formality, and grammatical agreement conventions.
infocontextual · 82% confidence
English CTA intent is clear in the sampled page
The sampled English page exposes distinct acquisition and sales actions, but localized CTA intent is not shown for comparison.
Found here
Hero · CTA buttons
https://www.heidihealth.com/en-us
What we saw
"Get Heidi free" and "Book a demo"
How to fix it
Verify that every locale preserves the distinction between starting access and requesting a sales demonstration.
infocontextual · 82% confidence
English UI contexts are identifiable
The evidence identifies navigation controls, search-related controls, and CTAs in English, but provides no translated UI strings for review.
Found here
Header · <nav>
https://www.heidihealth.com/en-us
What we saw
"Platform", "Solutions", "Resources", "⌘K", "Look up", and "Research"
How to fix it
Review each translated string in its actual button, navigation, search, or form component and adjust wording to fit the control.
infocontextual · 82% confidence
Product context is clear in the sampled English copy
The page consistently presents Heidi as an AI care partner for clinicians, but translated product terminology is not provided.
Found here
Hero · <h1>
https://www.heidihealth.com/en-us
What we saw
"Heidi | Your AI Care Partner for Modern Clinical Practice" and "The AI Care Partner for clinicians"
How to fix it
Preserve the clinician-focused product meaning and established product terms in every localized workflow and CTA.
infocontextual · 82% confidence
English strings have visible page context
The evidence places the sampled copy in navigation, hero, and CTA contexts, but does not provide target-language renderings for contextual review.
Found here
Hero · <h1>
https://www.heidihealth.com/en-us
What we saw
"Relief in every visit", "Get Heidi free", and "Book a demo" appear together in the sampled page text.
How to fix it
Review localized strings in their surrounding sections and components rather than approving them as isolated translation units.
infocontextual · 88% confidence
The sampled page clearly targets clinicians
The English title and hero explicitly frame the product for clinical practice and clinicians; localized audience fit is not shown.
Found here
Hero · <h1>
https://www.heidihealth.com/en-us
What we saw
"Your AI Care Partner for Modern Clinical Practice" and "The AI Care Partner for clinicians"
How to fix it
Keep clinician-facing terminology and professional positioning consistent across all target locales.
infovisual · 65% confidence
Localized assets cannot be verified
The supplied preview does not include image markup, asset names, or alt text, so locale-specific imagery and accessibility text remain unverified.
Found here
https://www.heidihealth.com/en-us
How to fix it
Inspect image elements and asset variants on each locale page, including their alt attributes, for language and cultural appropriateness.

Pages sampled

200 · https://www.heidihealth.com/en-us · lang=en-us
200 · https://www.heidihealth.com/en-us · lang=en-us
200 · https://www.heidihealth.com/en-gb · lang=en-gb
200 · https://www.heidihealth.com/en-ca · lang=en-ca
200 · https://www.heidihealth.com/fr-ca · lang=fr-ca
200 · https://www.heidihealth.com/en-au · lang=en-au
200 · https://www.heidihealth.com/en-nz · lang=en-nz
200 · https://www.heidihealth.com/en-ie · lang=en-ie
200 · https://www.heidihealth.com/en-hk · lang=en-hk
200 · https://www.heidihealth.com/en-za · lang=en-za
200 · https://www.heidihealth.com/en-sg · lang=en-sg
200 · https://www.heidihealth.com/de-de · lang=de-de
200 · https://www.heidihealth.com/fr-fr · lang=fr-fr
200 · https://www.heidihealth.com/es-es · lang=es-es
200 · https://www.heidihealth.com/it-it · lang=it-it

Email me a summary

Optional. Enter your work email and we will send a concise summary of this public report.

Next step

Solid baseline with room to improve. Create a workspace for continuous locale monitoring, or book an audit review.

Book an audit review