Rapport de localisation
linkedin.com
Produit: LinkedIn is a professional networking platform where members manage their professional identity, build networks, access insights, explore career opportunities, and post jobs.
Voix de marque: Professional, opportunity-focused, informative
Score de localisation
68/100
À améliorerLes utilisateurs peuvent rencontrer des problèmes de localisation perceptibles.
- 81Audit technique
- 60Audit linguistique
- 55Audit contextuel
- 77Audit visuel
15 pages échantillonnées parmi les crédits de localisation techniques, linguistiques, contextuels et visuels. Comment nous évaluons les audits de localisation
Comment vous vous comparez
Rang #14 sur 22 audits publics
À corriger en priorité
- hightechnical · 100 % de confiance
Valid sitemap not found
No fetchable XML sitemap with URL entries was found at /sitemap.xml or via robots.txt.
Trouvé ici
Sitemap · sitemap.xml
Ce que nous avons constaté
robots.txt was found, but it does not reference a sitemap and /sitemap.xml was missing or empty
Comment le corriger
Publish a valid XML sitemap and reference it from robots.txt with an absolute Sitemap: URL.
- mediumtechnical · 95 % de confiance
Missing hreflang self-reference
The page lists hreflang alternates but does not include itself.
Trouvé ici
Document head · <link rel="alternate" hreflang>
https://www.linkedin.com/?trk=guest_homepage-basic_nav-header-logoCe que nous avons constaté
<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.com/">
Comment le corriger
Add a self-referencing hreflang alternate for this page.
- mediumtechnical · 78 % de confiance
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.
Trouvé ici
Header · <button>
https://www.linkedin.com/Ce que nous avons constaté
"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","es-mx","es-pa","es-pe","es-pr","es-sv","es-uy","es-ve","fr-fr","fr-lu","id","it","ja-jp","ko","ms-my","nl","no","pl","pt-br","pt-pt","ro","ru","sv-se","th","tl","tr","uk-ua","vi-vn","zh-cn","zh-tw"]" and "buttons":["Show more","Show less","Choose a topic to learn about","العربية (Arabic)","বাংলা (Bangla)","Čeština (Czech)"]
Comment le corriger
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.
Critères d’audit
5 réussis · 14 à corriger · 16 non applicable
À examiner (14)
Language switcher
Échec70techniqueVisitors should move between locales without losing the current page.
- mediumtechnical · 78 % de confiance
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.
Trouvé ici
Header · <button>
https://www.linkedin.com/Ce que nous avons constaté
"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","es-mx","es-pa","es-pe","es-pr","es-sv","es-uy","es-ve","fr-fr","fr-lu","id","it","ja-jp","ko","ms-my","nl","no","pl","pt-br","pt-pt","ro","ru","sv-se","th","tl","tr","uk-ua","vi-vn","zh-cn","zh-tw"]" and "buttons":["Show more","Show less","Choose a topic to learn about","العربية (Arabic)","বাংলা (Bangla)","Čeština (Czech)"]
Comment le corriger
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
Échec18techniqueLike 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 % de confiance
Valid sitemap not found
No fetchable XML sitemap with URL entries was found at /sitemap.xml or via robots.txt.
Trouvé ici
Sitemap · sitemap.xml
Ce que nous avons constaté
robots.txt was found, but it does not reference a sitemap and /sitemap.xml was missing or empty
Comment le corriger
Publish a valid XML sitemap and reference it from robots.txt with an absolute Sitemap: URL.
Structured data
Échec84techniqueJSON-LD inLanguage should match the page locale when structured data is present.
- lowtechnical · 95 % de confiance
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
Trouvé ici
JSON-LD · <script type="application/ld+json">
https://www.linkedin.com/top-content/career/Ce que nous avons constaté
CollectionPage is present but inLanguage is missing
Comment le corriger
Set JSON-LD inLanguage to match each page locale.
Terminology consistency
Échec50linguistiqueImportant concepts should not be translated differently across pages.
- infolinguistic · 92 % de confiance
Cross-locale terminology cannot be verified
The supplied page records are English only, so consistency of important terms across translated pages is not assessable.
Trouvé ici
Page content · <body>
https://www.linkedin.com/Ce que nous avons constaté
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.
Comment le corriger
Compare the same product concepts across the available locale pages and maintain a shared terminology glossary.
Translation accuracy
Échec50linguistiqueTarget copy should preserve the source meaning, numbers, and product actions.
- infolinguistic · 92 % de confiance
Target-language accuracy cannot be verified
The evidence contains only English source copy and no translated target-language content, numbers, or product-action comparisons.
Trouvé ici
Main content · <body>
https://www.linkedin.com/Ce que nous avons constaté
"htmlLang":"en" and "text":"Skip to main content Agree & Join LinkedIn ... Welcome to your professional community Continue with "
Comment le corriger
Provide source-and-target comparisons for each locale, including consent text and all product actions, and review them against the source meaning.
Fluency
Échec50linguistiqueCopy should sound natural, without grammar issues or machine-translation artifacts.
- infolinguistic · 92 % de confiance
Localized fluency cannot be verified
No non-English copy is included in the evidence, so naturalness and possible machine-translation artifacts cannot be assessed.
Trouvé ici
Main content · <body>
https://www.linkedin.com/Ce que nous avons constaté
The recorded page has "htmlLang":"en" and English headings including "Explore top LinkedIn content" and "Find the right job or internship for you".
Comment le corriger
Review representative copy in every target locale with native-language reviewers, including headings, buttons, and legal text.
Brand voice
Échec55linguistiqueLocalized copy should preserve the intended tone of the source.
- infolinguistic · 90 % de confiance
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.
Trouvé ici
Hero · <h1>
https://www.linkedin.com/Ce que nous avons constaté
"Welcome to your professional community" and "Find the right job or internship for you"
Comment le corriger
Compare localized headings and calls to action with the source tone, preserving LinkedIn’s professional and welcoming voice.
Grammar and style
Échec55linguistiqueLocale-specific capitalization, punctuation, formality, and agreement should be correct.
- infolinguistic · 90 % de confiance
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.
Trouvé ici
Main content · <body>
https://www.linkedin.com/Ce que nous avons constaté
"htmlLang":"en" and "text":"Skip to main content Agree & Join LinkedIn ... Sign in Join now"
Comment le corriger
Run locale-specific proofreading for capitalization, punctuation, formality, and grammatical agreement across the translated interface.
CTA intent
Échec55contextuelLocalized calls to action should communicate the intended product action.
- infocontextual · 90 % de confiance
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.
Trouvé ici
Header · <button>
https://www.linkedin.com/Ce que nous avons constaté
"text":"... Sign in Join now Welcome to your professional community Continue with "
Comment le corriger
Check each locale’s labels for sign-in, joining, and continuation actions against the intended product flows.
Localized images and assets
Échec88visuelLanguage-specific images and alt text should match the page locale.
Visual hierarchy
Échec70visuelLocalization should not make headings or CTAs lose scanability.
- lowvisual · 80 % de confiance
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 2 sampled pages.
Trouvé ici
Ce que nous avons constaté
Upcoming Live Event, Aug 25: How to Turn AI Skeptics into Adoption Champions with Angie Jones
Comment le corriger
Shorten the heading so it does not crowd the visual hierarchy.
Text overflow
Échec75visuelText should not clip, truncate unexpectedly, or overflow buttons and navigation.
- infovisual · 60 % de confiance
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.
Trouvé ici
Header · <button>
https://www.linkedin.com/Ce que nous avons constaté
"buttons":["Show more","Show less","Choose a topic to learn about","العربية (Arabic)","বাংলা (Bangla)","Čeština (Czech)"]
Comment le corriger
Test long translated labels at supported widths and allow wrapping, resizing, or truncation only where it is intentional and accessible.
Layout breakage
Échec75visuelLocalized pages should not overlap, break grids, or overflow modals.
- infovisual · 60 % de confiance
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.
Trouvé ici
Page layout · <body>
https://www.linkedin.com/Ce que nous avons constaté
The evidence provides page status, language metadata, buttons, headings, and text, but no visual rendering or layout measurements.
Comment le corriger
Inspect representative locales at desktop and narrow widths for overlap, grid failures, and overflow in menus and dialogs.
Responsive localisation
Échec75visuelLocalized layouts should hold up across mobile, tablet, and desktop widths.
- infovisual · 60 % de confiance
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.
Trouvé ici
Page layout · <body>
https://www.linkedin.com/Ce que nous avons constaté
The supplied records include "status":200, "htmlLang":"en", headings, and text, but no viewport or responsive-rendering evidence.
Comment le corriger
Test localized pages at mobile, tablet, and desktop breakpoints, especially locales with longer labels and right-to-left text.
Audits réussis (5)
Non applicable (16)
Paramètres régionaux détectés
Résultats complets
- mediumtechnical · 95 % de confiance
Missing hreflang self-reference
The page lists hreflang alternates but does not include itself.
Trouvé ici
Document head · <link rel="alternate" hreflang>
https://www.linkedin.com/?trk=guest_homepage-basic_nav-header-logoCe que nous avons constaté
<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.com/">
Comment le corriger
Add a self-referencing hreflang alternate for this page.
- hightechnical · 100 % de confiance
Valid sitemap not found
No fetchable XML sitemap with URL entries was found at /sitemap.xml or via robots.txt.
Trouvé ici
Sitemap · sitemap.xml
Ce que nous avons constaté
robots.txt was found, but it does not reference a sitemap and /sitemap.xml was missing or empty
Comment le corriger
Publish a valid XML sitemap and reference it from robots.txt with an absolute Sitemap: URL.
- lowtechnical · 95 % de confiance
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
Trouvé ici
JSON-LD · <script type="application/ld+json">
https://www.linkedin.com/top-content/career/Ce que nous avons constaté
CollectionPage is present but inLanguage is missing
Comment le corriger
Set JSON-LD inLanguage to match each page locale.
- lowvisual · 80 % de confiance
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 2 sampled pages.
Trouvé ici
Ce que nous avons constaté
Upcoming Live Event, Aug 25: How to Turn AI Skeptics into Adoption Champions with Angie Jones
Comment le corriger
Shorten the heading so it does not crowd the visual hierarchy.
- mediumtechnical · 78 % de confiance
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.
Trouvé ici
Header · <button>
https://www.linkedin.com/Ce que nous avons constaté
"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","es-mx","es-pa","es-pe","es-pr","es-sv","es-uy","es-ve","fr-fr","fr-lu","id","it","ja-jp","ko","ms-my","nl","no","pl","pt-br","pt-pt","ro","ru","sv-se","th","tl","tr","uk-ua","vi-vn","zh-cn","zh-tw"]" and "buttons":["Show more","Show less","Choose a topic to learn about","العربية (Arabic)","বাংলা (Bangla)","Čeština (Czech)"]
Comment le corriger
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.
- infolinguistic · 92 % de confiance
Cross-locale terminology cannot be verified
The supplied page records are English only, so consistency of important terms across translated pages is not assessable.
Trouvé ici
Page content · <body>
https://www.linkedin.com/Ce que nous avons constaté
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.
Comment le corriger
Compare the same product concepts across the available locale pages and maintain a shared terminology glossary.
- infolinguistic · 92 % de confiance
Target-language accuracy cannot be verified
The evidence contains only English source copy and no translated target-language content, numbers, or product-action comparisons.
Trouvé ici
Main content · <body>
https://www.linkedin.com/Ce que nous avons constaté
"htmlLang":"en" and "text":"Skip to main content Agree & Join LinkedIn ... Welcome to your professional community Continue with "
Comment le corriger
Provide source-and-target comparisons for each locale, including consent text and all product actions, and review them against the source meaning.
- infolinguistic · 92 % de confiance
Localized fluency cannot be verified
No non-English copy is included in the evidence, so naturalness and possible machine-translation artifacts cannot be assessed.
Trouvé ici
Main content · <body>
https://www.linkedin.com/Ce que nous avons constaté
The recorded page has "htmlLang":"en" and English headings including "Explore top LinkedIn content" and "Find the right job or internship for you".
Comment le corriger
Review representative copy in every target locale with native-language reviewers, including headings, buttons, and legal text.
- infolinguistic · 90 % de confiance
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.
Trouvé ici
Hero · <h1>
https://www.linkedin.com/Ce que nous avons constaté
"Welcome to your professional community" and "Find the right job or internship for you"
Comment le corriger
Compare localized headings and calls to action with the source tone, preserving LinkedIn’s professional and welcoming voice.
- infolinguistic · 90 % de confiance
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.
Trouvé ici
Main content · <body>
https://www.linkedin.com/Ce que nous avons constaté
"htmlLang":"en" and "text":"Skip to main content Agree & Join LinkedIn ... Sign in Join now"
Comment le corriger
Run locale-specific proofreading for capitalization, punctuation, formality, and grammatical agreement across the translated interface.
- infocontextual · 90 % de confiance
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.
Trouvé ici
Header · <button>
https://www.linkedin.com/Ce que nous avons constaté
"text":"... Sign in Join now Welcome to your professional community Continue with "
Comment le corriger
Check each locale’s labels for sign-in, joining, and continuation actions against the intended product flows.
- infovisual · 60 % de confiance
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.
Trouvé ici
Header · <button>
https://www.linkedin.com/Ce que nous avons constaté
"buttons":["Show more","Show less","Choose a topic to learn about","العربية (Arabic)","বাংলা (Bangla)","Čeština (Czech)"]
Comment le corriger
Test long translated labels at supported widths and allow wrapping, resizing, or truncation only where it is intentional and accessible.
- infovisual · 60 % de confiance
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.
Trouvé ici
Page layout · <body>
https://www.linkedin.com/Ce que nous avons constaté
The evidence provides page status, language metadata, buttons, headings, and text, but no visual rendering or layout measurements.
Comment le corriger
Inspect representative locales at desktop and narrow widths for overlap, grid failures, and overflow in menus and dialogs.
- infovisual · 60 % de confiance
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.
Trouvé ici
Page layout · <body>
https://www.linkedin.com/Ce que nous avons constaté
The supplied records include "status":200, "htmlLang":"en", headings, and text, but no viewport or responsive-rendering evidence.
Comment le corriger
Test localized pages at mobile, tablet, and desktop breakpoints, especially locales with longer labels and right-to-left text.
Pages échantillonnées
- 200 · https://www.linkedin.com/ · lang=en
- 200 · https://www.linkedin.com/?trk=guest_homepage-basic_nav-header-logo · lang=en
- 200 · https://www.linkedin.com/legal/user-agreement?trk=linkedin-tc_auth-button_user-agreement · lang=en
- 200 · https://www.linkedin.com/legal/privacy-policy?trk=linkedin-tc_auth-button_privacy-policy · lang=en
- 200 · https://www.linkedin.com/legal/cookie-policy?trk=linkedin-tc_auth-button_cookie-policy · lang=en
- 200 · https://www.linkedin.com/top-content?trk=guest_homepage-basic_guest_nav_menu_topContent · lang=en
- 200 · https://www.linkedin.com/learning/search?trk=guest_homepage-basic_guest_nav_menu_learning · lang=en
- 200 · https://www.linkedin.com/jobs/search?trk=guest_homepage-basic_guest_nav_menu_jobs&position=1&pageNum=0 · lang=en
- 200 · https://www.linkedin.com/games?trk=guest_homepage-basic_guest_nav_menu_games · lang=en
- 200 · https://www.linkedin.com/login/?trk=guest_homepage-basic_nav-header-signin · lang=en
- 200 · https://www.linkedin.com/signup?trk=guest_homepage-basic_nav-header-join · lang=en
- 200 · https://www.linkedin.com/login/ · lang=en
- 200 · https://www.linkedin.com/signup · lang=en
- 200 · https://www.linkedin.com/top-content/career/ · lang=en
- 200 · https://www.linkedin.com/top-content/productivity/ · lang=en
Envoyez-moi un récapitulatif par e-mail
Facultatif. Saisissez votre adresse e-mail professionnelle et nous vous enverrons un résumé concis de ce rapport public.
Étape suivante
Bonne base, avec une marge d’amélioration. Créez un espace de travail pour un suivi continu de la localisation, ou réservez une revue d’audit.
