Yandex Search Engine Scraper (SERP API)

Yandex Search Engine Scraper: Yandex results by keyword and region, no API key

The same query put to Yandex from Moscow and from Istanbul does not come back as the same page. Yandex ranks by region, the region is a code in the URL, and you can ask for any of them from anywhere. One row per slot: rank, title, link, the domain Yandex shows, the snippet, sitelinks, and whether the slot is organic, a Direct ad or a featured block.

The honest part. Yandex does not always serve a query, and when it refuses you get an uncharged diagnostic row instead of results, so a run can come back with far fewer rows than you asked for. There is also no total-result count anywhere on a modern Yandex page, so nothing here can report one.

🔎 What Yandex Search Engine Scraper does

Give it keywords and a region code and it pages through the results, writing a row for every slot on the page in the order Yandex put them.

The region code is the point. lr=213 is Moscow, 225 is Russia, 11508 is Istanbul, 163 is Astana. Set one and you get that region's ranking wherever the run happens to execute. Leave it empty and Yandex picks, which is fine for a look and wrong for a comparison.

Three kinds of slot come back, and all three take up a rank position: organic listings, Yandex Direct ads, and featured blocks like video carousels, image strips and the AI answer teaser. Each row carries position for the slot's place on the page and organicPosition for its place among the organic rows only, which is the one rank trackers want.

📥 What you give it

{
  "queries": ["купить пластиковые окна", "ergonomic office chair"],
  "domain": "yandex.com.tr",
  "region": 213,
  "maxItemsPerQuery": 20,
  "maxItems": 100
}

Run it with no queries and no URLs and you get one labelled sample row.

📤 What you get back

A real row from a recent run. This one happens to be the AI answer teaser, which is why title and url are empty on it:

{
  "searchQuery": "ergonomic office chair",
  "page": 1,
  "position": 1,
  "positionOnPage": 1,
  "organicPosition": null,
  "type": "featured",
  "featureType": "neuro-answer",
  "isAd": false,
  "title": null,
  "url": null,
  "displayedUrl": null,
  "displayedDomain": null,
  "brandName": null,
  "snippet": "Yazeka Arama sonuclarina dayanarak olusturuldu Internette arama Uygun kaynak secimi ...",
  "sitelinks": [],
  "region": 213,
  "regionRequested": 213,
  "domain": "yandex.com.tr",
  "domainRequested": "yandex.com.tr",
  "searchUrl": "https://yandex.com.tr/search/?text=ergonomic+office+chair&lr=213",
  "scrapedAt": "2026-09-21T01:45:43.797Z"
}

🧾 Reading the output

Three kinds of row can land in your dataset.

Diagnostic and notice rows are never charged.

▶️ How to run it

1. Open Yandex Search Engine Scraper and click Try for free. 2. Put your keywords into Search queries, replacing the example. 3. Set Region (Yandex lr code) to the market you care about. This is the setting that changes the answer. 4. Set Max results in total low for the first run, then click Start. 5. Download the dataset as JSON, CSV or Excel, or read it from the Apify API.

💰 How much does it cost?

$3.40 per 1,000 results. Flat on every Apify plan, no volume tiers.

Every row with a rank counts, ads and featured blocks included, because they take up a rank slot. If you only want organic listings, turn includeAds and includeFeatured off and you stop paying for them.

Sample rows, notice rows and diagnostic rows are not charged, and a query Yandex refuses costs you nothing.

💡 What people use it for

• Tracking where a site ranks in Moscow, Almaty or Istanbul, where a Google-only view says nothing.
• Watching which advertisers are buying a keyword, through displayedDomain on the ad rows.
• Pulling the snippet Yandex writes for your pages, which is not always the meta description.
• Comparing the same keyword across regions by running it once per lr code.
• Checking whether featured blocks are pushing the organic results down a market you care about.

🚧 What it does not do

• No total result count. Yandex does not print one any more, so nothing can report it.
• Leave region empty and each query keeps its own. Every query pins to whatever region its

first page came back with, so two queries in one run can be ranked for different places. Set region whenever you are comparing anything.

• yandex.uz ignores the region code and always ranks for Uzbekistan.
• An ad row can come back typed organic. The tell is the link: an ad's url points at a

yabs.yandex click tracker, and the advertiser's own domain sits in displayedDomain.

• The AI answer block is a teaser, so its row carries the visible text with title and url

empty, as above.

• Some queries will not be served. You get an uncharged row saying so, and a run can end with

very few results.

• About 20 pages is the realistic depth for one query, whatever the page cap allows.
• Web results only. No images, video, maps or news verticals.
• A ranking is a snapshot, and Yandex personalises less than Google but still moves daily.

🧭 Which Yandex scraper do you need?

❓ Questions people ask

Do I need a Yandex account or an API key? No. Nothing to apply for and no quota to watch.

Which region code should I use? The one for the market you sell in. 213 for Moscow, 225 for Russia as a whole, 11508 for Istanbul, 163 for Astana. The list in the input has the verified ones.

Why did I get fewer rows than I asked for? Either the query ran out of pages, or Yandex refused it. The diagnostic row tells you which, and neither costs you anything.

Can I search in Russian? Yes, and in Turkish, Kazakh and English. Put the query in whatever language you want to rank in.

Does the domain I pick change the ranking? The index is the same. The region code is what changes the ranking, except on yandex.uz, which ignores it.

Is scraping search results legal? They are public pages. Apify's write-up on scraping and the law is a good starting point, and we are not lawyers.

🆘 If something breaks

Open the Issues tab on the actor page. Send the query, the region code and the run ID. The errorCode on the diagnostic row usually names the problem on its own.