# Manageo Email Scraper (`email_scraper/manageo-email-scraper`) Actor

Manageo Email Scraper extracts publicly available email addresses from Manageo using targeted keywords, locations, and custom email domains. Build structured contact and lead datasets for business research, prospecting, market analysis, and outreach workflows.

- **URL**: https://apify.com/email\_scraper/manageo-email-scraper.md
- **Developed by:** [Email Scraper](https://apify.com/email_scraper) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### 🔍 Manageo Email Scraper – Overview

**Manageo Email Scraper** extracts publicly discoverable email addresses from Manageo profiles based on the keywords, locations, and email domains you specify. It is designed for lead research, business prospecting, contact discovery, market research, and building structured contact datasets from Manageo search results.

Instead of manually opening profiles and looking for contact information, **Manageo Email Scraper** searches for relevant Manageo results, reads the available profile information, identifies matching email addresses, and stores the results in an Apify Dataset.

> **💡 Manageo Email Scraper at a glance**
>
> - Search Manageo profiles using multiple keywords
> - Optionally narrow searches by country, state, city, or region
> - Filter results by specific email domain suffixes
> - Exclude profiles whose descriptions contain unwanted terms
> - Remove duplicate email addresses across the run
> - Store results incrementally in an Apify Dataset
> - Use a configurable email target from 1 to 10,000 per keyword/domain combination
> - Free users are limited to 100 emails by the Actor's plan handling

The easiest workflow is simple: enter specific keywords, optionally provide a location, choose the email domains you need, set the maximum number of emails, and start the Actor.

### 🔹 Manageo Email Scraper – Key Features

**Manageo Email Scraper** combines keyword targeting, geographic filtering, domain filtering, exclusion rules, and structured lead collection in one workflow.

> **🚀 Key Features**
>
> - **Keyword-based discovery:** Search using one or many business-related keywords.
> - **Location targeting:** Add a city, country, state, or other geographic term when regional targeting is required.
> - **Custom email domains:** Target domains such as `@gmail.com`, `@yahoo.com`, `@outlook.com`, or other suffixes.
> - **Exclude words:** Skip profile snippets containing selected words or phrases.
> - **Per-combination limits:** Set a maximum email target for every keyword + domain combination.
> - **Duplicate prevention:** The same email address is not collected repeatedly during the run.
> - **Structured dataset:** Results are stored with keyword, title, description, URL, and email information.
> - **Incremental storage:** Records are pushed as they are discovered instead of waiting for the entire run to finish.
> - **Resume support:** Run progress is retained so interrupted processing can continue from its stored position.

These features make **Manageo Email Scraper** suitable for both small targeted searches and larger keyword-based contact discovery jobs.

### 📊 Manageo Email Scraper – What Data Can You Extract?

The main purpose of **Manageo Email Scraper** is to turn relevant Manageo search results into structured lead records.

Each collected record contains the search context and information associated with the discovered result.

> **📦 Output / Data Fields**
>
> | Field         | Description                                         |
> | ------------- | --------------------------------------------------- |
> | `keyword`     | Keyword that produced the result                    |
> | `title`       | Title associated with the discovered result         |
> | `description` | Search-result description or profile snippet        |
> | `url`         | URL associated with the result                      |
> | `email`       | Email address discovered in the result              |
> | `network`     | Source network value identifying the Manageo source |

The dataset view is configured to prominently display `keyword`, `title`, `description`, `url`, and `email`, making the results easy to inspect and process.

The **Manageo Email Scraper** does not claim to retrieve private contact information. Results depend on email addresses that are publicly exposed in the searchable information available to the Actor.

### ⚙️ Manageo Email Scraper – How to Use It

Using **Manageo Email Scraper** requires only a few input decisions. The quality of the search terms has a direct effect on the relevance and volume of the results.

#### 📝 1. Add your keywords

Enter one or more keywords describing the businesses, professions, services, or topics you want to discover.

Specific combinations usually provide more focused results than very broad terms.

For example, instead of only searching:

```text
fitness
```

consider:

```text
fitness coach
fitness trainer
online fitness coach
fitness instructor
```

Multiple related keywords allow **Manageo Email Scraper** to cover different search intents.

#### 📍 2. Add an optional location

Use the `location` field when you need geographic targeting.

Examples include:

```text
New York
Paris
France
Texas
Chicago
```

Leave the field empty when geographic filtering is unnecessary.

#### ✉️ 3. Choose email domains

The `customDomains` field controls which email suffixes the Actor searches for.

Example:

```json
["@gmail.com", "@yahoo.com", "@outlook.com"]
```

You can also use a company-specific domain when your search requires business email addresses.

#### 🔢 4. Set the email limit

`maxEmails` accepts values from **1 to 10,000**.

The limit is applied separately to each **keyword + email-domain combination**, rather than being one shared number for the entire run.

For example, with:

```text
3 keywords × 2 email domains × 20 max emails
```

the Actor processes six combinations, with a target of up to 20 emails for each combination. Duplicate addresses can reduce the final unique count.

#### 🚫 5. Add exclusions

Use `excludeWords` to skip unwanted profile descriptions.

For example:

```json
["crypto", "onlyfans"]
```

A matching description is skipped so that an email is not collected from that result.

Single-word exclusions use whole-word matching, while phrases can match as text within the description. Matching is case-insensitive.

### 🔎 How to Extract Manageo Emails with Specific Keywords

The most practical way to use **Manageo Email Scraper** is to build a keyword set around the type of contact you need.

For business prospecting, combine a broad industry term with specific roles, services, or specialties.

For example:

```text
web designer
web development agency
freelance web designer
ecommerce developer
```

You can then add several email domains:

```json
["@gmail.com", "@yahoo.com", "@outlook.com"]
```

This creates multiple search combinations and increases the number of opportunities for discovering relevant email addresses.

Location can be added when the project is limited to a market such as:

```text
London
United Kingdom
Manchester
```

> **🎯 Search-quality tip**
>
> - More specific keywords can improve relevance.
> - Related keyword variations can expand coverage.
> - Removing a location can broaden discovery.
> - Adding additional email domains can reveal different contact types.
> - Narrow searches may naturally return fewer emails.

### 🧩 Can Manageo Email Scraper Search by Location?

Yes. **Manageo Email Scraper** supports an optional `location` input.

The field accepts a manually entered country, state, city, or similar geographic term. This allows users to combine business intent with geographic targeting.

For example:

```text
Keyword: dental clinic
Location: Paris
Domain: @gmail.com
```

This approach can be useful when building location-specific prospect lists or researching businesses in a defined geographic market.

Leaving `location` blank removes that geographic keyword from the search and provides broader coverage.

### 🛠️ Manageo Email Scraper – Input

The following inputs are available in the Actor configuration.

| Input           | Type    | Required | Default                 | Range / Notes                           |
| --------------- | ------- | -------: | ----------------------- | --------------------------------------- |
| `keywords`      | Array   |      Yes | `skincare`, `cosmetics` | One or more search terms                |
| `location`      | String  |       No | Empty                   | Country, state, city, or region         |
| `customDomains` | Array   |       No | `@gmail.com`            | Email suffixes to target                |
| `maxEmails`     | Integer |       No | `10`                    | 1–10,000 per keyword/domain combination |
| `excludeWords`  | Array   |       No | Empty                   | Words or phrases to skip                |

#### 📥 Sample Input

```json
{
  "keywords": [
    "fitness coach",
    "personal trainer",
    "online fitness coach"
  ],
  "location": "New York",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com"
  ],
  "maxEmails": 20,
  "excludeWords": [
    "crypto",
    "onlyfans"
  ]
}
```

This configuration tells **Manageo Email Scraper** to search three keyword variations, apply the New York location, look for three email suffixes, target up to 20 emails for each combination, and skip descriptions containing the excluded terms.

### 📤 Manageo Email Scraper – Output

The collected records are stored in an Apify Dataset, where they can be reviewed and processed as structured data.

#### Sample Output

```json
{
  "network": "Manageo.com",
  "keyword": "fitness coach",
  "title": "Example Fitness Coach",
  "description": "Example profile description containing a public email address.",
  "url": "https://example.com/profile",
  "email": "contact@example.com"
}
```

A real result will depend on what is publicly available for the searched terms and domains. The Actor does not guarantee that every searched profile contains an email address.

The dataset is particularly useful for downstream analysis because each record preserves the original search keyword alongside the discovered contact and result context.

### 💼 Manageo Email Scraper – Use Cases

**Manageo Email Scraper** can support a range of contact-discovery and research workflows where public email information is useful.

> **📌 Common Use Cases**
>
> - **Lead generation:** Build targeted prospect datasets around specific industries or services.
> - **B2B prospecting:** Search professional and business-related keywords with company email domains.
> - **Local business research:** Combine keywords with cities, regions, or countries.
> - **Market research:** Collect publicly listed contact information for defined market segments.
> - **Agency prospecting:** Discover businesses that may require marketing, design, development, or consulting services.
> - **Outreach list preparation:** Create structured datasets that can be reviewed before use in an outreach workflow.
> - **Competitive research:** Explore businesses and public contact information within selected categories.
> - **Data enrichment:** Combine the collected email, URL, title, and description with information from other workflows.

Results should be reviewed for accuracy, relevance, and appropriate use before contacting individuals or organizations.

### 💰 Pricing and Usage Limits

The provided Actor configuration does not specify a fixed monetary price, so this README does not state an invented per-run or per-result price.

The Actor does include plan-dependent result handling.

> **💳 Important Usage Note**
>
> - **Free users:** The Actor applies a maximum of **100 collected emails**.
> - **Paid users:** The Actor does not impose that 100-email result ceiling.
> - `maxEmails` still controls the requested collection target and accepts values from 1 to 10,000.
> - Actual results may be lower than the requested target because matching public email addresses may not be available.

The final number of records also depends on duplicate emails, keyword relevance, available search results, email-domain availability, exclusions, and other search conditions.

### ✅ Tips and Best Practices for Manageo Email Scraper

Good input design usually matters more than simply increasing the email limit.

#### 🎯 Use specific keyword variations

Build keyword groups around roles, business types, services, and specialties.

```text
restaurant
restaurant owner
restaurant manager
restaurant consultant
```

This gives **Manageo Email Scraper** more search variations to work with.

#### 🌎 Start with the right geographic scope

Use a city or country when geographic precision matters. Remove the location when broader discovery is preferred.

#### ✉️ Test several email domains

Start with the domains most relevant to the project, then expand when results are sparse.

```text
@gmail.com
@yahoo.com
@outlook.com
@hotmail.com
```

Business domains may also be useful for B2B-oriented searches.

#### 🚫 Use exclusions carefully

Exclusion words can improve dataset relevance, but overly broad exclusions may remove useful results.

Use specific terms that clearly identify unwanted profiles.

#### 📈 Understand per-combination limits

The `maxEmails` value is not a single global target.

For example:

```text
5 keywords × 4 domains × 10 emails
```

creates 20 keyword/domain combinations, each with its own requested target. Duplicate prevention still applies across the run, so the final number of unique emails can be lower.

> **⚠️ Important**
>
> A higher `maxEmails` value does not guarantee more results. The Actor can only collect emails that are actually discoverable and match the selected search conditions.

### 🔄 Resume and Incremental Collection

**Manageo Email Scraper** saves progress during collection and pushes discovered records incrementally into the dataset.

This design is useful for longer jobs because the Actor does not depend entirely on completing every search before storing results.

The Actor also maintains a record of already discovered email addresses, helping prevent the same email from being added repeatedly during a run.

Collection may stop when the search produces insufficient new email results, when available result pages are exhausted, when repeated search failures occur, or when the configured target has been reached.

### ⚠️ Limitations

No scraper can guarantee a fixed number of contacts from a public source.

Important limitations for **Manageo Email Scraper** include:

- Only email addresses discoverable in the relevant searchable result information can be collected.
- A keyword may produce few or no matching email addresses.
- Narrow location filters can reduce the number of available results.
- Restrictive email-domain filters can reduce coverage.
- Exclusion terms can remove otherwise relevant profiles.
- Duplicate email addresses are ignored.
- The requested email target is a maximum target, not a guaranteed result count.
- Search availability and source content can change over time.

These limitations are normal for public web data extraction and should be considered when planning large lead-research projects.

### ❓ Frequently Asked Questions

#### 🔍 What is Manageo Email Scraper?

**Manageo Email Scraper** is an Apify Actor for discovering publicly available email addresses associated with relevant Manageo search results using keywords, optional locations, and selected email domains.

#### 📧 What email domains can Manageo Email Scraper search?

You can supply custom email suffixes through `customDomains`, including common providers such as `@gmail.com`, `@yahoo.com`, and `@outlook.com`, as well as other domains you need to target.

#### 📍 Can Manageo Email Scraper target a specific city or country?

Yes. The optional `location` field can be used to narrow searches by a city, country, state, or region.

#### 🔢 What is the maximum email limit?

The `maxEmails` input supports values from **1 to 10,000**. The configured target applies independently to each keyword + domain combination.

#### 🆓 Is there a free-user limit?

Yes. The Actor applies a **100-email maximum for free users**. Paid users do not have that code-imposed 100-email ceiling.

#### 🚫 How does the excludeWords filter work?

**Manageo Email Scraper** checks result descriptions for the supplied exclusion terms. Matching is case-insensitive. Single words are matched as whole words, while phrases are matched as text.

#### ♻️ Does the Actor remove duplicate emails?

Yes. Email addresses already discovered during the run are tracked so the same address is not collected repeatedly.

#### 📊 Where are the results stored?

Results are pushed to an **Apify Dataset**, where they can be viewed as structured records and used for downstream data workflows available through Apify.

#### 🎯 Why did I receive fewer emails than my maxEmails value?

`maxEmails` is a target limit, not a guarantee. The available search results may contain fewer matching addresses, or duplicates, exclusions, location filters, and selected domains may reduce the final count.

#### 💡 How can I improve Manageo Email Scraper results?

Use several specific keyword variations, consider removing an overly narrow location, test additional email domains, and keep exclusion rules focused. Combining related search terms is often more useful than relying on one broad keyword.

### 📞 Support

For questions, customization requests, or assistance related to **Manageo Email Scraper**, contact:

- contact me by email : <alphascraper69@gmail.com>

# Actor input Schema

## `keywords` (type: `array`):

A list of keywords or queries to search for.

## `location` (type: `string`):

Optional country, state or city used to narrow the search. Leave it empty to search without a geographic filter.

## `customDomains` (type: `array`):

List of custom email domains

## `maxEmails` (type: `integer`):

How many addresses each search keyword + domain suffix combination may collect before the finder moves on to the next one. This is a per-combination target, not a run-wide total: with 3 keyword and 2 Domains and a limit of 20, the run works through all 6 combinations and aims for up to 20 addresses in each, so up to 120 overall. Lower values finish sooner and cost less; higher values dig deeper but never guarantee a fuller result, since the run can only find what is publicly listed.

## `excludeWords` (type: `array`):

Words or phrases you do not want to see.

## Actor input object example

```json
{
  "keywords": [
    "entreprise",
    "gérant"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com"
  ],
  "maxEmails": 5,
  "excludeWords": []
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "entreprise",
        "gérant"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com"
    ],
    "excludeWords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("email_scraper/manageo-email-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": [
        "entreprise",
        "gérant",
    ],
    "location": "",
    "customDomains": ["@gmail.com"],
    "excludeWords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("email_scraper/manageo-email-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "entreprise",
    "gérant"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com"
  ],
  "excludeWords": []
}' |
apify call email_scraper/manageo-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,email_scraper/manageo-email-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/yy51dFlWfu06FoSAr/builds/bfbsUidEO8bKQtxct/openapi.json