현지화 보고서

Heidi

Healthcare AI

heidihealth.com

제품: 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.

브랜드 보이스: Practical, supportive, clinically focused

현지화 점수

78/100

좋음

웹사이트는 전반적으로 현지화가 잘되어 있지만, 개선할 부분이 있습니다.

82기술 감사
74언어 품질 감사
88맥락 감사
67시각적 감사

감사 완료일: 2026. 9. 8.범위: 공개 스마트 샘플 · 기술·언어·맥락·시각적 크레딧신뢰도: 샘플링한 페이지를 기반으로 한 개략적인 상태 점검 — 전체 사이트 크롤링은 아닙니다.

기술, 언어, 맥락 및 시각적 현지화 크레딧 전반에서 15개 페이지를 표본으로 추출했습니다. 현지화 감사 점수 산정 방법

다른 사람들과의 비교

공개 감사 23개 중 #7위

Ahead of 16 other public audits공개 평균: 70/100

전체 순위표 보기

우선 수정할 항목

1
high
Untranslated call to action
A fr-ca page still uses source-language CTA copy. Affects 3 sampled pages.
See details
2
medium
Sitemap omits some published locales
Locale-prefixed pages for fr, de do not appear in sampled sitemap URLs.
See details
3
medium
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

감사 기준

5 passed · 14 to watch · 8 to fix · 8 not applicable

확인 필요 (8)

Language switcher
실패74기술적
Visitors should move between locales without losing the current page.
- mediumtechnical · 신뢰도 62%
  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.
  발견 위치
  Header · <nav>
  https://www.heidihealth.com/
  확인한 내용
  "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"
  해결 방법
  Test the language switcher from representative inner pages and confirm that each locale preserves the equivalent path.
Structured data
실패0기술적
JSON-LD inLanguage should match the page locale when structured data is present.
- lowtechnical · 신뢰도 95%
  Structured data omits inLanguage
  JSON-LD is present but does not declare inLanguage on sampled pages.
  발견 위치
  JSON-LD · <script type="application/ld+json">
  https://www.heidihealth.com/
  확인한 내용
  Organization is present but inLanguage is missing
  해결 방법
  Set JSON-LD inLanguage to match each page locale.
Translation completeness
실패34언어적
Localized pages should not leave source-language copy in place, except brand names and URLs.
- highlinguistic · 신뢰도 92%
  Untranslated call to action
  A fr-ca page still uses source-language CTA copy. Affects 3 sampled pages.
  발견 위치
  Link · <a>
  https://www.heidihealth.com/fr-ca
  확인한 내용
  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
  해결 방법
  Translate leftover source-language CTAs to match the surrounding locale copy.
Translation accuracy
실패72언어적
Target copy should preserve the source meaning, numbers, and product actions.
Text expansion
실패40시각적
Longer translations should not create obvious length pressure versus the source UI.
- mediumvisual · 신뢰도 88%
  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.
  발견 위치
  Heading · heading
  https://www.heidihealth.com/fr-ca
  확인한 내용
  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
  해결 방법
  Shorten the translation or give the control more room so the longer copy does not overflow.
Localized images and assets
실패74시각적
Language-specific images and alt text should match the page locale.
Visual hierarchy
실패58시각적
Localization should not make headings or CTAs lose scanability.
- lowvisual · 신뢰도 80%
  Heading is excessively long
  A localized heading may crowd the visual hierarchy. Affects 4 sampled pages.
  발견 위치
  Page body · heading
  https://www.heidihealth.com/de-de
  확인한 내용
  „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
  해결 방법
  Shorten the heading so it does not crowd the visual hierarchy.
Component consistency
실패70시각적
Repeated components should stay visually consistent across locales.
- lowvisual · 신뢰도 95%
  Repeated components differ across locales
  Button counts differ between the source locale and fr.
  발견 위치
  Page body · <button>
  https://www.heidihealth.com/fr-ca
  확인한 내용
  Source locale has 13 buttons; fr has 8.
  해결 방법
  Keep the same repeated controls across locales, or drop unused ones on purpose.

Worth a look (14)

Sitemap
Watch76기술적
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%
  Sitemap omits some published locales
  Locale-prefixed pages for fr, de do not appear in sampled sitemap URLs.
  발견 위치
  Sitemap · sitemap.xml
  https://www.heidihealth.com/sitemap-index.xml
  확인한 내용
  Sitemap locales in sample: en; missing: fr, de
  해결 방법
  Include URLs for every published locale prefix in the sitemap.
Accessibility localisation
Watch84기술적
lang, aria-label, and alt text should match the page locale.
Terminology consistency
Watch80언어적
Important concepts should not be translated differently across pages.
Fluency
Watch86언어적
Copy should sound natural, without grammar issues or machine-translation artifacts.
Brand voice
Watch84언어적
Localized copy should preserve the intended tone of the source.
Grammar and style
Watch86언어적
Locale-specific capitalization, punctuation, formality, and agreement should be correct.
CTA intent
Watch89맥락적
Localized calls to action should communicate the intended product action.
UI context
Watch88맥락적
Translations should fit the UI component: button, nav, form, modal, or error.
Product context
Watch86맥락적
Language should match product concepts such as plans, settings, and workflows.
Contextual meaning
Watch87맥락적
Strings should be judged in surrounding page and component context, not in isolation.
Audience context
Watch89맥락적
Language should fit the intended audience, such as consumer, enterprise, or developer.
Text overflow
Watch76시각적
Text should not clip, truncate unexpectedly, or overflow buttons and navigation.
Layout breakage
Watch76시각적
Localized pages should not overlap, break grids, or overflow modals.
Responsive localisation
Watch76시각적
Localized layouts should hold up across mobile, tablet, and desktop widths.

통과한 감사 항목 (5)

해당 없음 (8)

감지된 로캘

독일어(벨기에)
de-be · hreflang
고지 독일어(스위스)
de-ch · hreflang
독일어(독일)
de-de · hreflang
독일어(룩셈부르크)
de-lu · hreflang
영어(아랍에미리트)
en-ae · hreflang
영어(오스트레일리아)
en-au · hreflang
영어(캐나다)
en-ca · hreflang
영어(영국)
en-gb · hreflang
영어(홍콩[중국 특별행정구])
en-hk · hreflang
영어(아일랜드)
en-ie · hreflang
영어(말레이시아)
en-my · hreflang
영어(뉴질랜드)
en-nz · hreflang
영어(사우디아라비아)
en-sa · hreflang
영어(싱가포르)
en-sg · hreflang
영어(미국)
en-us · hreflang
영어(남아프리카)
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
일본어(일본)
ja-jp · hreflang

표본 페이지#+#+#+#+

다음 단계

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.