Preply Email Scraper
Pricing
from $2.49 / 1,000 results
Preply Email Scraper
Preply Email Scraper SD - Preply Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Preply results by keyword, location and email domain - Preply email extractor.
Pricing
from $2.49 / 1,000 results
Rating
0.0
(0)
Developer
Neuro Scraper
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
11 days ago
Last modified
Categories
Share
Preply Email Scraper — Extract Public Contact Emails from Preply Tutor Pages
The Preply Email Scraper finds publicly indexed contact emails connected to Preply tutor profiles and question pages, and returns them as clean, structured lead data.
You give it keywords such as tutor or language teacher, choose the email domains you care about, and the Preply Email Scraper writes a dataset of leads with account names, tutor handles, snippets and profile URLs.
Preply is a global one-to-one tutoring marketplace, strongest in language learning but now spanning maths, music, programming and test preparation.
Every tutor gets a real public profile at preply.com/en/tutor/{id}, which is why Preply results usually carry a usable handle and a canonical profile link rather than just a display name.
Important: the Preply Email Scraper never logs into Preply, never uses a Preply API, and never opens preply.com itself. Every record comes from publicly indexed Google search results.
One honest expectation to set up front: Preply deliberately keeps tutor contact details private and routes students through its own messaging system, so publicly listed email addresses are less common here than on creator platforms.
That makes the Preply Email Scraper a Preply email extractor for tutor recruiting, edtech lead generation, language-school partnerships and market research — with steady rather than spectacular volume.
Key Features of the Preply Email Scraper
Everything listed below is a capability the Preply Email Scraper genuinely has.
| Feature | What it means in practice |
|---|---|
Google site: search collection | The Preply Email Scraper queries Google restricted to preply.com, so only Preply pages are parsed |
| Tutor-profile awareness | Handles are recovered from the /tutor/ path, producing a clean preply.com/en/tutor/{id} link |
| Multilingual path handling | Locale segments such as /en/, /es/, /de/, /fr/, /pt/, /ja/ and /tr/ are handled when recovering a handle |
| Country targeting | countryCode steers the search proxy, which materially changes which tutors surface — a real lever on a marketplace this international |
| Query expansion | Each keyword × domain pair is searched in several phrasings: base, quoted, intitle:, plus one variant per query modifier |
| Domain-filtered extraction | Only addresses ending in your customDomains list are kept |
| Global deduplication | An email appears once across every query and every page of the run |
| Obfuscation-aware parser | Understands name [at] domain [dot] com, name (at) domain, name @ domain.com, 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 | Discards a hit that is only the tail of another address in the same result block |
| Structural HTML parsing | Finds the <h3> title then the smallest enclosing block — it does not depend on Google's CSS class names |
| Whole-page fallback parser | If Google's markup changes, the run degrades to "emails without account details" rather than "no emails" |
| Concurrency | An asyncio worker pool runs several queries in parallel with a shared stop signal on maxEmails |
| 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 |
| Blocked-query requeue | Failed or blocked queries are re-queued once at the end of the run |
| Resumable state | Progress is kept in the key-value store keyed by a hash of your input, saved on PERSIST_STATE, MIGRATING and ABORTING |
| Streaming dataset writes | Each lead is pushed to the Apify dataset the moment it is found |
| Run summary | Logs pages fetched, blocked pages, retries and emails per page |
How the Preply Email Scraper Works
The pipeline is short and deliberately transparent. There is no browser, no JavaScript rendering, no authentication and no cookies.
1. Read input. The Preply Email Scraper loads your keywords, optional location phrase, email domains and run limits.
2. Build queries. It composes Google queries with the site: operator, for example site:preply.com spanish tutor "@gmail.com" "Madrid".
3. Fetch search pages. Requests go out asynchronously with aiohttp through the Apify GOOGLE_SERP proxy, with retries and a fresh proxy session per attempt.
4. Parse result blocks. For each hit the scraper locates the <h3> title, walks up to the smallest surrounding block, and reads the title, site label and snippet.
5. Extract and normalise addresses. A domain-filtered regex pulls emails out of the block text, then normalisation and the junk filter clean the result.
6. Deduplicate and push. Every unique address is written to the dataset immediately, so you can begin exporting mid-run.
Because base queries run before expanded ones, the first rows the Preply Email Scraper writes are usually the highest-signal ones.
Why countryCode is a real lever on Preply
Preply localises heavily. The same tutor catalogue is indexed under many language paths, and Google's results shift accordingly.
Running countryCode: "ES" with Spanish keywords, then DE with German keywords, then BR with Portuguese ones, reaches parts of the index a single default run never touches.
Treating those as separate Preply Email Scraper runs and merging the exports is usually more productive than one large undifferentiated crawl.
What Data Does the Preply Email Scraper Extract?
The Preply Email Scraper produces exactly one dataset item per unique email, and every item carries the same 14 fields.
Alongside the address you get the account label Google printed, a parsed display name, the tutor handle when Preply exposes one, a canonical tutor profile link, and the snippet the email came from.
You also get full provenance: the keyword and the exact Google query behind the lead, plus a UTC timestamp.
That provenance is practical. It shows which language and subject keywords actually surface contactable tutors in your target market.
Nothing beyond these 14 fields is collected. The Preply Email Scraper reports no lesson prices, no ratings, no student data and nothing behind a login.
Preply Email Scraper Input Schema
Every field below is taken verbatim from the Actor's input schema, including its default value.
| Field | Type | Default | Description |
|---|---|---|---|
keywords | array (required) | ["tutor", "language teacher"] | Search terms describing the Preply accounts you want (language, subject, specialism) |
location | string | "" | Optional location phrase added to every query |
customDomains | array | ["@gmail.com", "@yahoo.com"] | Only emails on these domains are collected; the leading @ is optional |
maxEmails | integer (1–10000) | 20 | Stop once this many unique emails have been collected |
countryCode | string | "" | Two-letter country code for the search proxy (ES, DE, BR, US…) |
expandQueries | boolean | true | Search each keyword × domain pair with several phrasings |
queryModifiers | array | ["email", "contact", "enroll", "coaching", "workshop"] | Extra words combined with each keyword when expansion is on |
maxPagesPerQuery | integer (1–50) | 30 | Page cap per query |
maxConcurrency | integer (1–20) | 5 | How many queries run in parallel |
JSON input example
{"keywords": ["spanish tutor", "business english teacher", "IELTS preparation"],"location": "Madrid","customDomains": ["@gmail.com", "@hotmail.com", "@outlook.com"],"maxEmails": 250,"countryCode": "ES","expandQueries": true,"queryModifiers": ["email", "contact", "enroll", "coaching", "workshop"],"maxPagesPerQuery": 30,"maxConcurrency": 5}
Language-plus-specialism keywords such as business english teacher or DELF preparation tutor outperform a bare tutor by a wide margin.
Preply Email Scraper Output Schema
Every dataset item produced by the Preply Email Scraper contains all 14 fields listed below.
| 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 (tutor handle or display name) |
fullName | Display name parsed from a profile-style title; empty for question or article pages |
username | URL-safe handle when Preply exposes one; otherwise null |
profileUrl | Canonical tutor URL when a handle is known; otherwise empty |
url | Direct platform link when exposed, else the profile URL |
description | Bio or page snippet, cleaned of labels and counters |
email | Lower-cased email address |
emailDomain | The matched domain (e.g. @gmail.com) |
possiblyTruncated | true when Google's snippet ellipsis touched the email — verify before sending |
foundAt | ISO 8601 UTC timestamp |
JSON output example
{"network": "Preply","keyword": "business english teacher","query": "site:preply.com business english teacher \"@gmail.com\" \"Madrid\"","title": "Elena R. - Business English Tutor | Preply","accountName": "elena-r-8241735","fullName": "Elena R.","username": "elena-r-8241735","profileUrl": "https://preply.com/en/tutor/elena-r-8241735","url": "https://preply.com/en/tutor/elena-r-8241735","description": "Business English and IELTS tutor based in Madrid. Corporate group bookings and workshop enquiries: elena.r.english@gmail.com","email": "elena.r.english@gmail.com","emailDomain": "@gmail.com","possiblyTruncated": false,"foundAt": "2026-08-31T10:44:19Z"}
How to Use the Preply Email Scraper
Step 1 — open the Actor. Launch the Preply Email Scraper on the Apify platform.
Step 2 — enter language and subject keywords. Tutors describe themselves by language, exam and niche, so TOEFL tutor, conversational japanese and french for kids beat generic terms.
Step 3 — set countryCode. This is a genuine lever on Preply: ES, DE, FR, BR, JP and TR each surface a different slice of the index.
Step 4 — choose email domains. Start with @gmail.com, then add @hotmail.com, @outlook.com and @yandex.com depending on the market you are targeting.
Step 5 — set maxEmails and run. Leave expandQueries on so the Preply Email Scraper can work past Google's per-query ceiling.
Step 6 — export. Download the Preply Email Scraper dataset as JSON, CSV or XLSX, or pull it into your CRM through the Apify API.
If you want the children's-education equivalent — group classes rather than one-to-one lessons — the Outschool Email Scraper is the closest sibling to this workflow.
Use Cases for the Preply Email Scraper
| Use case | How the Preply Email Scraper helps |
|---|---|
| Tutor recruiting | Source experienced online tutors by language, subject and country |
| Language-school partnerships | Find independent teachers open to corporate or group work |
| Edtech product marketing | Reach tutors who already deliver lessons online and pay for tools |
| Course-platform growth | Recruit tutors to launch structured courses elsewhere |
| Test-prep collaborations | Identify IELTS, TOEFL, DELE and JLPT specialists |
| Corporate training sourcing | Build shortlists of business-language tutors in a target city |
| Affiliate and referral programs | Approach tutors with an existing student audience |
| Market research | Study how tutors position rates, specialisms and availability via description snippets |
| CRM enrichment | Attach tutor handles and profile URLs to records you already hold |
| Agency prospecting | Assemble outreach lists for language-learning and edtech clients |
Preply's tutor population is segmented by language and exam far more than by geography, so your keyword choice matters more than your location phrase.
In every one of these scenarios the Preply Email Scraper does the tedious part — reading thousands of search results — and leaves judgement to you.
Why Choose This Preply Email Scraper
It returns real profile links. Because Preply publishes /en/tutor/{id} pages, most rows come with a profileUrl you can actually open and verify.
It is honest about its source. The Preply Email Scraper reads Google's public index. Nothing more, nothing concealed.
It is built for an international index. Locale handling plus countryCode targeting make multi-market runs practical.
It is resilient. Structural parsing plus a whole-page fallback means a Google layout change degrades output quality instead of breaking the crawler.
It is part of a family. The same engine powers sibling Actors across the education category, including the Udemy Email Scraper for marketplace instructors and the Kajabi Email Scraper for independent coaching businesses.
Limitations of the Preply Email Scraper
These are real constraints. Read them before setting expectations.
- Platform messaging reduces public emails. Preply keeps tutor contact details private by default and routes students through its own messaging system, so publicly listed addresses are less common than on creator platforms. Expect steady, moderate volume rather than a flood.
- Only publicly indexed emails. If an address is not visible in Google's index, the Preply Email Scraper cannot find it. Private data is never accessed.
- Google's ~300-result cap. One query returns roughly 300 results at most. Query expansion exists precisely to work around this, so keep
expandQuerieson. possiblyTruncated. When Google's snippet ellipsis touches an address, the flag is set totrue. Verify those rows before sending.- Apify GOOGLE_SERP proxy required. The Actor cannot run without Apify proxy credentials.
- Free-plan cap. Free Apify plans are limited to 100 emails per run. Paid plans are uncapped.
usernameandprofileUrlavailability. These are only filled in when Google's result exposes a handle. Rows sourced from Preply's question or article pages will haveaccountNameandfullNamebut an emptyusernameandprofileUrl. That is a Google limitation, not a bug.- No guaranteed volume. Results vary with keywords, domains, language and country.
Nothing here is affiliated with, endorsed by or officially supported by Preply.
Related Actors
| Actor | What it collects |
|---|---|
| Preply Email and Phone Number Scraper | Emails and phone numbers from Preply |
| Preply Phone Number Scraper | Public phone numbers from Preply |
| Academia.edu Email Scraper | Public contact emails from Academia.edu |
| Buy Me a Coffee Email Scraper | Public contact emails from Buy Me a Coffee |
| Carrd Email Scraper | Public contact emails from Carrd |
| Domestika Email Scraper | Public contact emails from Domestika |
| edX Email Scraper | Public contact emails from edX |
| Gumroad Email Scraper | Public contact emails from Gumroad |
| Kaggle Email Scraper | Public contact emails from Kaggle |
| Kajabi Email Scraper | Public contact emails from Kajabi |
| Ko-fi Email Scraper | Public contact emails from Ko-fi |
| Linktree Email Scraper | Public contact emails from Linktree |
| MasterClass Email Scraper | Public contact emails from MasterClass |
| Meetup Email Scraper | Public contact emails from Meetup |
| Pluralsight Email Scraper | Public contact emails from Pluralsight |
| ResearchGate Email Scraper | Public contact emails from ResearchGate |
| Skillshare Email Scraper | Public contact emails from Skillshare |
| Teachable Email Scraper | Public contact emails from Teachable |
| Udemy Email Scraper | Public contact emails from Udemy |
| Academia.edu Email and Phone Number Scraper | Emails and phone numbers from Academia.edu |
| Buy Me a Coffee Email and Phone Number Scraper | Emails and phone numbers from Buy Me a Coffee |
| Carrd Email and Phone Number Scraper | Emails and phone numbers from Carrd |
| Domestika Email and Phone Number Scraper | Emails and phone numbers from Domestika |
| edX Email and Phone Number Scraper | Emails and phone numbers from edX |
| Gumroad Email and Phone Number Scraper | Emails and phone numbers from Gumroad |
| Kaggle Email and Phone Number Scraper | Emails and phone numbers from Kaggle |
| Kajabi Email and Phone Number Scraper | Emails and phone numbers from Kajabi |
| Ko-fi Email and Phone Number Scraper | Emails and phone numbers from Ko-fi |
| Linktree Email and Phone Number Scraper | Emails and phone numbers from Linktree |
| MasterClass Email and Phone Number Scraper | Emails and phone numbers from MasterClass |
| Meetup Email and Phone Number Scraper | Emails and phone numbers from Meetup |
| Pluralsight Email and Phone Number Scraper | Emails and phone numbers from Pluralsight |
| ResearchGate Email and Phone Number Scraper | Emails and phone numbers from ResearchGate |
| Skillshare Email and Phone Number Scraper | Emails and phone numbers from Skillshare |
| Teachable Email and Phone Number Scraper | Emails and phone numbers from Teachable |
| Academia.edu Phone Number Scraper | Public phone numbers from Academia.edu |
| Buy Me a Coffee Phone Number Scraper | Public phone numbers from Buy Me a Coffee |
| Carrd Phone Number Scraper | Public phone numbers from Carrd |
| Domestika Phone Number Scraper | Public phone numbers from Domestika |
| edX Phone Number Scraper | Public phone numbers from edX |
| Gumroad Phone Number Scraper | Public phone numbers from Gumroad |
| Kaggle Phone Number Scraper | Public phone numbers from Kaggle |
Preply Email Scraper Example Run
A corporate language-training provider needs business English tutors across three European markets.
They run the Preply Email Scraper three times — countryCode: "ES", "DE" and "FR" — each with keywords: ["business english teacher", "corporate english tutor"] and customDomains: ["@gmail.com", "@outlook.com"].
Query expansion turns two keywords into a dozen phrasings per run, the Preply Email Scraper paginates through Google, and each dataset fills with tutor handles, bios and addresses.
They merge the three exports, open a sample of profileUrl links to confirm specialism, drop rows flagged possiblyTruncated, and hand a clean CSV to their recruiting team.
Preply Email Scraper FAQ
Does the Preply Email Scraper log into Preply?
No. It never logs in, never uses a Preply API and never opens preply.com. All data comes from publicly indexed Google search results.
Where do the emails actually come from?
From Google result titles, site labels and snippets for pages on preply.com — typically tutor profiles and question pages where an address was published publicly.
Do Preply tutors publish their email addresses?
Some do, many do not. Preply keeps tutor contact details private and pushes students toward in-platform messaging, so the Preply Email Scraper finds a meaningful but not exhaustive slice of the tutor population.
Will I get real profile URLs?
Usually yes. Preply publishes tutor pages at preply.com/en/tutor/{id}, so most rows carry a working profileUrl alongside the email.
Should I set countryCode?
On Preply, yes. It is a genuine lever — ES, DE, FR, BR, JP and TR each surface a different slice of the index, so separate runs beat one generic crawl.
Is this a Preply email extractor or a full profile scraper?
It is a Preply email extractor. It returns the 14 documented fields and nothing else — no lesson prices, no ratings, no availability calendars.
Do I need an Apify proxy?
Yes. The Preply Email Scraper requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.
How many emails can one run collect?
Free Apify plans are capped at 100 emails per run. Paid plans are uncapped, bounded only by your maxEmails value and what Google has indexed.
Why is username empty on some rows?
Because Google did not expose a tutor handle in that result — common for Preply's question and article pages. Those rows still carry accountName, fullName and the snippet.
What does possiblyTruncated: true mean?
Google's snippet ellipsis touched the email, so the address may be cut off. Verify those rows before sending anything.
Should I leave query expansion enabled?
Yes. Google caps a single query at roughly 300 results, and expansion is how the Preply Email Scraper reaches past that ceiling.
Does the Preply Email Scraper deduplicate?
Yes, globally. An email appears once per run regardless of how many queries or pages surfaced it.
What happens if a run is interrupted?
Progress is stored in the key-value store keyed by a hash of your input and flushed on PERSIST_STATE, MIGRATING and ABORTING, so restarting resumes rather than starting over.
Is this affiliated with Preply?
No. The Preply Email Scraper is an independent tool and is not affiliated with, endorsed by or officially supported by Preply.
How should I use the results responsibly?
Follow GDPR, CAN-SPAM and any other law that applies to you. Publicly visible does not mean consent to bulk marketing — keep outreach relevant and honour opt-outs.
Leave a review
If the Preply 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, bug reports or a custom build request? Email neurodata.apify@gmail.com and include your run ID so the Preply Email Scraper logs can be checked quickly.