Rapport de localisation
wordsintranslation.com
wordsintranslation.com
Score de localisation
63/100
À améliorerLes utilisateurs peuvent rencontrer des problèmes de localisation perceptibles.
- 89Audit technique
- 89Audit linguistique
- 88Audit contextuel
- 82Audit 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 #16 sur 22 audits publics
À corriger en priorité
- mediumtechnical · 90 % de confiance
Only one locale signal detected
The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).
Trouvé ici
Sampled pages · document
https://www.wordsintranslation.com/Ce que nous avons constaté
Detected locale signals: en-gb
Comment le corriger
Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.
- mediumtechnical · 88 % de confiance
HTML language is not region-specific
The locale inventory identifies en-GB, but the sampled pages declare only en in the htmlLang field.
Trouvé ici
Document root · <html>
https://www.wordsintranslation.com/Ce que nous avons constaté
"locales":["en-gb"] ... "htmlLang":"en"
Comment le corriger
Set the document language to <html lang="en-GB"> on the en-GB pages, and verify localized alt text and ARIA labels across the full markup.
- 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.wordsintranslation.com/Ce que nous avons constaté
LocalBusiness is present but inLanguage is missing
Comment le corriger
Set JSON-LD inLanguage to match each page locale.
Critères d’audit
7 réussis · 12 à corriger · 16 non applicable
À examiner (12)
Locale routing
Échec72techniqueLocalized pages should use a consistent URL structure and resolve successfully.
- mediumtechnical · 90 % de confiance
Only one locale signal detected
The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).
Trouvé ici
Sampled pages · document
https://www.wordsintranslation.com/Ce que nous avons constaté
Detected locale signals: en-gb
Comment le corriger
Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.
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.wordsintranslation.com/Ce que nous avons constaté
LocalBusiness is present but inLanguage is missing
Comment le corriger
Set JSON-LD inLanguage to match each page locale.
Accessibility localisation
Échec78techniquelang, aria-label, and alt text should match the page locale.
- mediumtechnical · 88 % de confiance
HTML language is not region-specific
The locale inventory identifies en-GB, but the sampled pages declare only en in the htmlLang field.
Trouvé ici
Document root · <html>
https://www.wordsintranslation.com/Ce que nous avons constaté
"locales":["en-gb"] ... "htmlLang":"en"
Comment le corriger
Set the document language to <html lang="en-GB"> on the en-GB pages, and verify localized alt text and ARIA labels across the full markup.
Fluency
Échec82linguistiqueCopy should sound natural, without grammar issues or machine-translation artifacts.
- lowlinguistic · 84 % de confiance
Leading punctuation in page title
The guide page title begins with a colon, which reads like a missing or misplaced title element.
Trouvé ici
Document title · <title>
https://www.wordsintranslation.com/launching-into-new-market-gtm-guideCe que nous avons constaté
"title":": GTM & Launching into a new market | Free quickstart guide"
Comment le corriger
Remove the leading colon and set the title to a complete, natural phrase.
- lowlinguistic · 84 % de confiance
Invisible character in heading
The guide page contains a zero-width character before the second heading, which may indicate an editing artifact.
Trouvé ici
Ce que nous avons constaté
"headings":["LAUNCHING INTO A NEW MARKET A PRACTICAL GUIDE FOR GLOBAL BRANDS","The next great frontier, your next great campaign."]
Comment le corriger
Remove the invisible character before the heading text and recheck the rendered copy.
Brand voice
Échec88linguistiqueLocalized copy should preserve the intended tone of the source.
Grammar and style
Échec84linguistiqueLocale-specific capitalization, punctuation, formality, and agreement should be correct.
- lowlinguistic · 84 % de confiance
Nonstandard compound spelling
The testimonial uses “turn arounds” as two words; “turnarounds” is the standard compound spelling in this context.
Trouvé ici
Testimonial · <blockquote>
https://www.wordsintranslation.com/Ce que nous avons constaté
"Thank you so much for all the hard work and fast turn arounds. You saved our skin on many occasions and there is no way this launch could have happened without you."
Comment le corriger
Change “turn arounds” to “turnarounds” and confirm the approved editorial style.
Cultural adaptation
Échec88contextuelCurrency, dates, addresses, and local examples should fit the market.
Localized images and assets
Échec88visuelLanguage-specific images and alt text should match the page locale.
Visual hierarchy
Échec76visuelLocalization should not make headings or CTAs lose scanability.
- lowvisual · 80 % de confiance
Heading is excessively long
A localized heading may crowd the visual hierarchy.
Trouvé ici
Page body · heading
https://www.wordsintranslation.com/Ce que nous avons constaté
Thank you so much for all the hard work and fast turn arounds. You saved our skin on many occasions and there is no way this launch could have happened without you.
Comment le corriger
Shorten the heading so it does not crowd the visual hierarchy.
Text overflow
Échec82visuelText should not clip, truncate unexpectedly, or overflow buttons and navigation.
Layout breakage
Échec82visuelLocalized pages should not overlap, break grids, or overflow modals.
Responsive localisation
Échec82visuelLocalized layouts should hold up across mobile, tablet, and desktop widths.
Audits réussis (7)
Non applicable (16)
Paramètres régionaux détectés
Résultats complets
- mediumtechnical · 90 % de confiance
Only one locale signal detected
The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).
Trouvé ici
Sampled pages · document
https://www.wordsintranslation.com/Ce que nous avons constaté
Detected locale signals: en-gb
Comment le corriger
Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.
- 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.wordsintranslation.com/Ce que nous avons constaté
LocalBusiness 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.
Trouvé ici
Page body · heading
https://www.wordsintranslation.com/Ce que nous avons constaté
Thank you so much for all the hard work and fast turn arounds. You saved our skin on many occasions and there is no way this launch could have happened without you.
Comment le corriger
Shorten the heading so it does not crowd the visual hierarchy.
- infotechnical · 68 % de confiance
No locale-sensitive values observed
The supplied page excerpts do not show dates, numbers, currencies, or calendar values that can be checked against en-GB conventions.
Trouvé ici
Ce que nous avons constaté
"locales":["en-gb"]
Comment le corriger
Review all rendered dates, numbers, prices, and currency symbols on the full pages against en-GB formatting rules.
- mediumtechnical · 88 % de confiance
HTML language is not region-specific
The locale inventory identifies en-GB, but the sampled pages declare only en in the htmlLang field.
Trouvé ici
Document root · <html>
https://www.wordsintranslation.com/Ce que nous avons constaté
"locales":["en-gb"] ... "htmlLang":"en"
Comment le corriger
Set the document language to <html lang="en-GB"> on the en-GB pages, and verify localized alt text and ARIA labels across the full markup.
- lowlinguistic · 84 % de confiance
Leading punctuation in page title
The guide page title begins with a colon, which reads like a missing or misplaced title element.
Trouvé ici
Document title · <title>
https://www.wordsintranslation.com/launching-into-new-market-gtm-guideCe que nous avons constaté
"title":": GTM & Launching into a new market | Free quickstart guide"
Comment le corriger
Remove the leading colon and set the title to a complete, natural phrase.
- lowlinguistic · 84 % de confiance
Invisible character in heading
The guide page contains a zero-width character before the second heading, which may indicate an editing artifact.
Trouvé ici
Ce que nous avons constaté
"headings":["LAUNCHING INTO A NEW MARKET A PRACTICAL GUIDE FOR GLOBAL BRANDS","The next great frontier, your next great campaign."]
Comment le corriger
Remove the invisible character before the heading text and recheck the rendered copy.
- lowlinguistic · 84 % de confiance
Nonstandard compound spelling
The testimonial uses “turn arounds” as two words; “turnarounds” is the standard compound spelling in this context.
Trouvé ici
Testimonial · <blockquote>
https://www.wordsintranslation.com/Ce que nous avons constaté
"Thank you so much for all the hard work and fast turn arounds. You saved our skin on many occasions and there is no way this launch could have happened without you."
Comment le corriger
Change “turn arounds” to “turnarounds” and confirm the approved editorial style.
Pages échantillonnées
- 200 · https://www.wordsintranslation.com/ · lang=en
- 200 · https://www.wordsintranslation.com/launching-into-new-market-gtm-guide · lang=en
- 200 · https://www.wordsintranslation.com/about · lang=en
- 200 · https://www.wordsintranslation.com/services · lang=en
- 200 · https://www.wordsintranslation.com/services/cultural-consultation · lang=en
- 200 · https://www.wordsintranslation.com/services/localisation-audit-international-brands · lang=en
- 200 · https://www.wordsintranslation.com/services/international-tone-of-voice · lang=en
- 200 · https://www.wordsintranslation.com/services/marketing-translation-services · lang=en
- 200 · https://www.wordsintranslation.com/services/transcreation-services · lang=en
- 200 · https://www.wordsintranslation.com/services/multilingual-copywriting · lang=en
- 200 · https://www.wordsintranslation.com/services/machine-translation-post-editing-mtpe · lang=en
- 200 · https://www.wordsintranslation.com/services/certified-translation-services-uk · lang=en
- 200 · https://www.wordsintranslation.com/asset-localisation-and-versioning · lang=en
- 200 · https://www.wordsintranslation.com/international-subtitling-captions · lang=en
- 200 · https://www.wordsintranslation.com/international-voice-over-services · 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.
