# Dubizzle Email Scraper (`email_scraper/dubizzle-email-scraper`) Actor

Dubizzle Email Scraper extracts publicly listed email addresses from Dubizzle search results using targeted keywords, locations, and custom email domains. Build structured contact datasets for lead research, market research, prospecting, and data collection.

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

### Dubizzle Email Scraper

Dubizzle Email Scraper is an Apify Actor that finds publicly listed email addresses associated with Dubizzle search results using keywords or queries. You can provide multiple search terms, optionally narrow the search by country, state, or city, choose email-domain suffixes to include, and exclude results containing selected words or phrases.

The Actor returns structured records containing the keyword, result title, description snippet, URL, and extracted email address. This makes the dataset useful for contact research, market research, regional prospecting, and other workflows based on publicly available information.

Each keyword and email-domain combination is processed separately. `maxEmails` controls the target for each combination. Duplicate addresses found across different searches are not added again, so the final unique total can be lower than the arithmetic maximum.

### What Is the Dubizzle Email Scraper?

The Dubizzle Email Scraper is a keyword-driven email extraction tool for finding contact addresses exposed in searchable content associated with Dubizzle pages. Instead of manually reviewing many results and copying email addresses, you can define the search terms and collection rules in one Actor run.

It supports multiple keywords, optional geographic targeting, custom email-domain suffixes, and an exclude-words filter. Results depend on what is publicly available and discoverable for the terms you use, so a requested number of emails is a target rather than a guarantee.

### 🔍 Key Features

| Feature                | Description                                           | User Benefit                                               |
| ---------------------- | ----------------------------------------------------- | ---------------------------------------------------------- |
| Keyword-based search   | Search with one or more keywords or queries.          | Build targeted searches for specific markets or audiences. |
| Multiple keywords      | Process a list of terms in one run.                   | Expand coverage without separate runs for every term.      |
| Location filter        | Add a country, state, or city.                        | Narrow research geographically.                            |
| Custom email domains   | Target suffixes such as `@gmail.com` or `@yahoo.com`. | Focus on the email types you need.                         |
| Per-combination target | Set `maxEmails` for each keyword + domain pair.       | Control search depth.                                      |
| Exclude words          | Skip snippets containing chosen terms or phrases.     | Reduce unwanted matches.                                   |
| Duplicate prevention   | Previously collected emails are not added again.      | Keep results unique.                                       |
| Structured dataset     | Save each match as a structured record.               | Review and analyze results more easily.                    |

> **Tip:** Specific related searches can improve targeting. For example, use terms such as `Fitness Coach`, `Fitness Trainer`, and `Online Fitness Coach` instead of only `Fitness`.

### What Data Can You Extract?

The Actor returns the following fields for collected matches:

- **Network** — `Dubizzle.com`.
- **Keyword** — The search term responsible for the result.
- **Title** — The matching result title.
- **Description** — The available description or search-result snippet.
- **URL** — The result URL.
- **Email** — The extracted address matching a configured domain suffix.

The email comes from the available result description text. The Actor therefore should not be understood as providing private contact data or complete Dubizzle profile records.

### Why Use This Actor?

Manual contact research can involve repeated searching, opening results, copying addresses, and removing duplicates. The Dubizzle Email Scraper automates that repetitive collection workflow.

Key benefits include:

- **Automation:** Run keyword-based searches without manually checking every result.
- **Structured results:** Receive consistent keyword, title, description, URL, and email fields.
- **Targeted research:** Combine keywords with location targeting.
- **Domain filtering:** Search only for selected email suffixes.
- **Cleaner collection:** Exclude unwanted snippets and avoid duplicate emails.
- **Flexible depth:** Adjust `maxEmails` to control each search combination.

### Benefits and Practical Advantages

Multiple search terms let you cover different ways a business, service, role, or product may be described. A location can focus the search on a particular market, while several domain suffixes can broaden the types of addresses being sought.

The structured dataset is also useful for reviewing results, comparing searches, and building reusable contact research datasets.

### How to Use the Dubizzle Email Scraper

1. Enter one or more keywords or queries.
2. Add a country, state, or city when geographic targeting is needed.
3. Select the email-domain suffixes to include.
4. Set `maxEmails` for each keyword + domain combination.
5. Add exclude words or phrases when necessary.
6. Run the Actor and review the resulting dataset.

Start with a small test run. Once the search terms produce relevant records, expand the keyword, domain, or geographic scope.

### 📥 Input

| Field           | Type             | Required | Default                             | Description                                                                                                                       |
| --------------- | ---------------- | -------- | ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| `keywords`      | Array of strings | Yes      | `["UAE real estate", "automotive"]` | Keywords or search queries used to find Dubizzle results.                                                                         |
| `location`      | String           | No       | `""`                                | Optional country, state, or city filter.                                                                                          |
| `customDomains` | Array of strings | No       | `["@gmail.com"]`                    | Email-domain suffixes to include, such as `@gmail.com`.                                                                           |
| `maxEmails`     | Integer          | No       | `5`                                 | Maximum target per keyword + domain combination. Range: 1–10,000.                                                                 |
| `excludeWords`  | Array of strings | No       | `[]`                                | Words or phrases that cause a matching snippet to be skipped. Matching is case-insensitive; single words use whole-word matching. |

Use the documented `@domain.com` format for email suffixes. Leave `excludeWords` empty when no filtering is needed.

### 📥 Input Example

```json
{
  "keywords": [
    "UAE real estate",
    "property agent",
    "real estate consultant"
  ],
  "location": "Dubai, UAE",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com"
  ],
  "maxEmails": 10,
  "excludeWords": [
    "crypto",
    "onlyfans"
  ]
}
```

### 📤 Output

A structured record is written for each newly collected email address.

| Field         | Description                                           |
| ------------- | ----------------------------------------------------- |
| `network`     | Source identifier returned as `Dubizzle.com`.         |
| `keyword`     | Keyword or query associated with the result.          |
| `title`       | Matching result title.                                |
| `description` | Available description or search-result snippet.       |
| `url`         | URL associated with the result.                       |
| `email`       | Extracted email address matching a configured suffix. |

The default dataset view focuses on `keyword`, `title`, `description`, `url`, and `email`. The `network` field is also present in the dataset record.

### 📤 Output Example

```json
{
  "network": "Dubizzle.com",
  "keyword": "property agent",
  "title": "Example Property Services",
  "description": "Property services in Dubai. Contact us at example.agent@gmail.com for inquiries.",
  "url": "https://dubizzle.com/example-result",
  "email": "example.agent@gmail.com"
}
```

The values above are placeholders. Actual results depend on the publicly searchable Dubizzle content available for your inputs.

### Use Cases

Relevant use cases include:

- **Lead research:** Find publicly listed email contacts related to targeted Dubizzle searches.
- **Market research:** Explore contact information across products, services, and business segments.
- **Regional prospecting:** Use a location filter for a specific market.
- **Business intelligence:** Build datasets for analyzing publicly available contact information.
- **Competitive research:** Review publicly exposed contact information in relevant search areas.
- **Dataset creation:** Create structured contact and source-page datasets.
- **Automation:** Repeat similar collection jobs with different search settings.

Use collected information in accordance with applicable laws, platform rules, and the legitimate purpose for which it is processed.

### Limitations

Results depend on publicly discoverable information. The Actor cannot guarantee that every result contains an email address or that a requested target will be reached.

Narrow searches may return sparse results. Broadening keywords, adding related terms, removing a restrictive location, or including additional email domains may increase coverage.

`maxEmails` is a target per keyword + domain combination, not a guarantee. Duplicate addresses across searches are consolidated into the unique result set.

The actor configuration documents a default run timeout of 3600 seconds. Broad runs may require more time, so users can adjust the Apify run timeout when appropriate.

### Pros and Cons

| Pros                             | Cons                                                                            |
| -------------------------------- | ------------------------------------------------------------------------------- |
| Multiple keywords in one run.    | Results depend on publicly searchable content.                                  |
| Optional geographic targeting.   | Some searches may return few or no emails.                                      |
| Custom email-domain filtering.   | Requested targets are not guaranteed.                                           |
| Exclude-word filtering.          | Broad runs may require more runtime.                                            |
| Per-keyword + domain targets.    | Duplicate addresses do not increase the unique total.                           |
| Structured Apify dataset output. | Description may be a result snippet rather than a complete profile description. |

### Comparison With Alternative Approaches

| Capability               | Dubizzle Email Scraper                  | Manual / Typical Alternative                  |
| ------------------------ | --------------------------------------- | --------------------------------------------- |
| Keyword-based collection | Supported                               | Often repeated manually.                      |
| Multiple search terms    | Supported                               | Usually handled one search at a time.         |
| Location filtering       | Supported through `location`            | Applied manually to searches.                 |
| Email-domain targeting   | Supported through `customDomains`       | Requires manual filtering.                    |
| Exclude-word filtering   | Supported                               | Requires manual screening.                    |
| Duplicate handling       | Duplicate emails are not added again.   | Manual deduplication may be required.         |
| Structured dataset       | Supported through Apify dataset output. | Often requires manual copying and formatting. |

This comparison describes workflow differences and does not guarantee better results than another method.

### Competitive Advantages

The Actor's practical strengths are its focused Dubizzle workflow and its configurable search controls. Users can combine multiple keywords, location targeting, domain-specific email matching, and exclusion rules within one run.

The per-combination `maxEmails` setting also gives users control over search depth for each keyword + domain pair. Duplicate prevention and structured dataset records provide a clear input-to-output workflow for contact research.

### Best Practices

Use several specific, closely related keywords when an audience can be described in different ways.

Use `location` when geographic relevance matters, but remove an overly narrow location when results are sparse.

Include the email suffixes that match your research goal. For broader coverage, you can add common domains such as `@gmail.com`, `@yahoo.com`, and `@outlook.com`.

Start with a small `maxEmails` value and a limited keyword set. Review the output before expanding the run.

Use `excludeWords` selectively because overly broad exclusions can remove useful snippets.

### Troubleshooting

**Invalid input:** Confirm that `keywords` is an array of strings and `maxEmails` is an integer from 1 to 10,000. Email domains should use suffixes such as `@gmail.com`.

**Empty results:** Try related keywords, remove a restrictive location, or add additional domain suffixes.

**Partial results:** Fewer emails than requested can simply mean that the available public search content contains fewer unique matches.

**Missing fields:** Review `title`, `description`, `url`, and `email` together because the available source content can vary between results.

**Results stop before the target:** The available search results may become sparse or stop producing new email addresses. Broaden the search terms or geographic scope when appropriate.

### Frequently Asked Questions

**What does the Dubizzle Email Scraper do?**
It finds publicly listed email addresses associated with Dubizzle results using configured keywords, optional location, selected domains, and exclusion rules.

**What input is required?**
Only `keywords` is required. It accepts a list of search terms or queries.

**Can I use multiple keywords?**
Yes. Add multiple strings to the `keywords` array.

**Can I target a city or country?**
Yes. Use `location` to narrow the search to a country, state, or city.

**Can I search specific email domains?**
Yes. Use `customDomains` with suffixes such as `@gmail.com`, `@yahoo.com`, or `@outlook.com`.

**How does `maxEmails` work?**
It sets the target separately for each keyword + domain combination. Three keywords and two domains create six combinations.

**Why did I receive fewer emails than requested?**
The requested amount is a target, not a guarantee. The searchable content may contain fewer unique matching addresses.

**Does the Actor remove duplicate emails?**
Yes. An email already collected during the run is not added again.

**What does `excludeWords` do?**
It skips a result snippet when it contains a configured word or phrase. Matching ignores case, and single words use whole-word matching.

**Is the Dubizzle Email Scraper suitable for larger runs?**
It can process multiple keyword and domain combinations, but wider searches can take longer. Start small and adjust the Apify run timeout when necessary.

### NLP Keywords

- Dubizzle email scraper
- Dubizzle email extraction
- Dubizzle contact extraction
- Dubizzle lead scraper
- Dubizzle lead generation
- Dubizzle contact scraper
- Dubizzle email finder
- Dubizzle data scraper
- Dubizzle profile data
- Dubizzle contact data
- Dubizzle public emails
- Dubizzle search scraper
- Dubizzle keyword scraper
- Dubizzle business leads
- Dubizzle prospecting data
- Dubizzle email collection
- Dubizzle structured data
- Dubizzle contact research
- Dubizzle dataset
- Dubizzle lead data

### Related Keywords

- scrape Dubizzle emails
- extract emails from Dubizzle
- find Dubizzle email addresses
- Dubizzle contact list scraper
- Dubizzle leads extraction
- Dubizzle prospect research
- Dubizzle business contact finder
- Dubizzle email lead generation
- Dubizzle public contact data
- Dubizzle keyword search scraper
- Dubizzle real estate email scraper
- Dubizzle business leads scraper
- Dubizzle regional lead scraper
- Dubizzle email collector
- Dubizzle contact information scraper
- scrape Dubizzle profiles
- Dubizzle data extraction tool
- Dubizzle marketing leads
- Dubizzle research dataset
- automated Dubizzle email search

### Final Overview

The Dubizzle Email Scraper provides a focused way to collect publicly listed email addresses connected to Dubizzle search results. Its keyword list, optional location filter, custom email domains, exclusion rules, per-combination target, duplicate prevention, and structured dataset output support repeatable contact and market research workflows.

For better targeting, use specific related keywords, apply location only when needed, select the email domains you actually want, and validate a small test run before scaling the search.

*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": [
    "UAE real estate",
    "automotive"
  ],
  "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": [
        "UAE real estate",
        "automotive"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com"
    ],
    "excludeWords": []
};

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

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

```

## MCP server setup

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