VK Email Scraper

VK Email Scraper

VK Email Scraper for VKontakte Lead Generation

The VK Email Scraper is an Apify Actor that turns publicly indexed VKontakte pages into a clean, structured dataset of contact emails. It is built for anyone who needs to reach shop owners, community admins and creators across the Russian-speaking web.

Instead of logging into VKontakte, the VK Email Scraper builds targeted Google queries with the site:vk.com operator and parses the search results. Everything it collects is already public in Google's index.

That design matters for VK specifically. VK is where Russian and CIS small businesses publish an "email for advertising" line in a community description, and the VK Email Scraper is tuned to find exactly those lines.

You give it keywords, an optional location, and the email domains you care about. The VK Email Scraper returns a dataset of leads with account names, profile URLs, bio snippets and normalised email addresses.

Who this VK email extractor is for

Marketers running outreach in Russia, Belarus and Kazakhstan. Recruiters sourcing Russian-speaking talent. Agencies building media lists of VK communities. Anyone doing VK lead generation who is tired of copying emails by hand.

Key Features of the VK Email Scraper

Feature	What it means in practice
Google-based contact discovery	The VK Email Scraper reads publicly indexed vk.com results — no login, no cookies, no browser
Query expansion	Each keyword runs as a base query, a quoted query, an intitle: query and one variant per modifier
Domain-filtered extraction	Only emails on your customDomains list are kept, so you can target @mail.ru or @yandex.ru
Global deduplication	Every email is deduplicated across all queries and pages in the run
Email normalisation	Understands name [at] domain [dot] com, name (at) domain, name @ domain.com, zero-width characters and the full-width ＠
Junk filter	Rejects placeholders such as email@, yourname@, test@, xxx@ and single-character locals
Boundary-correct matching	@gmail.com will not match inside @gmail.company or @gmail.com.br
Soft-wrap repair	Drops a hit that is only the tail of another email in the same result block
Concurrency control	An asyncio worker pool runs several queries in parallel with a shared stop signal
Retry logic	Up to 3 attempts per page with exponential backoff and a fresh proxy session per request
Block detection	CAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty
Resumable state	Progress is checkpointed in the key-value store and survives PERSIST_STATE, MIGRATING and ABORTING events
Fallback parser	If Google's markup changes, the crawler degrades to "emails without account details" rather than "no results"
Structured output	Fourteen fields per row, ready for CSV, JSON or Excel export from the Apify dataset

How the VK Email Scraper Works

1. Read input. Keywords, location, email domains and limits are validated.
2. Build queries. The VK Email Scraper composes Google queries such as site:vk.com интернет магазин "@mail.ru" "Москва".
3. Fetch search results. Pages are requested asynchronously through the Apify GOOGLE_SERP proxy using aiohttp.
4. Parse structurally. The parser locates each <h3> title, then the smallest surrounding block — it does not depend on Google's CSS class names, which change often.
5. Extract emails. A domain-filtered regex pulls addresses out of the block text, including obfuscated forms.
6. Deduplicate and store. Each unique lead is pushed to the Apify dataset immediately, so partial runs still produce usable data.

Base queries always run first, so the highest-signal results land in your dataset early. Blocked or failed queries are re-queued once at the end of the run.

The VK Email Scraper never opens vk.com itself. There is no JavaScript rendering, no authentication and no session on the platform.

What Data Does It Extract?

Every row is one email paired with the account metadata Google printed alongside it. On VK that usually means a community name, a personal page name, or a shop title.

The username and profileUrl fields are filled when Google exposes a handle such as vk.com/some_shop. When Google shows only a display name, you still get accountName, fullName, the bio snippet and the email.

Numeric VK pages (vk.com/id...) and vanity URLs are both handled, and the description field is cleaned of navigation labels and engagement counters before it reaches your dataset.

Input Fields and Configuration

Field	Type	Default	Meaning
keywords	array (required)	["founder", "shop"]	Search terms — niche, job title or industry
location	string	""	Optional location phrase added to every query
customDomains	array	["@gmail.com","@yahoo.com"]	Only emails on these domains are kept; the @ is optional
maxEmails	integer 1–10000	20	Stop after this many unique emails
countryCode	string	""	Two-letter country for the search proxy (US, GB, DE...)
expandQueries	boolean	true	Search each keyword × domain pair in several phrasings
queryModifiers	array	["email","contact","business","cooperation","advertising"]	Extra words combined with each keyword when expansion is on
maxPagesPerQuery	integer 1–50	30	Pagination cap per query
maxConcurrency	integer 1–20	5	Parallel queries

Using countryCode with the VK Email Scraper

countryCode is genuinely useful here. VKontakte's index is heavily regional, and Google returns different result sets depending on the country the search proxy appears to come from.

Set RU for the core Russian market, BY for Belarus, KZ for Kazakhstan or UA for Ukrainian-language results. DE and IL surface Russian-speaking diaspora communities that a US search will often miss.

Run the VK Email Scraper twice with different country codes and merge the datasets — global deduplication happens per run, so cross-run overlap is easy to drop in your CRM.

Choosing the right email domains

The default @gmail.com and @yahoo.com are safe, but they are not where the VK audience lives. Russian and CIS accounts overwhelmingly publish @mail.ru, @yandex.ru, @bk.ru, @inbox.ru and @list.ru addresses.

Set customDomains to those and the VK Email Scraper's yield changes dramatically. You can also add a corporate domain such as @company.ru when you are prospecting one specific group.

Choosing keywords

Keywords are inserted into the Google query verbatim, so Cyrillic works exactly as well as Latin script. магазин, реклама, сотрудничество, мастер, студия and доставка are all valid inputs.

Mixing scripts in one run is fine. The VK Email Scraper treats every keyword independently and records which one produced each lead.

Output Schema and Dataset Fields

Field	Meaning
network	Platform name
keyword	The keyword that produced the lead
query	The exact Google query used
title	Raw result title
accountName	Account label Google prints (handle or display name)
fullName	Display name parsed from a profile-style title; empty for post captions
username	URL-safe handle when VK exposes one; otherwise null
profileUrl	Canonical account URL when a handle is known; otherwise empty
url	Direct platform link when exposed, else the profile URL
description	Bio or caption snippet, cleaned of labels and counters
email	Lower-cased email address
emailDomain	The matched domain, e.g. @mail.ru
possiblyTruncated	true when Google's snippet ellipsis touched the email — verify before sending
foundAt	ISO 8601 UTC timestamp

The query and keyword fields make the output auditable. You can always trace a lead back to the exact search that produced it, which is invaluable when you are tuning a VK lead generation campaign.

How to Use the VK Email Scraper

1. Open the VK Email Scraper on Apify and click Try for free.
2. Enter your keywords — start with two or three specific terms rather than one broad one.
3. Replace customDomains with the Russian free-mail providers listed above.
4. Set countryCode to RU (or your target CIS market).
5. Set maxEmails to the size of the list you actually need.
6. Run the Actor, then export the dataset as CSV, JSON or Excel.

For a first test, leave maxPagesPerQuery and maxConcurrency at their defaults. Raise concurrency only if your Apify plan has the memory headroom.

You can also call the VK Email Scraper from the Apify API or any of the Apify SDK clients, which makes it easy to schedule recurring contact discovery runs.

Use Cases for the VK Email Scraper

Use case	How the VK Email Scraper helps
CIS e-commerce prospecting	Find VK shops and sellers that publish an order or wholesale email
Community and pablik outreach	Collect the "по рекламе" advertising contacts that VK community admins post publicly
Influencer and SMM partnerships	Build media lists of Russian-language creators open to cooperation
Recruiting Russian-speaking talent	Source designers, developers and marketers by keyword and city
Agency client research	Map which niches in a city already advertise on VK
Market research	Sample how a vertical presents itself across VKontakte before entering the market
Event and conference sourcing	Gather speaker and sponsor contacts from event communities
CRM enrichment	Add public VK contact emails to records you already hold

Most CIS outreach programmes run on two channels at once. Pair the VK Email Scraper with the Telegram Email Scraper to cover the public channels the same admins operate.

For B2B campaigns, layering the LinkedIn Email Scraper on top of a VK Email Scraper run gives you both the corporate identity and the community-side contact for the same company.

Why Use This VK Email Scraper

Most email tools are generic web crawlers pointed at any domain. This one is a purpose-built VKontakte scraper: the query modifiers, the username pattern and the profile URL template are all tuned for VK.

The parsing is structural, not cosmetic. Because the VK Email Scraper finds the <h3> and walks outward, a Google redesign degrades quality gracefully instead of breaking the run.

Runs are resumable. If the platform migrates your Actor mid-run, the VK Email Scraper picks up from its checkpoint rather than starting over.

And it is honest about what it produces. possiblyTruncated tells you when a snippet ellipsis may have clipped an address, so you never send to a half-parsed mailbox.

If you also work in Western markets, the same engine powers the Facebook Email Scraper and the Instagram Email Scraper — the input schema is identical, so a workflow built around the VK Email Scraper transfers directly.

Limitations of the VK Email Scraper

Read this section before you buy. These constraints are real and none of them are bugs.

• Only publicly indexed emails. The VK Email Scraper finds addresses that are already visible in Google's index. Private data, hidden fields and login-gated content are out of reach.
• Google caps a single query at roughly 300 results. That cap is the reason query expansion exists — more phrasings mean more distinct result sets.
• Google indexes VK less completely than Western networks. Regional platforms get thinner coverage, and a large share of what is indexed is in Russian. Expect lower volume than an equivalent Facebook or Instagram run.
• username and profileUrl may be empty. They are only filled when Google exposes a handle. Some rows will carry accountName and fullName only. That is a Google limitation.
• possiblyTruncated: true means verify. Google's snippet ellipsis may have cut the address short.
• Requires the Apify GOOGLE_SERP proxy. The Actor cannot run without Apify proxy credentials.
• Free Apify plans are capped at 100 emails per run. Paid plans are uncapped.
• No volume guarantee. Results vary with keywords, domains, country and location.

The VK Email Scraper is not affiliated with or endorsed by VK. Use the output in line with GDPR, Russian data law and your own outreach policy.

Related Actors

Actor	What it collects
VK Email and Phone Number Scraper	Emails and phone numbers from VK
VK Phone Number Scraper	Public phone numbers from VK
Behance Email Scraper	Public contact emails from Behance
Bigo Live Email Scraper	Public contact emails from Bigo Live
Bluesky Email Scraper	Public contact emails from Bluesky
Bumble Email Scraper	Public contact emails from Bumble
Clubhouse Email Scraper	Public contact emails from Clubhouse
Dailymotion Email Scraper	Public contact emails from Dailymotion
DeviantArt Email Scraper	Public contact emails from DeviantArt
Discord Email Scraper	Public contact emails from Discord
Dribbble Email Scraper	Public contact emails from Dribbble
Facebook Email Scraper	Public contact emails from Facebook
Goodreads Email Scraper	Public contact emails from Goodreads
Hinge Email Scraper	Public contact emails from Hinge
Instagram Email Scraper	Public contact emails from Instagram
KakaoTalk Email Scraper	Public contact emails from KakaoTalk
Kick Email Scraper	Public contact emails from Kick
Lemon8 Email Scraper	Public contact emails from Lemon8
Likee Email Scraper	Public contact emails from Likee
LINE Email Scraper	Public contact emails from LINE
LinkedIn Email Scraper	Public contact emails from LinkedIn
Mastodon Email Scraper	Public contact emails from Mastodon
Medium Email Scraper	Public contact emails from Medium
Mixcloud Email Scraper	Public contact emails from Mixcloud
Patreon Email Scraper	Public contact emails from Patreon
Pinterest Email Scraper	Public contact emails from Pinterest
Quora Email Scraper	Public contact emails from Quora
Reddit Email Scraper	Public contact emails from Reddit
Rumble Email Scraper	Public contact emails from Rumble
Snapchat Email Scraper	Public contact emails from Snapchat
SoundCloud Email Scraper	Public contact emails from SoundCloud
Substack Email Scraper	Public contact emails from Substack
Telegram Email Scraper	Public contact emails from Telegram
Threads Email Scraper	Public contact emails from Threads
TikTok Email Scraper	Public contact emails from TikTok
Tinder Email Scraper	Public contact emails from Tinder
Tumblr Email Scraper	Public contact emails from Tumblr
Twitch Email Scraper	Public contact emails from Twitch
Vimeo Email Scraper	Public contact emails from Vimeo
WeChat Email Scraper	Public contact emails from WeChat
Weibo Email Scraper	Public contact emails from Weibo
X Email Scraper	Public contact emails from X

Example Run

A realistic input for a VK Email Scraper run targeting Saint Petersburg beauty studios:

{
  "keywords": ["студия красоты", "барбершоп", "shop"],
  "location": "Санкт-Петербург",
  "customDomains": ["@mail.ru", "@yandex.ru", "@bk.ru"],
  "maxEmails": 300,
  "countryCode": "RU",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "business", "cooperation", "advertising"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

One dataset item produced by that run:

{
  "network": "VK",
  "keyword": "студия красоты",
  "query": "site:vk.com студия красоты \"@mail.ru\" \"Санкт-Петербург\"",
  "title": "Студия красоты Аврора (@studio_avrora) | ВКонтакте",
  "accountName": "studio_avrora",
  "fullName": "Студия красоты Аврора",
  "username": "studio_avrora",
  "profileUrl": "https://vk.com/studio_avrora",
  "url": "https://vk.com/studio_avrora",
  "description": "Студия красоты в центре Санкт-Петербурга. Запись и сотрудничество: avrora.spb@mail.ru",
  "email": "avrora.spb@mail.ru",
  "emailDomain": "@mail.ru",
  "possiblyTruncated": false,
  "foundAt": "2025-03-14T09:41:22Z"
}

Every row the VK Email Scraper writes carries all fourteen fields, so the JSON shape is stable and safe to map into a database schema.

Because the VK Email Scraper pushes each lead as soon as it is found, you can open the dataset and start working while the run is still going.

VK Email Scraper FAQ

What is the VK Email Scraper?

An Apify Actor that extracts publicly indexed contact emails from VKontakte search results and returns them as a structured dataset.

Does the VK Email Scraper log into VK?

No. It never opens vk.com, never authenticates and never uses VK's API. All data comes from Google search results.

Can it scrape private VK profiles or hidden emails?

No. If an address is not publicly visible in Google's index, the VK Email Scraper cannot find it.

Which email domains should I use for VK?

@mail.ru, @yandex.ru, @bk.ru, @inbox.ru and @list.ru are the highest-yield choices for Russian and CIS accounts.

Do Cyrillic keywords work?

Yes. Keywords are passed into the Google query as written, so магазин and реклама work exactly like English terms.

What does possiblyTruncated mean?

Google's snippet ellipsis may have clipped the email. Verify those addresses before adding them to a send list.

Why are some username and profileUrl values empty?

Google sometimes prints only a display name with no handle. The VK Email Scraper fills those fields when a handle is exposed and leaves them empty otherwise.

Does the VK Email Scraper need a proxy?

Yes. It requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.

How many emails can I collect per run?

Free Apify plans are capped at 100 emails per run. Paid plans are uncapped, up to the maxEmails value you set (maximum 10000).

Should I leave expandQueries on?

Yes, in almost every case. Google caps one query at around 300 results, and expansion is how the VK Email Scraper works around that ceiling.

Can I run the VK Email Scraper on a schedule?

Yes. Use Apify Schedules or the API. Runs are resumable and state is checkpointed in the key-value store.

What export formats are supported?

The VK Email Scraper writes to a standard Apify dataset, which exports to JSON, CSV, Excel, XML and HTML and can be read through the Apify API.

Is the VK Email Scraper affiliated with VK?

No. It is an independent Apify Actor and has no affiliation with or endorsement from VK.

Leave a review

If the VK Email Scraper saved you time, please leave a star rating and a short review on the Actor page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to build next.

If something did not work, email neurodata.apify@gmail.com instead - bugs get fixed faster than they get complained about.

Support

Questions, feature requests or need a custom build? Email neurodata.apify@gmail.com and we will get back to you.