Go to example tasks

Track Tatar Yandex SERPs at scale

Pull Tatar Yandex search results in bulk, pay per result: organic listings with titles, links, and snippets as JSON, language preset to Tatar.

Try for free
Яндекс Yandex  | Парсер Поиска Яндекса
Яндекс Yandex | Парсер Поиска Яндексаjohnvc/yandex-scrape-yandex-search-results-at-scale---per-result
Result type
Results in item
Query
Domain
+6 fields
Text
Number
Boolean
List
Object

Input

Search Query(required):Казан яңалыклары
Yandex Domain:yandex.ru
Language:tt
Location/Region:225

Output fields

Result type
Results in item
Query
Domain
Language
Region ID
Page
Pages processed
Total organic results
Run time

How it works

Sign up on Apify or log in

The Яндекс Yandex | Парсер Поиска Яндекса Actor is ready to run with the inputs already set for "Track Tatar Yandex SERPs at scale". Sign up or log in and you'll land in Apify Console with a copy of this exact task.

Start the "Track Tatar Yandex SERPs at scale" task

The Яндекс Yandex | Парсер Поиска Яндекса Actor will start running based on the input automatically. You can also change all the input fields, like search query, yandex domain, and more, to match your specific use case.

Receive the "Track Tatar Yandex SERPs at scale" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as result type, results in item, query, and more.

Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also run the "Track Tatar Yandex SERPs at scale" task via API.

Image

Integrate "Track Tatar Yandex SERPs at scale" into your workflow

Connect "Track Tatar Yandex SERPs at scale" with 100+ integrations, or run it via API or MCP.

Webhook

Webhook

n8n

n8n

Make

Make

Zapier

Zapier

Airbyte

Airbyte

Keboola

Keboola

IFTTT

IFTTT

Hubspot

Hubspot

GDrive

GDrive

Gmail

Gmail

Apify MCP

Apify MCP

GitHub

GitHub

Slack

Slack

LangChain

LangChain

LlamaIndex

LlamaIndex

Flowise

Flowise

Pinecone

Pinecone

OpenAI

OpenAI

Mastra

Mastra

Clay

Clay

Frequently asked questions

Each item is one SERP page for Казан яңалыклары: yandex_domain yandex.ru, lang tt, lr 225, page_number, pages_processed and search_timestamp, then the Tatar organic listings as position, title, link, snippet and date.

The example searches Казан яңалыклары on yandex.ru with lang tt and lr 225, the id for all of Russia, since Tatar has no Yandex domain of its own. Keep lang tt and narrow lr to a city id when you want a local view of Kazan or elsewhere.

run-sync-get-dataset-items on the Apify API returns the Tatar rows as JSON at once. For a keyword list, call it once a query via apify-client, swapping Казан яңалыклары each time and leaving yandex.ru, lang tt and lr 225 fixed.

Schedule it from the Actions menu in Apify Console with 0 6 1 * *, the first of the month at six. Monthly is plenty for a slow-moving Tatar SERP, and the stored datasets form a timeline for Казан яңалыклары on yandex.ru.

Install https://mcp.apify.com/?tools=actors,docs,johnvc/yandex-scrape-yandex-search-results-at-scale---per-result in Claude or Cursor, ask for the Tatar SERP of Казан яңалыклары and the Actor runs with lang tt, lr 225.

Pay per event: the Actor charges a start fee for the Tatar run and then a fee for every page of results it fetches from yandex.ru. The old per-result name in the URL is history; nothing is billed for a listing and empty pages are free.

Both run on yandex.ru with lr 225. The Tatar task sets lang tt, which tells Yandex to return Tatar-language results, while Track Russian Yandex SERPs at scale uses lang ru. Pass lang as tt,ru to see both languages in a single run.