# Axesor Email Scraper (`email_scraper/axesor-email-scraper`) Actor

Axesor Email Scraper extracts publicly indexed business emails using targeted keywords, location filters, custom email domains, and exclusion terms. Build structured Axesor contact datasets for business research, lead discovery, company research, and contact analysis.

- **URL**: https://apify.com/email\_scraper/axesor-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

### Axesor Email Scraper

Axesor Email Scraper is an Apify Actor for finding publicly indexed email addresses associated with Axesor pages using targeted search keywords. It lets you search with multiple keywords, optionally narrow results by country, city, or region, select the email domains to look for, and exclude unwanted words or phrases from result descriptions.

The Actor returns structured contact records containing the search keyword, result title, description, URL, and extracted email address. This makes the resulting dataset useful for business research, lead discovery, company research, contact analysis, and structured data collection.

Instead of manually reviewing search results one by one, you can configure your keywords and email-domain targets and let the Actor collect matching publicly indexed contact information into an Apify dataset.

### What Is an Axesor Email Scraper?

An Axesor Email Scraper is a data extraction tool designed to identify email addresses appearing in publicly indexed Axesor search results.

The Actor uses the keywords you provide to search for relevant Axesor pages and looks for email addresses matching your selected domain suffixes. For example, you can search with terms such as `administrador`, `empresa`, `director`, or other business-related queries.

You can also add a location such as a country or city to narrow the search. If no location is provided, the search is not restricted by a geographic term.

The resulting records are structured so that each collected email can be reviewed together with the keyword, page title, description, and source URL that produced it.

### Key Features

| Feature                      | Description                                                            | User Benefit                                              |
| ---------------------------- | ---------------------------------------------------------------------- | --------------------------------------------------------- |
| Keyword-based search         | Search Axesor using one or multiple keywords or queries                | Build targeted searches for different business categories |
| Location filtering           | Optionally add a country, state, or city                               | Narrow research to a geographic area                      |
| Custom email domains         | Specify domains such as `@gmail.com`, `@yahoo.com`, or other suffixes  | Focus collection on the email types you need              |
| Per-combination email target | Set a maximum number of emails for each keyword and domain combination | Control the depth of individual searches                  |
| Exclude words                | Skip result descriptions containing selected words or phrases          | Reduce unwanted matches                                   |
| Duplicate prevention         | Previously collected email addresses are not added again               | Keep the dataset from containing repeated email addresses |
| Structured dataset           | Results are stored as structured records                               | Makes collected data easier to review and analyze         |
| Multiple keywords            | Process a list of search terms in one run                              | Support broader research workflows                        |

### What Data Can You Extract?

Axesor Email Scraper returns five user-facing data fields for each collected contact.

| Field         | Description                                                     |
| ------------- | --------------------------------------------------------------- |
| `keyword`     | The keyword associated with the search that produced the result |
| `title`       | The title of the matching search result                         |
| `description` | The description or snippet associated with the result           |
| `url`         | The URL of the matching result                                  |
| `email`       | The email address extracted from the result description         |

The combination of these fields provides context around each email address rather than returning an email address alone.

For example, the `keyword` helps identify the search intent, while the `title`, `description`, and `url` provide context about the source result.

### Why Use This Actor?

Manual contact research can require repeatedly searching for different business terms, reviewing search results, checking descriptions, and recording relevant email addresses.

Axesor Email Scraper turns this into a configurable data collection workflow.

You can provide several related keywords in the same run and configure different email-domain suffixes according to your research requirements. Location filtering can further narrow the search when geographic targeting is important.

The structured dataset is particularly useful when the collected contacts need to be reviewed alongside their associated search context.

### Benefits

- **Automated contact discovery:** Reduce repetitive manual searching for publicly indexed Axesor contact information.
- **Targeted research:** Use specific keywords instead of relying on a single broad search term.
- **Geographic targeting:** Add a country, state, or city when location is relevant.
- **Domain targeting:** Search specifically for configured email suffixes.
- **Structured results:** Receive keyword, title, description, URL, and email in separate fields.
- **Filtering control:** Exclude result descriptions containing unwanted words or phrases.
- **Multi-search workflows:** Process several keywords and domain combinations in one Actor run.
- **Dataset creation:** Build a structured collection of discovered contacts for later analysis.

### How to Use the Axesor Email Scraper

The basic workflow is straightforward:

1. Enter one or more keywords in the `keywords` input.
2. Optionally enter a country, state, city, or other geographic location.
3. Add the email-domain suffixes you want to search for.
4. Set `maxEmails` to control the target for each keyword and domain combination.
5. Optionally add words or phrases to `excludeWords`.
6. Start the Actor.
7. Review the structured results in the Apify dataset.

For better coverage, use several specific keywords instead of one very broad term. For example, business research could use terms such as `administrador`, `empresa`, `director`, and other relevant business queries rather than relying on only `empresa`.

### Input

The Actor requires the `keywords` field. The remaining configuration fields are optional.

| Field           | Type             | Required | Default                        | Description                                                                               |
| --------------- | ---------------- | -------- | ------------------------------ | ----------------------------------------------------------------------------------------- |
| `keywords`      | Array of strings | Yes      | `["administrador", "empresa"]` | Keywords or search queries used to find relevant Axesor results                           |
| `location`      | String           | No       | `""`                           | Optional country, state, or city used to narrow the search                                |
| `customDomains` | Array of strings | No       | `["@gmail.com"]`               | Email-domain suffixes to search for                                                       |
| `maxEmails`     | Integer          | No       | `5`                            | Target number of addresses for each keyword + domain combination; valid range is 1–10,000 |
| `excludeWords`  | Array of strings | No       | `[]`                           | Words or phrases that cause a result description to be skipped                            |

The `keywords` input is an array, allowing multiple search terms in one run.

The `location` field can be left empty when no geographic filter is needed.

The `customDomains` field accepts email suffixes such as `@gmail.com`, `@yahoo.com`, or `@outlook.com`. You can also provide other domain suffixes relevant to your research.

The `maxEmails` value applies independently to each keyword and domain combination. For example, three keywords and two domains create six keyword-domain combinations, each with its own configured target.

The `excludeWords` filter is case-insensitive. A single word is matched as a whole word, while phrases are matched as phrases. When a result description matches an exclusion term, that result is skipped.

### Input Example

```json
{
  "keywords": [
    "administrador",
    "empresa",
    "director"
  ],
  "location": "Madrid",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com"
  ],
  "maxEmails": 10,
  "excludeWords": [
    "crypto",
    "onlyfans"
  ]
}
```

This configuration searches using three business-related keywords, narrows the search to Madrid, checks three email-domain suffixes, targets up to 10 emails for each keyword-domain combination, and excludes matching descriptions containing the specified terms.

### Output

Axesor Email Scraper stores collected results as structured dataset records.

Each record connects an extracted email with the search keyword and the source result information. This context can help users understand why a particular contact was collected and which result produced it.

| Field         | Example                     | Description                                                   |
| ------------- | --------------------------- | ------------------------------------------------------------- |
| `keyword`     | `administrador`             | Search keyword used for the result                            |
| `title`       | `Example Business`          | Title of the matching result                                  |
| `description` | `Contact information...`    | Search-result description containing the relevant information |
| `url`         | `https://www.axesor.es/...` | Source result URL                                             |
| `email`       | `contact@gmail.com`         | Extracted email address                                       |

Only email addresses matching the configured domain suffixes are collected.

The Actor also avoids adding the same email address more than once during the run, helping reduce duplicate contacts in the resulting dataset.

### Output Example

```json
{
  "keyword": "administrador",
  "title": "Example Business",
  "description": "Business information and contact details including contact@gmail.com",
  "url": "https://www.axesor.es/ejemplo",
  "email": "contact@gmail.com"
}
```

The exact title, description, URL, and email values depend on the publicly indexed search results available for the configured keywords and filters.

### Use Cases

Axesor Email Scraper can support several research and data-collection workflows.

- **Business research:** Find publicly indexed contact information associated with business-related searches.
- **Lead research:** Build structured lists of publicly discoverable business contacts.
- **Company research:** Search using company-related or professional keywords and retain the associated result context.
- **Market research:** Explore different business categories using multiple targeted search terms.
- **Geographic research:** Focus searches on specific cities, states, countries, or regions.
- **Contact analysis:** Analyze collected email addresses together with their associated titles and descriptions.
- **Dataset creation:** Build structured datasets from multiple keyword and domain combinations.
- **Research automation:** Repeat a configured search workflow through Apify instead of performing every search manually.

Use collected information responsibly and in accordance with applicable laws, website terms, privacy requirements, and applicable communication regulations.

### Competitive Advantages

The Actor provides several practical configuration options in one workflow.

- Multiple keywords can be supplied in a single run.
- Geographic filtering is optional rather than mandatory.
- Email-domain targeting can be customized.
- Each keyword-domain combination can have its own email target.
- Unwanted result descriptions can be filtered using exclusion terms.
- Output is organized into separate fields for search context and contact information.
- Duplicate email addresses are not added repeatedly during collection.

These capabilities make the Actor configurable for both broad and focused Axesor research workflows.

### Advantages

- **Flexible keyword targeting:** Useful when a research project covers several related business terms.
- **Configurable domains:** Lets users decide which email suffixes are relevant to their task.
- **Optional location control:** Supports both geographically focused and broader searches.
- **Context-rich output:** Emails are returned together with titles, descriptions, URLs, and keywords.
- **Adjustable collection depth:** `maxEmails` can be increased or reduced according to the desired search depth.
- **Exclusion filtering:** Helps remove result descriptions containing terms that are not relevant to the research.

### Limitations

- Results depend on information that is publicly indexed and available through the search process.
- The Actor does not guarantee that every Axesor profile contains a publicly visible email address.
- A requested `maxEmails` value is a target, not a guarantee that the corresponding number of unique addresses will be available.
- Narrow keywords, restrictive locations, or uncommon email domains can produce fewer results.
- Exclusion terms can intentionally remove otherwise relevant results when they match the configured words or phrases.
- Multiple keyword-domain combinations can increase the amount of search work required for a run.
- The Actor searches for configured email-domain suffixes; email addresses using domains not included in `customDomains` are not targeted.
- Free-tier runs may have platform-level result restrictions that can affect how many addresses can be collected.

### Pros and Cons

| Pros                                  | Cons                                                           |
| ------------------------------------- | -------------------------------------------------------------- |
| Supports multiple search keywords     | Results depend on publicly indexed information                 |
| Optional location filtering           | Narrow searches may return fewer contacts                      |
| Custom email-domain targeting         | Domains must be configured when specific suffixes are required |
| Exclusion word and phrase filtering   | Exclusion terms can remove matching results                    |
| Structured five-field output          | Not every result will necessarily contain an extractable email |
| Per keyword-domain collection targets | Higher targets can require broader search coverage             |

### Comparison With Alternative Approaches

| Capability               | Axesor Email Scraper                  | Manual Search                           |
| ------------------------ | ------------------------------------- | --------------------------------------- |
| Keyword-based collection | Supported                             | Requires repeated manual searches       |
| Multiple keywords        | Supported in one run                  | Usually handled separately              |
| Location filtering       | Supported                             | Must be applied manually                |
| Email-domain targeting   | Configurable                          | Requires manual search refinement       |
| Exclusion filtering      | Supported                             | Requires manual review                  |
| Structured output        | Dataset fields                        | Requires manual organization            |
| Duplicate prevention     | Supported during collection           | Requires manual checking                |
| Repeatable workflow      | Supported through Actor configuration | Requires repeating the research process |

The main distinction is workflow automation and structured collection. Manual research may still be appropriate when a user needs to inspect individual results closely or perform a highly selective review.

### Best Practices

- Start with a small `maxEmails` value to validate the search configuration.
- Use several specific keywords that represent the audience or business category you are researching.
- Add a location only when geographic targeting is important.
- Use multiple relevant email domains when broader email coverage is required.
- Avoid overly restrictive keyword combinations when results are sparse.
- Review exclusion terms carefully because matching descriptions are skipped entirely.
- Test your configuration before running a large multi-keyword search.
- Review collected records and validate important contact information before using it in downstream workflows.
- If results are below the target, consider broader keywords, additional relevant domains, or a less restrictive location filter.

### Troubleshooting

**Invalid or unexpected input:** Check that `keywords`, `customDomains`, and `excludeWords` are supplied as arrays of strings and that `maxEmails` is an integer between 1 and 10,000.

**Empty results:** Try broader or more specific related keywords depending on the research goal. You can also remove the location filter or add additional email domains.

**Too few emails:** A target does not guarantee that the requested number exists. Broaden the search terms, use additional relevant domains, or adjust the location.

**Unexpectedly missing results:** Check whether the result description contains an excluded word or phrase. Matching descriptions are skipped.

**Results vary between searches:** Public indexing can change over time, so search availability and indexed information may vary.

**Large runs take longer:** Multiple keywords combined with multiple domains create more search combinations. Consider testing a smaller configuration before expanding the run.

### Frequently Asked Questions

**What does the Axesor Email Scraper do?**

It searches for publicly indexed Axesor results using your configured keywords and extracts matching email addresses from result descriptions.

**What data does the Axesor Email Scraper return?**

Each user-facing dataset record contains `keyword`, `title`, `description`, `url`, and `email`.

**Can I use multiple keywords?**

Yes. The `keywords` field accepts an array of search terms, allowing several related queries to be processed in one run.

**Can I target a specific city or country?**

Yes. Use the optional `location` field to add a country, state, city, or other geographic term.

**Can I search for different email domains?**

Yes. The `customDomains` field accepts multiple email-domain suffixes, such as `@gmail.com`, `@yahoo.com`, and `@outlook.com`.

**What does `maxEmails` control?**

It sets the target number of email addresses for each keyword and domain combination. It is not a guarantee that the requested number will be found.

**How does `excludeWords` work?**

The Actor checks result descriptions for configured words or phrases. Matching descriptions are skipped, so no email is extracted from those results.

**Does the Actor return duplicate emails?**

The Actor keeps track of collected email addresses and does not add the same email address repeatedly during collection.

**Why did my run return fewer emails than requested?**

The configured target may be higher than the number of publicly indexed matching contacts available for the selected keywords, domains, and location. Narrow searches and exclusion filters can also reduce results.

**Is the output structured for further analysis?**

Yes. Results are stored as structured dataset records with separate keyword, title, description, URL, and email fields.

### NLP Keywords

- Axesor email scraper
- Axesor email extraction
- Axesor contact data
- Axesor business contacts
- Axesor email addresses
- Axesor lead extraction
- Axesor data scraper
- Axesor contact scraper
- Axesor company research
- Axesor business research
- Axesor search scraper
- Axesor lead research
- Axesor structured data
- Axesor contact discovery
- Axesor email finder
- business email extraction
- public email discovery
- business contact extraction
- email domain filtering
- keyword-based email scraping

### Related Keywords

- Axesor email scraper
- scrape Axesor emails
- Axesor contact scraper
- Axesor business email extractor
- Axesor lead scraper
- extract emails from Axesor
- Axesor email finder
- Axesor company contact data
- Axesor business contact extraction
- Axesor lead generation data
- Axesor email data extraction
- Axesor keyword scraper
- Axesor search data scraper
- Axesor public contact data
- Axesor company research tool
- Axesor business research scraper
- Axesor email collection
- Axesor contact discovery tool
- Axesor email domain scraper
- Axesor structured contact dataset

### Final Overview

Axesor Email Scraper provides a configurable way to collect publicly indexed email addresses associated with Axesor search results. Users can combine multiple keywords with optional geographic targeting, custom email-domain suffixes, configurable collection targets, and exclusion words or phrases.

The resulting dataset connects each extracted email with its keyword, result title, description, and source URL. This makes the data useful for business research, lead research, company analysis, contact discovery, and structured dataset creation.

For the most useful results, begin with a focused test run, use several relevant keywords, select appropriate email domains, and adjust the location or exclusions when the search is too restrictive.

*Contact me:* <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": [
    "administrador",
    "empresa"
  ],
  "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": [
        "administrador",
        "empresa"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com"
    ],
    "excludeWords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("email_scraper/axesor-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": [
        "administrador",
        "empresa",
    ],
    "location": "",
    "customDomains": ["@gmail.com"],
    "excludeWords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("email_scraper/axesor-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": [
    "administrador",
    "empresa"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com"
  ],
  "excludeWords": []
}' |
apify call email_scraper/axesor-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,email_scraper/axesor-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/aYc7zDXkCR2KDOqhV/builds/ZcarELHFt5i1N2hT3/openapi.json