현지화 보고서

Figma

Design and collaboration software

figma.com

제품: Figma is a collaborative canvas bringing design, code, and AI together, helping teams move from initial ideas to shipped products in one place. Its offerings include design, prototyping, developer handoff, whiteboarding, presentations, and related creative workflows.

브랜드 보이스: collaborative, creative, product-focused

현지화 점수

71/100

개선 필요

사용자는 눈에 띄는 현지화 문제를 겪을 수 있습니다.

76기술 감사
71언어 품질 감사
74맥락 감사
64시각적 감사

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

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

다른 사람들과의 비교

공개 감사 23개 중 #14위

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

전체 순위표 보기

우선 수정할 항목

1
high
URL locale and html lang disagree
Path locale ai expects html lang ai, but the page declares en.
See details
2
high
Language links return to the homepage
Locale links were found, but they appear to drop the current page path.
See details
3
high
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
See details

감사 기준

5 passed · 10 to watch · 16 to fix · 4 not applicable

확인 필요 (16)

Language switcher
실패58기술적
Visitors should move between locales without losing the current page.
- hightechnical · 신뢰도 95%
  Language links return to the homepage
  Locale links were found, but they appear to drop the current page path.
  발견 위치
  Header · <nav> language links
  https://www.figma.com/
  확인한 내용
  <a href="https://www.figma.com/ai/">AI workflows</a> drops the current page path
  해결 방법
  Point language-switcher links at the equivalent localized path, not the locale homepage.
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.figma.com/
  확인한 내용
  Organization is present but inLanguage is missing
  해결 방법
  Set JSON-LD inLanguage to match each page locale.
International formatting
실패50기술적
Dates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.
- infotechnical · 신뢰도 42%
  Locale-sensitive values are not shown
  The provided evidence contains no dates, numbers, currencies, or calendar values, so international formatting cannot be verified.
  확인한 내용
  The preview shows page titles, buttons, headings, and cookie text, but no dates, numbers, currency amounts, or calendar values.
  해결 방법
  Audit representative localized pages for date, number, currency, digit, and calendar formatting.
Terminology consistency
실패40언어적
Important concepts should not be translated differently across pages.
- mediumlinguistic · 신뢰도 95%
  Terminology inconsistency
  "Figma Socials" appears both untranslated and translated across de pages. Affects 11 sampled pages.
  발견 위치
  Header · <nav> or <button>
  https://www.figma.com/de-de/
  확인한 내용
  "Figma Socials" appears untranslated on some de pages and translated on others Seen on 5 pages, e.g. https://www.figma.com/de-de/, https://www.figma.com/fr-fr/, https://www.figma.com/it-it/
  해결 방법
  Use one translated label for "Figma Socials" across de pages.
Translation accuracy
실패72언어적
Target copy should preserve the source meaning, numbers, and product actions.
- mediumlinguistic · 신뢰도 67%
  Opt-out wording may not preserve the source action
  The German translation "Ausschluss" does not clearly communicate the consent-management action expressed by the English "Opt-Out" and may be semantically inaccurate in this UI context.
  발견 위치
  Privacy controls · <button>
  https://www.figma.com/de-de/
  확인한 내용
  English: "Opt-Out"; German: "Ausschluss"; German longer label: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
  해결 방법
  Use established German consent terminology such as “Ablehnen” or “Opt-out” consistently, and validate it with German legal and UX reviewers.
Fluency
실패70언어적
Copy should sound natural, without grammar issues or machine-translation artifacts.
- mediumlinguistic · 신뢰도 73%
  German privacy copy reads awkwardly
  The sampled German cookie notice contains an unnatural construction around selling and distributing behavioral advertising.
  발견 위치
  Cookie notice · <p>
  https://www.figma.com/de-de/
  확인한 내용
  "Wir nutzen Cookies für Verkaufszwecke und Verteilung der verhaltensgebundenen Werbung oder für zielgerichtete Werbung."
  해결 방법
  Rewrite the sentence in idiomatic German and have a native copy editor review the full privacy notice.
CTA intent
실패72맥락적
Localized calls to action should communicate the intended product action.
- mediumcontextual · 신뢰도 76%
  German opt-out CTA is ambiguous
  The German CTA "Ausschluss" does not clearly tell users that they can opt out of selling or sharing personal information.
  발견 위치
  Privacy controls · <button>
  https://www.figma.com/de-de/
  확인한 내용
  Source button: "Opt-Out"; German button: "Ausschluss"; German extended button: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
  해결 방법
  Replace “Ausschluss” with a clear action-oriented German label that explicitly conveys opting out of sale or sharing.
Cultural adaptation
실패55맥락적
Currency, dates, addresses, and local examples should fit the market.
- infocontextual · 신뢰도 45%
  Market-specific adaptation is not evidenced
  The preview identifies many regional Spanish locales but does not show localized currencies, dates, addresses, examples, or market-specific content.
  확인한 내용
  The locale list includes regional variants such as "es-ar", "es-mx", and "es-es", while the visible page evidence contains only general product and privacy copy.
  해결 방법
  Review regional pages for market-appropriate formats, terminology, examples, and legal or privacy language.
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 de string is 167% the length of the source, which often causes overflow. Affects 26 sampled pages.
  발견 위치
  Heading · heading
  https://www.figma.com/de-de/
  확인한 내용
  EN "Use cases" → DE "Anwendungsfälle" (167%) Seen on 9 pages, e.g. https://www.figma.com/de-de/, https://www.figma.com/es-es/, https://www.figma.com/es-la/
  해결 방법
  Shorten the translation or give the control more room so the longer copy does not overflow.
Font and script support
실패62시각적
Typography should support the target script without generic fallback-only stacks, tofu glyphs, or missing CJK fonts.
- highvisual · 신뢰도 95%
  No CJK-capable font detected
  A ja-jp page shows CJK text but the embedded/inline font stack has no known CJK typeface. Affects 2 sampled pages.
  발견 위치
  Page body · font-family
  https://www.figma.com/ja-jp/
  확인한 내용
  font-family: monospace, inherit, var(--global-font-sans, var(--global-font-mono Seen on 2 pages, e.g. https://www.figma.com/ja-jp/, https://www.figma.com/ko-kr/
  해결 방법
  Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
Localized images and assets
실패50시각적
Language-specific images and alt text should match the page locale.
- infovisual · 신뢰도 35%
  Images and alt text are not included in the evidence
  The preview provides no image elements, asset references, or alt text, so localized visual assets cannot be verified.
  확인한 내용
  The provided page preview lists titles, buttons, headings, and text, but contains no <img> markup or alt-text values.
  해결 방법
  Inspect localized pages for image sources, embedded text, and alt attributes, then verify that language-specific assets and descriptions match each locale.
Visual hierarchy
실패55시각적
Localization should not make headings or CTAs lose scanability.
- lowvisual · 신뢰도 80%
  Heading is excessively long
  A localized heading may crowd the visual hierarchy. Affects 6 sampled pages.
  발견 위치
  Page body · heading
  https://www.figma.com/de-de/
  확인한 내용
  Mache rasch Fortschritte in die richtige Richtung auf einer KI-nativen Arbeitsfläche. Seen on 5 pages, e.g. https://www.figma.com/de-de/, https://www.figma.com/fr-fr/, https://www.figma.com/id-id/
  해결 방법
  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 ai.
  발견 위치
  Page body · <button>
  https://www.figma.com/ai/
  확인한 내용
  Source locale has 7 buttons; ai has 13.
  해결 방법
  Keep the same repeated controls across locales, or drop unused ones on purpose.
Text overflow
실패68시각적
Text should not clip, truncate unexpectedly, or overflow buttons and navigation.
- lowvisual · 신뢰도 62%
  Long localized privacy labels may require overflow testing
  The extended German privacy button is substantially longer than the English source and could stress fixed-width controls; no screenshot or layout measurements are provided.
  발견 위치
  Privacy controls · <button>
  https://www.figma.com/de-de/
  확인한 내용
  "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" versus the English "Do Not Sell/Share My Personal Info + Opt-Out".
  해결 방법
  Test the label at mobile and desktop widths; allow wrapping or expand the control instead of clipping or truncating text.
Layout breakage
실패68시각적
Localized pages should not overlap, break grids, or overflow modals.
- lowvisual · 신뢰도 60%
  Long privacy CTA warrants layout testing
  The longer German privacy control may affect button width or modal layout, but the evidence contains no visual capture confirming a breakage.
  발견 위치
  Privacy controls · <button>
  https://www.figma.com/de-de/
  확인한 내용
  "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" is shown as a button label.
  해결 방법
  Check the privacy control and any consent modal at narrow widths, and support flexible button sizing and wrapping.
Responsive localisation
실패68시각적
Localized layouts should hold up across mobile, tablet, and desktop widths.
- infovisual · 신뢰도 58%
  Responsive behavior is not directly evidenced
  The preview contains no screenshots, viewport measurements, or responsive DOM details; the longer localized CTA should therefore be treated as a test risk rather than a confirmed defect.
  발견 위치
  Privacy controls · <button>
  https://www.figma.com/de-de/
  확인한 내용
  The evidence shows the long German label "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" but no viewport or layout output.
  해결 방법
  Run mobile, tablet, and desktop visual checks for all locales with long navigation and privacy labels.

Worth a look (10)

Locale detection
Watch82기술적
Pages should declare a correct html lang that matches the URL and content locale.
- hightechnical · 신뢰도 95%
  URL locale and html lang disagree
  Path locale ai expects html lang ai, but the page declares en.
  발견 위치
  Document head · <html lang>
  https://www.figma.com/ai/
  확인한 내용
  <html lang="en"> while the path locale is ai
  해결 방법
  Set html lang="ai" so it matches this page’s URL locale.
Sitemap
Watch88기술적
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 ai do not appear in sampled sitemap URLs.
  발견 위치
  Sitemap · sitemap.xml
  https://www.figma.com/sitemap.xml
  확인한 내용
  Sitemap locales in sample: id, de, es, fr, it, nl, pl, pt, hi, ja, ko, th; missing: ai
  해결 방법
  Include URLs for every published locale prefix in the sitemap.
Accessibility localisation
Watch78기술적
lang, aria-label, and alt text should match the page locale.
- infotechnical · 신뢰도 82%
  Page language metadata matches sampled locales
  The sampled German and Spanish pages expose matching htmlLang values, supporting correct language metadata.
  발견 위치
  Document root · <html>
  https://www.figma.com/de-de/
  확인한 내용
  German page: "htmlLang":"de" with title "Figma: kollaborative Arbeitsfläche für Design, Code und KI"; Spanish page: "htmlLang":"es-es" with title "Figma: El lienzo colaborativo para diseño, código e IA".
Translation completeness
Watch82언어적
Localized pages should not leave source-language copy in place, except brand names and URLs.
- highlinguistic · 신뢰도 92%
  Untranslated call to action
  A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
  발견 위치
  Pricing hero · <button>
  https://www.figma.com/de-de/
  확인한 내용
  Primary CTA: "Community" Seen on 10 pages, e.g. https://www.figma.com/de-de/, https://www.figma.com/es-es/, https://www.figma.com/es-la/
  해결 방법
  Translate leftover source-language CTAs to match the surrounding locale copy.
- infolinguistic · 신뢰도 84%
  Sampled navigation and headings are localized
  The German and Spanish samples translate page titles, navigation labels, and headings rather than retaining the English source copy.
  발견 위치
  Header · <nav>
  https://www.figma.com/de-de/
  확인한 내용
  German buttons: "Produkte","Lösungen","Community","Ressourcen"; Spanish buttons: "Productos","Soluciones","Comunidad","Recursos".
Brand voice
Watch83언어적
Localized copy should preserve the intended tone of the source.
Grammar and style
Watch76언어적
Locale-specific capitalization, punctuation, formality, and agreement should be correct.
- lowlinguistic · 신뢰도 70%
  German terminology and capitalization need review
  The privacy notice uses awkward nominal phrasing and borrowed terminology that may not align with polished German style.
  발견 위치
  Cookie notice · <p>
  https://www.figma.com/de-de/
  확인한 내용
  "Diese Website verwendet Cookies, Zählpixel und lokale Speicherung zu Performance-, Personalisierungs- und Marketingzwecken."
  해결 방법
  Review the sentence for idiomatic German, including terminology such as “Performance” and the construction after “Speicherung”.
UI context
Watch76맥락적
Translations should fit the UI component: button, nav, form, modal, or error.
- mediumcontextual · 신뢰도 70%
  Privacy CTA context is unclear in German
  The short label "Ausschluss" is difficult to interpret as a button action, especially when paired with a longer personal-data opt-out label.
  발견 위치
  Privacy controls · <button>
  https://www.figma.com/de-de/
  확인한 내용
  German buttons include "Ausschluss" and "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
  해결 방법
  Use a concise, recognizable consent action in the button and keep the longer explanation in supporting text or an accessible label.
Product context
Watch82맥락적
Language should match product concepts such as plans, settings, and workflows.
Contextual meaning
Watch78맥락적
Strings should be judged in surrounding page and component context, not in isolation.
Audience context
Watch82맥락적
Language should fit the intended audience, such as consumer, enterprise, or developer.

통과한 감사 항목 (5)

해당 없음 (4)

감지된 로캘

ai
URL path
독일어(독일)
de-de · URL path
영어
en · page language
스페인어(아르헨티나)
es-ar · hreflang
스페인어(볼리비아)
es-bo · hreflang
스페인어(칠레)
es-cl · hreflang
스페인어(콜롬비아)
es-co · hreflang
스페인어(코스타리카)
es-cr · hreflang
스페인어(쿠바)
es-cu · hreflang
스페인어(도미니카 공화국)
es-do · hreflang
스페인어(에콰도르)
es-ec · hreflang
스페인어(유럽)
es-es · hreflang
스페인어(과테말라)
es-gt · hreflang
스페인어(온두라스)
es-hn · hreflang
스페인어(라오스)
es-la · URL path
스페인어(멕시코)
es-mx · hreflang
스페인어(니카라과)
es-ni · hreflang
스페인어(파나마)
es-pa · hreflang
스페인어(페루)
es-pe · hreflang
스페인어(푸에르토리코)
es-pr · hreflang
스페인어(파라과이)
es-py · hreflang
스페인어(엘살바도르)
es-sv · hreflang
스페인어(우루과이)
es-uy · hreflang
스페인어(베네수엘라)
es-ve · hreflang
프랑스어(프랑스)
fr-fr · URL path
힌디어(인도)
hi-in · URL path
인도네시아어(인도네시아)
id-id · URL path
이탈리아어(이탈리아)
it-it · URL path
일본어(일본)
ja-jp · URL path
한국어(대한민국)
ko-kr · URL path
네덜란드어(네덜란드)
nl-nl · URL path
폴란드어(폴란드)
pl-pl · URL path
포르투갈어(브라질)
pt-br · hreflang
태국어(태국)
th-th · URL path

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

다음 단계

Solid baseline with room to improve. Claim this domain to monitor locales as you ship, or 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.