> For the complete documentation index, see [llms.txt](https://developers.weglot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.weglot.com/cms/wordpress/use-cases/exemple-of-snippet-to-translate-search-from-jetsearch-plugin.md).

# Exemple of snippet to translate search from JetSearch plugin

In this example, we use custom code to translate the search result provide by the plugin jetSearch

To translate the results of the JetSearch plugin, reverse-translate the search term back into your original language before the query runs, then declare the JSON keys JetSearch returns so Weglot translates them.

```php
add_action( 'jet-search/ajax-search/search-query', 'modify_weglot_search_query', 10, 2 );
function modify_weglot_search_query( $instance, $args ) {
    $parser_services      = weglot_get_service( 'Parser_Service_Weglot' );
    $parser               = $parser_services->get_parser();
    $language_services    = weglot_get_service( 'Language_Service_Weglot' );
    $original_language    = $language_services->get_original_language()->getInternalCode();
    $destination_languages = weglot_get_destination_languages();
    $current_language     = weglot_get_current_language();

    if ( $original_language === $current_language ) {
        return;
    }

    foreach ( $destination_languages as $destination ) {
        if ( $destination['language_to'] === $current_language && ! empty( $destination['custom_code'] ) ) {
            $current_language = substr( $destination['custom_code'], 0, 2 );
        }
    }

    if ( ! empty( $instance->search_query['s'] ) ) {
        $instance->search_query['s'] = $parser->translate( $instance->search_query['s'], $current_language, $original_language );
    }
}

add_filter( 'weglot_add_json_keys', 'custom_weglot_add_json_keys' );
function custom_weglot_add_json_keys( $keys ) {
    $keys[] = 'title';
    $keys[] = 'link';
    $keys[] = 'before_title';
    $keys[] = 'posts';
    return $keys;
}
```


---

# 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://developers.weglot.com/cms/wordpress/use-cases/exemple-of-snippet-to-translate-search-from-jetsearch-plugin.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.
