# Translating with Polylang

Unlike WPML, Polylang supports string translations natively.

## Follow these steps to translate the plugin correctly

1\) Place the search shortcode somewhere visible on any page (or use the widget)

2\) Open up that page, so the translations will get registered first

3\) Open up the **Settings -> Languages** menu

![](http://i.imgur.com/TMANUyG.png)

4\) Navigate to the **String Translations** panel, and change the **View all groups** option to "ajax-search-pro", so only strings from Ajax Search Pro are visible

![](http://i.imgur.com/u98occx.png)

5\) That's it. Now the list will display all ajax search pro related translatable texts. All you need to do now is to translate them as you like :)

*Please note that the number after each text in the Name column represents the search instance. This way different search instances with the same text can have different translations.*

![](http://i.imgur.com/1oxv6J9.png)


---

# 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://documentation.ajaxsearchpro.com/translating-components/translating-with-polylang.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.
