Russian-language SERP monitoring
Use Yandex endpoints to turn russian-language serp monitoring into repeatable API requests with documented inputs and JSON responses.
Collect Yandex organic result positions, destination URLs, display breadcrumbs, snippets, and pagination, then pair them with language-aware Yandex autocomplete phrases.
Extract Yandex organic web results and localized autocomplete suggestions as structured JSON with page and language controls.
Endpoint families
2
Documented params
7
Examples
2
Live catalog snapshot
Active endpoints
2
Methods
GET
Required params
4
Schema refs
2
{
"platform": "Yandex",
"endpoint": "yandex-search",
"method": "GET",
"path": "/yandex/search",
"auth": "apiKey"
}Use cases
Extract Yandex organic web results and localized autocomplete suggestions as structured JSON with page and language controls.
Use Yandex endpoints to turn russian-language serp monitoring into repeatable API requests with documented inputs and JSON responses.
Use Yandex endpoints to turn regional search research into repeatable API requests with documented inputs and JSON responses.
Use Yandex endpoints to turn localized query expansion into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Yandex endpoint catalog — 2 endpoints, 7 documented request parameters, and 2 published response schemas — the same catalog Docs and Playground run against.
2 documented Yandex endpoints, grouped into 2 request families — Search and Suggest.
7 request parameters are documented across those Yandex endpoints, 4 of them required — the full input contract is public before you write any integration code.
2 of the 2 Yandex endpoints ship a recorded example response, and 2 carry a documented response schema — you can code against the real JSON before the first request.
Yandex endpoints document their error responses (400, 429, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
2 hosted MCP tools back the Yandex endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/yandex/search
/yandex/suggest
Endpoint catalog
/yandex/searchReturns organic Yandex web results for a query: title, destination URL, display URL, and snippet, with page-based pagination. Advertisements are not returned. Yandex challenges a portion of requests with a captcha; the service retries and returns 503 if every attempt is challenged, so callers should retry on 503. Results are localized by Yandex to the location the request is made from.
Response notes
- Yandex challenges a share of requests with a captcha. The service retries up to three times and never tries to solve the captcha; if every attempt is challenged it returns `503`, and the call can simply be retried. - Yandex localizes results to the egress location, so the same query can return a different region's ranking across calls. - `description` is omitted for rows where Yandex shows no snippet (for example some social profiles); `display_url` is Yandex's host breadcrumb. - A response page with no organic results and no captcha marker is reported as `503` (parser drift), never as an empty success. - `pagination.next_page` is present only when Yandex offers a next page and `page` is below `10`.
MCP tool yandex_search
/yandex/suggestReturns Yandex search-box autocomplete completions for a query prefix, in Yandex's own ranking order. `lang` is the two-letter Yandex UI language (en, ru, tr, ...) and re-ranks the list; Yandex ignores codes it does not support.
Response notes
- Yandex sometimes inlines answer rows (for example weather) in the list; those rows are reduced to their query text. - Yandex ignores a well-formed `lang` it does not support; only the format is validated here. - A prefix with no completions returns a valid empty `suggestions` array, not an error.
MCP tool yandex_suggest
Related APIs
Search & Web Discovery
Use a Google Trends API — an API for Google Trends data — to track search demand, trending terms, interest over time, regional interest, related and rising queries, plus Google Suggest discovery, as structured JSON for demand research and trend monitoring.
Search & Web Discovery
Extract Google News results — headlines, source names, article URLs, snippets, thumbnails, and recency — as structured JSON for media monitoring, brand mention tracking, and news aggregation workflows.
Search & Web Discovery
Extract Google Jobs results — job titles, listing snippets, and locations — as structured JSON for job-market intelligence, hiring-trend analysis, and recruitment sourcing workflows.
How to scrape Yandex
Yandex's current Webmaster documentation describes a crawler-built index and explains that indexed pages must be accessible to Yandex's crawler, while current Search support pages document region, language, date, and suggestion settings. Crawlora's /yandex/search contract returns normalized organic rows and excludes advertisements; /yandex/suggest returns ranked query completions. Web search accepts 1-based page values through 10 and localizes to the service egress region. Suggest accepts count through 20 and a two-letter UI language such as en, ru, or tr.
GET /yandex/search with required q and optional page from 1 through 10. Each organic row carries position, title, URL, display_url, and description when Yandex shows a snippet.
Yandex localizes results to Crawlora's egress location, so the endpoint is unsuitable for claiming a caller-selected city or country. Record run time and observed market context when comparing rankings.
Store pagination.page and follow pagination.next_page only when present. A page with neither organic rows nor a captcha marker is treated as parser drift and reported as an upstream failure, not a successful empty SERP.
GET /yandex/suggest with q, count from 1 to 20, and a two-letter lang such as ru. Yandex may reduce inline answer rows to their query text and silently ignore a well-formed language code it does not support.
FAQ
It returns query, organic rows with position, title, destination URL, Yandex's display breadcrumb, and description when present, plus page and next_page metadata. Advertisements are excluded.
No region parameter is exposed in this contract. Results are localized by Yandex to the service egress location, so callers should preserve that limitation when interpreting rankings.
Pass a two-letter UI language such as en, ru, or tr. The endpoint validates the format, while Yandex can ignore a syntactically valid language it does not support. Count accepts 1 through 20.
On 2026-10-06, page 1 for искусственный интеллект returned 10 organic rows and next_page 2; the first row was the Russian Wikipedia article. The suggest prefix искусственный with lang=ru returned five phrases led by искусственный интеллект. These are observations, not guaranteed rankings.
Crawlora retries across browser profiles and returns a documented 503 when every attempt is challenged. Treat that as retriable upstream unavailability, not an empty result set.