Yandex Search SERP Scraper

Scrape organic search results from Yandex Search for any list of queries. Every organic result comes back as clean, structured JSON with title, URL, domain, breadcrumb, snippet, and its exact position in the SERP — ready for rank tracking, SEO monitoring, and competitor research. Ads and vertical blocks are skipped, so positions reflect the true organic ranking.

Why This Scraper

• Organic results only: ads and vertical blocks (news, images, videos) are filtered out, so every emitted position is a real organic rank.
• Position tracking built in: each result carries its query, 1-based SERP page, and a continuous 1-based position across the whole walk for that query.
• Two domains from one input: yandex.com and yandex.ru, with access checks handled automatically — no extra setup for either.
• Web, image, and video search: pick the vertical with searchType. Image and video rows add media fields (thumbnail, original image URL, duration, views, publish date, embed URL).
• Per-query pagination (page 1 is &p=0), stopping early when a page stops yielding new results.
• A hard total cap (maxItems) keeps run size and cost predictable.

Data You Get

Sample shape, values are illustrative placeholders, not from a live SERP.

Field	Example
query	best coffee grinder
page	1
position	1
title	Sample Store — Burr Coffee Grinders
url	https://www.example-store.com/burr-grinders
domain	example-store.com
breadcrumb	example-store.com › burr-grinders
snippet	Compare burr coffee grinders in stock at Sample Store...

How to Use

Search yandex.com:

{
  "queries": ["best coffee grinder", "espresso machine review"],
  "maxPages": 3,
  "maxItems": 100
}

Search yandex.ru with a region and pagination:

{
  "queries": ["купить кофемолку"],
  "domain": "yandex.ru",
  "lr": 213,
  "maxPages": 2
}

Input Parameters

Parameter	Type	Default	Description
queries	array		One or more search queries. Each query gets its own SERP walk.
searchType	string	web	web, images, or videos. Image and video rows carry extra media fields. Image search always runs on yandex.com and ignores domain and lr.
maxPages	integer	1	SERP pages per query, 1–10. The walk stops early if a page returns no new organic results.
domain	string	yandex.com	yandex.com or yandex.ru.
lr	integer	none	Yandex region code for the SERP locale, e.g. 213 (Moscow), 2 (Saint Petersburg), 21265 (San Francisco). Only meaningful on yandex.ru. Leave empty for auto-detection.
maxItems	integer	none	Hard cap on results emitted across the whole run. Leave empty for no cap (very large runs need a long run timeout).
proxySettings	object	Apify residential	Proxy configuration. Residential is the default (RU for yandex.ru, US for yandex.com) and returns the fullest result pages.

Access Checks

Yandex occasionally asks the search session to confirm it is operated by a person. The actor resolves these checks automatically and continues the walk. Resolving a check may involve a small per-check service fee (typically under half a cent, resolved within about a minute), and total check spending is capped: if a run would spend more than $1 per 1000 dataset items on checks, it stops with a clear message instead of spending more. The run summary always reports how many checks were resolved and the total spent.

Output Example

Sample shape, values are illustrative placeholders, not from a live SERP.

{
  "query": "best coffee grinder",
  "page": 1,
  "position": 1,
  "title": "Sample Store — Burr Coffee Grinders",
  "url": "https://www.example-store.com/burr-grinders",
  "domain": "example-store.com",
  "breadcrumb": "example-store.com › burr-grinders",
  "snippet": "Compare burr coffee grinders in stock at Sample Store..."
}

Plan Requirement

The default run works on any plan that includes Apify Proxy. An RU-region proxy selection is recommended for yandex.ru runs.

Resume & Recurring Updates

• Resume (resumeFromRunId): paste a previous run ID or dataset ID to continue an interrupted pull — results already collected there are skipped, never re-emitted. Cannot be combined with incremental mode.
• Incremental mode (incrementalMode): for daily or recurring monitoring of the same search. The first run returns everything as NEW; later runs return only NEW and UPDATED rows, with changeType, changedFields, firstSeenAt and lastSeenAt on every row. UNCHANGED rows are suppressed unless emitUnchanged is on; vanished rows are tombstoned EXPIRED only after a fully completed scan and only when emitExpired is on. State is keyed per search (or your optional stateKey) in a named key-value store.
• Position and page are not content: a pure rank move classifies UNCHANGED (the row still carries the live position), so only title/snippet/URL changes mark a row UPDATED.