# Localization

The frontend language of Content Egg can be different from your main WordPress language and admin dashboard language. Content Egg has its own setting for this:

* Go to **Content Egg > Settings > Frontend**.
* Set the **"Website Language"** option to choose the language used for the frontend display.

<figure><img src="/files/mY8bfM22Lu5XjUM6DlNS" alt=""><figcaption></figcaption></figure>

For most use cases, you can translate frontend strings directly from the WordPress dashboard. Please follow this guide:

{% content-ref url="/pages/-MTVwlBz33RRB9fYuKte" %}
[Translation](/frontend/translation.md)
{% endcontent-ref %}

### Translation via POT File

Content Egg includes two localization files:

* One for the **admin interface**
* One for the **frontend display**

In most cases, you only need to translate the **frontend**.

These localization files are located in the plugin's `/languages/` directory.

#### **Recommended Method: Loco Translate**

The easiest way to manage translations is by using the [Loco Translate](https://wordpress.org/plugins/loco-translate/) plugin.

**Steps to Translate the Frontend Strings:**

1. Install and activate the Loco Translate plugin
2. Go to **Loco Translate > Home**, then click on `Content Egg`
3. In the **Content Egg Frontend (content-egg-tpl)** section, click on `New language`

<figure><img src="/files/XvoeH8WaZGtRaRzJGgrr" alt=""><figcaption></figcaption></figure>

4. Initialize new translations

⚠️ Important – Avoid Common Mistakes:

* In the **Language selection**, choose `Custom language`
* Enter the **two-letter language code** that matches the one set in\
  Content Egg > Settings > Frontend > Website Language.

**✅ Correct:** `content-egg-tpl-fr.po`\
\&#xNAN;**❌ Incorrect:** `content-egg-tpl-fr_FR.po`

<figure><img src="/files/eeLKAytapZ0mfN0EQLJl" alt=""><figcaption></figcaption></figure>

5. Click **"Start Translating"**
6. Translate all the required strings and save your changes


---

# Agent Instructions: 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:

```
GET https://ce-docs.keywordrush.com/customization/localization.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.