Localization checklist

Localization QA checklist for multilingual websites

Review language routing, text expansion, responsive layouts, locale formats and translated content with this localization QA checklist.

Updated August 28, 20268 minute readBy the VisualRunner team

Localization QA verifies that translated content works inside the real website—not only in a string table. A good review covers language routing, layout, imagery, formats, interactions and the production behavior of every important locale.

✓Language routing and metadata
✓Text expansion and overflow
✓Locale-specific formats
✓Cross-language visual review
1

Map every language variant

Document the supported locales and how each one is addressed: path prefix, subdomain, domain, query parameter or cookie. Confirm language switching preserves the intended page and does not silently fall back to the default language.

2

Review text expansion in context

Capture navigation, headings, buttons, forms, cards and dialogs at representative viewports. Look for clipping, wrapping that hides meaning, overlapping labels and containers with fixed heights.

  • Long navigation labels
  • Buttons and compact controls
  • Tables, filters and breadcrumbs
  • Mobile menus and dialogs
3

Verify locale-specific content

Check dates, times, numbers, currencies, addresses and units. Confirm translated images and legal text are present where required, and ensure placeholders or untranslated strings do not reach production.

4

Check language metadata

Verify the page language, title, description, canonical URL and hreflang implementation. Confirm each language page links to the correct alternatives and that canonical tags do not collapse valid localized pages into one URL.

5

Test directionality and interactions

For right-to-left languages, review alignment, icon direction and mixed-direction text. Exercise forms, validation messages, menus, tabs and modal states in each priority locale.

6

Preserve comparable evidence

Use consistent viewports and states across languages and releases. A visual history makes it easier to identify when overflow or missing content was introduced.

Questions

Frequently asked questions

What is the difference between translation QA and localization QA?

Translation QA focuses on linguistic correctness. Localization QA also checks routing, layout, formats, imagery, interaction behavior and cultural suitability in the rendered product.

Which languages should be tested first?

Prioritize high-traffic locales, languages with substantial text expansion, right-to-left languages and markets tied to important campaigns or revenue.

Can screenshots find every localization problem?

No. Screenshots reveal visual and contextual issues, but qualified language reviewers and functional checks remain essential.

Continue exploring

Related resources

Turn the checklist into a repeatable workflow

Discover your pages, capture the important states and keep a visual history of every meaningful change.

Start free trial