Go to example tasks

Track Latvian Yandex SERPs at scale

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

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):labākie telefoni 2026
Yandex Domain:yandex.com
Language:lv
Location/Region:111

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 Latvian 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 Latvian 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 Latvian 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 Latvian Yandex SERPs at scale" task via API.

Image

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

Connect "Track Latvian 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

The Latvian task writes one item a page: yandex_domain yandex.com, lang lv, lr 111, page_number, pages_processed, search_timestamp and an organic_results list of position, title, link and snippet for labākie telefoni 2026.

labākie telefoni 2026 on yandex.com, lang lv, lr 111. The lr value is the Europe region id, the replacement for the retired yandex.eu domain; lang lv does the Latvian work. Put your own keyword in text and leave the rest.

Run it from code: the Apify API takes the task id plus an input body, and run-sync-get-dataset-items hands back the Latvian items as JSON. labākie telefoni 2026 is only the example; send any text with yandex.com, lang lv and lr 111.

Set a schedule under Actions in Apify Console (0 8 * * * is eight daily) and add the Google Sheets integration or an n8n flow, so every Latvian snapshot of labākie telefoni 2026 on yandex.com lands in a sheet or Slack channel.

Via the MCP server https://mcp.apify.com/?tools=actors,docs,johnvc/yandex-scrape-yandex-search-results-at-scale---per-result, Claude can run the Latvian preset (lang lv, lr 111) on labākie telefoni 2026 and quote the listings.

Cost follows max_pages rather than run time or result count: a start fee plus a page fee for each Latvian SERP page the run fetches. The per-result slug is a legacy name; billing is by page now. Pages with nothing on them are not billed.

lang lv against lang lt. Everything else matches: yandex.com, lr 111 for Europe and the same output fields. Set lang to lv,ru when Russian-language pages matter for the Latvian market as well.