Localisation report

wordsintranslation.com

Localisation score

63/100

Needs improvement

Users may encounter noticeable localisation problems.

This score uses an earlier scoring method. Run the audit again to compare it with current reports.

89Technical Audit
89Linguistic Audit
88Contextual Audit
82Visual Audit

Audited: Aug 15, 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 #18 of 22 public audits

Ahead of 4 other public auditsPublic average: 71/100

See the full leaderboard

Fix first

1
medium
Only one locale signal detected
The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).
See details
2
medium
HTML language is not region-specific
The locale inventory identifies en-GB, but the sampled pages declare only en in the htmlLang field.
See details
3
low
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
See details

Audit criteria

7 passed · 11 to watch · 1 to fix · 16 not applicable

Needs attention (1)

Locale routing
Fail72technicalWeight 3
Localized pages should use a consistent URL structure and resolve successfully.
- mediumtechnical · 90% confidence
  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.

Worth a look (11)

Structured data
Watch84technicalWeight 1
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.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
Watch78technicalWeight 2
lang, aria-label, and alt text should match the page locale.
- mediumtechnical · 88% confidence
  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
Watch82linguisticWeight 2
Copy should sound natural, without grammar issues or machine-translation artifacts.
- lowlinguistic · 84% confidence
  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-guide
  What 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.
- lowlinguistic · 84% confidence
  Invisible character in heading
  The guide page contains a zero-width character before the second heading, which may indicate an editing artifact.
  Found here
  Hero · <h2>
  https://www.wordsintranslation.com/launching-into-new-market-gtm-guide
  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
Watch88linguisticWeight 1
Localized copy should preserve the intended tone of the source.
Grammar and style
Watch84linguisticWeight 2
Locale-specific capitalization, punctuation, formality, and agreement should be correct.
- lowlinguistic · 84% confidence
  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
Watch88contextualWeight 2
Currency, dates, addresses, and local examples should fit the market.
Localized images and assets
Watch88visualWeight 1
Language-specific images and alt text should match the page locale.
Visual hierarchy
Watch76visualWeight 1
Localization should not make headings or CTAs lose scanability.
- lowvisual · 80% confidence
  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
Watch82visualWeight 3
Measured in the rendered page: localized buttons, links, labels, and headings should not clip their text more than the source page does.
Layout breakage
Watch82visualWeight 3
Measured at desktop width: localized pages should not push content past the viewport when the source page does not.
Responsive localisation
Watch82visualWeight 2
Measured at mobile width: localized pages should not scroll sideways or clip labels when the source page does not.

Passed audits (7)

Not applicable (16)

Other findings

Findings not listed under a criterion above.

infotechnical · 68% confidence
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
https://www.wordsintranslation.com/
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.

Detected locales

British English
en-gb · 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.