> For the complete documentation index, see [llms.txt](https://nghiaxchis.gitbook.io/ncmaz-blog-magazine-full-site-editing-wordpress/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nghiaxchis.gitbook.io/ncmaz-blog-magazine-full-site-editing-wordpress/basics/localization.md).

# Localization

Every WordPress theme contains some texts that need to be translated into your language if you are building a non-English website. This theme if fully translation ready.

The theme also supports RTL languages.

To enable your language in the WordPress website, please [switch WordPress into the desired language localization](https://developer.wordpress.org/advanced-administration/before-install/in-your-language/).

{% hint style="info" %}
**Adding languages into WordPress**

Check out tutorial on how to [install WordPress in your language](https://www.wpbeginner.com/wp-tutorials/how-to-install-wordpress-in-other-languages/).
{% endhint %}

{% hint style="info" %}

#### **Tip:** Multilingual Navigation block

If you are building a multilingual website and having issues making the Navigation block multilingual, try using [**Classic Menu in Navigation Block** plugin](https://wordpress.org/plugins/classic-menu-in-navigation-block/). It allows you to display classic menus in Navigation block which should resolve the issues.

The plugin was tested and working well with popular *Polylang* and *WPML* multilingual plugins.
{% endhint %}

### **Translating in WordPress admin**

If you would like to translate the theme directly in your WordPress dashboard you need to use a specialized plugin. Check out [**Loco Translate** plugin](https://wordpress.org/plugins/loco-translate/) and instructions on how to use it at [beginner's guide](https://localise.biz/wordpress/plugin/beginners) and [technical overview](https://localise.biz/wordpress/plugin/overview).

#### Translate Plugins Too!

Your website is built with WordPress system itself, a theme and some plugins.

There is a high chance that [WordPress itself is already translated into your language](https://developer.wordpress.org/advanced-administration/before-install/in-your-language/). So, you don't have to translate it on your own. You have also learned how to translate the theme above. But what about plugins and their texts?

If you are lucky, your plugin contains your language translations already and you don't have to do anything. But if you need to translate a plugin, the best advice is to check the plugin's documentation for the best approach.

Alternatively you can also use [**Loco Translate** plugin](https://wordpress.org/plugins/loco-translate/) (again) to translate your plugins directly in your WordPress admin area.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://nghiaxchis.gitbook.io/ncmaz-blog-magazine-full-site-editing-wordpress/basics/localization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.