Communik.io : Site & App builder
communik.io

Check each language version before going live

Test the path a visitor follows through translated pages, links and actions.
Published on 11/15/2026

1. Choose a short visitor journey

Start with the home page, a key service page, a CMS record and a page with an action such as a contact form. Write down the languages and the result you expect for each step. Use test data for anything that writes a record.

2. Find missing values and review visible text

Choose the content language in Lang. Check headings, menus, buttons and error messages. In Translations, use Untranslated to find missing values, then proofread the completed ones. Check how long strings wrap on a narrow screen.

The filter used to find untranslated items.

3. Follow published links on desktop and mobile

Publish privately, open each language path directly, reload it and navigate as a visitor. Switch languages on a page and on a CMS record, and return to the language you started with. Check the page heading, URL, metadata and layout at both widths.

The translated page reached through its language link.
The same journal record reached at its translated address.

4. Test each important action until it completes

For a form, trigger a validation error, send a valid test response and find it at its destination. For booking or checkout, verify the stored result and test notifications through the relevant test accounts. If a step depends on external access, record what access is needed and keep that step open.

5. Decide whether to share the version

Mark each step verified, to fix or waiting on external access. Recheck a corrected page and the actions immediately before and after it. Resolve blockers on essential tasks before sending visitors to the new language.

See also Translate page addresses and check language links.