Localization Testing: What It Is and What to Check Before Release
Localization testing checks whether a translated website, application or software product actually works for users in the target language and market. It goes beyond proofreading: reviewers check the language in context, interface layout, navigation, forms, dates, currencies, units, placeholders, error messages and other locale-specific details before release.
What is localization testing?
Localization testing is the quality-assurance stage used to check whether a localized product is linguistically correct, technically functional and appropriate for the target locale. It is performed after translated content has been integrated into the product or staging environment.
Linguistic quality
Review grammar, terminology, tone, consistency and whether the wording makes sense in the real user context.
Visual quality
Check truncation, overlapping text, broken layouts, line wrapping, buttons, menus and responsive behaviour.
Locale behaviour
Verify dates, numbers, currencies, units, address formats, sorting, text direction and other locale-specific settings.
Localization testing is not the same as proofreading
Proofreading checks whether the translated text is correct and natural. Localization testing adds another layer: it checks how the localized content behaves after implementation.
This distinction matters because many localization defects cannot be seen in the translation file itself. A reviewer may only notice the problem once the text appears inside the interface, checkout, onboarding flow, settings menu or error state.
What should be checked during localization testing?
Untranslated strings
Search for source-language text that remains in menus, pop-ups, tooltips, notifications, forms or system messages.
Truncation and overflow
Languages expand differently. Check buttons, tabs, tables, cards, headers and mobile layouts for cut-off text.
Terminology consistency
Product names, commands, feature labels and recurring technical terms should use consistent translations across the product.
Dates and time
Verify date order, month names, time format, time zones and locale-specific conventions.
Numbers and currencies
Check decimal separators, thousands separators, currency symbols, symbol placement and numeric grouping.
Units and measurements
Confirm whether units should remain unchanged or be adapted for the target market and verify that values are not accidentally altered.
Forms and validation
Test field labels, placeholders, validation messages, required-field notices and confirmation messages.
Links and navigation
Confirm that menus, buttons and internal links lead to the correct target-language pages or screens.
Variables and placeholders
Check that variables, tags and placeholders remain intact and are displayed correctly in the final product.
Why screenshots and product context matter
Translators often receive strings without seeing where they will appear. A short phrase such as “Open”, “Order”, “Save” or “Close” can require different wording depending on whether it is a verb, noun, menu item, button or status label.
Screenshots, developer notes, character limits and access to a staging environment make it easier to choose the right wording before release and reduce unnecessary correction cycles.
Localization testing for websites
Website localization testing should cover both content and user journeys. A page can look correct in isolation while still sending the visitor into the wrong-language checkout, contact form or confirmation page.
Navigation
Test menus, breadcrumbs, language selectors and contextual internal links.
Forms
Check labels, placeholders, validation messages, consent text and confirmation screens.
Responsive layouts
Review desktop, tablet and mobile views because text expansion often creates problems at smaller breakpoints.
Metadata and links
Confirm localized titles, meta descriptions and links where they are included in the project scope.
Localization testing for software and mobile applications
User interface
Review menus, buttons, settings, onboarding, dialogs, notifications and system states in the localized build.
Functional flows
Test account creation, login, purchase, subscription, search, filters and other core workflows in the target language.
Platform behaviour
Check whether localization works consistently across relevant operating systems, browsers, devices and screen sizes.
A practical localization testing workflow
The exact process depends on the product, but a structured testing cycle makes issues easier to reproduce, assign and close before release.
What a useful localization bug report should contain
- Target language and locale
- Build or version number
- Page, screen or feature where the issue appears
- Screenshot or screen recording
- Current text and recommended correction
- Steps needed to reproduce the problem
- Issue type: linguistic, visual, functional or locale-related
- Severity or release priority
Localization testing mistakes to avoid
Testing only the translation file
A spreadsheet cannot show truncation, wrong navigation or incorrect implementation in the final product.
Skipping hidden states
Errors often remain in validation messages, empty states, pop-ups, notifications and rare user flows.
No developer context
Reviewers need enough technical context to know whether an issue is linguistic or caused by implementation.
No retesting
A reported issue is not closed until the corrected build has been checked again.
Localization and digital translation services
Continue reading
Localization Testing — Frequently Asked Questions
What is localization testing?
Localization testing checks whether a translated and localized product works correctly for users in a specific language and market. It covers language quality as well as layout, formatting, locale settings, navigation, forms, dates, currencies, units and other market-specific elements.
Is localization testing the same as translation proofreading?
No. Proofreading focuses mainly on language quality. Localization testing checks the translated content in context and also looks for interface, layout, functional and locale-specific problems.
When should localization testing be done?
Localization testing should be planned before release and performed on a representative localized build or staging environment. It is especially important after translated content has been integrated into the website, software or app.
What should be checked during localization testing?
Typical checks include untranslated strings, truncation, broken layouts, incorrect date or number formats, currencies, units, text direction, form validation, links, buttons, error messages, placeholders and terminology consistency.
Does localization testing include SEO?
Not automatically. Localization testing can verify localized pages, metadata and links, but SEO keyword research, search-intent adaptation and ranking strategy are separate tasks unless they are explicitly included in the project scope.
Who should perform localization testing?
The best setup often combines native-language reviewers or localization specialists with developers or QA staff. Linguistic and technical issues are easier to catch when both perspectives are included.
Preparing a website, app or software product for another market?
Send the content, target languages and information about the platform or product. We can review the localization scope, file formats, terminology and testing requirements before preparing a quote.