> For the complete documentation index, see [llms.txt](https://ae-docs.keywordrush.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ae-docs.keywordrush.com/localization.md).

# Localization

The plugin includes two localization files — one for the admin area and one for the frontend. In most cases, you only need to localize the frontend.

Localization files are located in the `language` folder of the plugin.

For the most convenient way to translate from the admin area, we recommend using the [Loco Translate](https://wordpress.org/plugins/loco-translate/) plugin. You'll need to configure it before editing frontend translation files. Go to `Loco Translate` → `Plugins` and find `Affiliate Egg`. Then go to the **Setup** tab and configure the following settings. (These may be configured automatically — if so, leave them as-is.)

![](/files/-M5WT4KbkFkZcJcR6NrE)

Save the file. You can now create a new language or use an existing one for frontend localization.

To create a new language, click **New language**.

![](/files/-M5WTFAvabD9_RO_bVhG)

{% hint style="warning" %}
The plugin uses its own language setting for the frontend and does not use WordPress's language setting. Set the language in `Affiliate Egg` → `Settings` → `Website language`.
{% endhint %}

Select **Custom language** and enter the locale (**two letters**) that matches the value set in `Affiliate Egg` → `Settings` → `Website language`.

When creating a new language in Loco Translate, the locale must not include a regional suffix. For example, for Finnish, the filename must be `fi`, not `fi_FI` as is standard in WordPress.

![](/files/-M5WU-Z_87cyqV99n-ji)


---

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

```
GET https://ae-docs.keywordrush.com/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.