# Hotfrog Phone Number Scraper (`neuro-scraper/hotfrog-phone-number-scraper`) Actor

Hotfrog Phone Number Scraper SD - Hotfrog Phone Number Scraper is a lead generation tool that extracts leads with public phone numbers, account names and profile URLs from Hotfrog results by keyword, location and country - Hotfrog phone number extractor.

- **URL**: https://apify.com/neuro-scraper/hotfrog-phone-number-scraper.md
- **Developed by:** [Neuro Scraper](https://apify.com/neuro-scraper) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.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?

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

### Hotfrog Phone Number Scraper

**Hotfrog Phone Number Scraper** turns a keyword into a contact sheet of phone numbers published on Hotfrog. Give it search terms and it returns the accounts that publish a way to reach them, with the account name, handle and profile URL beside each contact.

It reads only what Hotfrog and Google already show a signed-out visitor. No login, no cookies, no private or partner API, no browser and no JavaScript rendering.

**Read this before your first run.** Hotfrog blocks most of its listing pages from search engines, so the Hotfrog Phone Number Scraper often returns nothing; the Brownbook, Cylex and Fyple Actors cover the same local-directory ground far better.

***

### What the Hotfrog Phone Number Scraper does

The Hotfrog Phone Number Scraper searches Google with a contact dork rather than a plain keyword: `site:hotfrog.com small business whatsapp "+44"`. That asks for the pages which already publish a phone number, instead of every page matching a word.

Each result block yields the account and the phone number together, in one request. Google no longer prints the target URL on most layouts, so the handle comes from what it does print: the "Hotfrog - handle" site label, the breadcrumb, or a `Name (@handle)` title.

Every row is written to the dataset the moment it is found and logged as it is written, so a run is readable while it is still going.

Phone numbers are validated by libphonenumber against the real numbering plan of the country you searched, so order numbers, dates and follower counts cannot reach the dataset. Each number is returned in E.164 form and in the national format its country uses.

***

### Input reference for the Hotfrog Phone Number Scraper

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array | `small business, services` | Search terms - a niche, job title or industry. |
| `location` | string | `""` | Added to every query, e.g. `New York`. |
| `countries` | array | US, UK, India | Which countries' numbers to look for. Name, ISO code or dial code. Each one multiplies the searches. |
| `maxEmails` | integer 1-10000 | `20` | Stop once this many unique contacts are found. |
| `expandQueries` | boolean | `true` | Search each keyword in several phrasings. |
| `queryModifiers` | array | per platform | Extra words combined with each keyword. |
| `maxPagesPerQuery` | integer 1-50 | `30` | Google result pages per query. |
| `maxConcurrency` | integer 1-20 | `5` | Queries run in parallel. |
| `countryCode` | string | `""` | Two-letter country for the search proxy. |

### Output

Every row the Hotfrog Phone Number Scraper writes:

| Field | Meaning |
|---|---|
| `network` | Platform name |
| `keyword` | The keyword that found this row |
| `query` | The exact Google query used |
| `phone` | The number in E.164 form, e.g. `+447590574946` |
| `phoneNational` | The same number as its country writes it |
| `phoneCountry` | ISO country the number belongs to |
| `accountName` | Account label as the platform shows it |
| `fullName` | Display name where published |
| `username` | Handle |
| `profileUrl` | Canonical profile URL |
| `url` | The page the result pointed at |
| `description` | The result snippet, cleaned |
| `foundAt` | ISO 8601 UTC timestamp |

```json
{
  "network": "Hotfrog",
  "keyword": "small business",
  "accountName": "examplestudio",
  "fullName": "Example Studio",
  "username": "examplestudio",
  "profileUrl": "https://www.hotfrog.com/company/examplestudio",
  "phone": "+447590574946",
  "phoneNational": "07590 574946",
  "phoneCountry": "GB"
}
```

### How to use the Hotfrog Phone Number Scraper

1. Put your search terms in **Keywords** - the niche, job title or industry you sell to.
2. Add a **Location** if the list should be local.
3. Pick the **Countries** whose numbers you want. Every number is validated against that country's numbering plan.
4. Set **Max results** to cap the run, then start it.
5. Export the dataset as CSV, JSON or Excel, or pull it through the Apify API.

### Use cases

**Lead generation.** Build a list of Hotfrog accounts in one niche that publish a phone number, with the handle and profile URL for context before you write.

**Recruiting.** Find people describing themselves with a role keyword and reach them on the contact they chose to publish.

**Agency prospecting.** Search a niche and a city, and get a prospect sheet with the account and the contact side by side.

**CRM enrichment.** Feed `profileUrl` and `phone` straight into your CRM; the `keyword` and `query` columns record where each row came from.

### Limitations, stated plainly

- Only contacts already published in public Hotfrog pages indexed by Google. Nothing hidden from a signed-out visitor is reachable, and none is guessed from a name.
- Hotfrog blocks most of its listing pages from search engines, so the Hotfrog Phone Number Scraper often returns nothing; the Brownbook, Cylex and Fyple Actors cover the same local-directory ground far better.
- Coverage depends on what Google has indexed, so a narrow niche returns fewer rows than a broad one. Raising **Max pages per query** and adding keywords helps.
- The free Apify plan caps a run at 20 results.
- A number written without its country code can only be validated against the country you searched, so search the countries you actually sell to.

### Pricing

Pay per result: you are charged for each row written to the dataset, and nothing for a run that finds nothing. Platform and proxy costs are included in that price.

### Hotfrog Phone Number Scraper vs manual research

Done by hand, one qualified contact takes two to four minutes: find the account, open it, read
the page, copy the phone number, paste it into a sheet.

The Hotfrog Phone Number Scraper does the same work continuously, with no tab switching and no
transcription errors. A hundred records is minutes rather than an afternoon.

It also captures what manual research usually skips. The account name, the profile URL and the
exact keyword that surfaced the row all land in the same record.

That context turns a raw list into a prioritised one. The Hotfrog Phone Number Scraper lets you
sort and filter before a single message is written.

### Using the Hotfrog Phone Number Scraper in a workflow

Most teams run the Hotfrog Phone Number Scraper on a schedule and treat the dataset as a feed
rather than a one-off export.

Point a webhook at your own endpoint and each finished run pushes its rows straight into your
CRM, with no manual download step.

The stable output schema matters here. Because every row from the Hotfrog Phone Number Scraper
has identical keys, your integration never needs to handle a missing field.

A common pattern is a nightly keyword run feeding a dedupe step. Another is enrichment: widen
the keyword list and let the Hotfrog Phone Number Scraper fill the gaps in an existing sheet.

#### Troubleshooting the Hotfrog Phone Number Scraper

**Few or no rows.** The keyword is probably too broad or too narrow. Ten specific keywords beat
one generic one, and adding a location raises the hit rate.

**Rows without contacts.** That is normal - most accounts publish none. The Hotfrog Phone
Number Scraper reports only what is genuinely on the page.

**The run is slow to start.** Lower the concurrency. The Hotfrog Phone Number Scraper is
querying faster than the proxy pool is comfortable with.

**Fewer results than requested.** Google caps one query at roughly 300 results. Query expansion
is what reaches past that ceiling, so leave it on.

#### How the Hotfrog Phone Number Scraper handles export and integration

Export the Hotfrog Phone Number Scraper dataset as CSV, JSON, Excel or XML from the Apify
console, or pull it through the API.

Every field is flat - no nested objects - so the CSV opens cleanly in Excel or Google Sheets
without a parsing step.

### Related Actors

| Actor | What it collects |
|---|---|
| [Hotfrog Email Scraper](https://apify.com/leads-scraper/hotfrog-email-scraper) | Public contact emails from Hotfrog |
| [Hotfrog Email and Phone Number Scraper](https://apify.com/neuro-scraper/hotfrog-email-and-phone-number-scraper) | Emails and phone numbers from Hotfrog |
| [Angi Email Scraper](https://apify.com/leads-scraper/angi-email-scraper) | Public contact emails from Angi |
| [Bark Email Scraper](https://apify.com/leads-scraper/bark-email-scraper) | Public contact emails from Bark |
| [Better Business Bureau Email Scraper](https://apify.com/leads-scraper/better-business-bureau-email-scraper) | Public contact emails from Better Business Bureau |
| [Bizapedia Email Scraper](https://apify.com/neuro-scraper/bizapedia-email-scraper) | Public contact emails from Bizapedia |
| [Brownbook Email Scraper](https://apify.com/neuro-scraper/brownbook-email-scraper) | Public contact emails from Brownbook |
| [Callupcontact Email Scraper](https://apify.com/neuro-scraper/callupcontact-email-scraper) | Public contact emails from CallUpContact |
| [Capterra Email Scraper](https://apify.com/leads-scraper/capterra-email-scraper) | Public contact emails from Capterra |
| [Clutch Email Scraper](https://apify.com/leads-scraper/clutch-email-scraper) | Public contact emails from Clutch |
| [Crunchbase Email Scraper](https://apify.com/leads-scraper/crunchbase-email-scraper) | Public contact emails from Crunchbase |
| [Cybo Email Scraper](https://apify.com/neuro-scraper/cybo-email-scraper) | Public contact emails from Cybo |
| [Cylex Email Scraper](https://apify.com/neuro-scraper/cylex-email-scraper) | Public contact emails from Cylex |
| [EC21 Email Scraper](https://apify.com/neuro-scraper/ec21-email-scraper) | Public contact emails from EC21 |
| [Europages Email Scraper](https://apify.com/leads-scraper/europages-email-scraper) | Public contact emails from Europages |
| [ExportHub Email Scraper](https://apify.com/neuro-scraper/exporthub-email-scraper) | Public contact emails from ExportHub |
| [FindUsLocal Email Scraper](https://apify.com/neuro-scraper/finduslocal-email-scraper) | Public contact emails from FindUsLocal |
| [Foursquare Email Scraper](https://apify.com/neuro-scraper/foursquare-email-scraper) | Public contact emails from Foursquare |
| [Fyple Email Scraper](https://apify.com/neuro-scraper/fyple-email-scraper) | Public contact emails from Fyple |
| [G2 Email Scraper](https://apify.com/neuro-scraper/g2-email-scraper) | Public contact emails from G2 |
| [Houzz Email Scraper](https://apify.com/leads-scraper/houzz-email-scraper) | Public contact emails from Houzz |
| [Infobel Email Scraper](https://apify.com/neuro-scraper/infobel-email-scraper) | Public contact emails from Infobel |
| [Kompass Email Scraper](https://apify.com/leads-scraper/kompass-email-scraper) | Public contact emails from Kompass |
| [Lacartes Email Scraper](https://apify.com/neuro-scraper/lacartes-email-scraper) | Public contact emails from Lacartes |
| [Manta Email Scraper](https://apify.com/leads-scraper/manta-email-scraper) | Public contact emails from Manta |
| [MapQuest Email Scraper](https://apify.com/neuro-scraper/mapquest-email-scraper) | Public contact emails from MapQuest |
| [N49 Email Scraper](https://apify.com/neuro-scraper/n49-email-scraper) | Public contact emails from N49 |
| [Porch Email Scraper](https://apify.com/neuro-scraper/porch-email-scraper) | Public contact emails from Porch |
| [Scoot Email Scraper](https://apify.com/neuro-scraper/scoot-email-scraper) | Public contact emails from Scoot |
| [Thomasnet Email Scraper](https://apify.com/leads-scraper/thomasnet-email-scraper) | Public contact emails from Thomasnet |
| [Thumbtack Email Scraper](https://apify.com/leads-scraper/thumbtack-email-scraper) | Public contact emails from Thumbtack |
| [Touch Local Email Scraper](https://apify.com/leads-scraper/touch-local-email-scraper) | Public contact emails from Touch Local |
| [TradeIndia Email Scraper](https://apify.com/leads-scraper/tradeindia-email-scraper) | Public contact emails from TradeIndia |
| [Trustpilot Email Scraper](https://apify.com/leads-scraper/trustpilot-email-scraper) | Public contact emails from Trustpilot |
| [Tupalo Email Scraper](https://apify.com/leads-scraper/tupalo-email-scraper) | Public contact emails from Tupalo |
| [Yalwa Email Scraper](https://apify.com/leads-scraper/yalwa-email-scraper) | Public contact emails from Yalwa |
| [Yellow Pages Email Scraper](https://apify.com/leads-scraper/yellow-pages-email-scraper) | Public contact emails from Yellow Pages |
| [Angi Email and Phone Number Scraper](https://apify.com/neuro-scraper/angi-email-and-phone-number-scraper) | Emails and phone numbers from Angi |
| [Bark Email and Phone Number Scraper](https://apify.com/neuro-scraper/bark-email-and-phone-number-scraper) | Emails and phone numbers from Bark |
| [Better Business Bureau Email and Phone Number Scraper](https://apify.com/leads-scraper/better-business-bureau-email-and-phone-number-scraper) | Emails and phone numbers from Better Business Bureau |
| [Bizapedia Email and Phone Number Scraper](https://apify.com/neuro-scraper/bizapedia-email-and-phone-number-scraper) | Emails and phone numbers from Bizapedia |
| [Brownbook Email and Phone Number Scraper](https://apify.com/neuro-scraper/brownbook-email-and-phone-number-scraper) | Emails and phone numbers from Brownbook |

### FAQ

#### Does the Hotfrog Phone Number Scraper need a login or cookies?

No. It reads public search results and public Hotfrog pages only.

#### Where do the phone numbers come from?

From the public page the search result points at - the same text any visitor can read.

#### Are the numbers real?

Every number is checked against its country's numbering plan before it is written, so invalid strings are dropped rather than shipped.

#### Can I run it on a schedule?

Yes, with Apify Schedules. Progress is saved, so a migrated run continues instead of starting over.

**Something is missing or wrong.**\
Email <neurodata.apify@gmail.com>.

### More about the Hotfrog Phone Number Scraper

The Hotfrog Phone Number Scraper writes one dataset row per contact found, which keeps billing
proportional to the value returned rather than to the time a run spends searching.

Because the Hotfrog Phone Number Scraper reads only pages Google has already indexed, it never
needs a login, a cookie jar or an API key from the platform it reads.

Run the Hotfrog Phone Number Scraper with a narrow keyword set first. A short test run shows
the yield of a niche before a large run is paid for.

The Hotfrog Phone Number Scraper deduplicates within a run, so the same contact discovered
through two different queries is written once, not twice.

Output from the Hotfrog Phone Number Scraper is flat - no nested objects - so a CSV export
opens cleanly in Excel or Google Sheets with no parsing step.

Pair the Hotfrog Phone Number Scraper with Apify Schedules to rebuild a prospect list weekly
and catch accounts that published contact details since the last run.

The Hotfrog Phone Number Scraper reports honestly when a niche is empty. A run that finds
nothing writes nothing, and nothing is charged for it.

Proxy and platform costs are already inside the per-result price of the Hotfrog Phone Number
Scraper, so the figure quoted on the Store page is the figure you pay.

#### Hotfrog Phone Number Scraper at a glance

Every field the Hotfrog Phone Number Scraper returns is documented in the output table above,
and the schema does not change between runs or between platforms.

Teams that outgrow manual prospecting usually reach for the Hotfrog Phone Number Scraper first,
because it needs no setup beyond a keyword list and a result cap.

The Hotfrog Phone Number Scraper records the source query alongside every row, which makes a
list auditable when a prospect asks where their details came from.

Concurrency on the Hotfrog Phone Number Scraper is adjustable, so a run can be tuned for speed
on a quiet network or for reliability on a busy one.

If a run of the Hotfrog Phone Number Scraper is interrupted, Apify migrates it and progress
resumes rather than restarting from the first query.

Agencies commonly schedule the Hotfrog Phone Number Scraper weekly, then diff each dataset
against the last to surface only newly published contacts.

The Hotfrog Phone Number Scraper applies the same validation to every record, so the quality of
a row does not depend on which query happened to find it.

Nothing in the Hotfrog Phone Number Scraper guesses a contact from a name pattern. A value is
written only when it appears on the page itself.

Because the Hotfrog Phone Number Scraper shares its output schema with every other scraper in
this catalogue, a pipeline built once works across all of them.

### Leave a review

If the Hotfrog Phone Number Scraper saved you time, please leave a star rating and a short
review on the Hotfrog Phone Number Scraper page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to
build next.

If something did not work, email <neurodata.apify@gmail.com>
instead - bugs get fixed faster than they get complained about.

### Support

Questions, bugs or a custom build: <neurodata.apify@gmail.com>.

# Actor input Schema

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

Search terms describing the Hotfrog accounts you want (niche, job title, industry).

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

Optional location phrase added to every query (e.g. "New York").

## `countries` (type: `array`):

Which countries' phone numbers to look for. The search asks Google for that country's dial code, and every number found is validated against that country's real numbering plan. Country name, ISO code or dial code all work. Each extra country multiplies the number of searches.

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

Stop once this many unique contacts have been collected.

## `countryCode` (type: `string`):

Two-letter country code for the search proxy (e.g. US, GB, DE). Empty for any.

## `expandQueries` (type: `boolean`):

Search each keyword x domain pair with several phrasings. Recommended - Google caps a single query at ~300 results.

## `queryModifiers` (type: `array`):

Extra words combined with each keyword when Expand queries is on. Tuned for Hotfrog.

## `maxPagesPerQuery` (type: `integer`):

Google rarely returns more than ~30 pages for one query.

## `maxConcurrency` (type: `integer`):

How many queries run in parallel.

## Actor input object example

```json
{
  "keywords": [
    "small business",
    "services"
  ],
  "location": "",
  "countries": [
    "United States",
    "United Kingdom",
    "India"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "enquiries",
    "owner",
    "get a quote"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Records produced by Hotfrog Phone Number Scraper, 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": [
        "small business",
        "services"
    ],
    "location": "",
    "countries": [
        "United States",
        "United Kingdom",
        "India"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "enquiries",
        "owner",
        "get a quote"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("neuro-scraper/hotfrog-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": [
        "small business",
        "services",
    ],
    "location": "",
    "countries": [
        "United States",
        "United Kingdom",
        "India",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "enquiries",
        "owner",
        "get a quote",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("neuro-scraper/hotfrog-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": [
    "small business",
    "services"
  ],
  "location": "",
  "countries": [
    "United States",
    "United Kingdom",
    "India"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "enquiries",
    "owner",
    "get a quote"
  ]
}' |
apify call neuro-scraper/hotfrog-phone-number-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,neuro-scraper/hotfrog-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/UqqKxGvBLPPCSdsAb/builds/8GdJuu0ye8BMM3ueJ/openapi.json