Yandex rank tracking
Check where your pages rank on Yandex for each target keyword and language. Store position and URL per day to see which pages gain or lose ground in Russian, Turkish or Kazakh results.
- 1search
- Rank history
Yandex search results, ranked and typed: position, title, URL, display URL and snippet for any query, in 13 regional languages, plus a Yandex Maps places scraper on the list. Public data only.
Pick the data you need. Yandex Search takes one keyword and gives you clean JSON back for 2 credits per successful call. The Yandex Maps places scraper is on the list without a live path yet.
GET/api/v2/yandex-search/Organic yandex.com results for one query: position, type, title, URL, display URL and snippet, a page at a time.
INqueryPlaces for a query such as "coffee in Moscow": name, category, address, phone, website, coordinates, rating, review count, opening hours, metro and photos.
Pick an endpoint, fill in the input and press Run. Without a key you see the catalog sample and nothing is billed. With your API key it runs a real call from your browser.
Every successful call costs 1 credit, whether the page holds one profile or a page of comments. Failed calls cost nothing. A free tier lets you try it first.
On Pro, 1,000 calls at 1 credit cost $1.58. Scale brings that to $1.20, so 250,000 Yandex calls a month is $299.
See all plans →| Plan | Price / mo | Credits / mo | Per 1,000 calls |
|---|---|---|---|
| Free | $0 | Free tier | — |
| Hobby | $29 | 15,000 | $1.93 |
| Pro | $79 | 50,000 | $1.58 |
| Scale | $299 | 250,000 | $1.20 |
Built to be easy to start with, even if you've never scraped a search engine. Here's how to get Yandex results in a few minutes:
yandex-search returns the organic results for one query on yandex.com.queries per call, plus an optional language such as ru, tr or kk.next_cursor; pass it back as cursor for the next page. null means the last page. The language stays locked in the cursor.X-API-Key header, or ask your AI agent over MCP.Every endpoint takes the same kind of input.
You don't know the items yet: find them with a keyword.
python tutorial// GET /api/v2/yandex-search/ { "queries": "python tutorial", "language": "en" }
| Send this | Parameter | And you can get |
|---|---|---|
| Keyword | queries | Ranked organic results with title, URL, display URL and snippet |
| Language | language | Regional ranking in en, ru, uk, de, fr, tr, be, kk, uz, az, lv, lt or et |
| Cursor | cursor | The next page of the same query and language |
| Raw mode | raw_data | The raw upstream payload instead of the formatted results |
Optional on list endpoints: cursor (pass back next_cursor for the next page). Auth is one header: X-API-Key. Send parameters in the query string (GET) or as a JSON body (POST).
The one thing to know: each data type has its own shape. Field names stay the same on every call, so code and agents read them directly. Samples below come from the live catalog.
// GET /api/v2/yandex-search/?queries=python tutorial // one item of data.results · catalog sample { "position": 1, "type": "organic", "url": "https://docs.python.org/3/tutorial/index.html", "title": "The Python Tutorial — Python 3.14.7 documentation", "display_url": "Docs.Python.org", "snippet": "This tutorial introduces the reader informally to the basic concepts and features of the Python language and system.", "page": 0, "query": "python tutorial" }
Every response is {"success": true, "data": {…}}: your input echoed back, the result under its own key (profile, posts, comments…) and next_cursor for the next page.
Public Yandex results power SEO in Russian-speaking and CIS markets, competitor research and content planning. Here are three common jobs and the Yandex scraper endpoint each one uses.
Check where your pages rank on Yandex for each target keyword and language. Store position and URL per day to see which pages gain or lose ground in Russian, Turkish or Kazakh results.
Run your category keywords and count how often each competitor domain appears in the top results. Use display_url to group results by site and spot new entrants early.
Read the titles and snippets that rank for a topic in a new market before you write for it. Compare languages side by side to see how intent changes between regions.
Yandex Scraper fetches clean, structured Yandex search results at a fixed cost per call: built for rank tracking, market research and AI agents.
Each request reads Yandex at call time, so results reflect the ranking at that moment.
Same field names on every call, numbers as numbers, ready for code, sheets or an LLM.
Results come a page at a time with next_cursor; run up to 3 requests in parallel per key.
Every result has the same fields: position, type, URL, title, display URL, snippet and page.
The Scrapier MCP server reaches every Yandex endpoint from Claude Code, Cursor, Windsurf and VS Code with one command.
Plain REST: Python, Node.js, cURL, n8n, Make, Zapier or Google Sheets.
Public data only. No Yandex account, login or Yandex Cloud setup; Scrapier routes the request for you.
When Yandex changes its pages, Scrapier updates the scraper; your field names stay the same.
2 credits per call, however many results the page holds. Failed calls are never billed.
The official Yandex Search API runs inside Yandex Cloud and needs a cloud account, a service account and billing set up first. Scrapier reads the same public result pages with one API key, at a price you know before the call runs.
Any non-2xx response is free, so retries cost nothing.
At 2 credits a call. Flat per-call pricing, no compute units or bandwidth to estimate.
No Yandex Cloud account, service account or IAM token to create.
The same key and JSON envelope cover Google, Amazon, TikTok, YouTube and more.
| Feature | Scrapier Yandex Scraper | Yandex Search API | DIY scraper |
|---|---|---|---|
| Whose data | Public Yandex results | Yandex search results | Public Yandex results |
| Setup | One API key | Yandex Cloud account and service account | Proxies, browsers, parsers |
| Maintenance | Handled by Scrapier | Keys and API version changes | Breaks on layout changes |
| Cost | From $1.20 per 1,000 calls | Paid, per Yandex Cloud pricing | Servers, proxies and engineering time |
| AI agents | MCP server included | Build your own | Build your own |
Organic yandex.com results for one query. Each result has position, type, url, title, display_url, snippet, page and the query you sent, so you can store rankings without parsing HTML. The response also echoes your query and gives next_cursor for the next page.
Yes. Set language to one of en, ru, uk, de, fr, tr, be, kk, uz, az, lv, lt or et for regional ranking; the default is en. The language is locked into the cursor, so every page of one query uses the same ranking.
Read next_cursor from the response and send it back as cursor. Each page is one call at 2 credits. When next_cursor is null you have reached the last page Yandex shows for that query.
A Yandex Maps places scraper is on Scrapier's Yandex list: it takes a query such as a business type and city and returns name, category, address, phone, website, rating, review count and opening hours. It has no live endpoint in the catalog yet, so no path or price is published.
No. Each call takes one keyword in queries. To track a list, loop over it and run up to 3 calls in parallel per key; failed or throttled calls cost nothing, so retries are free.
No. Scrapier reads public Yandex result pages for you, so there is no Yandex account, cloud folder or service account to create. You only need a Scrapier API key in the X-API-Key header.
Each Yandex Search call costs 2 credits per successful call, however many results the page holds. Failed calls are free. Plans: Hobby $29 for 15,000 credits, Pro $79 for 50,000, Scale $299 for 250,000, Enterprise custom. A free tier lets you try it first.
Yes. Set raw_data to true and the response carries the raw upstream payload under raw_responses instead of the formatted results. Pagination with cursor and next_cursor works the same way in both modes.
It depends on what you collect, where you are and how you use it, so this is not legal advice. Scrapier returns publicly visible Yandex data only. Some of it can be personal data under GDPR or CCPA, so collect only what you have a legitimate reason to use and check Yandex's terms.
Yes. Any tool that can make an HTTP request works: n8n, Make, Zapier, Google Sheets, Airbyte or your own code. Send your key in the X-API-Key header and read the JSON under data.
Yes. Run claude mcp add -t http scrapier https://mcp.scrapier.io/mcp with your key in an X-API-Key header. The agent finds the right Yandex endpoint with search_endpoints and calls it with run_scrape, in Claude Code, Cursor or Windsurf.
Check the status code first: 401 means the X-API-Key header is missing, 403 an invalid key, 402 no credits left, 429 too many requests (wait Retry-After seconds). If it's still wrong, report it with the request and the response.
Run up to 3 requests in parallel per API key. If you go faster, the API answers 429 with a Retry-After header: wait that many seconds and retry. 429 and 5xx responses are never billed, and long-running endpoints need a client timeout of 210 seconds or more.
Use the requests library: requests.get("https://proxy.scrapier.io/api/v2/yandex-search/", headers={"X-API-Key": key}, params={"queries": "python tutorial"}, timeout=210). The response is JSON, so read r.json()["data"]["results"] directly; there is no HTML to parse. Each call returns one page.
Free API key. No sales call, no proxy setup, and failed calls are free.