Practical guides

Quality-check website translations beyond words

Two pages can be translated sentence by sentence yet offer different experiences. Multilingual testing must cover the complete journey in each language.

Go to the method

Two colleagues comparing French and English versions of a web page

Identify genuinely equivalent pages

Map URLs by language and the purpose of each page. Missing content may need a relevant alternative, not an artificial translation. Preserve promises and limits that genuinely differ by audience.

Google guidance on localized versions explains alternate signals. Hreflang links should point to real, accessible and coherent pages.

  • Page mapping documented.
  • Real reciprocal alternates.
  • No empty translation to fill a list.

Review meaning, facts and actions

Check prices, dates, units, deadlines, product names and conditions in each language. A correct translation of an old sentence is still wrong information. Ask someone familiar with the context to review specialist terms and promises.

Test buttons, forms, confirmations and associated emails. Language switching should lead to the current page equivalent where one exists; internal links should not always return to the original language. The multilingual guide

  • Facts and conditions checked.
  • Actions and messages translated.
  • Links stay in the right language.

Check layout and media

On phones, check that headings, buttons and cards tolerate longer words. Review reading direction, dates, numbers and special characters for each language. A menu that fits French may overflow in German or Finnish.

Check text embedded in images, captions, alternative text and downloadable documents. A photo may be shared if it represents the same reality, but its caption must suit the language and page.

  • Length and direction tested.
  • Alternatives and captions reviewed.
  • Documents suited to the audience.

Repeat checks after each change

Link each translation to its source and review date. A price or service change should trigger review of affected versions even if the template stays the same. Record decisions not to translate.

Before release, open every URL and verify status, title, canonical, alternates and navigation links. Check again after deployment: a route can work locally and fail on the server. The prelaunch guide

  • Source and date known.
  • Metadata and links checked.
  • Production check repeated.