Logo HyperlocaliseLogo Hyperlocalise
Yêu cầu bản demo

Báo cáo bản địa hóa

Atlassian logo

Atlassian

Team collaboration software

atlassian.com

Sản phẩm: Atlassian provides team collaboration software and AI-powered apps that help teams plan, organize, discuss, and complete shared work. Its products include Jira, Confluence, Loom, Bitbucket, and Jira Service Management.

Giọng điệu thương hiệu: Collaborative, confident, productivity-focused

Điểm bản địa hóa

69/100

Cần cải thiện

Người dùng có thể gặp phải các vấn đề bản địa hóa đáng chú ý.

  • 63Kiểm tra kỹ thuật
  • 64Kiểm tra ngôn ngữ
  • 83Kiểm tra theo ngữ cảnh
  • 65Kiểm tra trực quan
Audited: 15 thg 8, 2026Scope: Mẫu thông minh công khai · ghi công về kỹ thuật, ngôn ngữ, ngữ cảnh và hình ảnhĐộ tin cậy: Kiểm tra sơ bộ tình trạng từ các trang được lấy mẫu — không phải quá trình quét toàn bộ trang web.

Đã lấy mẫu 15 trang dựa trên các tiêu chí tín dụng bản địa hóa về kỹ thuật, ngôn ngữ, ngữ cảnh và hình ảnh. Cách chúng tôi chấm điểm các cuộc kiểm tra bản địa hóa

Bạn so sánh như thế nào

Xếp hạng #15 trong số 23 cuộc kiểm tra công khai

Ahead of 8 other public auditsĐiểm trung bình công khai: 70/100
Xem bảng xếp hạng đầy đủ

Khắc phục trước

  1. 1
    high

    Untranslated call to action

    A fr page still uses source-language CTA copy. Affects 7 sampled pages.

    See details
  2. 2
    high

    Page script does not match the locale

    A zh page is dominated by Latin-script copy. Affects 2 sampled pages.

    See details
  3. 3
    high

    No CJK-capable font detected

    A ja page shows CJK text but the embedded/inline font stack has no known CJK typeface. Affects 3 sampled pages.

    See details

Tiêu chí kiểm tra

4 passed · 11 to watch · 16 to fix · 4 not applicable

Cần chú ý (16)

  • Language switcher

    Fail65kỹ thuật

    Visitors should move between locales without losing the current page.

    • mediumtechnical · 82% độ tin cậy

      Locale routes are evidenced, but switching is not

      The evidence confirms separate locale URLs, but does not show a visible language switcher or preserve-current-page mapping.

      Tìm thấy tại đây

      https://www.atlassian.com/

      Điều chúng tôi nhận thấy

      "locales":["br","de","en","es","fr","it","ja","ko","nl","pl","pt-br","ru","zh"] and pages including "https://www.atlassian.com/", "https://www.atlassian.com/ja/", and "https://www.atlassian.com/fr/"

      Cách khắc phục

      Add an explicit language selector to the shared header or footer. Make each locale option link to the equivalent current page where available.

  • hreflang

    Fail20kỹ thuật

    Localized versions should be linked with valid, reciprocal hreflang including self and x-default.

    • mediumtechnical · 95% độ tin cậy

      Missing hreflang self-reference

      The page lists hreflang alternates but does not include itself.

      Tìm thấy tại đây

      Document head · <link rel="alternate" hreflang>

      https://www.atlassian.com/

      Điều chúng tôi nhận thấy

      <link rel="alternate" hreflang="ja" href="https://www.atlassian.com/ja/"> <link rel="alternate" hreflang="fr" href="https://www.atlassian.com/fr/"> <link rel="alternate" hreflang="de" href="https://www.atlassian.com/de/"> <link rel="alternate" hreflang="es" href="https://www.atla…

      Cách khắc phục

      Add a self-referencing hreflang alternate for this page.

    • lowtechnical · 95% độ tin cậy

      Missing x-default hreflang

      hreflang is present but does not declare an x-default fallback. Affects 12 sampled pages.

      Tìm thấy tại đây

      Document head · <link rel="alternate" hreflang>

      https://www.atlassian.com/

      Điều chúng tôi nhận thấy

      hreflang is present but none of the alternates use hreflang="x-default". Seen on 12 pages, e.g. https://www.atlassian.com/, https://www.atlassian.com/ja/, https://www.atlassian.com/fr/

      Cách khắc phục

      Add an x-default hreflang fallback for users whose locale is not listed.

  • Localized SEO metadata

    Fail65kỹ thuật

    Titles, descriptions, and og:locale should be localized per locale.

    • mediumtechnical · 95% độ tin cậy

      Page titles are not localized

      Sampled locales share the same document title.

      Tìm thấy tại đây

      Document head · <title>

      https://www.atlassian.com/

      Điều chúng tôi nhận thấy

      <title>Filter Icon</title> is reused across sampled locales

      Cách khắc phục

      Localize the document title for each page locale.

  • Sitemap

    Fail60kỹ thuật

    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 · 90% độ tin cậy

      Sitemap is missing localized URLs

      A sitemap was found, but sampled entries do not include locale-prefixed URLs.

      Tìm thấy tại đây

      Sitemap · sitemap.xml

      https://www.atlassian.com/blog/post-sitemap.xml

      Điều chúng tôi nhận thấy

      Sitemap https://www.atlassian.com/blog/post-sitemap.xml has no locale-prefixed URLs in the sample

      Cách khắc phục

      Include localized URLs in the sitemap for every published locale.

  • Structured data

    Fail0kỹ thuật

    JSON-LD inLanguage should match the page locale when structured data is present.

    • lowtechnical · 95% độ tin cậy

      Structured data omits inLanguage

      JSON-LD is present but does not declare inLanguage on sampled pages.

      Tìm thấy tại đây

      JSON-LD · <script type="application/ld+json">

      https://www.atlassian.com/

      Điều chúng tôi nhận thấy

      Organization is present but inLanguage is missing

      Cách khắc phục

      Set JSON-LD inLanguage to match each page locale.

  • International formatting

    Fail50kỹ thuật

    Dates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.

    • infotechnical · 90% độ tin cậy

      Formatting coverage cannot be verified

      The supplied page extracts contain no dates, numbers, currencies, addresses, or calendar examples to assess against locale conventions.

      Điều chúng tôi nhận thấy

      The provided page text includes navigation and product descriptions such as "Featured apps" and "Flexible project management", but no dates, numbers, or currency values.

      Cách khắc phục

      Audit localized pages containing prices, dates, quantities, and addresses with locale-aware formatting rules.

  • Accessibility localisation

    Fail72kỹ thuật

    lang, aria-label, and alt text should match the page locale.

    • infotechnical · 88% độ tin cậy

      Document language is localized

      The English, Japanese, and French page samples explicitly declare matching htmlLang values.

      Tìm thấy tại đây

      Document root · <html>

      https://www.atlassian.com/

      Điều chúng tôi nhận thấy

      "htmlLang":"en" for "https://www.atlassian.com/", "htmlLang":"ja" for "https://www.atlassian.com/ja/", and "htmlLang":"fr" for "https://www.atlassian.com/fr/"

      Cách khắc phục

      Keep the html lang value synchronized with the rendered locale on every localized route.

    • mediumtechnical · 88% độ tin cậy

      ARIA labels and alt text are not shown

      The truncated evidence does not include aria-label attributes or image alt text, so accessibility localization cannot be confirmed.

      Điều chúng tôi nhận thấy

      The preview lists buttons, headings, and text, but contains no "aria-label" or "alt" markup.

      Cách khắc phục

      Review all accessible names and image alt attributes for untranslated or hard-coded source-language strings.

  • Translation completeness

    Fail0linguistic

    Localized pages should not leave source-language copy in place, except brand names and URLs.

    • highlinguistic · 92% độ tin cậy

      Untranslated call to action

      A fr page still uses source-language CTA copy. Affects 7 sampled pages.

      Tìm thấy tại đây

      Pricing hero · <button>

      https://www.atlassian.com/fr/

      Điều chúng tôi nhận thấy

      Primary CTA: "Solutions" Seen on 7 pages, e.g. https://www.atlassian.com/fr/, https://www.atlassian.com/de/, https://www.atlassian.com/es/

      Cách khắc phục

      Translate leftover source-language CTAs to match the surrounding locale copy.

    • highlinguistic · 95% độ tin cậy

      Page script does not match the locale

      A zh page is dominated by Latin-script copy. Affects 2 sampled pages.

      Tìm thấy tại đây

      Page body · sampled copy

      https://www.atlassian.com/zh/

      Điều chúng tôi nhận thấy

      ___ 跳至内容 产品 精选 开发人员 产品经理 IT 专业人员 业务团队 领导团队 查看所有应用 精选应用 Jira 灵活的项目管理 Confluence 知识，全部集中在一处 Jira Service Management 高速交付服务 Atlassian 集合 无缝地增强团队合作 Jira Confluence Loom 自信地优化策略与成果 Focus Talent Align 高速交付服务 Jira Service Management Customer Service Management Assets 快速交付优质的软件 Rovo Dev…

      Cách khắc phục

      Write this zh page in the expected script instead of leftover Latin-script copy.

  • Terminology consistency

    Fail40linguistic

    Important concepts should not be translated differently across pages.

    • mediumlinguistic · 95% độ tin cậy

      Terminology inconsistency

      "Manage preferences" appears both untranslated and translated across ja pages. Affects 26 sampled pages.

      Tìm thấy tại đây

      Header · <nav> or <button>

      https://www.atlassian.com/ja/

      Điều chúng tôi nhận thấy

      "Manage preferences" appears untranslated on some ja pages and translated on others Seen on 11 pages, e.g. https://www.atlassian.com/ja/, https://www.atlassian.com/fr/, https://www.atlassian.com/de/

      Cách khắc phục

      Use one translated label for "Manage preferences" across ja pages.

  • Cultural adaptation

    Fail55contextual

    Currency, dates, addresses, and local examples should fit the market.

    • infocontextual · 88% độ tin cậy

      No market-specific adaptation is evidenced

      The supplied extracts contain global product navigation and descriptions but no local currencies, dates, addresses, or market-specific examples to assess.

      Điều chúng tôi nhận thấy

      The samples show product and audience labels such as "Atlassian Collections", "By Use Case", and "By Team", with no local market data or examples.

      Cách khắc phục

      Review pricing, date, address, legal, and example content separately for each target market.

  • Text expansion

    Fail40trực quan

    Longer translations should not create obvious length pressure versus the source UI.

    • mediumvisual · 88% độ tin cậy

      Localized text is much longer than the source

      A fr string is 200% the length of the source, which often causes overflow. Affects 37 sampled pages.

      Tìm thấy tại đây

      Control · <button>

      https://www.atlassian.com/fr/

      Điều chúng tôi nhận thấy

      EN "IT professionals" → FR "Professionnels de l'informatique" (200%) Seen on 9 pages, e.g. https://www.atlassian.com/fr/, https://www.atlassian.com/de/, https://www.atlassian.com/es/

      Cách khắc phục

      Shorten the translation or give the control more room so the longer copy does not overflow.

  • Font and script support

    Fail48trực quan

    Typography should support the target script without generic fallback-only stacks, tofu glyphs, or missing CJK fonts.

    • highvisual · 95% độ tin cậy

      No CJK-capable font detected

      A ja page shows CJK text but the embedded/inline font stack has no known CJK typeface. Affects 3 sampled pages.

      Tìm thấy tại đây

      Page body · font-family

      https://www.atlassian.com/ja/

      Điều chúng tôi nhận thấy

      font-family: Charlie Display, Charlie Text, Atlassian Sans, var(--bxp-charlie-text-font-family), var(--bxp-charlie-display-font-family), inherit, var(--_bs1jwf), var(--_1vugql0), var(--ds-font-family-code, var(--ds-font-family-body, unset, SFMono-MediumItalic Seen on 3 pages, e.g…

      Cách khắc phục

      Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.

  • CJK typography

    Fail72trực quan

    Korean pages should avoid word-break: break-all and prefer word-break: keep-all; CJK forms should use local name-field conventions.

    • highvisual · 94% độ tin cậy

      Korean text uses word-break: break-all

      break-all can split Hangul mid-word and makes Korean body copy harder to read.

      Tìm thấy tại đây

      CSS · word-break

      https://www.atlassian.com/ko/

      Điều chúng tôi nhận thấy

      word-break: break-all, break-word, keep-all, normal, unset

      Cách khắc phục

      Use word-break: keep-all for Korean text instead of break-all.

  • Localized images and assets

    Fail50trực quan

    Language-specific images and alt text should match the page locale.

    • infovisual · 90% độ tin cậy

      Localized assets and image alt text are not evidenced

      The truncated page extracts contain no image markup, asset references, or alt attributes, so image localization cannot be assessed.

      Điều chúng tôi nhận thấy

      The preview includes buttons, headings, and text fields but no "<img>" fragment, asset URL, or "alt" attribute.

      Cách khắc phục

      Audit image assets and their alt text on every locale, replacing embedded source-language text where necessary.

  • Text overflow

    Fail74trực quan

    Text should not clip, truncate unexpectedly, or overflow buttons and navigation.

    • mediumvisual · 62% độ tin cậy

      Long localized labels may require overflow testing

      The evidence includes comparatively long navigation labels, but provides no viewport measurements or screenshots to confirm whether text clips or overflows.

      Tìm thấy tại đây

      Header navigation · <nav>

      https://www.atlassian.com/fr/

      Điều chúng tôi nhận thấy

      French labels include "Professionnels de l'informatique" and "Équipes de direction"; Japanese includes "IT プロフェッショナル" and "ビジネス・チーム".

      Cách khắc phục

      Test long labels at narrow widths and allow wrapping, flexible button widths, or a collapsed navigation pattern instead of clipping.

  • Responsive localisation

    Fail74trực quan

    Localized layouts should hold up across mobile, tablet, and desktop widths.

    • mediumvisual · 58% độ tin cậy

      Responsive behavior is unverified

      The evidence confirms locale-specific pages but contains no mobile, tablet, or desktop screenshots and no viewport-specific markup or measurements.

      Điều chúng tôi nhận thấy

      The supplied preview lists page URLs and extracted text only; it contains no viewport dimensions or responsive layout results.

      Cách khắc phục

      Perform responsive checks for every supported locale, prioritizing long labels such as "Professionnels de l'informatique" and translated header navigation.

Worth a look (11)

  • Translation accuracy

    Watch88linguistic

    Target copy should preserve the source meaning, numbers, and product actions.

    • infolinguistic · 78% độ tin cậy

      Core navigation and product descriptions preserve meaning

      The Japanese and French extracts correspond to the English navigation and product sections while retaining product names such as Jira and Confluence.

      Tìm thấy tại đây

      Primary navigation and featured apps · <nav>, <h2>

      https://www.atlassian.com/fr/

      Điều chúng tôi nhận thấy

      English: "Featured apps" and "Flexible project management"; Japanese: "おすすめのアプリ" and "柔軟なプロジェクト管理"; French: "Apps recommandées" and "Gestion de projet flexible"

  • Fluency

    Watch88linguistic

    Copy should sound natural, without grammar issues or machine-translation artifacts.

    • infolinguistic · 78% độ tin cậy

      Sampled localized copy reads naturally

      The provided Japanese and French navigation and product labels appear coherent and idiomatic, with no explicit machine-translation artifacts in the sample.

      Tìm thấy tại đây

      Navigation and featured apps · <nav>, <section>

      https://www.atlassian.com/ja/

      Điều chúng tôi nhận thấy

      French: "Apps recommandées", "Collections Atlassian", and "Par cas d’usage"; Japanese: "おすすめのアプリ", "ユース ケース別", and "チーム別"

  • Brand voice

    Watch84linguistic

    Localized copy should preserve the intended tone of the source.

    • infolinguistic · 76% độ tin cậy

      Product-led, concise tone is retained

      Localized labels preserve the concise, professional tone of the English source while keeping the Atlassian product naming intact.

      Tìm thấy tại đây

      Featured apps and collections · <section>

      https://www.atlassian.com/fr/

      Điều chúng tôi nhận thấy

      English: "Knowledge, all in one place"; Japanese: "すべての知識を 1 か所に"; French: "Les connaissances réunies au même endroit"

  • Grammar and style

    Watch86linguistic

    Locale-specific capitalization, punctuation, formality, and agreement should be correct.

    • infolinguistic · 76% độ tin cậy

      Sampled locale grammar and capitalization are consistent

      The extracted French and Japanese headings and navigation labels follow coherent locale-specific conventions in the sampled content.

      Tìm thấy tại đây

      Navigation and headings · <nav>, <h2>

      https://www.atlassian.com/fr/

      Điều chúng tôi nhận thấy

      French: "Responsables produit", "Professionnels de l'informatique", and "Équipes métier"; Japanese: "プロダクト マネージャー" and "ビジネス・チーム"

  • UI context

    Watch88contextual

    Translations should fit the UI component: button, nav, form, modal, or error.

    • infocontextual · 80% độ tin cậy

      Navigation and heading translations fit their UI roles

      The evidence distinguishes localized buttons from headings and shows role-appropriate short labels in multiple locales.

      Tìm thấy tại đây

      Header and page sections · <button>, <h2>

      https://www.atlassian.com/

      Điều chúng tôi nhận thấy

      Buttons include "Sign in", "サインイン", "Connexion", and "Einloggen"; headings include "Featured apps", "おすすめのアプリ", and "Apps recommandées"

  • Product context

    Watch88contextual

    Language should match product concepts such as plans, settings, and workflows.

    • infocontextual · 80% độ tin cậy

      Product terminology remains recognizable and contextualized

      Product names remain unchanged while surrounding descriptions are translated for the locale.

      Tìm thấy tại đây

      Featured apps and collections · <section>

      https://www.atlassian.com/ja/

      Điều chúng tôi nhận thấy

      The extracts retain "Jira", "Confluence", "Jira Service Management", "Atlassian Collections", and "Focus Talent Align" alongside localized descriptions.

      Cách khắc phục

      Maintain an approved glossary for product names and product-specific concepts across all locales.

  • Contextual meaning

    Watch86contextual

    Strings should be judged in surrounding page and component context, not in isolation.

    • infocontextual · 78% độ tin cậy

      Strings are supported by surrounding page context

      The samples provide consistent relationships between navigation labels, section headings, product names, and descriptions across locales.

      Tìm thấy tại đây

      Page navigation and featured apps · <nav>, <section>

      https://www.atlassian.com/ja/

      Điều chúng tôi nhận thấy

      English groups "Featured apps", "Atlassian Collections", "By Use Case", and "By Team"; Japanese groups "おすすめのアプリ", "Atlassian Collections", "ユース ケース別", and "チーム別".

  • Audience context

    Watch88contextual

    Language should fit the intended audience, such as consumer, enterprise, or developer.

    • infocontextual · 82% độ tin cậy

      Professional audience segments are localized

      Audience-oriented navigation labels for developers, product managers, IT professionals, business teams, and leadership teams are represented in localized samples.

      Tìm thấy tại đây

      Primary navigation · <nav>

      https://www.atlassian.com/fr/

      Điều chúng tôi nhận thấy

      English: "Developers", "Product Managers", "IT professionals", and "Business Teams"; French: "Développeurs", "Responsables produit", "Professionnels de l'informatique", and "Équipes métier"

  • Visual hierarchy

    Watch76trực quan

    Localization should not make headings or CTAs lose scanability.

    • lowvisual · 80% độ tin cậy

      Heading is excessively long

      A localized heading may crowd the visual hierarchy.

      Tìm thấy tại đây

      Page body · heading

      https://www.atlassian.com/pl/

      Điều chúng tôi nhận thấy

      Ponad 350 000 zespołów nie do zatrzymania wykorzystuje potencjał sztucznej inteligencji

      Cách khắc phục

      Shorten the heading so it does not crowd the visual hierarchy.

  • Component consistency

    Watch78trực quan

    Repeated components should stay visually consistent across locales.

    • infovisual · 68% độ tin cậy

      Repeated text components appear structurally consistent

      The same button and heading categories are present across the English, Japanese, French, and German extracts, but screenshots or computed styles are not provided.

      Tìm thấy tại đây

      Header and section components · <button>, <h2>

      https://www.atlassian.com/

      Điều chúng tôi nhận thấy

      Each sample exposes localized button arrays and corresponding headings, including "Sign in"/"サインイン"/"Connexion"/"Einloggen" and translated featured-app headings.

      Cách khắc phục

      Run visual regression tests across locales to confirm spacing, typography, and component dimensions remain consistent.

  • Layout breakage

    Watch76trực quan

    Localized pages should not overlap, break grids, or overflow modals.

    • infovisual · 60% độ tin cậy

      No layout failure is visible in the supplied markup extract

      The page extracts show matching navigation and section structures across locales, but markup-only evidence cannot establish whether grids or overlays break visually.

      Tìm thấy tại đây

      Page shell and featured sections · <header>, <section>

      https://www.atlassian.com/

      Điều chúng tôi nhận thấy

      The samples expose the same broad page structure: navigation, featured apps, Atlassian Collections, use-case, and team sections across English, Japanese, and French.

      Cách khắc phục

      Capture localized screenshots and test grids, menus, and dialogs at representative desktop and mobile widths.

Các kiểm tra đã đạt (4)

Không áp dụng (4)

Other findings

Findings not listed under a criterion above.

  • infocontextual · 84% độ tin cậy

    Sign-in action is clearly localized

    The sampled sign-in control communicates the same authentication action across English, Japanese, French, and German.

    Tìm thấy tại đây

    Header · <button>

    https://www.atlassian.com/

    Điều chúng tôi nhận thấy

    English: "Sign in"; Japanese: "サインイン"; French: "Connexion"; German: "Einloggen"

Các ngôn ngữ được phát hiện

  • Tiếng Breton

    br · page language

  • Tiếng Đức

    de · hreflang

  • Tiếng Anh

    en · page language

  • Tiếng Tây Ban Nha

    es · hreflang

  • Tiếng Pháp

    fr · hreflang

  • Tiếng Italy

    it · hreflang

  • Tiếng Nhật

    ja · hreflang

  • Tiếng Hàn

    ko · hreflang

  • Tiếng Hà Lan

    nl · hreflang

  • Tiếng Ba Lan

    pl · hreflang

  • Tiếng Bồ Đào Nha (Brazil)

    pt-br · hreflang

  • Tiếng Nga

    ru · hreflang

  • Tiếng Trung

    zh · page language

Các trang được lấy mẫu

Bước tiếp theo

Solid baseline with room to improve. Claim this domain to monitor locales as you ship, or book an audit review.

Đặt lịch xem xét kiểm tra

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.