# WordPress Phone Number Scraper (`phone_number_scraper/wordpress-phone-number-scraper`) Actor

\[1k/2.5$] Scrape WordPress phone numbers at scale. Find direct contact numbers for site owners and agencies and build targeted lead lists for sales, marketing and recruiting. Easy WordPress phone number scraper with CSV, JSON and Excel export.

- **URL**: https://apify.com/phone_number_scraper/wordpress-phone-number-scraper.md
- **Developed by:** [Phone Number Scraper](https://apify.com/phone_number_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

### WordPress Phone Number Scraper

> 📞 **WordPress Phone Number Scraper** collects public phone numbers of web agencies and bloggers from WordPress. Search by keyword, country and city, validate each number, and export clean CSV, JSON or Excel data.

### 🔍 WordPress Phone Number Scraper – Overview

WordPress Phone Number Scraper is an Apify Actor that finds public phone numbers on WordPress and saves them as a structured phone lead list. WordPress is an open-source content management system and community, and its public pages sometimes show a call, booking or WhatsApp number in the title or description. WordPress Phone Number Scraper is built to find contact numbers of web agencies and bloggers.

WordPress Phone Number Scraper validates every number against the numbering plan of the country you select and removes duplicates. Logging in to WordPress is not required, and results export to CSV, JSON or Excel for your CRM, dialler or WhatsApp outreach. WordPress Phone Number Scraper suits lead generation, sales prospecting and market research.

> ✅ **WordPress Phone Number Scraper at a glance**
>
> - **Source:** public pages on WordPress (wordpress.org)
> - **Default country:** United States (+1)
> - **Prefilled keywords:** `developer`, `blogger`
> - **Default limit:** 5 phone numbers per keyword (maximum 10,000)
> - **Output:** one dataset row per phone number from WordPress, in JSON, CSV or Excel

### ✨ WordPress Phone Number Scraper – Key Features

WordPress Phone Number Scraper combines wide country coverage with practical filters:

- **Keyword search on WordPress:** WordPress Phone Number Scraper runs one keyword or a long list, each searched separately.
- **194 countries, one or many:** numbers are validated against each selected dial code and numbering plan.
- **City targeting on WordPress:** add places such as Austin or Denver, each searched on its own.
- **Three number modes:** WhatsApp, call or booking, or any number published on WordPress.
- **Number filters:** mobile or landline, area-code prefixes, fake and premium-rate removal.
- **Profile and text filters:** profile pages only, follower range, include and exclude words, one number per account.
- **Optional extras:** line type, carrier, area, formats, WhatsApp links, profile details and emails for WordPress leads.
- **Only new leads:** remember earlier runs and keep a do-not-call list, so you never pay twice for the same lead from WordPress.
- **Cost control:** per-keyword and total limits, page caps, 1 to 10 parallel searches.
- **API and scheduling:** run WordPress Phone Number Scraper through the Apify API or on a schedule.

> 💡 **Why use WordPress Phone Number Scraper?** One repeatable run replaces manual searching on WordPress: validated numbers, no duplicates, data ready for your CRM or dialler.

### 🚀 WordPress Phone Number Scraper – How to Use It

Follow these steps to run WordPress Phone Number Scraper from the Apify Console:

- **Step 1 – Open WordPress Phone Number Scraper** on the Apify Store and go to the Input tab.
- **Step 2 – Add keywords** to WordPress Phone Number Scraper, such as `developer` or `blogger`.
- **Step 3 – Choose a country,** such as United States (+1), and optionally add cities like Austin to narrow your search on WordPress.
- **Step 4 – Pick the number mode** for WordPress and set Max Phone Numbers.
- **Step 5 – Add filters and extras** for WordPress if you need them.
- **Step 6 – Run WordPress Phone Number Scraper** and export the dataset as JSON, CSV or Excel, or read it through the API.

While it runs, the status message shows how many searches have finished and how many phone numbers were saved.

#### 🔎 How to scrape WordPress phone numbers for a city or region?

WordPress Phone Number Scraper searches every keyword with every place in Cities or regions, such as Austin and Denver. The selected country still decides the dial code. Two keywords and two cities make four searches, so add a total limit for long lists.

#### 💬 Can WordPress Phone Number Scraper find WhatsApp or booking numbers on WordPress?

Yes. WordPress Phone Number Scraper offers three modes: WhatsApp numbers (the default), call or booking numbers, and any number without a contact word. Choose mobile numbers when you plan WhatsApp or SMS outreach.

### 💡 WordPress Phone Number Scraper – Use Cases

Typical ways to use WordPress Phone Number Scraper:

- Find web agencies and developers that list a number on WordPress pages.
- Build a regional list of site-building studios.
- Collect theme and plugin company lines shown on WordPress.
- Run recurring searches on WordPress and receive only new phone numbers each time.

> 📌 Numbers from WordPress come from public pages. Review them and follow local marketing and privacy rules before you contact anyone.

### ⚙️ WordPress Phone Number Scraper – Input

WordPress Phone Number Scraper needs only two fields: **keywords** and **country**. Everything else is optional and tunes how WordPress is searched.

| Field | What it does |
|---|---|
| `keywords` | **Required.** Words to search for on WordPress, one search each. Default: `developer`, `blogger`. |
| `perKeywordMaxContacts` | Max Phone Numbers applies per keyword (off: one total for the run). Default: on. |
| `country` | **Required.** Dial code and numbering plan used to validate numbers. Default: United States (+1). |
| `additionalCountries` | More countries searched on WordPress in the same run. Default: none. |
| `locations` | Cities or regions searched on WordPress with every keyword. Default: none. |
| `contactIntent` | `whatsapp`, `callOrBooking` or `anyNumber`. Default: whatsapp. |
| `resultsFreshness` | Pages on WordPress indexed in the past `day`, `week`, `month` or `year`. Default: any. |
| `maxPhoneNumbers` | Numbers to collect from WordPress, 1 to 10,000. Default: 5. |
| `maxTotalPhoneNumbers` | Hard stop for the whole run. 0 means none. Default: 0. |
| `maxConcurrentSearches` | Parallel searches, 1 to 10. Default: 5. |
| `phoneNumberType` | `any`, `mobile` or `landline`. Default: any. |
| `onePhonePerProfile` | Keep the first number per account on WordPress only. Default: off. |
| `onlyAreaCodes` | Keep only prefixes such as `+44 20`. Default: none. |
| `skipFakeNumbers` | Drop sequential, repeated and premium-rate numbers. Default: off. |
| `profilesOnly` | Keep only profile pages like wordpress.org/name. Default: off. |
| `minFollowers` | Minimum followers. 0 is off. Default: 0. |
| `maxFollowers` | Maximum followers. 0 is off. Default: 0. |
| `includeWords` | Words required in the title or description. Default: none. |
| `includeWordsMatch` | `any` or `all` of the include words. Default: any. |
| `excludeWords` | Skip results from WordPress containing these words. Default: none. |
| `addNumberDetails` | Adds line type, carrier, area, formats and WhatsApp link. Default: off. |
| `addProfileDetails` | Adds username, page type, followers and tier. Default: off. |
| `extractEmails` | Adds emails found next to the number. Default: off. |
| `skipPreviouslyFoundNumbers` | Skip numbers saved by earlier runs. Default: off. |
| `historyStoreName` | History name: lowercase letters, numbers, hyphens. Default: `wordpress-phone-history`. |
| `excludePhoneNumbers` | Do-not-call list. `+4470*` skips a range. Default: none. |
| `excludeAccounts` | Usernames or profile links on WordPress to skip. Default: none. |
| `maxPagesPerSearch` | Result pages per search. 0 is automatic. Default: 0. |
| `stopAfterIdlePages` | End a search after this many pages without new numbers. Default: 3. |
| `proxyConfiguration` | Optional. The default suits most runs. Default: automatic. |

Leave the optional fields at their defaults for a first WordPress Phone Number Scraper run, then tighten the filters.

#### 🧪 Sample input for WordPress Phone Number Scraper

This example searches WordPress for developer and blogger in Austin and Denver, looks for call or booking numbers, keeps any type of number, adds profile details, and remembers numbers between runs.

```json
{
  "keywords": ["developer", "blogger"],
  "country": "United States (+1)",
  "locations": ["Austin", "Denver"],
  "contactIntent": "callOrBooking",
  "maxPhoneNumbers": 50,
  "maxTotalPhoneNumbers": 200,
  "phoneNumberType": "any",
  "addNumberDetails": true,
  "addProfileDetails": true,
  "skipPreviouslyFoundNumbers": true,
  "historyStoreName": "wordpress-phone-history"
}
```

### 📦 WordPress Phone Number Scraper – Output and Data Fields

WordPress Phone Number Scraper saves one dataset row per phone number, together with the page on WordPress it came from. Optional fields appear only when their option is on. Run totals are also saved to a SUMMARY record in the key-value store.

| Field | Meaning |
|---|---|
| `phone_number` | Number in international E.164 format, such as `+12015550123`. |
| `country` | Country the number was validated for. |
| `dial_code` | Dial code of that country. |
| `keyword` | Keyword of the search that found it. |
| `location` | City or region searched (only with Cities or regions). |
| `title` | Title of the result on WordPress. |
| `description` | Snippet that contained the number. |
| `url` | Link to the page on WordPress. |
| `platform` | `WordPress`. |
| `proxyGroups` | Technical field, filled in automatically. |
| `phoneType` | Number details: mobile, landline, voip, toll-free or unknown. |
| `carrier` | Number details: original network, when known. |
| `numberArea` | Number details: city or region of a landline, when known. |
| `phoneInternational` | Number details: such as `+1 201-555-0123`. |
| `phoneNational` | Number details: such as `(201) 555-0123`. |
| `whatsappLink` | Number details: click-to-chat link such as `https://wa.me/12015550123`. |
| `username` | Profile details: account name from the address or title. |
| `pageType` | Profile details: `profile` (wordpress.org/name), `post`, `reel` or `other`. |
| `followersCount` | Profile details: followers shown in the result, else empty. |
| `influencerTier` | Profile details: `nano`, `micro`, `macro` or `mega`. |
| `emails` | Extract emails: addresses found in the same snippet. |

Every row from WordPress Phone Number Scraper keeps the keyword and country, so lists from different runs can be merged safely.

#### 🧾 Sample output

Sample record from WordPress Phone Number Scraper with every option switched on (illustrative values):

```json
{
  "phone_number": "+12015550123",
  "country": "United States",
  "dial_code": "+1",
  "keyword": "developer",
  "location": "Austin",
  "title": "Example Studio - WordPress",
  "description": "12.4K followers. Call +1 201-555-0123 to book or ask a question - hello@example.com",
  "url": "https://www.wordpress.org/examplebrand",
  "platform": "WordPress",
  "proxyGroups": ["<automatic>"],
  "phoneType": "landline or mobile",
  "carrier": null,
  "numberArea": "New Jersey",
  "phoneInternational": "+1 201-555-0123",
  "phoneNational": "(201) 555-0123",
  "whatsappLink": "https://wa.me/12015550123",
  "username": "examplebrand",
  "pageType": "profile",
  "followersCount": 12400,
  "influencerTier": "micro",
  "emails": ["hello@example.com"]
}
```

### 💰 Pricing

> 💰 WordPress Phone Number Scraper bills per result: each phone number from WordPress saved to the dataset is one result. Numbers removed by a filter, skip list, history or limit are not saved and not charged. See the Pricing tab on the Actor page for the current rate.

Free Apify accounts receive up to 20 rows per run with WordPress Phone Number Scraper. Max Phone Numbers, the total limit and the maximum cost per run keep spending predictable, and the run stops cleanly when a limit is reached.

### 🛠️ Tips and Best Practices

- **Start small with WordPress Phone Number Scraper.** Keep the default of 5 numbers per keyword for a test run, then raise Max Phone Numbers.
- **Match mode and type.** Pair WhatsApp mode with mobile numbers, and call or booking mode with landlines when you search WordPress.
- **Thin results?** Add related keywords, switch to Any number, or raise the page depth and idle-page limits for WordPress.
- **Profile filters expect wordpress.org/name addresses.** Leave Profile pages only off when pages on WordPress use longer addresses.
- **Follower filters need a visible count.** Results from WordPress without one are skipped while a follower filter is on.
- **Schedule WordPress Phone Number Scraper.** Turn on Skip phone numbers found in earlier runs to receive only new leads.
- **Large runs.** Raise the run timeout in Run options. The default is 3,600 seconds.
- **Review before outreach.** Snippets can be cut off, so check numbers from WordPress and respect local rules.

### ❓ Frequently Asked Questions

#### ❔ What does WordPress Phone Number Scraper do?

WordPress Phone Number Scraper searches public pages on WordPress for phone numbers that match your keywords and country, validates them and saves them as dataset rows. Export the data as CSV, JSON or Excel.

#### 🌍 Can WordPress Phone Number Scraper target one country or city on WordPress?

Yes. WordPress Phone Number Scraper accepts one of 194 countries, optionally more, and a list of cities. Each combination is searched separately, and numbers found on WordPress are validated for the country they belong to.

#### 📱 Can WordPress Phone Number Scraper add WhatsApp links to the numbers it finds on WordPress?

Yes. Switch on number details and WordPress Phone Number Scraper adds a click-to-chat link to each row, plus line type, carrier and area when known. The link opens a chat but does not prove that the number has a WhatsApp account.

#### 🔐 Does WordPress Phone Number Scraper need a login or API key for WordPress?

No. WordPress Phone Number Scraper works without logging in to WordPress, so you need no cookies, passwords or API keys. You only need an Apify account.

#### 📊 How many phone numbers can I collect from WordPress per run?

Max Phone Numbers accepts up to 10,000, per keyword by default, and the total limit caps the whole run. Free Apify accounts receive up to 20 rows per run.

#### ⚖️ Is it legal to scrape phone numbers from WordPress?

WordPress Phone Number Scraper reads publicly visible text on WordPress only, but phone numbers can be personal data. Check the rules that apply to you, such as GDPR, PECR or do-not-call registries. This is not legal advice.

### 🤝 Support

Questions, feature ideas or a custom version of WordPress Phone Number Scraper? Use the Issues tab on the Actor page, or write to the address below.

- contact me by email : alphascraper69@gmail.com

# Actor input Schema

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

A list of keywords to search for. (Example: John, marketing, etc.)

## `perKeywordMaxContacts` (type: `boolean`):

ON (default): "Max Phone Numbers" is a target for EACH keyword, so the scraper works through every keyword instead of stopping once the first one fills up. OFF: it is a single total for the whole run. ⚠️ Heads-up: with this ON the run can collect (and be billed for) Max Phone Numbers × number of keywords, and takes proportionally longer.

## `country` (type: `string`):

Select a country to scrape related phone numbers.

## `additionalCountries` (type: `array`):

Optional extra countries searched in the same run, so one job can cover for example the United Kingdom, Ireland and Australia. Every country is searched on its own with its own dial code, and only numbers valid for that country are kept for it, so numbers from different markets never get mixed up (the country and dial_code fields of each row show which one found it). The country chosen above is always included. When "Per Keyword Scrape Max Contacts" is ON, each keyword + country (+ location) combination gets its own limit. The searches multiply: 2 keywords × 3 countries = 6 searches, so pair a long list with the total phone number limit. Cities in "Cities or regions" are used for every country, so leave that list empty or use names that make sense everywhere.

## `locations` (type: `array`):

Optional cities, regions or neighbourhoods used to find local businesses and creators, for example: London, Manchester, Leeds. Every location is searched on its own together with each keyword, so one run can cover many places. They are search words only: the selected Country still decides the dial code and which phone numbers are accepted. Leave the list empty to search the whole country. When "Per Keyword Scrape Max Contacts" is ON, each keyword + location combination gets its own limit. The searches multiply: 3 keywords × 5 locations = 15 searches, so pair a long list with the total phone number limit below. A number found under more than one location is only saved once.

## `contactIntent` (type: `string`):

Controls the contact words the search relies on. 'WhatsApp numbers' (default, the original behaviour) looks for pages that mention WhatsApp next to a number with the selected dial code. 'Call or booking numbers' looks for pages that use words such as call, phone, tel, mobile, booking or contact instead, which suits salons, clinics, restaurants, studios and other businesses that take bookings by phone. 'Any number' drops the contact word and only needs your keyword and the dial code: it reaches the most pages but brings more noise, so combine it with the filters below. Every number is still validated for the selected country.

## `resultsFreshness` (type: `string`):

Keeps only pages that Google has indexed or updated within the chosen period. Useful for scheduled runs that should surface fresh posts and newly active accounts, and for skipping abandoned profiles. Google applies the date to the page as it knows it, so profile pages without a clear date can be left out, and shorter periods return far fewer results. 'Any time' (default) applies no date filter, which is the original behaviour.

## `maxPhoneNumbers` (type: `integer`):

Maximum number of phone numbers 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.

## `maxTotalPhoneNumbers` (type: `integer`):

A hard stop for the entire run, across every keyword and location. Once this many phone numbers have been collected the run finishes cleanly and keeps everything found so far. Use it to keep pay-per-result costs predictable: with "Per Keyword Scrape Max Contacts" ON, 20 keywords with a limit of 50 each could otherwise return up to 1,000 numbers. Leave at 0 to rely only on Max Phone Numbers above.

## `maxConcurrentSearches` (type: `integer`):

Every keyword + location  combination is its own search, and the searches do not depend on each other, so the Actor can run several at the same time instead of one after another. Most of a search is spent waiting for Google, so 4 searches at a time finish a long list roughly 3 to 4 times sooner, at the same cost per result. Limits, duplicate removal, filters and the total limit work exactly as before: an number found by two searches at once is still saved only once, and the total limit is never exceeded. What changes is the order: rows arrive as searches finish, and an number that several searches find is credited to whichever found it first. Set 1 to run one search at a time in the original order. Higher numbers finish sooner but send more requests at once, which can slow Google's answers down; 10 is the maximum. It makes no difference when there is only one search.

## `phoneNumberType` (type: `string`):

Keep only mobile numbers (best for WhatsApp, SMS and personal outreach) or only landlines (shops, clinics, offices). The type comes from the numbering plan of the selected country, so it is a good guide but not a guarantee. In countries where mobile and landline numbers share the same ranges (for example the United States and Canada) the type cannot be told apart, and those numbers are kept by both filters. Toll-free, VoIP, premium-rate and other special numbers are only kept with 'Any type of number'.

## `onePhonePerProfile` (type: `boolean`):

A bio or caption sometimes lists several numbers (for example a landline and a WhatsApp number), and by default each one is saved as its own row. Switch this on to keep only the first number found for each WordPress account, so every row is a different account and you pay for one number per account. When a result cannot be tied to an account, the page itself counts as the profile. Off by default.

## `onlyAreaCodes` (type: `array`):

Only keep numbers that start with one of these area codes or prefixes, for example to target a single city or only mobile ranges. Write each one with the international dial code and a plus sign: +44 20 (London), +1 212 (Manhattan), +49 30 (Berlin), +44 7 (UK mobile numbers). Spaces, dashes and brackets are ignored. Leave empty to accept every number. A prefix from another country than the one selected matches nothing. Numbers outside the list are not saved, not counted towards your limits and not charged.

## `skipFakeNumbers` (type: `boolean`):

A quality filter that drops numbers which are very unlikely to reach a real person: repeated or sequential digits (for example 07777 777777 or 01234 567890) and premium-rate or shared-cost numbers, which are usually paid service lines. Off by default, so existing setups behave as before. Skipped numbers are not saved and not charged.

## `profilesOnly` (type: `boolean`):

Most Google results for WordPress are not profiles: they are individual posts, reels and explore / tag pages. Switch this on to keep only results that point to a profile page (wordpress.org/username), so every saved row is one account. Recommended for influencer and B2B lead lists. Off by default, so existing setups behave as before.

## `minFollowers` (type: `integer`):

Only keep profiles with at least this many followers. Handy for skipping empty or brand-new accounts. When a follower filter is set, results whose follower count Google does not show (this includes most posts and reels) are skipped.

## `maxFollowers` (type: `integer`):

Only keep profiles with at most this many followers. Combine with the minimum to target a range, for example 10,000 to 100,000 for micro-influencers. Profiles for which Google shows no follower count are skipped when this filter is set.

## `includeWords` (type: `array`):

Words or phrases that must appear in the page's title or description snippet. A result is kept only if it contains at least one of them, for example: booking, appointments, orders, collab. Matching ignores letter case, and single words only match as whole words. Leave empty to keep every result. This is stricter than the search keywords, which Google matches loosely. If a result contains both an include word and an exclude word, it is skipped.

## `includeWordsMatch` (type: `string`):

Applies to 'Must-include words'. 'Any one of the words' keeps a result that contains at least one of them (the original behaviour). 'All of the words' keeps a result only if it contains every word, for stricter targeting, for example booking AND whatsapp. Has no effect while the must-include list is empty.

## `excludeWords` (type: `array`):

Words or phrases you do not want to see, for example: escort, crypto, giveaway. If any of them appears in a page's title or description snippet, that whole snippet is skipped and no phone number is taken from it. Matching ignores letter case, and single words only match as whole words. Leave empty to keep every snippet.

## `addNumberDetails` (type: `boolean`):

Adds these fields to every row: phoneType (mobile, landline, voip, toll-free and so on, or unknown), carrier (the network the number was originally allocated to, when known), numberArea (the city or region of a landline, when known), phoneInternational (for example +44 113 496 0789), phoneNational (for example 0113 496 0789) and whatsappLink (for example https://wa.me/441134960789). Carrier and area come from an offline numbering-plan database: a number that has since moved to another network can still show its original carrier, and the area is only available for some countries. A WhatsApp link opens a chat but does not prove that the number has a WhatsApp account.

## `addProfileDetails` (type: `boolean`):

Adds these fields to every row: username (the WordPress handle, when it can be identified), pageType (profile, post, reel or other), followersCount (when Google shows it in the result, otherwise empty) and influencerTier (nano, micro, macro or mega, worked out from followersCount). Everything comes from the Google result, so no extra requests are made and no WordPress login is used.

## `extractEmails` (type: `boolean`):

When the same bio or caption snippet also contains an email address, return it in an emails field next to the phone number, so one row carries both contact channels. Off by default because email addresses are personal data and a snippet can be cut off, so review them before use.

## `skipPreviouslyFoundNumbers` (type: `boolean`):

When switched on, the run loads the list of phone numbers saved under the history name below, skips any number already on it, and adds every new number to it. The result is a dataset that contains only new leads, which is ideal for scheduled runs. Off by default, so every run starts from scratch.

## `historyStoreName` (type: `string`):

Name of the saved history used by 'Skip phone numbers found in earlier runs'. Use the same name across runs to share one history, or a different name for each campaign to keep campaigns separate. Only lowercase letters, numbers and hyphens, 3–63 characters. The history is kept in a named Apify storage that stays in your account until you delete it.

## `excludePhoneNumbers` (type: `array`):

Phone numbers that must never appear in the results, for example people who asked not to be contacted, existing customers, or contacts already in your CRM. Enter full numbers in any common format (+44 113 496 0789 or 0113 496 0789; local formats are read for the selected country), or end a prefix with an asterisk to skip a whole range (for example +4470\*). A skipped number is not saved and not charged.

## `excludeAccounts` (type: `array`):

WordPress accounts whose results must never be saved, for example competitors, existing customers or brands you already work with. Enter usernames (the @ is optional) or profile links such as wordpress.org/brandname. Matching ignores letter case. A skipped account is not saved and not charged.

## `maxPagesPerSearch` (type: `integer`):

Caps how deep every search may go, for example 5 = the first 50 Google results. A search normally ends by itself when Google runs out of results or several pages in a row bring nothing new, so a cap only matters if you want shorter, cheaper runs. Leave at 0 for no cap.

## `stopAfterIdlePages` (type: `integer`):

A search ends when this many result pages in a row bring no new phone number. The default of 3 is a good balance. Raise it (5 to 10) to dig deeper on keywords with sparse results, at the cost of more requests and a longer run; lower it to finish sooner.

## `proxyConfiguration` (type: `object`):

Configure proxies for this Actor.

## Actor input object example

```json
{
  "keywords": [
    "developer",
    "blogger"
  ],
  "perKeywordMaxContacts": true,
  "country": "United States (+1)",
  "additionalCountries": [],
  "locations": [],
  "contactIntent": "whatsapp",
  "resultsFreshness": "any",
  "maxPhoneNumbers": 5,
  "maxTotalPhoneNumbers": 0,
  "maxConcurrentSearches": 5,
  "phoneNumberType": "any",
  "onePhonePerProfile": false,
  "onlyAreaCodes": [],
  "skipFakeNumbers": false,
  "profilesOnly": false,
  "minFollowers": 0,
  "maxFollowers": 0,
  "includeWords": [],
  "includeWordsMatch": "any",
  "excludeWords": [],
  "addNumberDetails": false,
  "addProfileDetails": false,
  "extractEmails": false,
  "skipPreviouslyFoundNumbers": false,
  "historyStoreName": "wordpress-phone-history",
  "excludePhoneNumbers": [],
  "excludeAccounts": [],
  "maxPagesPerSearch": 0,
  "stopAfterIdlePages": 3
}
```

# Actor output Schema

## `results` (type: `string`):

Structured records extracted by WordPress Phone Number Scraper and stored in the run's default dataset.

# 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": [
        "developer",
        "blogger"
    ],
    "additionalCountries": [],
    "locations": [],
    "onlyAreaCodes": [],
    "includeWords": [],
    "excludeWords": [],
    "excludePhoneNumbers": [],
    "excludeAccounts": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("phone_number_scraper/wordpress-phone-number-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": [
        "developer",
        "blogger",
    ],
    "additionalCountries": [],
    "locations": [],
    "onlyAreaCodes": [],
    "includeWords": [],
    "excludeWords": [],
    "excludePhoneNumbers": [],
    "excludeAccounts": [],
}

# Run the Actor and wait for it to finish
run = client.actor("phone_number_scraper/wordpress-phone-number-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": [
    "developer",
    "blogger"
  ],
  "additionalCountries": [],
  "locations": [],
  "onlyAreaCodes": [],
  "includeWords": [],
  "excludeWords": [],
  "excludePhoneNumbers": [],
  "excludeAccounts": []
}' |
apify call phone_number_scraper/wordpress-phone-number-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,phone_number_scraper/wordpress-phone-number-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/Ln1vK6VP4fSoVlWMl/builds/9rBSkBVGh3tfqqHo6/openapi.json