Localisation report

Deel

Global HR and payroll technology

deel.com

Product: Deel is a global people platform for hiring, managing, paying, and equipping teams in 150+ countries. It provides payroll, HR, IT, benefits, hiring, mobility, and compliance solutions.

Brand voice: global, streamlined, confident

Localisation score

75/100

Good

The website is generally well localised, with some issues to improve.

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

63Technical Audit
79Linguistic Audit
86Contextual Audit
72Visual Audit

Audited: Aug 16, 2026Scope: Public smart sample · technical, linguistic, contextual, and visual creditsConfidence: Indicative health check from sampled pages — not a full site crawl.

Sampled 12 pages across technical, linguistic, contextual, and visual localisation credits. How we score localisation audits

How you compare

Rank #10 of 22 public audits

Ahead of 11 other public auditsPublic average: 71/100

See the full leaderboard

Fix first

1
critical
Page returned HTTP 404
A sampled localisation URL did not return a successful HTML response. Affects 2 sampled pages.
See details
2
critical
hreflang target returns HTTP 404
Alternate link for ko-kr points to a failing URL. Affects 20 sampled pages.
See details
3
high
No CJK-capable font detected
A ko-kr page shows CJK text but the embedded/inline font stack has no known CJK typeface. Affects 2 sampled pages.
See details

Audit criteria

6 passed · 14 to watch · 9 to fix · 6 not applicable

Needs attention (9)

Locale routing
Fail44technicalWeight 3
Localized pages should use a consistent URL structure and resolve successfully.
- criticaltechnical · 100% confidence
  Page returned HTTP 404
  A sampled localisation URL did not return a successful HTML response. Affects 2 sampled pages.
  Found here
  Sampled page · document
  https://www.deel.com/ko-kr/
  What we saw
  HTTP 404 Seen on 2 pages, e.g. https://www.deel.com/ko-kr/, https://www.deel.com/zh-tw/
  How to fix it
  Fix the localized URL so it returns a successful HTML response.
hreflang
Fail0technicalWeight 3
Localized versions should be linked with valid, reciprocal hreflang including self and x-default.
- criticaltechnical · 100% confidence
  hreflang target returns HTTP 404
  Alternate link for ko-kr points to a failing URL. Affects 20 sampled pages.
  Found here
  Document head · <link rel="alternate" hreflang>
  https://www.deel.com/ko-kr/
  What we saw
  <link rel="alternate" hreflang="ko-kr" href="https://www.deel.com/ko-kr/"> returns HTTP 404 Seen on 2 pages, e.g. https://www.deel.com/ko-kr/, https://www.deel.com/zh-tw/
  How to fix it
  Fix the ko-kr hreflang target so it returns a successful HTML response.
Sitemap
Fail70technicalWeight 1
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.
- mediumtechnical · 88% confidence
  Sitemap omits some published locales
  Locale-prefixed pages for fr, de, es, pt, ja, nl, ko, sv, da do not appear in sampled sitemap URLs.
  Found here
  Sitemap · sitemap.xml
  https://www.deel.com/sitemap.xml
  What we saw
  Sitemap locales in sample: zh; missing: fr, de, es, pt, ja, nl, ko, sv, da
  How to fix it
  Include URLs for every published locale prefix in the sitemap.
Structured data
Fail0technicalWeight 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.deel.com/
  What we saw
  WebPage is present but inLanguage is missing
  How to fix it
  Set JSON-LD inLanguage to match each page locale.
Terminology consistency
Fail40linguisticWeight 2
Important concepts should not be translated differently across pages.
- mediumlinguistic · 95% confidence
  Terminology inconsistency
  "Necessary 92" appears both untranslated and translated across fr pages. Affects 127 sampled pages.
  Found here
  Header · <nav> or <button>
  https://www.deel.com/fr/
  What we saw
  "Necessary 92" appears untranslated on some fr pages and translated on others Seen on 10 pages, e.g. https://www.deel.com/fr/, https://www.deel.com/de/, https://www.deel.com/es/
  How to fix it
  Use one translated label for "Necessary 92" across fr pages.
Text expansion
Fail40visualWeight 1
Longer translations should not create obvious length pressure versus the source UI.
- mediumvisual · 88% confidence
  Localized text is much longer than the source
  A fr string is 283% the length of the source, which often causes overflow. Affects 49 sampled pages.
  Found here
  Control · <button>
  https://www.deel.com/fr/
  What we saw
  EN "Secure visas" → FR "Gérer les RH et les collaborateurs" (283%) Seen on 11 pages, e.g. https://www.deel.com/fr/, https://www.deel.com/de/, https://www.deel.com/es/
  How to fix it
  Shorten the translation or give the control more room so the longer copy does not overflow.
Font and script support
Fail62visualWeight 2
Typography should support the target script without generic fallback-only stacks, tofu glyphs, or missing CJK fonts.
- highvisual · 95% confidence
  No CJK-capable font detected
  A ko-kr page shows CJK text but the embedded/inline font stack has no known CJK typeface. Affects 2 sampled pages.
  Found here
  Page body · font-family
  https://www.deel.com/ko-kr/
  What we saw
  font-family: Inter, BagossStandardVF, BagossCondensedFont, inherit, var(--font-bagoss-condensed) Seen on 2 pages, e.g. https://www.deel.com/ko-kr/, https://www.deel.com/zh-tw/
  How to fix it
  Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
Visual hierarchy
Fail55visualWeight 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. Affects 7 sampled pages.
  Found here
  Page body · heading
  https://www.deel.com/
  What we saw
  Get the latest insights on today's world of work delivered straight to your inbox. Seen on 7 pages, e.g. https://www.deel.com/, https://www.deel.com/fr/, https://www.deel.com/de/
  How to fix it
  Shorten the heading so it does not crowd the visual hierarchy.
Component consistency
Fail70visualWeight 1
Repeated components should stay visually consistent across locales.
- lowvisual · 95% confidence
  Repeated components differ across locales
  Button counts differ between the source locale and ko.
  Found here
  Page body · <button>
  https://www.deel.com/ko-kr/
  What we saw
  Source locale has 33 buttons; ko has 7.
  How to fix it
  Keep the same repeated controls across locales, or drop unused ones on purpose.

Worth a look (14)

Language switcher
Watch75technicalWeight 2
Visitors should move between locales without losing the current page.
Accessibility localisation
Watch82technicalWeight 2
lang, aria-label, and alt text should match the page locale.
- infotechnical · 84% confidence
  Sampled document language matches locale
  The sampled English, French, and German pages declare matching HTML language codes. The evidence does not expose aria-label or alt attributes, so those aspects cannot be fully verified.
  Found here
  Document root · <html>
  https://www.deel.com/fr/
  What we saw
  "url":"https://www.deel.com/fr/","status":200,"htmlLang":"fr"; "url":"https://www.deel.com/de/","status":200,"htmlLang":"de"
  How to fix it
  Audit all localized pages’ aria-label and alt attributes, and ensure each localized string matches the declared page language.
Translation accuracy
Watch78linguisticWeight 3
Target copy should preserve the source meaning, numbers, and product actions.
- mediumlinguistic · 94% confidence
  Cookie consent copy remains in English
  The French and German page evidence contains English cookie-consent text instead of localized copy.
  Found here
  Cookie consent · modal text
  https://www.deel.com/fr/
  What we saw
  "url":"https://www.deel.com/fr/" ... "text":"Consent Details ... About This website uses cookies We use cookies to improve your experience, analyze traffic, support marketing, and share usage data with our advertising, social media, and analytics partners."
  How to fix it
  Translate the cookie-consent interface and supporting text for each target locale.
- mediumlinguistic · 94% confidence
  Unresolved localization placeholders are exposed
  A cookie-consent button exposes an unresolved IAB localization token rather than user-facing text.
  Found here
  Cookie consent · <button>
  https://www.deel.com/fr/
  What we saw
  "buttons":["Necessary 92","Preferences 7","Statistics 138","Marketing 108","Unclassified 888","[#IABV2_LABEL_PURPOSES#]"]
  How to fix it
  Resolve the IAB localization token before rendering and provide a localized accessible label.
Fluency
Watch80linguisticWeight 2
Copy should sound natural, without grammar issues or machine-translation artifacts.
- mediumlinguistic · 91% confidence
  English cookie text interrupts localized fluency
  The French and German page samples include a long block of untranslated English cookie-consent copy.
  Found here
  Cookie consent · modal text
  https://www.deel.com/fr/
  What we saw
  "text":"... About This website uses cookies We use cookies to improve your experience, analyze traffic, support marketing, and share usage data with our advertising, social media, and analytics partners."
  How to fix it
  Replace the English consent text with professionally reviewed translations for each locale.
- mediumlinguistic · 91% confidence
  Technical placeholder appears as visible UI copy
  The unresolved token is a machine-generated artifact and does not read as natural interface language.
  Found here
  Cookie consent · <button>
  https://www.deel.com/fr/
  What we saw
  "[#IABV2_LABEL_PURPOSES#]"
  How to fix it
  Fix the consent-component translation lookup so the resolved localized label is rendered.
Grammar and style
Watch87linguisticWeight 2
Locale-specific capitalization, punctuation, formality, and agreement should be correct.
- lowlinguistic · 88% confidence
  German heading uses nonstandard adjective capitalization
  The German heading capitalizes the adjective “Globale” in a way that is inconsistent with standard German sentence-style capitalization.
  Found here
  Hero · heading
  https://www.deel.com/de/
  What we saw
  "headings":["Stellen, verwalten, bezahlen und ausrüsten Sie jeden, überall.","Die Globale Personalplattform","Deel Payroll","Deel HR"]
  How to fix it
  Change the heading to “Die globale Personalplattform” unless the brand’s approved style guide explicitly requires title case.
CTA intent
Watch84contextualWeight 2
Localized calls to action should communicate the intended product action.
UI context
Watch79contextualWeight 1
Translations should fit the UI component: button, nav, form, modal, or error.
- mediumcontextual · 82% confidence
  Cookie-consent control exposes an unresolved label
  A button in the consent interface displays a localization token, which is unsuitable for a user-facing control.
  Found here
  Cookie consent · <button>
  https://www.deel.com/fr/
  What we saw
  "buttons":["Necessary 92","Preferences 7","Statistics 138","Marketing 108","Unclassified 888","[#IABV2_LABEL_PURPOSES#]"]
  How to fix it
  Render the translated human-readable label instead of the unresolved token.
Product context
Watch88contextualWeight 1
Language should match product concepts such as plans, settings, and workflows.
Contextual meaning
Watch88contextualWeight 1
Strings should be judged in surrounding page and component context, not in isolation.
Audience context
Watch89contextualWeight 1
Language should fit the intended audience, such as consumer, enterprise, or developer.
Localized images and assets
Watch84visualWeight 1
Language-specific images and alt text should match the page locale.
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 (6)

Not applicable (6)

Other findings

Findings not listed under a criterion above.

lowvisual · 72% confidence
No Korean word-break rule found in sampled CSS
Embedded CSS was found, but it does not declare word-break: keep-all for Hangul.
Found here
CSS · word-break
https://www.deel.com/ko-kr/
What we saw
Sampled <style>/inline CSS declares fonts but no word-break: keep-all
How to fix it
Add word-break: keep-all for Korean text containers.

Detected locales

Danish (Denmark)
da-dk · hreflang
German
de · hreflang
English
en · page language
Spanish
es · hreflang
French
fr · hreflang
Japanese
ja · hreflang
Korean (South Korea)
ko-kr · hreflang
Dutch
nl · hreflang
Portuguese
pt · hreflang
Swedish (Sweden)
sv-se · hreflang
Chinese (China)
zh-cn · hreflang
Chinese (Taiwan)
zh-tw · hreflang

Linguistic notes

de
The sampled German hero heading has a likely capitalization issue.
- “Die Globale Personalplattform”
  In standard German sentence-style capitalization, the adjective would normally be lowercase: “Die globale Personalplattform.”

Pages sampled

Next step

Strong localisation signals. Claim this domain to keep locales healthy as you ship, or book a deeper 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.