Localisation report
wordsintranslation.com
Localisation score
63/100
Needs improvementUsers may encounter noticeable localisation problems.
Sampled 15 pages across technical, linguistic, contextual, and visual localisation credits. How we score localisation audits
Rank #18 of 24 public audits
Only one locale signal detected
The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).
Found here
Sampled pages · document
https://www.wordsintranslation.com/What we saw
Detected locale signals: en-gb
How to fix it
Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.
HTML language is not region-specific
The locale inventory identifies en-GB, but the sampled pages declare only en in the htmlLang field.
Found here
Document root · <html>
https://www.wordsintranslation.com/What we saw
"locales":["en-gb"] ... "htmlLang":"en"
How to fix it
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.
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.wordsintranslation.com/What we saw
LocalBusiness is present but inLanguage is missing
How to fix it
Set JSON-LD inLanguage to match each page locale.
7 passed · 12 to fix · 16 not applicable
Locale routing
Fail72technicalLocalized pages should use a consistent URL structure and resolve successfully.
Only one locale signal detected
The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).
Found here
Sampled pages · document
https://www.wordsintranslation.com/What we saw
Detected locale signals: en-gb
How to fix it
Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.
Structured data
Fail84technicalJSON-LD inLanguage should match the page locale when structured data is present.
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.wordsintranslation.com/What we saw
LocalBusiness is present but inLanguage is missing
How to fix it
Set JSON-LD inLanguage to match each page locale.
Accessibility localisation
Fail78technicallang, aria-label, and alt text should match the page locale.
HTML language is not region-specific
The locale inventory identifies en-GB, but the sampled pages declare only en in the htmlLang field.
Found here
Document root · <html>
https://www.wordsintranslation.com/What we saw
"locales":["en-gb"] ... "htmlLang":"en"
How to fix it
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
Fail82linguisticCopy should sound natural, without grammar issues or machine-translation artifacts.
Leading punctuation in page title
The guide page title begins with a colon, which reads like a missing or misplaced title element.
Found here
Document title · <title>
https://www.wordsintranslation.com/launching-into-new-market-gtm-guideWhat we saw
"title":": GTM & Launching into a new market | Free quickstart guide"
How to fix it
Remove the leading colon and set the title to a complete, natural phrase.
Invisible character in heading
The guide page contains a zero-width character before the second heading, which may indicate an editing artifact.
Found here
What we saw
"headings":["LAUNCHING INTO A NEW MARKET A PRACTICAL GUIDE FOR GLOBAL BRANDS","The next great frontier, your next great campaign."]
How to fix it
Remove the invisible character before the heading text and recheck the rendered copy.
Brand voice
Fail88linguisticLocalized copy should preserve the intended tone of the source.
Grammar and style
Fail84linguisticLocale-specific capitalization, punctuation, formality, and agreement should be correct.
Nonstandard compound spelling
The testimonial uses “turn arounds” as two words; “turnarounds” is the standard compound spelling in this context.
Found here
Testimonial · <blockquote>
https://www.wordsintranslation.com/What we saw
"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."
How to fix it
Change “turn arounds” to “turnarounds” and confirm the approved editorial style.
Cultural adaptation
Fail88contextualCurrency, dates, addresses, and local examples should fit the market.
Localized images and assets
Fail88visualLanguage-specific images and alt text should match the page locale.
Visual hierarchy
Fail76visualLocalization should not make headings or CTAs lose scanability.
Heading is excessively long
A localized heading may crowd the visual hierarchy.
Found here
Page body · heading
https://www.wordsintranslation.com/What we saw
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.
How to fix it
Shorten the heading so it does not crowd the visual hierarchy.
Text overflow
Fail82visualText should not clip, truncate unexpectedly, or overflow buttons and navigation.
Layout breakage
Fail82visualLocalized pages should not overlap, break grids, or overflow modals.
Responsive localisation
Fail82visualLocalized layouts should hold up across mobile, tablet, and desktop widths.
Only one locale signal detected
The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).
Found here
Sampled pages · document
https://www.wordsintranslation.com/What we saw
Detected locale signals: en-gb
How to fix it
Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.
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.wordsintranslation.com/What we saw
LocalBusiness is present but inLanguage is missing
How to fix it
Set JSON-LD inLanguage to match each page locale.
Heading is excessively long
A localized heading may crowd the visual hierarchy.
Found here
Page body · heading
https://www.wordsintranslation.com/What we saw
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.
How to fix it
Shorten the heading so it does not crowd the visual hierarchy.
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.
Found here
What we saw
"locales":["en-gb"]
How to fix it
Review all rendered dates, numbers, prices, and currency symbols on the full pages against en-GB formatting rules.
HTML language is not region-specific
The locale inventory identifies en-GB, but the sampled pages declare only en in the htmlLang field.
Found here
Document root · <html>
https://www.wordsintranslation.com/What we saw
"locales":["en-gb"] ... "htmlLang":"en"
How to fix it
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.
Leading punctuation in page title
The guide page title begins with a colon, which reads like a missing or misplaced title element.
Found here
Document title · <title>
https://www.wordsintranslation.com/launching-into-new-market-gtm-guideWhat we saw
"title":": GTM & Launching into a new market | Free quickstart guide"
How to fix it
Remove the leading colon and set the title to a complete, natural phrase.
Invisible character in heading
The guide page contains a zero-width character before the second heading, which may indicate an editing artifact.
Found here
What we saw
"headings":["LAUNCHING INTO A NEW MARKET A PRACTICAL GUIDE FOR GLOBAL BRANDS","The next great frontier, your next great campaign."]
How to fix it
Remove the invisible character before the heading text and recheck the rendered copy.
Nonstandard compound spelling
The testimonial uses “turn arounds” as two words; “turnarounds” is the standard compound spelling in this context.
Found here
Testimonial · <blockquote>
https://www.wordsintranslation.com/What we saw
"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."
How to fix it
Change “turn arounds” to “turnarounds” and confirm the approved editorial style.
Optional. Enter your work email and we will send a concise summary of this public report.
Solid baseline with room to improve. Create a workspace for continuous locale monitoring, or book an audit review.
