# Wordpress Email Scraper - Bulk Keywords, Decodes Hidden Emails (`code-beat/wordpress-email-scraper-ultra-fast-and-precise`) Actor

🔵 WordPress Email Scraper extracts site owner, blogger and agency emails at scale using keywords. 🔓 Decodes encoded addresses, filters domains. 🔗 Built for link building, plugin marketing & guest post outreach.

- **URL**: https://apify.com/code-beat/wordpress-email-scraper-ultra-fast-and-precise.md
- **Developed by:** [Code Beat](https://apify.com/code-beat) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 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.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### Wordpress Email Scraper 🔍

**Wordpress Email Scraper** helps you extract emails from Wordpress faster and with less manual work. It’s built for marketers, recruiters, sales pros, and researchers who need Wordpress lead generation, a reliable email finder tool, and a practical way to collect public contact details at scale. ⚡

### 🌟 Key Features of Wordpress Email Scraper

| Feature | Benefit |
|---|---|
| ✅ **Targeted Keyword Search** | Uses your keywords to find relevant Wordpress pages and improve result quality. |
| ✅ **Location Filtering** | Optionally narrow results by location for more focused WordPress contact extraction. |
| ✅ **Custom Domain Filter** | Look for specific email domains such as `@gmail.com` or `@yahoo.com`. |
| ✅ **Maximum Email Cap** | Stop after the number of emails you want to control cost and runtime. |
| ✅ **Incremental Saving** | Saves results as they are found so long runs keep their progress. |
| ✅ **Built-In Proxy Support** | Uses built-in proxy support for more reliable scraping of public web data. |
| ✅ **Resume Support** | Continues from saved progress if a run is interrupted. |

### 📥 Input — Wordpress Email Scraper Parameters

```json
{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20
}
```

| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| `keywords` | Array | Yes | `["manager", "founder"]` | A list of keywords or queries to search for. |
| `location` | String | No | `""` | Location to filter search results. Leave empty if you do not need a location filter. |
| `customDomains` | Array | No | `["@gmail.com", "@yahoo.com"]` | List of email domains to include in the search, such as common personal domains or company domains. |
| `maxEmails` | Integer | No | `20` | Maximum number of emails to collect. The scraper stops when this limit is reached. |

### 📤 Output — What Wordpress Email Scraper Returns

The actor saves each result as a JSON record in your Apify dataset.

```json
{
  "keyword": "founder",
  "title": "About Jane Smith",
  "description": "Jane Smith leads growth and partnerships at a boutique digital agency in Austin. Contact: jane.smith@gmail.com",
  "url": "https://examplewordpresssite.com/about-jane-smith",
  "email": "jane.smith@gmail.com"
}
```

| Field | Label | Format | Description |
|---|---|---|---|
| `keyword` | Keyword | text | The keyword that led to this result. |
| `title` | Title | text | The page title or headline associated with the result. |
| `description` | Description | text | The visible page text where the email was found. |
| `url` | Url | link | The direct link to the page. |
| `email` | Email | text | The email address extracted from the page. |

### 💻 How to Use Wordpress Email Scraper — Step-by-Step

1. **Open the Actor** — Find **Wordpress Email Scraper** on Apify and open the actor page.
2. **Enter Keywords** — Add the job titles, roles, or topics you want to target.
3. **Set Location** — Optionally narrow your search with a location filter.
4. **Choose Email Domains** — Add domains like `@gmail.com`, `@yahoo.com`, or company domains.
5. **Set Max Emails** — Limit the number of emails collected in each run.
6. **Run the Actor** — Start the scraper and monitor live logs for progress.
7. **Export Results** — Download the dataset when the run finishes and use it in your email extraction software, CRM, or research workflow.

No coding required — just enter your filters and get results in minutes. 🚀

### 💡 Best Use Cases for Wordpress Email Scraper

- 🎯 **WordPress Lead Generation** — Build targeted contact lists from public Wordpress pages.
- 📣 **Email Marketing** — Collect publicly available contacts for outreach campaigns.
- 🤝 **Recruitment** — Find professional emails tied to Wordpress pages and public profiles.
- 🔬 **Market Research** — Discover contact info extraction opportunities across niche Wordpress content.
- 📊 **CRM Enrichment** — Add public email data to existing records for better segmentation.

### Disclaimer

This actor only accesses publicly available data on Wordpress. It does not access private profiles, authenticated pages, or password-protected content. You are responsible for using the results in compliance with applicable laws, including privacy and anti-spam regulations, as well as relevant website terms.

For data-removal requests, contact 📧 <codebeatapi@gmail.com>.

### 🆘 Support & Feedback

Have a question or found an issue with the **Wordpress Email Scraper**? We’re here to help.

- 🐞 **Bug Reports:** Share the issue with our team so we can investigate it
- ✨ **Custom Solutions & Feature Requests:** Reach out if you need tailored email extraction support
- 📧 **Email:** <codebeatapi@gmail.com>

Your feedback helps improve the WordPress email scraper experience for everyone.

### Country & Time Targeting

Both filters are applied to the Google query itself, so they shape which pages
the dork is answered from rather than filtering after the fact.

**Target Country** - runs the search as if from that country (`gl`). Turn on
**Strict country filter** to additionally restrict results to pages Google
attributes to it (`cr=countryXX`); that is much tighter and returns noticeably
fewer results. Leave the country on *Global (no country filter)* for worldwide
results.

**Result Language** - restricts results to a single language (`hl` + `lr`).

**Time Range** - limits results to a publication window: past hour, 24 hours,
week, month, year, or an explicit *Custom range* using **Custom range: from** /
**to** in `YYYY-MM-DD` form. A page Google indexed last week is far more likely
to carry a live mailbox than one it last saw five years ago.

Selecting *Custom range* without either date falls back to no time filter rather
than searching all of time by accident.

# Actor input Schema

## `scrapeMode` (type: `string`):

Find New Emails (default) searches Airbnb by keyword. Clean My List skips searching entirely and instead runs the emails you paste into Email List (below) through the same deliverability checks.

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

A list of keywords or queries to search for.

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

Location to filter search results.

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

List of custom email domains

## `emailList` (type: `array`):

Paste the emails you want checked for deliverability. Only used when Scrape Mode is set to "Clean My List".

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

Maximum number of emails to collect. The scraper will stop once this limit is reached. Setting a higher limit allows for more potential results but doesn't guarantee reaching that number. This helps save costs by controlling scraping time.

## `verificationMode` (type: `string`):

Quick Check (default) validates syntax and MX records only - fast, no added latency. Deep Check additionally flags disposable-domain addresses and checks each domain against a public spam blocklist (Spamhaus DBL). Off skips validation entirely.

## `minQualityScore` (type: `number`):

Drop any contact whose quality score (0.0-1.0) falls below this. Leave at 0 for no filter.

## `excludeCatchAll` (type: `boolean`):

Drop contacts on domains confirmed to accept mail for any address (only applies when that signal is available).

## `requireMxValid` (type: `boolean`):

Drop any contact whose domain has no valid mail server (MX record).

## `targetCountry` (type: `string`):

Ask Google to answer as if searching from this country. Leave on "Global (no country filter)" for worldwide results.

## `strictCountry` (type: `boolean`):

Restrict results to pages Google attributes to the target country (cr=countryXX), instead of only preferring them. Much tighter targeting, noticeably fewer results.

## `searchLanguage` (type: `string`):

Restrict results to one language. Leave on "Any language" for no filter.

## `timeRange` (type: `string`):

Only return pages Google indexed within this window. Recent pages are more likely to hold a mailbox that still works.

## `customDateFrom` (type: `string`):

Only used when Time Range is "Custom range". Format: YYYY-MM-DD.

## `customDateTo` (type: `string`):

Only used when Time Range is "Custom range". Format: YYYY-MM-DD.

## Actor input object example

```json
{
  "scrapeMode": "Find New Emails",
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "emailList": [],
  "maxEmails": 20,
  "verificationMode": "Quick Check",
  "minQualityScore": 0,
  "excludeCatchAll": false,
  "requireMxValid": false,
  "targetCountry": "Global (no country filter)",
  "strictCountry": false,
  "searchLanguage": "",
  "timeRange": "Any time",
  "customDateFrom": "",
  "customDateTo": ""
}
```

# 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": [
        "manager",
        "founder"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "emailList": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("code-beat/wordpress-email-scraper-ultra-fast-and-precise").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": [
        "manager",
        "founder",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "emailList": [],
}

# Run the Actor and wait for it to finish
run = client.actor("code-beat/wordpress-email-scraper-ultra-fast-and-precise").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": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "emailList": []
}' |
apify call code-beat/wordpress-email-scraper-ultra-fast-and-precise --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,code-beat/wordpress-email-scraper-ultra-fast-and-precise"
        }
    }
}

```

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/ruyt5lNiwt1xBLcC5/builds/wP0WYwjMLJj4fJRdh/openapi.json