# Resellerratings Email Scraper (`email_scraper/resellerratings-email-scraper`) Actor

Resellerratings Email Scraper extracts publicly available email addresses from Resellerratings using targeted keywords, locations, and email domains. Build structured contact datasets for seller research, e-commerce leads, market research, business intelligence, and contact discovery.

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

### Resellerratings Email Scraper

Resellerratings Email Scraper is an Apify Actor designed to find publicly available email addresses associated with relevant Resellerratings search results. You provide keywords, optional geographic targeting, email domain suffixes, and optional exclusion terms, and the Actor collects matching contact information into a structured dataset.

The Actor is useful for business research, seller research, market research, lead discovery, competitive research, and building structured contact datasets from relevant Resellerratings results.

You can search with multiple keywords such as `online store reviews` and `seller reviews`, target a country or city, and choose domains such as `@gmail.com`, `@yahoo.com`, or `@outlook.com`. Results include the search keyword, result title, description, URL, and extracted email address.

### What Is a Resellerratings Email Scraper?

A Resellerratings Email Scraper automates the process of finding email addresses that appear in relevant publicly available search-result information associated with Resellerratings.

Instead of manually searching for individual results and copying contact information, you can define a group of search terms and let the Actor collect matching email addresses into an Apify dataset.

The Actor is keyword-driven. This means the quality and coverage of results depend heavily on the search terms, email domains, and optional location that you provide.

It is particularly useful when you want to turn targeted Resellerratings research into structured contact data that can be reviewed, analyzed, or incorporated into a broader research workflow.

### Key Features

| Feature                | Description                                                                 | User Benefit                                                             |
| ---------------------- | --------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| Keyword-based search   | Search Resellerratings using one or multiple keywords or queries.           | Target specific topics, businesses, sellers, or review-related searches. |
| Email domain targeting | Specify one or more email suffixes such as `@gmail.com`.                    | Focus collection on the email domains that matter to your research.      |
| Location filtering     | Optionally provide a country, state, or city.                               | Narrow searches geographically when required.                            |
| Maximum email target   | Set a target from 1 to 10,000 for each keyword + domain combination.        | Control the amount of data collected for each search combination.        |
| Exclusion filtering    | Skip results whose descriptions contain specified words or phrases.         | Reduce unwanted results based on your research criteria.                 |
| Structured dataset     | Results are stored with keyword, title, description, URL, and email fields. | Make collected data easier to review and process.                        |
| Duplicate prevention   | Previously collected email addresses are tracked during the run.            | Helps avoid repeatedly storing the same email address.                   |
| Incremental collection | Results are pushed to the dataset as they are collected.                    | Makes collected records available progressively during a run.            |
| Resume support         | Run progress is persisted.                                                  | Helps the Actor continue from saved progress after an interruption.      |

### What Data Can You Extract?

The Resellerratings Email Scraper produces structured contact records containing five user-facing fields.

- **Keyword** — The keyword or search term associated with the collected result.
- **Title** — The title of the relevant search result.
- **Description** — The available search-result description containing the relevant information.
- **URL** — The URL associated with the search result.
- **Email** — The email address matching one of your configured email domains.

The Actor is focused specifically on email discovery and related search-result context. It does not document additional profile fields beyond the output fields listed above.

The resulting dataset can therefore be used as a starting point for contact research, seller research, business intelligence, and other workflows where a structured email list and its source context are useful.

### Why Use This Actor?

Manual research can require repeatedly entering searches, checking relevant results, looking for contact information, and organizing findings into a consistent format.

This Actor converts that repetitive search-and-collection workflow into a configurable Apify run.

You can provide several related search terms instead of relying on one broad query. For example, a Resellerratings research project might use:

- `online store reviews`
- `seller reviews`
- `ecommerce seller`
- `online retailer`
- `store reviews`

You can also combine keywords with several email domains and an optional location to create more targeted searches.

Because the resulting records contain both the email address and source context, you can review where each collected address came from instead of working with an email-only list.

### Benefits

The Actor provides several practical benefits for structured Resellerratings research.

- **Automated collection** — Reduce repetitive manual searching and copying.
- **Multiple keyword support** — Run several related searches in one Actor execution.
- **Domain-specific targeting** — Focus on the email suffixes relevant to your project.
- **Geographic targeting** — Narrow searches using a country, state, or city.
- **Structured records** — Keep the email and supporting search-result information together.
- **Filtering** — Exclude descriptions containing unwanted words or phrases.
- **Duplicate reduction** — Previously encountered email addresses are tracked to avoid repeated records.
- **Progress persistence** — Collection progress is saved during the run.

These capabilities make the Actor suitable for research workflows where consistent and searchable contact data is more useful than manually collected notes.

### How to Use the Resellerratings Email Scraper

The basic workflow is straightforward:

1. Enter one or more Resellerratings-related keywords.
2. Optionally provide a country, state, or city in the location field.
3. Add the email domains you want to search for.
4. Set the maximum number of emails for each keyword + domain combination.
5. Optionally add words or phrases that should be excluded.
6. Start the Actor.
7. Review the resulting dataset containing the keyword, title, description, URL, and email.

For a first run, use a small number of targeted keywords and a modest email target. Once you understand the results, you can broaden the search with additional keywords or domains.

### Input

The Actor accepts a JSON object containing the search configuration.

The `keywords` field is required. The remaining fields are optional and provide additional control over the search.

### Input Fields

| Field           | Type             | Required | Default                                      | Description                                                                             |
| --------------- | ---------------- | -------- | -------------------------------------------- | --------------------------------------------------------------------------------------- |
| `keywords`      | Array of strings | Yes      | `["online store reviews", "seller reviews"]` | Keywords or queries used for Resellerratings searches.                                  |
| `location`      | String           | No       | `""`                                         | Optional country, state, or city used to narrow the search.                             |
| `customDomains` | Array of strings | No       | `["@gmail.com"]`                             | Email domain suffixes to include when searching for addresses.                          |
| `maxEmails`     | Integer          | No       | `5`                                          | Maximum email target for each keyword + domain combination. Accepted range is 1–10,000. |
| `excludeWords`  | Array of strings | No       | `[]`                                         | Words or phrases that cause a matching result description to be skipped.                |

The `keywords` array can contain multiple search terms. More specific terms can help target a particular type of Resellerratings result.

The `location` value can be left empty when geographic filtering is not required.

For `customDomains`, use email suffixes such as:

- `@gmail.com`
- `@yahoo.com`
- `@outlook.com`
- `@hotmail.com`
- `@icloud.com`

The `maxEmails` setting applies independently to each keyword + domain combination. For example, with three keywords, two domains, and a limit of 20, the Actor can target up to 20 addresses for each of the six combinations, subject to what matching results are available.

For Apify free-tier runs, the Actor applies a 100-email maximum when the requested limit is higher than that or no limit is provided. Paid runs do not receive this Actor-level free-tier restriction.

### Input Example

```json
{
  "keywords": [
    "online store reviews",
    "seller reviews",
    "ecommerce seller"
  ],
  "location": "United States",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com"
  ],
  "maxEmails": 20,
  "excludeWords": [
    "crypto",
    "onlyfans"
  ]
}
```

### Output

The Actor stores collected results in the **Resellerratings Emails Dataset**.

Each result is represented as a structured record containing the search keyword, result title, description, source URL, and extracted email address.

The output is designed to preserve useful context around each email rather than returning an email address without its associated search information.

### Output Fields

| Field         | Description                                                        |
| ------------- | ------------------------------------------------------------------ |
| `keyword`     | The keyword used to find the corresponding result.                 |
| `title`       | The title of the search result.                                    |
| `description` | The search-result description associated with the result.          |
| `url`         | The source URL represented by the search result.                   |
| `email`       | The extracted email address matching the configured domain suffix. |

### Output Example

```json
{
  "keyword": "seller reviews",
  "title": "Example Online Seller Reviews",
  "description": "Example description containing contact@example.com and information about the seller.",
  "url": "https://www.resellerratings.com/",
  "email": "contact@example.com"
}
```

The example values above are illustrative. Actual results depend on the keywords, location, email domains, available search results, and publicly available information returned for the search.

### Use Cases

#### Business and Seller Research

Use targeted searches to identify contact information associated with relevant sellers, online stores, or review-related results.

#### Market Research

Build structured datasets for researching businesses and market segments represented in Resellerratings-related search results.

#### Lead Research

Use keyword and domain targeting to discover potentially relevant contact addresses for further manual qualification.

#### E-commerce Research

Search terms related to online stores, sellers, retailers, and e-commerce can help organize contact research around online commerce.

#### Competitive Research

Collect search-result context around relevant sellers or online businesses to support broader competitive research.

#### Business Intelligence

Combine structured email records with their keyword, description, and source URL for analysis and research workflows.

#### Dataset Creation

Create a consistent dataset of contact records instead of maintaining manually copied search results.

#### Research Automation

Use the Actor as one automated step within a larger Apify-based data collection or analysis workflow.

### Advantages

The Actor combines several controls that are useful for targeted Resellerratings research.

- Multiple keywords can be processed in one run.
- Multiple email domains can be configured.
- Searches can optionally be narrowed by location.
- Maximum email targets can be configured per keyword + domain combination.
- Unwanted descriptions can be filtered with exclusion words or phrases.
- Output records preserve both contact information and search context.
- Duplicate email addresses are tracked during collection.
- Progress is persisted during collection.

These controls let users start with a focused search and gradually expand coverage when additional data is needed.

### Limitations

Results depend on the publicly available information represented in relevant search results. The Actor cannot guarantee that every Resellerratings result contains an email address matching your configured domains.

A keyword may produce few or no matching records when the search is too specific, the selected domain is uncommon, or relevant public contact information is not available.

The `maxEmails` setting is a target or cap for each keyword + domain combination; it does not guarantee that the requested number of addresses will be found.

The Actor may also finish a search combination before reaching the configured target when relevant results are exhausted or additional pages do not provide enough new matching emails.

For free-tier Apify runs, the Actor-level collection limit is capped at 100 emails.

### Pros and Cons

| Pros                              | Cons                                                     |
| --------------------------------- | -------------------------------------------------------- |
| Supports multiple search keywords | Results depend on available public contact information   |
| Supports multiple email domains   | A configured target does not guarantee that many results |
| Optional location targeting       | Narrow searches may produce sparse results               |
| Exclusion words and phrases       | Some searches may contain irrelevant results             |
| Structured dataset output         | Output is limited to the documented fields               |
| Duplicate email tracking          | Not every source result contains a matching email        |
| Progress persistence              | Large or broad searches can take longer                  |

### Comparison With Alternative Approaches

| Capability                     | Resellerratings Email Scraper | Manual Research                                  |
| ------------------------------ | ----------------------------- | ------------------------------------------------ |
| Keyword-based collection       | Supported                     | Requires repeated searches                       |
| Multiple keywords              | Supported                     | Usually handled individually                     |
| Email-domain targeting         | Supported                     | Requires manual query construction               |
| Location targeting             | Supported                     | Requires manual search refinement                |
| Exclusion filtering            | Supported                     | Requires manual review                           |
| Structured output              | Supported                     | Usually requires manual organization             |
| Duplicate email tracking       | Supported during collection   | Requires manual checking                         |
| Incremental dataset collection | Supported                     | Usually manual                                   |
| Resume support                 | Progress is persisted         | Manual work must generally be tracked separately |

This Actor is not intended to replace human review when the quality or relevance of individual contacts is important. It is better viewed as an automated collection layer that produces structured research data.

### Best Practices

For better-targeted research, consider the following practices:

- Use several specific keywords instead of relying on one very broad term.
- Combine related search phrases that describe the businesses, sellers, or topics you want to research.
- Start with a small `maxEmails` value to evaluate the quality of results.
- Add multiple email domains when broader contact coverage is useful.
- Use the location field when geographic targeting is important.
- Leave the location empty when you want a broader search.
- Use `excludeWords` to remove descriptions containing clearly unwanted terms.
- Review a small test dataset before launching a large collection.
- Validate important contact information before using it in downstream workflows.
- Broaden your keywords if the initial run produces sparse results.

Specific search terms can be more useful than very general terms because they give the Actor clearer search intent.

### Troubleshooting

#### Invalid Input

Check that `keywords` is provided as an array of strings. Confirm that `maxEmails` is an integer between 1 and 10,000 when supplied.

#### Empty Results

Try broader or more specific keywords depending on the original query. You can also remove the location filter or add additional email domains.

#### Partial Results

A partial result set does not necessarily indicate a configuration problem. The available public information may simply contain fewer matching email addresses than the requested target.

#### Missing Emails

The Actor only collects email addresses matching the configured email domain suffixes. If you search only for `@gmail.com`, addresses using other domains will not match that configuration.

#### Excluded Results

Review your `excludeWords` values if expected records are missing. A matching word or phrase in a result description causes that entire result description to be skipped.

#### Interrupted Runs

Progress is persisted during collection. If a run is interrupted, the Actor is designed to retain its saved progress and continue from the stored position on a subsequent run.

#### Large Searches

Broad searches using many keywords and domains can require more processing time. The input documentation recommends increasing the Apify run timeout when necessary; the default run timeout described by the Actor configuration is 3600 seconds.

### Frequently Asked Questions

#### What does the Resellerratings Email Scraper do?

It searches for relevant Resellerratings results using your keywords and configured email domains, then collects matching email addresses together with their keyword, title, description, and URL.

#### What keywords should I use?

Use specific terms related to the businesses, sellers, products, or research topic you are interested in. Multiple related keywords can provide broader coverage than one general search term.

#### Can I use multiple keywords?

Yes. The `keywords` input accepts an array of strings, allowing multiple searches within the same run.

#### Can I search by country or city?

Yes. The optional `location` field accepts a country, state, or city and can be used to narrow the search geographically.

#### Which email domains are supported?

You can provide custom email suffixes through `customDomains`. Examples include `@gmail.com`, `@yahoo.com`, and `@outlook.com`.

#### What does `maxEmails` control?

`maxEmails` controls the maximum target for each keyword + domain combination. It accepts values from 1 through 10,000 in the input schema.

#### Does the Actor guarantee the requested number of emails?

No. `maxEmails` is a target or cap, not a guarantee. The Actor can only collect matching email addresses available in relevant public search results.

#### What fields are returned?

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

#### How does `excludeWords` work?

If a configured word or phrase appears in a result description, that result is skipped. Single words are matched case-insensitively as whole words, while phrases use case-insensitive matching.

#### Can the Actor avoid duplicate emails?

The Actor tracks collected email addresses and skips addresses that have already been encountered during collection.

#### Is the Resellerratings Email Scraper useful for automation?

Yes. It is designed as an Apify Actor and produces structured dataset records, making it suitable for automated research and data-collection workflows.

### NLP Keywords

- Resellerratings email scraper
- Resellerratings email extraction
- Resellerratings contact data
- Resellerratings leads
- Resellerratings seller research
- Resellerratings business data
- Resellerratings contact discovery
- Resellerratings email finder
- Resellerratings data extraction
- Resellerratings search results
- Resellerratings public information
- seller review research
- online store research
- ecommerce seller data
- business contact research
- email domain targeting
- location-based search
- structured contact dataset
- keyword-based email discovery
- automated contact collection

### Related Keywords

- Resellerratings scraper
- Resellerratings contact scraper
- Resellerratings email finder
- Resellerratings lead scraper
- Resellerratings data scraper
- scrape Resellerratings emails
- extract emails from Resellerratings
- Resellerratings business email search
- Resellerratings seller email search
- online store email scraper
- seller review email scraper
- ecommerce contact scraper
- ecommerce seller email finder
- seller contact research
- online retailer contact data
- business email extraction
- public email discovery
- keyword email scraper
- location-based email search
- Apify email scraper

### Final Overview

Resellerratings Email Scraper provides a configurable way to collect email addresses associated with relevant Resellerratings search results and organize them into a structured Apify dataset.

You can control the search with multiple keywords, optional locations, custom email domains, maximum email targets, and exclusion words. Each collected record includes the keyword, result title, description, URL, and matching email address.

For the best research workflow, begin with focused keywords and a small target, review the resulting records, and then expand your keywords, domains, or geographic scope as needed. Because results depend on publicly available information, thoughtful search configuration is important when building a useful dataset.

*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": [
    "online store reviews",
    "online store"
  ],
  "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": [
        "online store reviews",
        "online store"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com"
    ],
    "excludeWords": []
};

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

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

```

## MCP server setup

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