Yandex Reverse Image Search Scraper
Pricing
$4.00 / 1,000 heavy calls
Yandex Reverse Image Search Scraper
Reverse image search on Yandex — the strongest public engine for finding where a photo appears online. Give it an image URL and get the pages hosting it, visually similar images, other resolutions and Yandex's own tags.
Pricing
$4.00 / 1,000 heavy calls
Rating
0.0
(0)
Developer
ScrapeBadger
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
What does Yandex Reverse Image Search Scraper do?
Yandex Reverse Image Search Scraper extracts structured data from Yandex and delivers it as clean JSON — no proxies, browsers or anti-bot handling on your side. It is a practical Yandex API alternative for teams who need Yandex data on a schedule rather than a one-off export.
It covers 3 different Yandex surfaces behind a single Mode dropdown, so one Actor replaces a rack of single-purpose scrapers.
Why scrape Yandex?
- Every surface in one place — pick a mode, fill two fields, run.
- Anti-bot handled upstream — residential proxy rotation, TLS and browser fingerprinting, and CAPTCHA solving happen inside the ScrapeBadger API.
- Pay per call, not per row — a page of results costs the same as one lookup, so bulk work stays cheap.
- Runs on the Apify platform — scheduling, monitoring, webhooks, the API, and integrations with Make, Zapier, Google Sheets, Slack and Airtable all work out of the box.
- Partial results are kept — a transient upstream failure ends the run cleanly instead of discarding what you already paid for.
What data can Yandex Reverse Image Search Scraper extract?
Every record is pushed to the dataset as its own row. The most useful fields are below; the full record carries considerably more.
| Field | Type | Description |
|---|---|---|
title | string | Title of the record |
url | string (URL) | Canonical URL of the record |
description | string | Free-text description |
domain | string | Domain of the result |
Yandex scraping modes
Pick one Mode; the input form marks the fields it needs.
| Mode | What it returns | Charged as |
|---|---|---|
| Pages Containing Image | Web pages that host the image, with title, URL and thumbnail. | heavy-call |
| Visually Similar Images | Images Yandex considers visually similar to the input. | heavy-call |
| Other Sizes | Other resolutions of the same image found on the web. | heavy-call |
How to scrape Yandex
- Click Try for free and sign in to Apify.
- Open Settings → Environment variables and add
SCRAPEBADGER_API_KEYwith your key from scrapebadger.com, ticking Secret. - Choose a Mode from the dropdown.
- Fill in the fields that mode needs — the description on each field says which modes use it.
- Set Max items to cap the run.
- Press Start and watch the dataset fill up.
- Export as JSON, CSV, Excel or XML, or pull it from the API tab.
How much will it cost to scrape Yandex?
This Actor is pay per event: one event per API call, whatever that call returns. Fetching a page of 100 records costs the same as fetching one record, so larger pages are cheaper per row.
| Event | Price per event | What triggers it |
|---|---|---|
heavy-call | $0.0040 | A heavy call — comments, followers, transcripts, full detail pages. |
Apify also charges its standard $0.001 actor start fee per run. ScrapeBadger credits are consumed on your own account on top of this.
Input
See the Input tab for every option with inline documentation. A minimal run looks like this:
{"mode": "Pages Containing Image","image_url": "https://upload.wikimedia.org/wikipedia/commons/3/3a/Cat03.jpg","domain": "tr","max_items": 100}
Max items caps the run; the Actor pages until it reaches that number or Yandex runs out of results.
Output
You can download the dataset in various formats such as JSON, HTML, CSV, or Excel, or read it straight from the Apify API. Each record is one row:
{"title": "<title>","url": "https://example.com/record/1","description": "<description>","domain": "<domain>"}
What can you do with Yandex data?
A few things teams actually build with this Actor.
Verify an image before you publish it
Reverse search is the fastest way to check whether a photo is what someone claims. Yandex finds earlier appearances of an image more reliably than any other public engine, which makes it a standard tool in newsroom fact-checking and OSINT work.
Track counterfeit listings
Counterfeiters reuse the genuine product photography. Feeding your official images through reverse search surfaces the marketplace listings using them, with the exact page URL you need for a takedown notice.
Find the highest-resolution version
The Other Sizes mode returns the same image at every resolution Yandex has indexed — the practical way to recover a usable original from a thumbnail.
Build visual similarity sets
Visually Similar Images returns Yandex's own near-neighbour set, which is a cheap way to bootstrap a duplicate-detection or style-clustering pipeline without training a model first.
Tips for faster, cheaper runs
- Raise the page-size field (
count,limit,per_page— whichever the mode exposes) before raising Max items. Fewer, bigger calls cost less. - Use the cheap reference and autocomplete modes to resolve IDs before spending on the expensive detail modes.
- Schedule incremental runs with a low Max items rather than one huge sweep; you get fresher data and a smaller bill.
- Chain Actors with webhooks to push new rows straight into your warehouse.
Requirements
This Actor calls the ScrapeBadger API on your behalf, so it needs your key:
- Get one at scrapebadger.com — there is a free tier.
- In Settings → Environment variables, add
SCRAPEBADGER_API_KEYwith yoursb_live_…key and tick Secret.
Credits are consumed on your ScrapeBadger account in addition to the Apify event price.
Frequently asked questions
Is it legal to scrape Yandex?
Scraping publicly available data from Yandex is generally legal, and this Actor only ever reads pages a logged-out visitor could see. What you then do with the data is what matters — read the disclaimer below before collecting anything that could be personal data.
Do I need my own proxies?
No. Proxy rotation, browser fingerprinting and anti-bot handling all happen upstream in the ScrapeBadger API, so there is nothing to configure here.
Do I need a ScrapeBadger account?
Yes. The Actor calls the ScrapeBadger API on your behalf, so it needs your API key in the SCRAPEBADGER_API_KEY environment variable. There is a free tier at scrapebadger.com — see Requirements below.
How many results can I get in one run?
Set Max items to whatever you need. The Actor keeps paging until it hits that number or Yandex runs out of results, and stops cleanly either way.
How much does one run cost?
Events start at $0.0040 and are charged once per API call, not per row — so a page of 100 results costs the same as a single lookup. Apify adds its standard $0.001 actor start fee per run.
What happens if the run fails halfway through?
Whatever was already scraped stays in the dataset. The run ends with a status message explaining where it stopped instead of throwing your results away.
Can I run this on a schedule or from my own code?
Yes. Use the Schedules tab for recurring runs, or the API tab to start runs and read the dataset from your own application.
Is scraping Yandex reliable?
Anti-bot interstitials are a fact of life on Yandex. A blocked call is retried four times with exponential backoff against fresh exits, and if a run dies partway it keeps everything already scraped rather than throwing the dataset away. Upstream availability is monitored continuously.
Your feedback and support
Found a bug, missing a field, or need a mode that is not here? Open a ticket on the Issues tab, or email support@scrapebadger.com. The API tab has everything you need to run this Actor programmatically.
Disclaimer
Our Actors are ethical and do not extract any private user data, such as email addresses, gender, or location. They only extract what the user has chosen to share publicly. We therefore believe that our Actors, when used for ethical purposes by Apify users, are safe. However, you should be aware that your results could contain personal data. Personal data is protected by the GDPR in the European Union and by other regulations around the world. You should not scrape personal data unless you have a legitimate reason to do so. If you're unsure whether your reason is legitimate, consult your lawyers.