# Translate your locator into several languages

Source: https://locator.handledlocal.com/docs/multilingual-locator

Primary wording, a translation per language, and a visitor matched to the closest one, with one embed.

## One embed, every visitor's language

French visitors read French, German visitors read German, and the rest read whatever you set as the primary wording. The locator matches each visitor's browser language to the closest translation you have added, and falls back to the primary. One embed handles all of it; nothing changes on the page.

This guide is the recipe. The mechanics of matching and fallback are on the [several languages](https://locator.handledlocal.com/docs/widget-languages) page.

## 1. Write the primary wording

Open **Appearance → Labels**. Every phrase the locator shows is there: the search placeholder, "Get directions", "Open now", the days of the week, the empty states. Write them in the language most visitors read. This is also where "Nearby locations" becomes "Nearby dealers" for a single-language locator.

## 2. Add a language

1. **Open Language**: Under **Language**, add the language by its code, `fr`, `de`, `es-MX`.
2. **Translate the phrases**: Each phrase shows the primary next to an empty field. Fill the ones that matter first: the search placeholder, the filter headings, the buttons. A phrase left blank falls back to the primary, so a partial translation is still a working one.
3. **Add the next**: Repeat per language. Regional variants (`pt-BR` and `pt-PT`) can differ or share.

## 3. Test as a visitor

Change your browser's preferred language and reload the page. The locator picks the closest match: `fr-CA` finds `fr` when there is no `fr-CA`. The matching rules, including what happens when a visitor lists several languages, are under [how a visitor is matched](https://locator.handledlocal.com/docs/widget-languages#matching).

> **Location content is not translated**
>
> Labels, buttons, filter group headings and the locator's messages are interface text, and those are what a language covers. A location's name, description, tag names and custom field values are stored once and shown as written. Write a description in the language of its own customers, or keep descriptions short and let the interface carry the language.

## Tag names and custom field labels

Tag names and custom field labels are stored once, like location data, and are not translated. Name a tag in the language of the visitors who will filter by it, or use a name that reads the same across languages, a product name or a brand, which is what product and dealer-tier tags usually are anyway.

## A single non-English locator

If every visitor reads the same non-English language, there is nothing to add: write the primary wording in that language and stop. The [single-language notes](https://locator.handledlocal.com/docs/widget-languages#one-language-only) cover date and distance formatting.
