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

# Yandex

With Talordata SERP API, you can configure **Yandex Search** queries, including localization, geographic targeting, and advanced parameter output options.

<details>

<summary><strong><code>q</code> ,</strong>Search Query<strong>(Required)</strong></summary>

Define the search query for data crawling (default value: q=pizza). Any keywords in any language are supported.

**Example Request:**

Example with `q`:<mark style="color:blue;">pizza</mark> parameter

```sh
curl -X POST https://serpapi.talordata.net/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=yandex" \
 -d "text=pizza" \
 -d "json=1"
```

</details>

## Localization

<details>

<summary><code>yandex_domain</code> <strong>,</strong>Domain<strong>(Optional)</strong></summary>

This parameter defines the domain name used for crawling, with a default value:`yandex.com`.\
**Available options:**

* `yandex.com`
* `yandex.ru`
* `yandex.com.tr`\
  (Other regional domains supported)

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,`url`:<mark style="color:blue;">yandex.com.tr</mark>

```sh
curl -X POST https://serpapi.talordata.net/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=yandex" \
 -d "text=pizza" \
 -d "yandex_domain=yandex.com" \
 -d "json=1"
```

</details>

<details>

<summary><strong><code>lang</code> ,</strong>Language<strong>(Optional)</strong></summary>

This parameter defines the language used for search results during crawling, with a default value of "`en`". It is a two-letter language code (for example, `en`, `ru`, `es`).\
**Common values:**

* `en` (English)
* `ru` (Russian)
* `es` (Spanish)\
  Full list: [Yandex Language Codes](https://yandex.com/support/search/query-language.html)

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,`lang`:<mark style="color:blue;">en</mark>

```sh
curl -X POST https://serpapi.talordata.net/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=yandex" \
 -d "text=pizza" \
 -d "json=1" \
 -d "lang=en"
```

</details>

## Geographical Location

<details>

<summary><strong><code>lr</code> ,</strong>Location<strong>(Optional)</strong></summary>

Specify the region for search results (e.g., `lr=Moscow,Russia` displays only results from Moscow), which takes priority over IP-based geolocation.

\
Format: `lr=<Region_Name>` (e.g., `lr=Moscow,Russia`)

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,`lr`:<mark style="color:blue;">India</mark>

```sh
curl -X POST https://serpapi.talordata.net/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=yandex" \
 -d "text=pizza" \
 -d "json=1" \
 -d "lr=India"
```

</details>

<details>

<summary><strong><code>rstr</code> ,</strong>Location Strict Check<strong>(Optional)</strong></summary>

Dual filtering:

* Region lock: Forces results to match `lr` region
* Safe search: `rstr=family` blocks adult content

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,`rstr`:<mark style="color:blue;">true</mark>

```sh
curl -X POST https://serpapi.talordata.net/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=yandex" \
 -d "text=pizza" \
 -d "json=1" \
 -d "rstr=true"
```

</details>

## Pagination

<details>

<summary><strong><code>p</code> ,</strong>Page number<strong>(Optional)</strong></summary>

Page control (starts at `p=0`).&#x20;

It needs to be used in conjunction with the parameter for the number of items per page.

Example: `p`=2 retrieves results from the 3rd page.

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,`p`:<mark style="color:blue;">2</mark>

```sh
curl -X POST https://serpapi.talordata.net/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=yandex" \
 -d "text=pizza" \
 -d "json=1" \
 -d "p=2"
```

</details>

## Advanced Parameters

<details>

<summary><strong><code>within</code> ,</strong>Time period<strong>(Optional)</strong></summary>

Time/domain restrictions:

* Time range: `within=7d` (Past 7 days)
* Domain filter: `within=example.com`

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,`within`:<mark style="color:blue;">2</mark>

```sh
curl -X POST https://serpapi.talordata.net/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=yandex" \
 -d "text=pizza" \
 -d "json=1" \
 -d "within=2"
```

</details>

If you need further assistance, feel free to contact us via **live chat** or email **<support@talordata.com>**.


---

# 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://docs.talordata.com/serp-api/query-parameters/yandex.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.