> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/manage-your-site/site-structure/multilingual-sections.md).

# Multilingual sections

Set localized titles for your site, sections, section groups, and navigation

Localized titles let you show different titles for different languages on your published site.

Visitors see the title that matches the language they’re browsing in. If a translation isn’t set, GitBook shows the fallback title instead.

Use `localizedTitle` for header links and buttons, footer links, and footer groups. See [Layout and structure](/docs/manage-your-site/customization/layout-and-structure.md).

{% hint style="info" %}
Localized titles only appear when your site includes content in more than one language.
{% endhint %}

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNkEGS7hzeqa35sMXQZ4X%2Fuploads%2FlEY5s6qXpEy6k1ivmeL6%2Flocalized.mp4?alt=media&token=d8221dc1-54e1-401b-8699-3acd65343fc3>" %}

### Set up localized titles

{% stepper %}
{% step %}

#### Open the structure editor

From your docs site, open **Site structure** in the site sidebar.
{% endstep %}

{% step %}

#### Find the title you want to translate

Open the title field for your site, a section, or a section group.
{% endstep %}

{% step %}

#### Set the fallback title

By default, the fallback title is set to the current section name.
{% endstep %}

{% step %}

#### Add each translated title

Open the language selector again and choose a language.

Enter the title for that language, then repeat for each language you support.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gitbook.com/docs/manage-your-site/site-structure/multilingual-sections.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.