i18n Audit

The code you pasted, scored for translation readiness — hardcoded strings found, keys suggested, and the en.json starter written for you.

Back to SkillSafe
How it works

Nothing to paste? — a small React checkout with the classic problems planted: hardcoded JSX text, a "Hello " + name greeting, an item(s) plural hack, toFixed pricing and margin-left CSS. Or see a saved report with no run and no charge: · .

1

Paste the code

A component, a page, or several files with // file: markers — or drag the files straight in. The quick scan counts hardcoded string candidates, concatenation, plural hacks and physical CSS in your browser, free and with no sign-in. Copy it out as a checklist even if you never run the full audit.

2

Get the score

Six categories scored out of 30 — hardcoded strings, string building, formatting, plurals, RTL, infrastructure — each row quoting the code and showing counted numbers. Score bands decide the verdict: 27+ is localization-ready, 23–26 has minor gaps, below that needs extraction work.

3

Extract the strings

A key-by-key extraction plan — semantic, dot-namespaced suggestions matched to your existing style — and the en.json starter assembled from it, in nested shape so t('a.b') resolves under the react-i18next and vue-i18n defaults. Blank stubs for your target locales and a translator CSV come with it. Then pin that audit as a baseline, make the edits, re-audit, and the page shows you exactly which keys closed and which are new.