> ## Documentation Index
> Fetch the complete documentation index at: https://visitdocs.planpoint.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Languages

> Publish a Visit in up to seven languages and translate your own text.

English is the base language and is always available. On top of it you can switch on any of six more:

| Language | Native name | Code |
| -------- | ----------- | ---- |
| French   | Français    | `fr` |
| Spanish  | Español     | `es` |
| German   | Deutsch     | `de` |
| Dutch    | Nederlands  | `nl` |
| Italian  | Italiano    | `it` |
| Polish   | Polski      | `pl` |

## Enabling languages

Everything to do with languages lives on one page: **Languages → Translations** in the property sidebar. At the top, **Languages offered** lists the six optional languages with their flags — tick the ones this property should offer.

<Frame caption="Pick the languages this Visit should offer">
  <img src="https://mintcdn.com/planpoint-visit/0E3RRUq_T5nIh8kn/images/features/languages-settings.png?fit=max&auto=format&n=0E3RRUq_T5nIh8kn&q=85&s=997b2cdfc280d86bcf96fc12b2529b75" alt="Languages offered grid with flags and checkboxes" width="1600" height="784" data-path="images/features/languages-settings.png" />
</Frame>

As soon as more than one language is active, a flag button appears in the viewer's filter row. Visitors pick a language from the dropdown, which shows each language under its own name.

<Frame caption="Switching language in the viewer — interface labels and your own text both follow">
  <video src="https://mintcdn.com/planpoint-visit/0E3RRUq_T5nIh8kn/videos/features/languages.mp4?fit=max&auto=format&n=0E3RRUq_T5nIh8kn&q=85&s=3c5cb434694000ee5561a0b4d21cbdb5" controls muted loop playsInline preload="metadata" className="w-full rounded-lg" data-path="videos/features/languages.mp4" />
</Frame>

## Auto-detect

**Auto-detect the visitor's language** is a checkbox at the top of the page. When it is on, the viewer opens in the visitor's browser language if you have enabled it, and falls back to English otherwise. Visitors can always switch manually.

## One URL per language

Once a language is enabled, a **Viewer URLs per language** list appears with a copyable link for each — English on the plain URL, the rest with `?lang=xx`. This exists for listing software and MLS feeds that take a separate URL per language.

<Frame caption="A ready-made link per language, with a Copy button on each row">
  <img src="https://mintcdn.com/planpoint-visit/0E3RRUq_T5nIh8kn/images/features/language-urls.png?fit=max&auto=format&n=0E3RRUq_T5nIh8kn&q=85&s=2e74e7f478ee148eb06e3d799537bbd8" alt="Per-language viewer URLs with flags and copy buttons" width="1600" height="1084" data-path="images/features/language-urls.png" />
</Frame>

## Interface vs your text

Two different things get translated:

* **Interface labels** — *Request Information*, *All Floors*, *Back to exterior* and the rest. These ship translated; you do not have to do anything.
* **Your content** — property description, room names, room descriptions, hotspot titles, form copy. These are yours to translate.

## Translating your content

Below the language toggles, each enabled language gets its own expandable panel showing how many strings are done out of the total. Open one and you get every piece of text you have written, grouped by where it appears, with the English original beside an empty field to translate into.

<Frame caption="Every string you wrote, in one place, per language">
  <img src="https://mintcdn.com/planpoint-visit/0E3RRUq_T5nIh8kn/images/features/translations-tab.png?fit=max&auto=format&n=0E3RRUq_T5nIh8kn&q=85&s=52ae6c9efd76535c577d1b0906b28496" alt="Expanded French panel showing English source text next to translation fields" width="1600" height="1171" data-path="images/features/translations-tab.png" />
</Frame>

<Steps>
  <Step title="Enable the languages first">
    Panels only appear for languages that are ticked above.
  </Step>

  <Step title="Finish the English content first">
    Adding a room after you translate means coming back for it. Translate last.
  </Step>

  <Step title="Fill in what matters">
    The property description, room names and hotspot titles carry the most weight. Long room descriptions can come later.
  </Step>

  <Step title="Check the viewer">
    Open the Visit, switch language with the flag button and read it through.
  </Step>
</Steps>

<Note>
  Anything you leave blank falls back to the English original — a partly translated Visit still works, it just mixes languages.
</Note>

## How a language is chosen

1. An explicit `?lang=` in the URL wins.
2. Otherwise, with **auto-detect** on, the visitor's browser language is used — if you have enabled it.
3. Otherwise English.

Link straight to a language by appending the code:

```
https://visit.planpoint.io/42-oak-avenue?lang=fr
```

Useful when you are emailing a specific buyer — they land in their own language without touching the switcher.

## Terminology overrides and languages

[Label overrides](/customize/terminology) apply to the English base only. Translated locales use the built-in dictionaries, so an English override does not leak into the French version.