Linktree Email Scraper
Pricing
from $2.49 / 1,000 results
Linktree Email Scraper
Linktree Email Scraper SD - Linktree Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Linktree results by keyword, location and email domain - Linktree email extractor.
Pricing
from $2.49 / 1,000 results
Rating
0.0
(0)
Developer
Leads Scraper
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
17 days ago
Last modified
Categories
Share
Linktree Email Scraper - extract public creator and small-business emails from Linktree
The Linktree Email Scraper collects publicly indexed contact emails from Linktree link-in-bio pages: influencers, UGC creators, musicians, podcasters, coaches, restaurants, nonprofits and small businesses.
You supply keywords, an optional location and a list of email domains. The Linktree Email Scraper builds domain-scoped Google queries against linktr.ee, parses each result block and writes every matching address into a structured dataset.
There is no login, no Linktree API, no headless browser and no cookies. This Linktree email extractor reads only what Google has already indexed publicly.
Linktree is one of the strongest sources in this family. A link-in-bio hub exists precisely so people can reach the owner, so a business email is often right there in the page description.
In practice most parsed rows carry an account identity and a usable linktr.ee profile URL, which makes the Linktree Email Scraper unusually good at producing rows you can act on straight away.
Influencer marketing teams, UGC agencies, booking agents, local marketers and B2B prospectors use the Linktree Email Scraper for contact discovery at a scale manual browsing cannot match.
Features of the Linktree Email Scraper
Everything below is implemented in the Linktree Email Scraper today. No roadmap items, no aspirational claims.
| Feature | What it means in practice |
|---|---|
Google site: search automation | Every query is scoped to linktr.ee, so results stay on-platform |
| Query expansion | Base, quoted and intitle: variants plus one variant per query modifier |
| Creator-tuned modifiers | Defaults are email, contact, business inquiries, collab, booking, dm |
| Domain-filtered extraction | Only emails on your customDomains list are kept |
| Global deduplication | Each unique address reaches the dataset exactly once across all queries and pages |
| Obfuscation-aware parser | Understands name [at] domain [dot] com, name (at) domain, name @ domain.com, domain .com |
| Unicode normalisation | Handles zero-width characters and the full-width at sign |
| 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 email in the same result block |
| Concurrency control | An asyncio worker pool runs 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, never scored as empty |
| Re-queue pass | Blocked or failed queries are retried once more at the end of the run |
| Resumable state | Progress persists in the key-value store, keyed by a hash of your input |
| Structural parsing | Result blocks are located via the <h3> title, not by Google's CSS class names |
| Fallback parser | A Google markup change degrades to "emails without account details", not "no emails" |
| Streaming dataset writes | Leads appear in the dataset immediately, so exports can begin mid-run |
How the Linktree Email Scraper works
The Linktree Email Scraper is a search-results crawler. It never opens linktr.ee, never follows the outbound links on a page and never renders JavaScript.
1. Read input. Keywords, location, email domains, page caps and concurrency are validated first.
2. Build queries. Queries use the site: operator, for example:
site:linktr.ee fitness coach "@gmail.com" "Austin".
3. Expand queries. With expandQueries on, each keyword and domain pair is issued as a base query, a quoted variant, an intitle: variant and one variant per entry in queryModifiers. Base queries always run first.
4. Fetch pages. The Linktree Email Scraper fetches result pages asynchronously with aiohttp through the Apify GOOGLE_SERP proxy, paginating up to maxPagesPerQuery.
5. Parse result blocks. The parser locates the <h3> title, then the smallest surrounding block, so titles, snippets and site labels stay attached to the correct record.
6. Extract and normalise. A domain-filtered regex pulls candidates from the block text, normalises them, and removes junk, tails and boundary mismatches.
7. Deduplicate and store. Every new address is deduplicated globally and pushed straight into the Apify dataset as structured data.
The Linktree Email Scraper run summary logs pages fetched, blocked pages, retries and emails per page, so you can judge a keyword set on evidence rather than instinct.
What data does the Linktree Email Scraper extract?
Each row is one email paired with the account metadata Google exposed alongside it.
You get the address, the matched domain, the account label, a parsed display name, the handle and profile URL, a cleaned bio snippet and full provenance.
Provenance is the underrated part. The keyword and query fields tell you which phrasing surfaced a creator, which is exactly what you tune on the next lead generation run.
Because every Linktree page is keyed by handle, the Linktree Email Scraper resolves username and rebuilds profileUrl as https://linktr.ee/<handle> on the large majority of parsed results.
Input schema for the Linktree Email Scraper
Every Linktree Email Scraper input field is listed below with the exact name, type and default from the Actor input schema.
| Field | Type | Default | Description |
|---|---|---|---|
keywords | array (required) | ["creator", "small business"] | Search terms describing the Linktree accounts you want (niche, job title, industry) |
location | string | "" | Optional location phrase added to every query, e.g. "New York" |
customDomains | array | ["@gmail.com", "@yahoo.com"] | Only emails ending with one of these domains are collected; leading @ 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 (US, GB, DE). Empty for any |
expandQueries | boolean | true | Search each keyword and domain pair with several phrasings |
queryModifiers | array | ["email", "contact", "business inquiries", "collab", "booking", "dm"] | 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 |
Input example
{"keywords": ["ugc creator", "fitness coach", "makeup artist"],"location": "","customDomains": ["@gmail.com", "@outlook.com"],"maxEmails": 500,"countryCode": "US","expandQueries": true,"queryModifiers": ["email", "contact", "business inquiries", "collab", "booking", "dm"],"maxPagesPerQuery": 30,"maxConcurrency": 5}
Output schema of the Linktree Email Scraper
Every dataset item the Linktree Email Scraper produces carries all fourteen fields 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 (handle or display name) |
fullName | Display name parsed from a profile-style title; empty for generic page titles |
username | URL-safe handle when Linktree exposes one; otherwise null |
profileUrl | Canonical account URL when a handle is known; otherwise empty |
url | Direct Linktree link when exposed, else the profile URL |
description | Bio or page snippet, cleaned of labels and engagement 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 |
Output example
{"network": "Linktree","keyword": "ugc creator","query": "site:linktr.ee ugc creator \"@gmail.com\" business inquiries","title": "Priya Raman | UGC Creator | Linktree","accountName": "priyacreates","fullName": "Priya Raman","username": "priyacreates","profileUrl": "https://linktr.ee/priyacreates","url": "https://linktr.ee/priyacreates","description": "UGC and short-form video for beauty and wellness brands. Portfolio, rates and past work. Business inquiries: priya.ugc@gmail.com","email": "priya.ugc@gmail.com","emailDomain": "@gmail.com","possiblyTruncated": false,"foundAt": "2026-08-31T13:26:41.075Z"}
The Linktree Email Scraper dataset exports as JSON, CSV, Excel or XML from the Apify console, or streams through the Apify API into your CRM, influencer platform or outreach tool.
How to use the Linktree Email Scraper
Step 1 - describe the niche the way a bio does. Linktree titles and descriptions read like UGC Creator | Beauty & Wellness. Keywords such as ugc creator, fitness coach, tattoo artist, wedding photographer or food truck match that language.
Step 2 - pick email domains that fit independents. @gmail.com is by far the most common on link-in-bio pages. Add others only when your segment justifies it.
Step 3 - start small. Run the Linktree Email Scraper with maxEmails at 20 to 50 to confirm the keyword set surfaces the right creator tier, then scale.
Step 4 - keep the creator-tuned modifiers. business inquiries, collab and booking are the exact phrases creators put next to their address on a Linktree page.
Step 5 - use location for local segments. Local businesses and service providers often name a city, so a location phrase works well for that half of the audience and less well for global creators.
Step 6 - clean before you send. Filter out rows where possiblyTruncated is true, then put the remaining Linktree Email Scraper results through your normal email-verification step.
Use cases for the Linktree Email Scraper
| Use case | Who runs it | Typical keywords |
|---|---|---|
| Influencer and UGC campaign sourcing | Brand and influencer marketing teams | ugc creator, beauty, fitness coach |
| Creator partnership pipelines | Agencies and creator platforms | creator, podcast, streamer |
| Local small-business prospecting | Web agencies and local marketers | bakery, salon, photographer |
| Music and event booking | Bookers, promoters and venues | dj, band, producer |
| Coaching and services lead generation | Course sellers and lead-gen agencies | life coach, nutritionist, consultant |
| Affiliate and referral recruitment | Affiliate program managers | deals, review, discount code |
| Nonprofit and community outreach | Fundraisers and community teams | nonprofit, charity, mutual aid |
| Creator-economy market research | Analysts studying link-in-bio adoption | any niche keyword, varied by location |
Because a link hub is a contact page by design, the Linktree Email Scraper generally returns a higher share of rows with a real handle and profile URL than platforms where Google prints only a display name.
Creators who point their hub at a paid page will also appear in the Ko-fi Email Scraper and the Buy Me a Coffee Email Scraper, while people who built a one-page site instead of a link hub are covered by the Carrd Email Scraper.
Why choose this Linktree Email Scraper
Building an outreach list by hand means searching, opening a page, reading the bio, copying an address and repeating. The Linktree Email Scraper automates the loop and returns a deduplicated dataset.
Every row is auditable. The query and keyword fields show exactly how a lead was found, so unproductive keyword sets are easy to prune.
The extraction layer is deliberately conservative. Junk filtering, boundary-correct domain matching and soft-wrap repair mean far fewer garbage rows to clean downstream.
Long Linktree Email Scraper runs survive interruption. State persists in the key-value store and saves fire on Apify's PERSIST_STATE, MIGRATING and ABORTING events.
Worked example: a UGC creator shortlist
You run influencer marketing for a skincare brand and want 500 UGC creators with a published business email.
Set keywords to ["ugc creator", "skincare", "beauty creator"], customDomains to ["@gmail.com"], countryCode to "US" and maxEmails to 500, leaving expandQueries on.
The Linktree Email Scraper issues base, quoted and intitle: variants plus one query per modifier, paginating each independently and streaming leads as they are found.
Export the Linktree Email Scraper dataset to CSV, drop possiblyTruncated rows, group by keyword to see which niche performed best, then push the rest into your campaign tool.
Limitations you should know before running
The Linktree Email Scraper is deliberately transparent about its boundaries. Read these before planning a large data collection run.
Only publicly indexed emails. The Linktree Email Scraper returns addresses that already appear in Google's index. A creator who put their address only inside a button label Google never indexed will not surface.
No link following. The Actor reads Google's result blocks, not the destinations behind a Linktree page's outbound buttons.
Google's per-query ceiling. A single query caps out at roughly 300 results. Query expansion exists to work around that ceiling, which is why it defaults to on.
possiblyTruncated. When Google's snippet ellipsis touches an address, this field is true and the email may be incomplete. Verify those rows before sending.
Apify GOOGLE_SERP proxy required. The Linktree Email Scraper cannot run without Apify proxy credentials that include the GOOGLE_SERP group.
Free-plan cap. Running the Linktree Email Scraper on a free Apify plan limits results to 100 emails per run. Paid plans are uncapped.
Handle availability. username and profileUrl are populated only when Google's result exposes a Linktree handle. Linktree performs well here, but some rows will still carry accountName and fullName with an empty username and profileUrl, which is a Google limitation, not a bug.
No guaranteed volume. Linktree Email Scraper yield varies with keywords, domains and location. No result count is promised.
The Linktree Email Scraper is not affiliated with, endorsed by or officially supported by Linktree.
Related Actors
Every Actor below runs the same engine as the Linktree Email Scraper, with identical input fields and an identical output schema; only the target platform differs.
| Actor | What it collects |
|---|---|
| Linktree Email and Phone Number Scraper | Emails and phone numbers from Linktree |
| Linktree Phone Number Scraper | Public phone numbers from Linktree |
| 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 |
| MasterClass Email Scraper | Public contact emails from MasterClass |
| Meetup Email Scraper | Public contact emails from Meetup |
| Pluralsight Email Scraper | Public contact emails from Pluralsight |
| Preply Email Scraper | Public contact emails from Preply |
| 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 |
| 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 |
| Preply Email and Phone Number Scraper | Emails and phone numbers from Preply |
| 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 |
FAQ about the Linktree Email Scraper
What is the Linktree Email Scraper?
It is an Apify Actor that extracts publicly indexed contact emails from Linktree pages by running domain-scoped Google searches and parsing the resulting search-result blocks.
Does the Linktree Email Scraper open linktr.ee pages?
No. It never loads a Linktree page, never runs JavaScript and never logs in. It reads Google's indexed titles, snippets and site labels only.
Does it follow the links on a Linktree page?
No. The Linktree Email Scraper reads search-result blocks, so it does not visit the Instagram, YouTube or shop links a creator lists.
Why is Linktree a good source for creator emails?
A link-in-bio hub is where creators consolidate contact details, so a business address very often appears in the indexed page description.
Why is username empty on some rows?
Google does not always print a handle in the result. Those rows still carry accountName and fullName, but username is null and profileUrl is empty. On Linktree this is the minority case.
What does possiblyTruncated: true mean?
Google's snippet ellipsis touched the address, so it may be cut off. Verify those rows before contacting anyone.
How many emails will one run of the Linktree Email Scraper return?
maxEmails accepts 1 to 10000, but free Apify plans are capped at 100 emails per run and paid plans are uncapped. Real volume depends on keywords, domains and location.
Is a proxy required?
Yes. The Linktree Email Scraper requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.
Should I leave expandQueries on?
Almost always. Google returns roughly 300 results per query, and expansion multiplies your reachable surface through base, quoted, intitle: and modifier variants.
Can I target a specific country or city?
Yes. Set countryCode for the search proxy and add a location phrase. Location works best for local businesses and service providers.
What happens if my run is interrupted or migrated?
State persists in the key-value store keyed by a hash of your input, with throttled saves plus saves on PERSIST_STATE, MIGRATING and ABORTING, so an interrupted run resumes instead of restarting.
Can I email everyone in the dataset immediately?
Treat the Linktree Email Scraper output as raw lead data. Deduplication is automatic, but verification, consent and compliance with GDPR, CAN-SPAM and Linktree's terms remain your responsibility.
Leave a review
If the Linktree 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 about the Linktree Email Scraper, bug reports or a custom build? Email neurodata.apify@gmail.com.