Facebook Email Scraper
Pricing
from $1.49 / 1,000 results
Facebook Email Scraper
Facebook Email Scraper extracts publicly indexed Facebook email addresses using targeted keywords, locations, and email domains. Find relevant leads, business contacts, and prospect data with automated Google search, duplicate filtering, and structured Apify dataset output.
Pricing
from $1.49 / 1,000 results
Rating
0.0
(0)
Developer
Email Scraper
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Facebook Email Scraper Overview
Facebook Email Scraper is an Apify Actor designed to extract publicly visible email addresses associated with Facebook search results. It searches Google for Facebook pages and profiles using your keywords, optional location, and selected email-domain suffixes, then returns structured lead data in an Apify dataset.
The Facebook Email Scraper is useful for lead generation, prospect research, market research, contact discovery, and building targeted lists from publicly indexed Facebook content. You can combine multiple keywords, locations, and email domains to broaden or refine your search.
The scraper does not access private Facebook information. It works with information available through Google search results for publicly indexed Facebook pages and profiles.
Facebook Email Scraper Features
The Facebook Email Scraper provides a keyword-driven workflow for discovering publicly indexed Facebook contact information.
Key capabilities include:
- Keyword-based Facebook email extraction using Google search queries.
- Multiple keywords in a single Actor run.
- Multiple email domains, such as
@gmail.com,@yahoo.com, or custom domains. - Optional geographic targeting using a country, state, or city.
- Exclude-word filtering for removing unwanted search-result snippets.
- Per keyword + domain email targets controlled by
maxEmails. - Duplicate email detection across the entire run.
- Google SERP proxy usage through Apify's
GOOGLE_SERPproxy group. - Pagination through Google search results to discover additional indexed pages.
- Incremental dataset output as emails are discovered.
- Persistent progress tracking for improved recovery after interruptions.
- Structured lead information including keyword, title, description, URL, and email.
These features make the Facebook Email Scraper suitable for users who need a practical Facebook data extractor without manually searching individual pages.
How to Use the Facebook Email Scraper
Using the Facebook Email Scraper is straightforward:
- Enter one or more relevant keywords.
- Optionally enter a country, state, or city in the location field.
- Add the email-domain suffixes you want to search for.
- Set the maximum email target.
- Optionally add words or phrases to exclude.
- Start the Actor.
- Review the discovered leads in the Apify dataset.
For better coverage, use several specific keywords instead of one broad term.
For example, rather than searching only for:
fitness
you can use:
fitness coachfitness trainerfitness influenceronline fitness coachpersonal trainer
Each keyword is processed against each configured email domain.
The Facebook Email Scraper constructs Google searches using the following general pattern:
site:facebook.com <keyword> "<email-domain>"
When a location is supplied, the location is added to the search query as well.
Facebook Email Scraper Data Extraction
The Facebook Email Scraper parses Google organic search results and examines the result descriptions for email addresses matching your configured domain suffixes.
For example, when @gmail.com is selected, the scraper searches result descriptions for email addresses ending in that domain.
The extracted lead contains the original search keyword, result title, description, Facebook-related URL returned by the search result, and discovered email address.
This makes the resulting dataset useful for downstream lead research and data analysis.
The scraper also maintains a set of previously discovered email addresses. When the same email appears again during the run, it is not pushed as another unique result.
What the Facebook Email Scraper Searches
The search process is based on Google SERP results containing:
- Facebook URLs
- User-provided keywords
- Selected email-domain suffixes
- Optional location terms
The Actor does not directly crawl private Facebook profiles or require Facebook login credentials.
Facebook Email Scraper Use Cases
The Facebook Email Scraper can support several legitimate business and research workflows.
Lead Generation
Sales and marketing teams can search for publicly indexed Facebook contacts related to specific industries, professions, products, or services.
For example, keywords such as real estate agent, photographer, fitness coach, or restaurant owner can help discover relevant search results.
Market Research
Researchers can collect publicly indexed contact information associated with specific market segments and compare results across keywords or geographic areas.
Prospect Research
Businesses can use targeted search terms to identify potential prospects whose publicly indexed Facebook information includes an email address.
Competitor and Industry Research
The extracted title, description, URL, and email fields can provide additional context for researching businesses, creators, organizations, and other publicly indexed Facebook entities.
Data Analysis
Because results are pushed as structured dataset records, users can analyze discovered contacts according to keyword, domain, description, or source URL.
Contact Discovery
The Facebook Email Scraper can help discover publicly listed email addresses that may otherwise require substantial manual Google searching.
Always ensure that your use of collected contact information complies with applicable privacy, data-protection, anti-spam, and platform rules.
Facebook Email Scraper Input
The following inputs are available in the Actor configuration.
| Input | Type | Required | Default | Description |
|---|---|---|---|---|
keywords | Array of strings | Yes | ["skincare", "cosmetics"] | Keywords or search queries used to find relevant Facebook results. |
location | String | No | "" | Optional country, state, or city used to narrow Google searches. |
customDomains | Array of strings | No | ["@gmail.com"] | Email-domain suffixes to search for. |
maxEmails | Integer | No | 10 | Maximum email target for each keyword + domain combination. Valid range is 1–10,000. |
excludeWords | Array of strings | No | [] | Words or phrases that cause matching search-result snippets to be skipped. |
Keywords
keywords accepts multiple search terms.
Specific keywords generally provide more targeted search queries than extremely broad terms. You can therefore provide several related variations to expand search coverage.
Example:
{"keywords": ["skincare","skincare brand","beauty influencer","cosmetics store"]}
Location
location is optional.
For example:
{"location": "New York"}
The location is added to the Google search query to narrow results geographically. It is a search-query filter rather than a post-scrape verification of the profile's actual physical location.
Leave it empty when you want to search without a geographic term.
Custom Email Domains
customDomains controls which email suffixes the scraper looks for.
Example:
{"customDomains": ["@gmail.com","@yahoo.com","@outlook.com"]}
Custom domains can also be supplied when you want to search for specific business-domain addresses.
Maximum Emails
maxEmails defines the target for each keyword + domain combination.
For example, with:
- 3 keywords
- 2 email domains
maxEmails = 20
the Actor processes six keyword/domain combinations, with a target of up to 20 newly discovered addresses for each combination.
The configured value can be between 1 and 10,000.
For free users, the implementation applies a maximum overall run limit of 100 unique emails.
Exclude Words
excludeWords allows you to skip unwanted search-result descriptions.
Example:
{"excludeWords": ["crypto","onlyfans"]}
Single-word exclusions use case-insensitive whole-word matching. Phrases use case-insensitive substring matching.
If a result description matches an exclusion, the entire snippet is skipped and no email is extracted from that result.
Facebook Email Scraper Output Data
The Facebook Email Scraper pushes structured records to the Apify dataset.
| Field | Type | Description |
|---|---|---|
network | String | Source network identifier. The implementation sets this to Facebook.com. |
keyword | String | Keyword responsible for the search result. |
title | String | Title extracted from the Google organic result. |
description | String | Description/snippet associated with the search result. |
url | String | URL extracted from the Google search result. |
email | String | Unique email address extracted from the result description. |
The most important field for contact discovery is email. The keyword field shows which search term produced the result, while title, description, and url provide contextual information about the corresponding search result.
The network field identifies the intended source as Facebook.
The dataset view configured in actor.json displays keyword, title, description, url, and email in its primary table. The underlying records pushed by main.py also contain the network field.
Example Input
The following is a valid example using the Actor's supported input structure:
{"keywords": ["fitness coach","personal trainer","online fitness coach"],"location": "New York","customDomains": ["@gmail.com","@yahoo.com"],"maxEmails": 20,"excludeWords": ["crypto","onlyfans"]}
Example Output
A resulting dataset record follows the structure produced by main.py:
{"network": "Facebook.com","keyword": "fitness coach","title": "Example Fitness Coach | Facebook","description": "Fitness coach ... contact example@gmail.com ...","url": "https://www.facebook.com/example","email": "example@gmail.com"}
Actual titles, descriptions, URLs, and emails depend on the Google search results available for your selected keywords, domains, and location.
Facebook Email Scraper Search and Pagination
The Facebook Email Scraper processes each keyword and email-domain combination separately.
For every combination, it creates a Google search query and retrieves search-result pages. Pagination can continue through a large number of pages when useful results remain available.
The implementation has several stopping conditions designed to avoid continuing indefinitely when searches stop producing useful new email addresses.
The collector can stop when the configured target is reached, when multiple consecutive pages produce no new emails, when later pages become inefficient, when empty result pages persist, or when repeated request failures trigger an abort for the current pair.
This means the Actor does not blindly process every possible page when the search is no longer producing useful results.
Facebook Email Scraper Duplicate Handling
The Facebook Email Scraper maintains a set of emails already discovered during the run.
When an email address appears again in another search result, the Actor checks whether it has already been registered. Existing addresses are skipped instead of being pushed again.
This helps keep the resulting dataset focused on unique email addresses.
Duplicate handling applies across the run rather than only to an individual Google result page.
Facebook Email Scraper Proxy and Request Handling
The Facebook Email Scraper uses Apify's GOOGLE_SERP proxy group when initializing its Google search infrastructure.
The proxy manager can rotate the proxy URL when a request fails.
Google SERP requests also use retry behavior. If repeated page requests fail, the scraper records the failures and can stop processing the current keyword/domain combination after the configured failure threshold is reached.
This behavior is intended to make Google search retrieval more resilient while preventing a repeatedly failing search pair from continuing indefinitely.
Facebook Email Scraper Progress and Resume Behavior
The implementation persists scraping progress in an Apify key-value store.
The stored state includes:
- Previously discovered email addresses
- Current keyword position
- Current domain position
Progress is saved as results are processed and when keyword/domain combinations advance.
This allows the Actor to retain run state if execution is interrupted and provides a mechanism for continuing from the stored processing position rather than treating every execution step as completely new.
Facebook Email Scraper Result Limits
The maxEmails setting has a per keyword + domain combination target in the implementation.
For example:
Keywords: 2Domains: 3maxEmails: 10
creates six keyword/domain combinations, with each combination having its own target of up to 10 newly discovered emails.
The actual number returned can be lower because the scraper can only extract email addresses that are present in the retrieved search-result descriptions.
For free users, the code applies a maximum of 100 unique emails per run. Paid users are not subjected to that code-level free-tier ceiling.
Improving Facebook Email Scraper Results
If the Facebook Email Scraper returns fewer addresses than expected, consider broadening the search strategy.
Useful approaches include:
- Add related keyword variations.
- Replace extremely narrow phrases with broader terms.
- Add additional email domains.
- Remove the location filter when geographic targeting is unnecessary.
- Use several job titles or industry-specific terms.
- Review whether
excludeWordsis filtering too aggressively.
For example, instead of using only marketing, consider:
marketing agencydigital marketingmarketing consultantsocial media marketingmarketing manager
Using multiple relevant search terms can provide broader search coverage than relying on one keyword.
Facebook Email Scraper Search Intent
The Facebook Email Scraper is designed around search intent such as finding publicly indexed Facebook contact information, discovering email addresses associated with relevant Facebook results, researching businesses and professionals, and building structured contact datasets.
Common tasks include:
- Finding Facebook contacts by industry
- Discovering business-related email addresses
- Searching Facebook results by keyword
- Narrowing search results by location
- Searching specific email providers
- Extracting structured contact information
- Building datasets for research and analysis
The combination of keyword, location, and email-domain filters lets users create focused searches instead of relying on a single generic Facebook query.
Frequently Asked Questions
What is the Facebook Email Scraper?
The Facebook Email Scraper is an Apify Actor that searches Google for publicly indexed Facebook results and extracts email addresses matching the configured email-domain suffixes.
How does the Facebook Email Scraper find emails?
The Facebook Email Scraper builds Google queries using site:facebook.com, your keyword, and the selected email-domain suffix. It then extracts matching email addresses from Google result descriptions.
Can I search multiple Facebook keywords?
Yes. The keywords input accepts an array of strings, allowing multiple searches within one Actor run.
Can I use a location with the Facebook Email Scraper?
Yes. The optional location input accepts a country, state, city, or other geographic search term. It is added to the Google query to narrow search results.
Can I search multiple email domains?
Yes. The Facebook Email Scraper supports multiple values in customDomains, such as @gmail.com, @yahoo.com, and @outlook.com.
What does maxEmails mean?
maxEmails is the target for each keyword + domain combination. It is not simply one shared target across all configured keyword/domain combinations.
Does the Facebook Email Scraper remove duplicates?
Yes. The implementation maintains a set of previously discovered email addresses and skips emails that have already been collected during the run.
Can I exclude unwanted results?
Yes. Use excludeWords to skip search-result descriptions containing specified words or phrases.
Does the scraper access private Facebook profiles?
No. The implementation searches Google for publicly indexed Facebook results and extracts information available in those search-result descriptions. It does not log into Facebook or claim access to private profile information.
What data does the Facebook Email Scraper return?
Each pushed record contains network, keyword, title, description, url, and email.
Does the Facebook Email Scraper guarantee the requested number of emails?
No. maxEmails is a target/cap, not a guarantee. Results depend on what publicly indexed Google results contain for the selected search terms, domains, and location.
Why did my run return fewer emails?
A search may contain few relevant results, no matching email addresses, duplicate addresses, excluded snippets, or insufficient publicly indexed information. Broader keywords and additional domains can improve coverage.
Is the output structured?
Yes. The Facebook Email Scraper pushes structured records into the Apify dataset, making the collected lead information easier to review and process.
Why Use This Actor
The Facebook Email Scraper combines targeted search inputs with automated extraction so users do not have to manually inspect large numbers of Google results.
Its practical advantages include:
- Automated discovery instead of manual searching.
- Keyword targeting for specific industries and audiences.
- Location targeting when geographic search terms are useful.
- Domain targeting for selected email providers or domains.
- Duplicate prevention for cleaner results.
- Exclude filtering for unwanted search-result snippets.
- Structured dataset records for easier analysis.
- Incremental output as results are discovered.
- Progress persistence for improved recovery after interruptions.
- Proxy rotation and retry handling for Google SERP requests.
The result is a focused workflow for turning relevant search queries into structured Facebook contact data.
API and Automation
The Facebook Email Scraper runs as an Apify Actor and stores extracted records in its Apify dataset.
Users can configure the Actor's supported input fields and execute it through the Apify platform or compatible Apify automation workflows. Dataset records can then be processed using Apify's available dataset and Actor tooling.
The Actor itself does not define additional third-party integrations or custom API endpoints beyond the functionality provided by its Apify runtime.
Best Practices for Facebook Email Scraper
For stronger results, start with focused but sufficiently broad keywords.
A useful strategy is to combine:
- Industry terms
- Job titles
- Service categories
- Audience descriptions
- Product categories
- Geographic terms when necessary
For example:
Keyword 1: skincareKeyword 2: skincare brandKeyword 3: beauty storeKeyword 4: cosmetics business
You can then combine those searches with multiple email-domain suffixes.
Avoid making searches unnecessarily restrictive. A highly specific keyword, narrow location, single domain, and aggressive exclusion list can significantly reduce the number of matching public results.
Facebook Email Scraper Limitations
The Facebook Email Scraper depends on publicly indexed Google search results, so it cannot extract information that Google does not expose in the retrieved result pages.
Important considerations include:
- A Facebook page or profile may not be indexed by Google.
- A result may not contain an email address.
- An email may be present but use a domain you did not configure.
- Location filtering is based on the Google search query and is not a verified physical-location check.
maxEmailsdoes not guarantee that the requested number exists.- Exclusion rules can intentionally remove otherwise matching results.
- Repeated request failures can stop processing for a keyword/domain pair.
- Search-result availability can vary over time.
These limitations are inherent to a search-result-based extraction approach.
Getting Better Value From the Facebook Email Scraper
The best results usually come from combining several relevant search dimensions rather than relying on one broad keyword.
Start with a small number of targeted terms, review the returned data, and then expand with related keywords or email domains.
If results are sparse, consider removing the location filter or broadening your keywords. If results are too broad, use more specific terms or exclusion words to focus the dataset.
This approach makes the Facebook Email Scraper useful for both targeted contact discovery and broader market research workflows.
Support
If you encounter an issue with the Facebook Email Scraper, first review your keywords, email-domain settings, location, exclusion terms, and maxEmails configuration.
For Actor-specific assistance, customization requests, or bespoke scraper development, use the support contact provided in the Actor configuration:
When reporting an issue, include the relevant input configuration and a description of the unexpected behavior so it can be investigated efficiently.