Ulat sa Lokalisasyon
Atlassian
Team collaboration softwareatlassian.com
Produkto: 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.
Tinig ng brand: Collaborative, confident, productivity-focused
Iskor sa lokalisasyon
69/100
Kailangan ng pagpapabutiMaaaring makaranas ang mga user ng kapansin-pansing mga problema sa lokalisasyon.
- 63Teknikal na Audit
- 64Pagsusuring Pangwika
- 83Kontekstuwal na Pagsusuri
- 65Biswal na Pagsusuri
Nagsample ng 15 pahina sa mga teknikal, lingguwistiko, kontekstuwal, at biswal na credit ng lokalisasyon. Paano namin binibigyan ng marka ang mga audit sa lokalisasyon
Paano ka ikinukumpara
Ika-#15 sa 23 pampublikong audit
Unahin ang pag-aayos
- 1high
Untranslated call to action
A fr page still uses source-language CTA copy. Affects 7 sampled pages.
See details - 2high
Page script does not match the locale
A zh page is dominated by Latin-script copy. Affects 2 sampled pages.
See details - 3high
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
Pamantayan sa pag-audit
4 passed · 11 to watch · 16 to fix · 4 not applicable
Nangangailangan ng pansin (16)
Language switcher
Nabigo65teknikalVisitors should move between locales without losing the current page.
- mediumtechnical · 82% kumpiyansa
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.
Natagpuan dito
Ang nakita namin
"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/"
Paano ito ayusin
Add an explicit language selector to the shared header or footer. Make each locale option link to the equivalent current page where available.
hreflang
Nabigo20teknikalLocalized versions should be linked with valid, reciprocal hreflang including self and x-default.
- mediumtechnical · 95% kumpiyansa
Missing hreflang self-reference
The page lists hreflang alternates but does not include itself.
Natagpuan dito
Document head · <link rel="alternate" hreflang>
https://www.atlassian.com/Ang nakita namin
<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…
Paano ito ayusin
Add a self-referencing hreflang alternate for this page.
- lowtechnical · 95% kumpiyansa
Missing x-default hreflang
hreflang is present but does not declare an x-default fallback. Affects 12 sampled pages.
Natagpuan dito
Document head · <link rel="alternate" hreflang>
https://www.atlassian.com/Ang nakita namin
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/
Paano ito ayusin
Add an x-default hreflang fallback for users whose locale is not listed.
Localized SEO metadata
Nabigo65teknikalTitles, descriptions, and og:locale should be localized per locale.
- mediumtechnical · 95% kumpiyansa
Page titles are not localized
Sampled locales share the same document title.
Natagpuan dito
Document head · <title>
https://www.atlassian.com/Ang nakita namin
<title>Filter Icon</title> is reused across sampled locales
Paano ito ayusin
Localize the document title for each page locale.
Sitemap
Nabigo60teknikalLike 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% kumpiyansa
Sitemap is missing localized URLs
A sitemap was found, but sampled entries do not include locale-prefixed URLs.
Natagpuan dito
Sitemap · sitemap.xml
https://www.atlassian.com/blog/post-sitemap.xmlAng nakita namin
Sitemap https://www.atlassian.com/blog/post-sitemap.xml has no locale-prefixed URLs in the sample
Paano ito ayusin
Include localized URLs in the sitemap for every published locale.
Structured data
Nabigo0teknikalJSON-LD inLanguage should match the page locale when structured data is present.
- lowtechnical · 95% kumpiyansa
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
Natagpuan dito
JSON-LD · <script type="application/ld+json">
https://www.atlassian.com/Ang nakita namin
Organization is present but inLanguage is missing
Paano ito ayusin
Set JSON-LD inLanguage to match each page locale.
International formatting
Nabigo50teknikalDates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.
- infotechnical · 90% kumpiyansa
Formatting coverage cannot be verified
The supplied page extracts contain no dates, numbers, currencies, addresses, or calendar examples to assess against locale conventions.
Ang nakita namin
The provided page text includes navigation and product descriptions such as "Featured apps" and "Flexible project management", but no dates, numbers, or currency values.
Paano ito ayusin
Audit localized pages containing prices, dates, quantities, and addresses with locale-aware formatting rules.
Accessibility localisation
Nabigo72teknikallang, aria-label, and alt text should match the page locale.
- infotechnical · 88% kumpiyansa
Document language is localized
The English, Japanese, and French page samples explicitly declare matching htmlLang values.
Natagpuan dito
Document root · <html>
https://www.atlassian.com/Ang nakita namin
"htmlLang":"en" for "https://www.atlassian.com/", "htmlLang":"ja" for "https://www.atlassian.com/ja/", and "htmlLang":"fr" for "https://www.atlassian.com/fr/"
Paano ito ayusin
Keep the html lang value synchronized with the rendered locale on every localized route.
- mediumtechnical · 88% kumpiyansa
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.
Ang nakita namin
The preview lists buttons, headings, and text, but contains no "aria-label" or "alt" markup.
Paano ito ayusin
Review all accessible names and image alt attributes for untranslated or hard-coded source-language strings.
Translation completeness
Nabigo0pangwikaLocalized pages should not leave source-language copy in place, except brand names and URLs.
- highlinguistic · 92% kumpiyansa
Untranslated call to action
A fr page still uses source-language CTA copy. Affects 7 sampled pages.
Natagpuan dito
Pricing hero · <button>
https://www.atlassian.com/fr/Ang nakita namin
Primary CTA: "Solutions" Seen on 7 pages, e.g. https://www.atlassian.com/fr/, https://www.atlassian.com/de/, https://www.atlassian.com/es/
Paano ito ayusin
Translate leftover source-language CTAs to match the surrounding locale copy.
- highlinguistic · 95% kumpiyansa
Page script does not match the locale
A zh page is dominated by Latin-script copy. Affects 2 sampled pages.
Natagpuan dito
Page body · sampled copy
https://www.atlassian.com/zh/Ang nakita namin
___ 跳至内容 产品 精选 开发人员 产品经理 IT 专业人员 业务团队 领导团队 查看所有应用 精选应用 Jira 灵活的项目管理 Confluence 知识，全部集中在一处 Jira Service Management 高速交付服务 Atlassian 集合 无缝地增强团队合作 Jira Confluence Loom 自信地优化策略与成果 Focus Talent Align 高速交付服务 Jira Service Management Customer Service Management Assets 快速交付优质的软件 Rovo Dev…
Paano ito ayusin
Write this zh page in the expected script instead of leftover Latin-script copy.
Terminology consistency
Nabigo40pangwikaImportant concepts should not be translated differently across pages.
- mediumlinguistic · 95% kumpiyansa
Terminology inconsistency
"Manage preferences" appears both untranslated and translated across ja pages. Affects 26 sampled pages.
Natagpuan dito
Header · <nav> or <button>
https://www.atlassian.com/ja/Ang nakita namin
"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/
Paano ito ayusin
Use one translated label for "Manage preferences" across ja pages.
Cultural adaptation
Nabigo55KontekstuwalCurrency, dates, addresses, and local examples should fit the market.
- infocontextual · 88% kumpiyansa
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.
Ang nakita namin
The samples show product and audience labels such as "Atlassian Collections", "By Use Case", and "By Team", with no local market data or examples.
Paano ito ayusin
Review pricing, date, address, legal, and example content separately for each target market.
Text expansion
Nabigo40biswalLonger translations should not create obvious length pressure versus the source UI.
- mediumvisual · 88% kumpiyansa
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.
Natagpuan dito
Control · <button>
https://www.atlassian.com/fr/Ang nakita namin
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/
Paano ito ayusin
Shorten the translation or give the control more room so the longer copy does not overflow.
Font and script support
Nabigo48biswalTypography should support the target script without generic fallback-only stacks, tofu glyphs, or missing CJK fonts.
- highvisual · 95% kumpiyansa
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.
Natagpuan dito
Page body · font-family
https://www.atlassian.com/ja/Ang nakita namin
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…
Paano ito ayusin
Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
CJK typography
Nabigo72biswalKorean pages should avoid word-break: break-all and prefer word-break: keep-all; CJK forms should use local name-field conventions.
- highvisual · 94% kumpiyansa
Korean text uses word-break: break-all
break-all can split Hangul mid-word and makes Korean body copy harder to read.
Natagpuan dito
CSS · word-break
https://www.atlassian.com/ko/Ang nakita namin
word-break: break-all, break-word, keep-all, normal, unset
Paano ito ayusin
Use word-break: keep-all for Korean text instead of break-all.
Localized images and assets
Nabigo50biswalLanguage-specific images and alt text should match the page locale.
- infovisual · 90% kumpiyansa
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.
Ang nakita namin
The preview includes buttons, headings, and text fields but no "<img>" fragment, asset URL, or "alt" attribute.
Paano ito ayusin
Audit image assets and their alt text on every locale, replacing embedded source-language text where necessary.
Text overflow
Nabigo74biswalText should not clip, truncate unexpectedly, or overflow buttons and navigation.
- mediumvisual · 62% kumpiyansa
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.
Natagpuan dito
Header navigation · <nav>
https://www.atlassian.com/fr/Ang nakita namin
French labels include "Professionnels de l'informatique" and "Équipes de direction"; Japanese includes "IT プロフェッショナル" and "ビジネス・チーム".
Paano ito ayusin
Test long labels at narrow widths and allow wrapping, flexible button widths, or a collapsed navigation pattern instead of clipping.
Responsive localisation
Nabigo74biswalLocalized layouts should hold up across mobile, tablet, and desktop widths.
- mediumvisual · 58% kumpiyansa
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.
Ang nakita namin
The supplied preview lists page URLs and extracted text only; it contains no viewport dimensions or responsive layout results.
Paano ito ayusin
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
Watch88pangwikaTarget copy should preserve the source meaning, numbers, and product actions.
- infolinguistic · 78% kumpiyansa
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.
Natagpuan dito
Primary navigation and featured apps · <nav>, <h2>
https://www.atlassian.com/fr/Ang nakita namin
English: "Featured apps" and "Flexible project management"; Japanese: "おすすめのアプリ" and "柔軟なプロジェクト管理"; French: "Apps recommandées" and "Gestion de projet flexible"
Fluency
Watch88pangwikaCopy should sound natural, without grammar issues or machine-translation artifacts.
- infolinguistic · 78% kumpiyansa
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.
Natagpuan dito
Navigation and featured apps · <nav>, <section>
https://www.atlassian.com/ja/Ang nakita namin
French: "Apps recommandées", "Collections Atlassian", and "Par cas d’usage"; Japanese: "おすすめのアプリ", "ユース ケース別", and "チーム別"
Brand voice
Watch84pangwikaLocalized copy should preserve the intended tone of the source.
- infolinguistic · 76% kumpiyansa
Product-led, concise tone is retained
Localized labels preserve the concise, professional tone of the English source while keeping the Atlassian product naming intact.
Natagpuan dito
Featured apps and collections · <section>
https://www.atlassian.com/fr/Ang nakita namin
English: "Knowledge, all in one place"; Japanese: "すべての知識を 1 か所に"; French: "Les connaissances réunies au même endroit"
Grammar and style
Watch86pangwikaLocale-specific capitalization, punctuation, formality, and agreement should be correct.
- infolinguistic · 76% kumpiyansa
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.
Natagpuan dito
Navigation and headings · <nav>, <h2>
https://www.atlassian.com/fr/Ang nakita namin
French: "Responsables produit", "Professionnels de l'informatique", and "Équipes métier"; Japanese: "プロダクト マネージャー" and "ビジネス・チーム"
UI context
Watch88KontekstuwalTranslations should fit the UI component: button, nav, form, modal, or error.
- infocontextual · 80% kumpiyansa
Navigation and heading translations fit their UI roles
The evidence distinguishes localized buttons from headings and shows role-appropriate short labels in multiple locales.
Natagpuan dito
Header and page sections · <button>, <h2>
https://www.atlassian.com/Ang nakita namin
Buttons include "Sign in", "サインイン", "Connexion", and "Einloggen"; headings include "Featured apps", "おすすめのアプリ", and "Apps recommandées"
Product context
Watch88KontekstuwalLanguage should match product concepts such as plans, settings, and workflows.
- infocontextual · 80% kumpiyansa
Product terminology remains recognizable and contextualized
Product names remain unchanged while surrounding descriptions are translated for the locale.
Natagpuan dito
Featured apps and collections · <section>
https://www.atlassian.com/ja/Ang nakita namin
The extracts retain "Jira", "Confluence", "Jira Service Management", "Atlassian Collections", and "Focus Talent Align" alongside localized descriptions.
Paano ito ayusin
Maintain an approved glossary for product names and product-specific concepts across all locales.
Contextual meaning
Watch86KontekstuwalStrings should be judged in surrounding page and component context, not in isolation.
- infocontextual · 78% kumpiyansa
Strings are supported by surrounding page context
The samples provide consistent relationships between navigation labels, section headings, product names, and descriptions across locales.
Natagpuan dito
Page navigation and featured apps · <nav>, <section>
https://www.atlassian.com/ja/Ang nakita namin
English groups "Featured apps", "Atlassian Collections", "By Use Case", and "By Team"; Japanese groups "おすすめのアプリ", "Atlassian Collections", "ユース ケース別", and "チーム別".
Audience context
Watch88KontekstuwalLanguage should fit the intended audience, such as consumer, enterprise, or developer.
- infocontextual · 82% kumpiyansa
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.
Natagpuan dito
Primary navigation · <nav>
https://www.atlassian.com/fr/Ang nakita namin
English: "Developers", "Product Managers", "IT professionals", and "Business Teams"; French: "Développeurs", "Responsables produit", "Professionnels de l'informatique", and "Équipes métier"
Visual hierarchy
Watch76biswalLocalization should not make headings or CTAs lose scanability.
- lowvisual · 80% kumpiyansa
Heading is excessively long
A localized heading may crowd the visual hierarchy.
Natagpuan dito
Page body · heading
https://www.atlassian.com/pl/Ang nakita namin
Ponad 350 000 zespołów nie do zatrzymania wykorzystuje potencjał sztucznej inteligencji
Paano ito ayusin
Shorten the heading so it does not crowd the visual hierarchy.
Component consistency
Watch78biswalRepeated components should stay visually consistent across locales.
- infovisual · 68% kumpiyansa
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.
Natagpuan dito
Header and section components · <button>, <h2>
https://www.atlassian.com/Ang nakita namin
Each sample exposes localized button arrays and corresponding headings, including "Sign in"/"サインイン"/"Connexion"/"Einloggen" and translated featured-app headings.
Paano ito ayusin
Run visual regression tests across locales to confirm spacing, typography, and component dimensions remain consistent.
Layout breakage
Watch76biswalLocalized pages should not overlap, break grids, or overflow modals.
- infovisual · 60% kumpiyansa
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.
Natagpuan dito
Page shell and featured sections · <header>, <section>
https://www.atlassian.com/Ang nakita namin
The samples expose the same broad page structure: navigation, featured apps, Atlassian Collections, use-case, and team sections across English, Japanese, and French.
Paano ito ayusin
Capture localized screenshots and test grids, menus, and dialogs at representative desktop and mobile widths.
Mga audit na pumasa (4)
Hindi naaangkop (4)
Other findings
Findings not listed under a criterion above.
- infocontextual · 84% kumpiyansa
Sign-in action is clearly localized
The sampled sign-in control communicates the same authentication action across English, Japanese, French, and German.
Natagpuan dito
Header · <button>
https://www.atlassian.com/Ang nakita namin
English: "Sign in"; Japanese: "サインイン"; French: "Connexion"; German: "Einloggen"
Mga natukoy na locale
Breton
br · page language
German
de · hreflang
Ingles
en · page language
Spanish
es · hreflang
French
fr · hreflang
Italian
it · hreflang
Japanese
ja · hreflang
Korean
ko · hreflang
Dutch
nl · hreflang
Polish
pl · hreflang
Portuguese (Brazil)
pt-br · hreflang
Russian
ru · hreflang
Chinese
zh · page language
Mga pahinang sinuri sa sampol
Susunod na hakbang
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.