# Website Traffic Estimates – 1,000 Domains Per Run (`publicrows/website-traffic-estimates`) Actor

Estimated monthly search traffic for a whole list of domains in one run: organic and paid visits, featured-snippet and local-pack traffic, and the ranking keywords behind each, for any country. Licensed DataForSEO Labs data, nothing scraped. $5 per 1,000 domains + $0.15 per batch, first 20 free.

- **URL**: https://apify.com/publicrows/website-traffic-estimates.md
- **Developed by:** [PublicRows](https://apify.com/publicrows) (community)
- **Categories:** SEO tools, Lead generation, Marketing
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.50 / 1,000 domain estimateds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
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

## Website Traffic Estimates – 1,000 Domains Per Run

Estimated monthly search traffic for a whole list of domains in one run: organic and paid visits, featured-snippet and local-pack traffic, and the ranking keywords behind each, for any country. Licensed DataForSEO Labs data, nothing scraped. $5 per 1,000 domains + $0.15 per batch, first 20 free.

### Who this is for

Agencies qualifying prospect lists by traffic, SEO teams sizing competitors and link targets, investors and analysts comparing sites in a sector, and AI agents that need a traffic number for a domain without scraping a traffic-estimate site.

### Sample output

```json
{
  "domain": "wikipedia.org",
  "search_traffic_est": 2020224284.74,
  "organic_traffic_est": 2015321651.9335833,
  "organic_keywords": 49311612,
  "paid_traffic_est": 0,
  "paid_keywords": 0,
  "featured_snippet_traffic_est": 4894928.284481406,
  "featured_snippet_keywords": 9557,
  "local_pack_traffic_est": 7704.519666314125,
  "local_pack_keywords": 484,
  "location_code": 2840,
  "language_code": "en",
  "row_key": "wikipedia.org|2840|en",
  "source_url": "https://dataforseo.com/apis/dataforseo-labs-api"
}
```

### What you get

One row per domain. Every row also carries `_source` (attribution) and the recipe version.

| Field | Type |
| --- | --- |
| `domain` | string, always present |
| `search_traffic_est` | number |
| `organic_traffic_est` | number |
| `organic_keywords` | number |
| `paid_traffic_est` | number |
| `paid_keywords` | number |
| `featured_snippet_traffic_est` | number |
| `featured_snippet_keywords` | number |
| `local_pack_traffic_est` | number |
| `local_pack_keywords` | number |
| `location_code` | number, always present |
| `language_code` | string, always present |
| `row_key` | string, always present |
| `source_url` | string |

Estimates come from DataForSEO Labs under its licence: for each domain, the keywords it ranks for in the chosen country are multiplied by position-based click-through rates, so `organic_traffic_est` is estimated monthly visits from Google organic search, `paid_traffic_est` from Google Ads, and `featured_snippet_traffic_est` and `local_pack_traffic_est` from those features. `search_traffic_est` is their sum. This is search traffic, not total site visits: direct, social and referral visits are not included, so numbers run lower than SimilarWeb-style totals and are better for comparing sites than for sizing one.

`organic_keywords` and `paid_keywords` are the number of ranking keywords behind each estimate; a domain with no ranking keywords in that country comes back with zeros. Domains are deduplicated case-insensitively before sending, and `row_key` (domain, location, language) is unique per run.

Each request to the supplier carries up to 1,000 domains and is billed as one `lookup` ($0.15) on top of the per-domain price, so 1,000 domains cost $5.15 and 20 domains cost $0.15. Requests run one at a time, so 10,000 domains take about half a minute.

Bring your own DataForSEO credentials in the two optional inputs if you prefer the supplier charge on your own account; the row price here stays the same either way.

### Pricing

Pay per domain: $0.005 each ($5.00 per 1,000), plus $0.15 per lookup (one batch of up to 1,000 domains). The first 20 rows of every run are free; a 20-domain test therefore costs $0.15.

### How to run

1. Keep the defaults for the standard sample, or set the inputs (listed last, below).
2. Run. Results land in the dataset as JSON, CSV or Excel.
3. From code or an agent: call it through the API, or as an MCP tool via mcp.apify.com.

### Source and fair use

Data: DataForSEO Labs bulk traffic estimation, licensed. The data is bought from the supplier under its API terms on every run; nothing is scraped from any website. Rows are facts about domains, and no personal data of individuals is included.

### FAQ

**How fresh is the data?** Each run fetches live from the source.
**Can I get more fields?** Open an issue naming the field and where it appears at the source.
**Something broke?** Open an issue. Issues are answered within 12 hours.
**Found it useful?** A short review on this page helps other people find it, and tells us what to improve.

### Inputs

- `domains`: One domain per line (commas also work), without https:// (example.com; a subdomain or a full page URL also works). 1,000 domains travel in one request.
- `location`: Country whose Google results the estimates are based on.
- `language`: Language of the searches behind the estimates.
- `sandbox`: Use the supplier's test environment: same row structure, dummy numbers, no supplier charge. For wiring tests only.
- `dfsLogin`: Optional: your own DataForSEO API login (the account e-mail). Leave empty to use ours.
- `dfsPassword`: Optional: your own DataForSEO API password. Leave empty to use ours.
- `maxItems`: Stop after this many rows.

# Actor input Schema

## `domains` (type: `string`):

One domain per line (commas also work), without https:// (example.com; a subdomain or a full page URL also works). 1,000 domains travel in one request.

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

Country whose Google results the estimates are based on.

## `language` (type: `string`):

Language of the searches behind the estimates.

## `sandbox` (type: `boolean`):

Use the supplier's test environment: same row structure, dummy numbers, no supplier charge. For wiring tests only.

## `dfsLogin` (type: `string`):

Optional: your own DataForSEO API login (the account e-mail). Leave empty to use ours.

## `dfsPassword` (type: `string`):

Optional: your own DataForSEO API password. Leave empty to use ours.

## `maxItems` (type: `integer`):

Stop after this many rows.

## Actor input object example

```json
{
  "domains": "apify.com\npublicrows.com\nwikipedia.org\ngithub.com",
  "location": "2840",
  "language": "en",
  "sandbox": false,
  "maxItems": 10000
}
```

# Actor output Schema

## `rows` (type: `string`):

Dataset items, one per domain (domain, search_traffic_est, organic_traffic_est, organic_keywords, paid_traffic_est, paid_keywords, featured_snippet_traffic_est, featured_snippet_keywords, local_pack_traffic_est, local_pack_keywords, location_code, language_code, row_key, source_url). Append ?format=csv or ?format=xlsx for other formats.

## `runSummary` (type: `string`):

Pages fetched, response classes, cost estimate and the quality-gate checks for this run.

# 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 = {
    "domains": `apify.com
publicrows.com
wikipedia.org
github.com`,
    "location": "2840",
    "language": "en",
    "maxItems": 10000
};

// Run the Actor and wait for it to finish
const run = await client.actor("publicrows/website-traffic-estimates").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 = {
    "domains": """apify.com
publicrows.com
wikipedia.org
github.com""",
    "location": "2840",
    "language": "en",
    "maxItems": 10000,
}

# Run the Actor and wait for it to finish
run = client.actor("publicrows/website-traffic-estimates").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 '{
  "domains": "apify.com\\npublicrows.com\\nwikipedia.org\\ngithub.com",
  "location": "2840",
  "language": "en",
  "maxItems": 10000
}' |
apify call publicrows/website-traffic-estimates --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,publicrows/website-traffic-estimates"
        }
    }
}
```

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/OpaJLuYYZTYlyl72n/builds/APloupsmgJUNPQ6NB/openapi.json
