← ClaudeAtlas

apify-yandex-scraper-bulk-serplisted

A yandex scraper for bulk SERP collection where the bill is predictable, powered by the Apify Yandex Search per-result Actor (johnvc/yandex-scrape-yandex-search-results-at-scale---per-result). Run a keyword list through Yandex across 6 domains, 19 languages, and any lr region, and get structured items back with organic rows (position, title, link, displayed_link, snippet) plus optional ads, knowledge graph, and inline media, each result type billed as its own item so you pay only for what you collect. Use when the user wants a yandex scraper, wants yandex data or Yandex search results as JSON or CSV in volume, wants to scrape many Yandex queries at scale, needs a per-result cost model instead of per-run fees, or is building a Russian-market SERP dataset. Pay-per-result billing, MCP-ready for Claude and other AI agents.
johnisanerd/claude-skill-yandex-scraper-bulk-serp · ★ 0 · Data & Documents · score 66
Install: claude install-skill johnisanerd/claude-skill-yandex-scraper-bulk-serp
# Yandex Scraper: Bulk SERP Collection, Billed Per Result Collect Yandex search results in volume with a cost you can predict before you start. Every item you get is one page of one result type, and that item is exactly what you pay for, which makes a keyword list easy to budget. ## When to use this skill - The user wants a Yandex scraper for many queries, not a single lookup. - They want Yandex data as JSON or CSV for a keyword list, a market, or a research dataset. - They want the bill to scale with results collected rather than with runs started. - They are building a Russian-market or CIS-market SERP dataset and want organic results plus, where useful, ads, knowledge graph, or inline media. Not for: tracking one keyword's position over time (use the companion Yandex rank tracker skill), reverse image lookups (use the Yandex Reverse Image Search Actor), or Google SERPs. ## What you get (one dataset item per page, per result type) A run returns one item per page for each result type you turned on, tagged with `item_type` (`organic` on a default run). The rows live in a nested array on that item. `organic_results` rows carry `position`, `title`, `link`, `displayed_link`, and `snippet`. The other type arrays are `ads_results`, `knowledge_graph`, `inline_images`, `inline_videos`, `image_results`, and `video_results`, and they come back empty when that type is off or absent from the SERP. Every item also carries the query context and pagination state, which is what makes