# Reed Email Scraper (`email_scraper/reed-email-scraper`) Actor

Reed Email Scraper extracts publicly indexed email addresses from Reed.co.uk using targeted keywords, custom email domains, location filters, and exclusion terms. Build structured Reed leads with emails, titles, descriptions, and URLs for lead research, contact discovery, and market research.

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

### 🔍 Reed Email Scraper

Reed Email Scraper is an Apify Actor designed to discover email addresses associated with publicly indexed Reed.co.uk results using targeted keywords, email-domain filters, and optional location targeting.

You provide one or more search keywords, choose the email domains you want to find, and optionally specify a country, state, or city. The Actor searches for relevant Reed results and extracts matching email addresses from available search-result descriptions.

The resulting dataset contains the keyword used, result title, description snippet, URL, and discovered email address. This makes the Reed Email Scraper useful for lead research, business research, contact discovery, market research, and structured dataset creation.

The Actor supports multiple keyword and email-domain combinations. Each combination can have its own email target, allowing you to build broader searches without relying on a single search term.

### 🧭 What Is the Reed Email Scraper?

The Reed Email Scraper is a keyword-based email discovery tool focused on Reed.co.uk results. Instead of manually searching for individual Reed pages and checking search-result information, you can provide a list of relevant terms and let the Actor collect matching email addresses into a structured Apify dataset.

The Actor uses your keywords to identify Reed-related search results and looks for email addresses matching the domains you specify, such as `@gmail.com`.

Location targeting can further narrow the search when you want results associated with a particular country, state, or city. Leaving the location blank allows the search to run without a geographic filter.

Because email extraction is based on information available in indexed search-result descriptions, the Actor only returns addresses that are publicly discoverable through the available search results. It does not guarantee that every Reed profile contains an email address.

### 🚀 Reed Email Scraper Features

| Feature                 | Description                                                     | User Benefit                                          |
| ----------------------- | --------------------------------------------------------------- | ----------------------------------------------------- |
| Keyword search          | Search Reed.co.uk results using custom keywords or queries      | Target specific professions, businesses, or interests |
| Multiple keywords       | Provide a list of search terms                                  | Expand search coverage                                |
| Email-domain filtering  | Specify domains such as `@gmail.com` or `@yahoo.com`            | Focus on relevant email types                         |
| Location targeting      | Optionally add a country, state, or city                        | Narrow geographically relevant results                |
| Email extraction        | Extract matching email addresses from result descriptions       | Create structured contact data                        |
| Exclusion filtering     | Skip descriptions containing selected words or phrases          | Reduce unwanted results                               |
| Per-combination targets | Configure an email target for each keyword + domain combination | Control search depth                                  |
| Structured dataset      | Store title, description, URL, keyword, and email               | Simplify downstream research                          |
| Duplicate prevention    | Previously discovered email addresses are tracked               | Reduce duplicate email records                        |
| Incremental results     | Matching records are pushed as they are collected               | Make collected data available progressively           |

### 📊 What Data Can You Extract?

The Reed Email Scraper returns structured contact information connected to the search result where the email was discovered.

The primary dataset fields are:

| Field         | Description                                                              |
| ------------- | ------------------------------------------------------------------------ |
| `keyword`     | The keyword or query associated with the search                          |
| `title`       | Title of the Reed-related search result                                  |
| `description` | Search-result description or snippet containing the relevant information |
| `url`         | URL associated with the search result                                    |
| `email`       | Email address matching one of the configured domain suffixes             |

For example, if you search for `Business` with the domain `@gmail.com`, a matching search-result description containing a Gmail address can produce a record containing the keyword, result title, description, URL, and email.

The dataset is designed around contact discovery rather than complete profile extraction. Fields such as phone numbers, physical addresses, social profiles, follower counts, or other profile attributes are not part of the documented output.

### 💡 Why Use the Reed Email Scraper?

Manual contact research can require repeatedly searching different keywords, reviewing result snippets, identifying relevant addresses, and copying information into a spreadsheet.

The Reed Email Scraper turns this repetitive search process into a structured collection workflow. You can provide multiple search terms and email domains in one run, optionally apply geographic targeting, and receive the discovered records in an Apify dataset.

This can be useful when your research requires targeted rather than generic searches. For example, instead of searching only for `Business`, you can use more specific terms such as `Business Owner`, `Company Director`, or another role relevant to your project.

Results can also be filtered with exclusion words. If a description contains a word or phrase you do not want, that complete snippet is skipped instead of extracting an address from it.

### ✅ Benefits

The Actor provides several practical benefits for users working with Reed-related contact research:

- **Structured collection:** Results are returned with consistent fields for easier review and analysis.
- **Multiple search terms:** Several keywords can be processed within the same run.
- **Domain control:** You decide which email-domain suffixes should be considered.
- **Geographic targeting:** A location can be added when regional research is required.
- **Search refinement:** Exclusion words help remove unwanted descriptions.
- **Research automation:** Repetitive search and extraction work can be handled as an automated Actor run.
- **Dataset creation:** Collected contact records are organized in an Apify dataset.
- **Duplicate reduction:** The Actor tracks discovered email addresses during its progress workflow.

### ⚙️ How to Use the Reed Email Scraper

Using the Reed Email Scraper requires only a few configuration steps:

1. Enter the keywords or search queries you want to investigate.
2. Add an optional country, state, or city in the location field.
3. Select the email-domain suffixes you want to search for.
4. Set the maximum number of emails for each keyword + domain combination.
5. Add exclusion words or phrases if certain descriptions should be ignored.
6. Start the Actor run.
7. Review the resulting structured dataset.

For initial testing, use a small number of targeted keywords and a modest `maxEmails` value. Once you understand the type of results available for your search terms, you can expand the configuration.

### 📥 Input

The Reed Email Scraper accepts a JSON object based on the Actor input schema.

| Field           | Type             | Required | Default                   | Description                                                    |
| --------------- | ---------------- | -------- | ------------------------- | -------------------------------------------------------------- |
| `keywords`      | Array of strings | Yes      | `["Business", "Company"]` | Keywords or search queries used to find relevant Reed results  |
| `location`      | String           | No       | Empty                     | Optional country, state, or city used to narrow searches       |
| `customDomains` | Array of strings | No       | `["@gmail.com"]`          | Email-domain suffixes to include                               |
| `maxEmails`     | Integer          | No       | `5`                       | Target number of emails for each keyword + domain combination  |
| `excludeWords`  | Array of strings | No       | `[]`                      | Words or phrases that cause a result description to be skipped |

The `keywords` field is required and accepts multiple strings. More specific search terms can be useful when a broad keyword produces too many irrelevant results.

The `location` field is optional. You can enter a country, state, city, or another geographic phrase manually. Leave it empty when geographic filtering is unnecessary.

The `customDomains` field controls which email suffixes the Actor looks for. You can provide multiple domains.

`maxEmails` accepts values from 1 to 10,000 in the Actor input schema. The target applies independently to each keyword + domain combination.

### 🧾 Input Example

```json
{
  "keywords": [
    "Business Owner",
    "Company Director",
    "Business Manager"
  ],
  "location": "London",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com"
  ],
  "maxEmails": 10,
  "excludeWords": [
    "crypto",
    "onlyfans"
  ]
}
```

This configuration searches multiple business-related terms, narrows the search to London, checks three email-domain suffixes, targets up to 10 addresses for each keyword-domain combination, and skips descriptions containing the specified exclusion terms.

### 📤 Output

The Reed Email Scraper writes matching records to the `Reed Emails Dataset`.

Each record connects an extracted email address with the search context and the search-result information from which it was discovered.

| Field         | Description                                    |
| ------------- | ---------------------------------------------- |
| `keyword`     | Search term responsible for the result         |
| `title`       | Title of the discovered search result          |
| `description` | Available search-result description or snippet |
| `url`         | Result URL                                     |
| `email`       | Extracted email address                        |

The `email` field contains an address matching the configured email-domain suffixes. The `description` field provides context for understanding where the address was found.

### 📦 Output Example

```json
{
  "keyword": "Business Owner",
  "title": "Example Business Profile",
  "description": "Business owner profile with contact information example@gmail.com",
  "url": "https://www.reed.co.uk/example-profile",
  "email": "example@gmail.com"
}
```

The example illustrates the output structure. Actual titles, descriptions, URLs, and email addresses depend on the publicly indexed search results available for your selected keywords, locations, and domains.

### 🎯 Use Cases

The Reed Email Scraper can support several research and data-collection workflows where publicly discoverable contact information is relevant.

- **Lead research:** Discover email addresses associated with targeted business or professional search terms.
- **Business research:** Build datasets around companies, business-related keywords, and relevant contact information.
- **Market research:** Collect structured search-result data for a defined market or geographic area.
- **Professional research:** Search for terms representing occupations, roles, or professional categories.
- **Location-based research:** Narrow searches to cities, states, countries, or other geographic phrases.
- **Contact discovery:** Identify publicly indexed email addresses matching selected domain suffixes.
- **Dataset building:** Create structured Reed-related datasets for further review and analysis.
- **Research automation:** Replace repetitive manual keyword searches with a repeatable Actor workflow.

The quality and quantity of results depend on what is publicly indexed and discoverable for the terms you provide.

### 🏆 Advantages

The Actor's main practical strengths come from its configurable search workflow and structured output.

You can combine several search concepts with several email domains instead of relying on a single search phrase. Location filtering provides another way to narrow the research scope, while exclusion words help remove descriptions that are not relevant to your intended dataset.

The output is already organized around the keyword, result context, URL, and email address, making the collected information easier to review than unstructured search results.

The Actor also keeps track of previously discovered email addresses during its progress workflow, helping reduce repeated email records.

### ⚠️ Limitations

The Reed Email Scraper has important limitations that users should understand before running large searches.

- Results depend on publicly indexed Reed.co.uk information available through search results.
- An email address is only collected when it is discoverable in the relevant result description and matches a configured domain suffix.
- The Actor does not guarantee a specific number of results.
- A high `maxEmails` target does not guarantee that the target will be reached.
- Very narrow keywords or locations can produce sparse results.
- Search availability can vary over time.
- Output does not represent complete Reed profiles.
- Fields such as phone numbers, addresses, social links, and other profile metadata are not part of the documented dataset output.
- Free-tier users have a 100-email configuration ceiling; requested values above that ceiling are reduced accordingly.
- Paid users do not have that specific free-tier result restriction in the Actor logic.

Because duplicate email addresses are tracked, the number of unique records can also be lower than the combined theoretical targets across multiple keyword and domain combinations.

### ⚖️ Pros and Cons

| Pros                            | Cons                                           |
| ------------------------------- | ---------------------------------------------- |
| Supports multiple keywords      | Results depend on publicly indexed information |
| Supports multiple email domains | Not every search result contains an email      |
| Optional location filtering     | Narrow searches may return fewer results       |
| Exclusion-word filtering        | `maxEmails` is a target, not a guarantee       |
| Structured Apify dataset        | Does not provide complete profile data         |
| Duplicate email tracking        | Free-tier users have a 100-email ceiling       |
| Per keyword + domain targeting  | Search availability can change                 |

### 🔄 Comparison With Manual Search

The Reed Email Scraper is designed to automate a search-and-collect workflow that users could otherwise perform manually.

| Capability             | Reed Email Scraper               | Manual Search                           |
| ---------------------- | -------------------------------- | --------------------------------------- |
| Multiple keywords      | Supported                        | Requires repeated searches              |
| Multiple email domains | Supported                        | Requires separate searches or filtering |
| Location targeting     | Supported                        | Can be applied manually                 |
| Exclusion filtering    | Supported                        | Requires manual review                  |
| Structured dataset     | Supported                        | Usually requires manual organization    |
| Duplicate tracking     | Supported by the Actor workflow  | Usually manual                          |
| Result review          | Available through dataset fields | Performed manually                      |

This comparison describes workflow differences rather than guaranteeing that one approach is suitable for every research project.

### 🔍 Competitive Advantages

Users may choose the Reed Email Scraper when they need a configurable Reed-focused contact discovery workflow rather than manually collecting information from individual search results.

Its practical advantages include:

- A required keyword list with support for multiple search terms.
- Configurable email-domain suffixes.
- Optional geographic filtering.
- Exclusion-word controls for unwanted descriptions.
- A configurable email target for each keyword + domain combination.
- Structured dataset fields suitable for review and analysis.
- Incremental dataset collection during the run.
- Duplicate email tracking across the collection workflow.

These capabilities let users adjust the search scope according to the type of Reed-related research they are conducting.

### 💡 Best Practices

For better research workflows, consider the following recommendations:

- Use specific keywords rather than relying only on broad terms such as `Business`.
- Combine related job titles, professional roles, or business terms.
- Start with a small `maxEmails` target to evaluate result quality.
- Add several relevant email domains when broader coverage is required.
- Use a location only when geographic targeting is important.
- Remove the location filter when a narrow location produces sparse results.
- Use exclusion words for clearly unwanted categories or descriptions.
- Review descriptions and URLs before using collected contact information.
- Treat extracted information as research data and validate important contacts independently.
- Expand keywords gradually when a test run produces limited results.

### 🛠️ Troubleshooting

**Invalid Input:** Make sure `keywords` is provided as an array of strings and that other fields follow the documented types.

**Empty Results:** Try broader or more specific keywords, add additional relevant email domains, or remove an overly restrictive location filter.

**Partial Results:** A target value is not a guarantee. The Actor can only collect addresses that are publicly discoverable and match the configured search criteria.

**Missing Email:** A search result may not contain a publicly visible email address, or its address may not match the configured domain suffix.

**Too Many Irrelevant Results:** Use more specific keywords or add appropriate `excludeWords` entries.

**Location Produces Few Results:** Try a broader geographic term or leave `location` empty to search without geographic filtering.

**Large Runs Take Longer:** Multiple keywords and domains increase the amount of search work. Start with a smaller configuration and increase the scope when needed.

### ❓ Frequently Asked Questions

**What does the Reed Email Scraper do?**
The Reed Email Scraper discovers email addresses from publicly indexed Reed.co.uk search results using keywords and configured email-domain suffixes.

**What keywords can I use?**
You can provide business terms, professional roles, occupations, or other relevant search queries. Specific phrases are often useful for targeted research.

**Can I use multiple keywords?**
Yes. The `keywords` input accepts a list of search terms, allowing several related searches in one Actor run.

**Can I search a specific location?**
Yes. The optional `location` field accepts a country, state, or city and can be used to narrow the search.

**Which email domains are supported?**
You can specify email-domain suffixes through `customDomains`, including domains such as `@gmail.com`, `@yahoo.com`, and `@outlook.com`.

**What does `maxEmails` mean?**
It is the target number of addresses for each keyword + domain combination. It is not a guarantee that the requested number will be found.

**Does the Reed Email Scraper return complete profiles?**
No. The documented output focuses on keyword, title, description, URL, and email information associated with discovered search results.

**Why did my run return fewer emails than requested?**
The requested target can be higher than the number of publicly indexed matching addresses. Narrow keywords, locations, domains, or exclusion filters can also reduce results.

**Can I exclude certain types of results?**
Yes. Add words or phrases to `excludeWords`. If a description contains an excluded term, that snippet is skipped.

**Does the Actor avoid duplicate emails?**
Yes. The Actor tracks discovered email addresses during its progress workflow to reduce repeated email records.

**Can I use the Reed Email Scraper for research?**
Yes. Its structured results can support business research, lead research, market research, contact discovery, and dataset creation involving publicly discoverable information.

**Should I start with a large run?**
A small test run is recommended first. It lets you evaluate keyword relevance and result quality before expanding the search configuration.

### 🧩 Search Strategy

Search quality depends heavily on the terms used. Broad keywords can produce a wide range of results, while highly specific phrases can narrow the available data considerably.

For example, instead of using only `Business`, you can test combinations such as `Business Owner`, `Company Director`, `Business Manager`, or other terms directly related to your research objective.

You can also combine keyword targeting with multiple email domains. This gives the Reed Email Scraper several search combinations to evaluate and can broaden the range of publicly indexed contact information discovered.

If results are sparse, consider changing one variable at a time: broaden the keyword, add another domain, or remove the location filter. This makes it easier to understand which configuration produces useful results.

### 📋 Input-to-Output Workflow

The user-facing workflow is straightforward:

**Input → Search configuration → Reed-related search results → Email matching → Structured dataset**

You provide keywords, optional location information, email-domain suffixes, a result target, and optional exclusion terms.

The Actor then searches according to those settings and identifies matching email addresses in available result descriptions. Matching records are placed into the Apify dataset with their associated keyword, title, description, URL, and email.

This structure allows the resulting data to be reviewed as a consistent collection rather than as individual search pages.

### 🧠 NLP Keywords

- Reed email scraper
- Reed email extraction
- Reed contact scraper
- Reed email finder
- Reed.co.uk email scraper
- Reed lead scraper
- Reed contact extraction
- Reed business leads
- Reed professional contacts
- Reed email addresses
- Reed lead generation
- Reed contact discovery
- Reed search scraper
- Reed data extraction
- Reed public contact data
- Reed keyword search
- Reed location search
- Reed business contact data
- Reed structured dataset
- Reed research data

### 🔗 Related Keywords

- scrape emails from Reed
- extract emails from Reed.co.uk
- find Reed email addresses
- Reed contact data scraper
- Reed.co.uk contact finder
- Reed lead generation scraper
- Reed business email finder
- Reed professional email finder
- Reed keyword email extractor
- Reed email lead scraper
- Reed contact research tool
- Reed email data extraction
- Reed public email discovery
- Reed business contact extraction
- Reed location-based email search
- Reed email search by keyword
- Reed email search by domain
- Reed contact dataset
- Reed lead research tool
- Reed email collection

### 📝 Final Overview

Reed Email Scraper provides a focused way to discover publicly indexed email addresses associated with Reed.co.uk search results.

With keyword lists, configurable email domains, optional location targeting, exclusion filters, and per-combination email targets, you can adapt the Actor to different contact research requirements.

The structured dataset makes the resulting information easier to review, analyze, and incorporate into research workflows. For the most useful results, start with specific keywords, test a small configuration, and expand your search based on the quality and availability of returned data.

*Contact me:* [Alphascraper69@gmail.com](mailto: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": [
    "Business",
    "Company"
  ],
  "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": [
        "Business",
        "Company"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com"
    ],
    "excludeWords": []
};

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

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

```

## MCP server setup

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