Localisation audit for linkedin.com

Localisation report

Professional networking

linkedin.com

Product: LinkedIn is a professional networking platform where members manage their professional identity, build networks, access insights, explore career opportunities, and post jobs.

Brand voice: Professional, opportunity-focused, informative

Localisation score

68/100

Needs improvement

Users may encounter noticeable localisation problems.

81Technical Audit
60Linguistic Audit
55Contextual Audit
77Visual Audit

Audited: Aug 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 23 public audits

Ahead of 7 other public auditsPublic average: 70/100

See the full leaderboard

Fix first

1
high
Valid sitemap not found
No fetchable XML sitemap with URL entries was found at /sitemap.xml or via robots.txt.
See details
2
medium
Missing hreflang self-reference
The page lists hreflang alternates but does not include itself.
See details
3
medium
Current-page retention is unverified
The evidence shows a broad locale list and language buttons, but does not show locale links or confirm that switching preserves the current page path.
See details

Audit criteria

5 passed · 5 to watch · 9 to fix · 16 not applicable

Needs attention (9)

Language switcher
Fail70technical
Visitors should move between locales without losing the current page.
- mediumtechnical · 78% confidence
  Current-page retention is unverified
  The evidence shows a broad locale list and language buttons, but does not show locale links or confirm that switching preserves the current page path.
  Found here
  Header · <button>
  https://www.linkedin.com/
  What we saw
  "locales":["ar","cs-cz","da-dk","de-at","de-ch","de-de","en-au","en-ca","en-gb","en-gh","en-hk","en-ie","en-il","en-in","en-jm","en-ke","en-ng","en-nz","en-ph","en-pk","en-sg","en-tt","en-us","en-za","en-zw","es-ar","es-bo","es-cl","es-co","es-cr","es-do","es-ec","es-es","es-gt",…
  How to fix it
  Verify that each locale option links to the equivalent current path, not only to a locale homepage. Test switching from a non-homepage URL and confirm the path is retained.
Sitemap
Fail18technical
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.
- hightechnical · 100% confidence
  Valid sitemap not found
  No fetchable XML sitemap with URL entries was found at /sitemap.xml or via robots.txt.
  Found here
  Sitemap · sitemap.xml
  What we saw
  robots.txt was found, but it does not reference a sitemap and /sitemap.xml was missing or empty
  How to fix it
  Publish a valid XML sitemap and reference it from robots.txt with an absolute Sitemap: URL.
Terminology consistency
Fail50linguistic
Important concepts should not be translated differently across pages.
- infolinguistic · 92% confidence
  Cross-locale terminology cannot be verified
  The supplied page records are English only, so consistency of important terms across translated pages is not assessable.
  Found here
  Page content · <body>
  https://www.linkedin.com/
  What we saw
  The supplied records show "htmlLang":"en" and English copy such as "Welcome to your professional community" and "Sign in"; no translated page text is provided.
  How to fix it
  Compare the same product concepts across the available locale pages and maintain a shared terminology glossary.
Translation accuracy
Fail50linguistic
Target copy should preserve the source meaning, numbers, and product actions.
- infolinguistic · 92% confidence
  Target-language accuracy cannot be verified
  The evidence contains only English source copy and no translated target-language content, numbers, or product-action comparisons.
  Found here
  Main content · <body>
  https://www.linkedin.com/
  What we saw
  "htmlLang":"en" and "text":"Skip to main content Agree & Join LinkedIn ... Welcome to your professional community Continue with "
  How to fix it
  Provide source-and-target comparisons for each locale, including consent text and all product actions, and review them against the source meaning.
Fluency
Fail50linguistic
Copy should sound natural, without grammar issues or machine-translation artifacts.
- infolinguistic · 92% confidence
  Localized fluency cannot be verified
  No non-English copy is included in the evidence, so naturalness and possible machine-translation artifacts cannot be assessed.
  Found here
  Main content · <body>
  https://www.linkedin.com/
  What we saw
  The recorded page has "htmlLang":"en" and English headings including "Explore top LinkedIn content" and "Find the right job or internship for you".
  How to fix it
  Review representative copy in every target locale with native-language reviewers, including headings, buttons, and legal text.
Brand voice
Fail55linguistic
Localized copy should preserve the intended tone of the source.
- infolinguistic · 90% confidence
  Localized brand voice is unverified
  The English source appears professional and welcoming, but no localized copy is supplied to determine whether that tone is preserved.
  Found here
  Hero · <h1>
  https://www.linkedin.com/
  What we saw
  "Welcome to your professional community" and "Find the right job or internship for you"
  How to fix it
  Compare localized headings and calls to action with the source tone, preserving LinkedIn’s professional and welcoming voice.
Grammar and style
Fail55linguistic
Locale-specific capitalization, punctuation, formality, and agreement should be correct.
- infolinguistic · 90% confidence
  Locale-specific grammar and style are unverified
  The evidence exposes English content only and does not provide target-locale punctuation, capitalization, formality, or agreement for review.
  Found here
  Main content · <body>
  https://www.linkedin.com/
  What we saw
  "htmlLang":"en" and "text":"Skip to main content Agree & Join LinkedIn ... Sign in Join now"
  How to fix it
  Run locale-specific proofreading for capitalization, punctuation, formality, and grammatical agreement across the translated interface.
CTA intent
Fail55contextual
Localized calls to action should communicate the intended product action.
- infocontextual · 90% confidence
  Localized CTA intent is unverified
  The English actions are visible, but no translated CTA labels are provided to confirm that the intended sign-in and registration actions remain clear.
  Found here
  Header · <button>
  https://www.linkedin.com/
  What we saw
  "text":"... Sign in Join now Welcome to your professional community Continue with "
  How to fix it
  Check each locale’s labels for sign-in, joining, and continuation actions against the intended product flows.
Visual hierarchy
Fail70visual
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 2 sampled pages.
  Found here
  Page body · heading
  https://www.linkedin.com/learning/search?trk=guest_homepage-basic_guest_nav_menu_learning
  What we saw
  Upcoming Live Event, Aug 25: How to Turn AI Skeptics into Adoption Champions with Angie Jones
  How to fix it
  Shorten the heading so it does not crowd the visual hierarchy.

Worth a look (5)

Structured data
Watch84technical
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.linkedin.com/top-content/career/
  What we saw
  CollectionPage is present but inLanguage is missing
  How to fix it
  Set JSON-LD inLanguage to match each page locale.
Localized images and assets
Watch88visual
Language-specific images and alt text should match the page locale.
Text overflow
Watch75visual
Text should not clip, truncate unexpectedly, or overflow buttons and navigation.
- infovisual · 60% confidence
  Text overflow cannot be determined from the evidence
  The supplied DOM/text preview contains no screenshots, computed dimensions, or clipping indicators, so overflow across locales is only an informed estimate.
  Found here
  Header · <button>
  https://www.linkedin.com/
  What we saw
  "buttons":["Show more","Show less","Choose a topic to learn about","العربية (Arabic)","বাংলা (Bangla)","Čeština (Czech)"]
  How to fix it
  Test long translated labels at supported widths and allow wrapping, resizing, or truncation only where it is intentional and accessible.
Layout breakage
Watch75visual
Localized pages should not overlap, break grids, or overflow modals.
- infovisual · 60% confidence
  Layout integrity cannot be determined from the evidence
  No screenshots, layout measurements, or CSS/rendering output are provided, so overlap, broken grids, and modal overflow cannot be confirmed.
  Found here
  Page layout · <body>
  https://www.linkedin.com/
  What we saw
  The evidence provides page status, language metadata, buttons, headings, and text, but no visual rendering or layout measurements.
  How to fix it
  Inspect representative locales at desktop and narrow widths for overlap, grid failures, and overflow in menus and dialogs.
Responsive localisation
Watch75visual
Localized layouts should hold up across mobile, tablet, and desktop widths.
- infovisual · 60% confidence
  Responsive localization cannot be determined from the evidence
  The page records do not include viewport-specific screenshots or measurements, so mobile, tablet, and desktop behavior remains unverified.
  Found here
  Page layout · <body>
  https://www.linkedin.com/
  What we saw
  The supplied records include "status":200, "htmlLang":"en", headings, and text, but no viewport or responsive-rendering evidence.
  How to fix it
  Test localized pages at mobile, tablet, and desktop breakpoints, especially locales with longer labels and right-to-left text.

Passed audits (5)

Not applicable (16)

Other findings

Findings not listed under a criterion above.

mediumtechnical · 95% confidence
Missing hreflang self-reference
The page lists hreflang alternates but does not include itself.
Found here
Document head · <link rel="alternate" hreflang>
https://www.linkedin.com/?trk=guest_homepage-basic_nav-header-logo
What we saw
<link rel="alternate" hreflang="de" href="https://de.linkedin.com/"> <link rel="alternate" hreflang="en-IE" href="https://ie.linkedin.com/"> <link rel="alternate" hreflang="uk-UA" href="https://ua.linkedin.com/"> <link rel="alternate" hreflang="en-US" href="https://www.linkedin.c…
How to fix it
Add a self-referencing hreflang alternate for this page.

Detected locales

Arabic
ar · hreflang
Czech (Czechia)
cs-cz · hreflang
Danish (Denmark)
da-dk · hreflang
Austrian German
de-at · hreflang
Swiss High German
de-ch · hreflang
German (Germany)
de-de · hreflang
Australian English
en-au · hreflang
Canadian English
en-ca · hreflang
British English
en-gb · hreflang
English (Ghana)
en-gh · hreflang
English (Hong Kong SAR China)
en-hk · hreflang
English (Ireland)
en-ie · hreflang
English (Israel)
en-il · hreflang
English (India)
en-in · hreflang
English (Jamaica)
en-jm · hreflang
English (Kenya)
en-ke · hreflang
English (Nigeria)
en-ng · hreflang
English (New Zealand)
en-nz · hreflang
English (Philippines)
en-ph · hreflang
English (Pakistan)
en-pk · hreflang
English (Singapore)
en-sg · hreflang
English (Trinidad & Tobago)
en-tt · hreflang
American English
en-us · hreflang
English (South Africa)
en-za · hreflang
English (Zimbabwe)
en-zw · hreflang
Spanish (Argentina)
es-ar · hreflang
Spanish (Bolivia)
es-bo · hreflang
Spanish (Chile)
es-cl · hreflang
Spanish (Colombia)
es-co · hreflang
Spanish (Costa Rica)
es-cr · hreflang
Spanish (Dominican Republic)
es-do · hreflang
Spanish (Ecuador)
es-ec · hreflang
European Spanish
es-es · hreflang
Spanish (Guatemala)
es-gt · hreflang
Mexican Spanish
es-mx · hreflang
Spanish (Panama)
es-pa · hreflang
Spanish (Peru)
es-pe · hreflang
Spanish (Puerto Rico)
es-pr · hreflang
Spanish (El Salvador)
es-sv · hreflang
Spanish (Uruguay)
es-uy · hreflang
Spanish (Venezuela)
es-ve · hreflang
French (France)
fr-fr · hreflang
French (Luxembourg)
fr-lu · hreflang
Indonesian
id · hreflang
Italian
it · hreflang
Japanese (Japan)
ja-jp · hreflang
Korean
ko · hreflang
Malay (Malaysia)
ms-my · hreflang
Dutch
nl · hreflang
Norwegian
no · hreflang
Polish
pl · hreflang
Brazilian Portuguese
pt-br · hreflang
European Portuguese
pt-pt · hreflang
Romanian
ro · hreflang
Russian
ru · hreflang
Swedish (Sweden)
sv-se · hreflang
Thai
th · hreflang
Filipino
tl · hreflang
Turkish
tr · hreflang
Ukrainian (Ukraine)
uk-ua · hreflang
Vietnamese (Vietnam)
vi-vn · hreflang
Chinese (China)
zh-cn · hreflang
Chinese (Taiwan)
zh-tw · hreflang

Pages sampled

Next step

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

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.