Landinker

Translations

The Translations section (under Content) is your group's centralized text dictionary: define your translation keys and copy per language once, and use them across your landing pages.

Instead of building and maintaining a distinct landing for each language, Landinker lets you link each text field to a dictionary key. The page resolves and serves automatically in the appropriate language for each visitor.

Group languages

• Use the Languages button to configure your group's active language list.
• You can enable up to 20 languages per group, using standard BCP 47 codes (e.g. es, en, pt, en-US, es-419).
• Route control: you cannot add a language if any landing in your group already uses that route (for example, if you have a page at /es or /en/promotions), avoiding ambiguity with language prefixes on public URLs.

Key dictionary

Each dictionary entry consists of:

• Key: lowercase identifier format (e.g. hero.title, cta.button, nav.contact).
• Values: translated copy for each language enabled in the group (up to 5,000 characters per value).

You can register up to 3,000 translation keys per group. You can search the table by key name as well as translated copy.

Predefined keys

Landinker provides built-in system keys for standard texts and components.

• These keys automatically appear in your list marked as Predefined, without needing to create them manually.
• You can modify a predefined key to customize its copy for your group. Upon doing so, the key is marked as Modified.
• If you wish to revert to original system text, the Reset action removes your group's local version and restores the built-in defaults.

Paths per language

Each language of a landing is published with the language in front: /precios in English is /en/precios. If you want the address translated too, in the landing settings (Languages section) you can write each language's path, for example /pricing for English. The English page then lives at /en/pricing and the Spanish one at /es/precios.

• The language in front decides: someone who comes in at /es/pricing is taken to /es/precios, and /en/precios goes to /en/pricing.
• Paths with parameters: the translated path keeps the same ones, for example /product/:id for /producto/:id.
• Internal links on your landings point straight to the path of the language the page is shown in.
• A translated path can't repeat another landing's path or a redirect's, nor start with a language.

Availability

Translations are available on the Pro and Enterprise plans.

Who can use it

The Owner and members with landing editing permissions can create, modify, and delete keys, as well as configure group languages. Members with read-only permissions can view the dictionary.