Communik.io : Site & App builder
communik.io

Translate a CMS record and its address

Save a separate record translation and verify that the published detail page still points to the same record.
Published on 11/15/2026

1. Make the fields localizable

In Data, open the collection. Review which fields should vary by language and enable localization for their columns. A title or introduction often changes by language, while a shared code or inventory value can stay the same. Configure the site language as well.

2. Translate a record in its editor

Open the record. Use its Lang menu to choose the target content language, enter the translation and save the row. Switch back to the default language to compare the original. The example stores a French headline while keeping the English value.

The title entered into the French version of the CMS record.

3. Set the two parts of a CMS address

In Translations, expand the collection to find its records. Translate the detail template’s path and each record’s slug separately. Keep [slug] in the template and use a short, unique slug for the record. Save each value, then publish to the private preview.

The localized template path retains its record placeholder.
The French slug stored separately from the original.

4. Check that it is still the same record

Open the old language and the translated version. Compare the title, introduction and language paths, then use the language links to make a round trip. The Willow example visits both versions of the same journal entry on desktop and mobile. Check the title and description in search metadata when your template uses translated fields.

The same journal record reached at its translated address.

See also Translate page titles and descriptions for search.