# Domain Prospect Profile – Tech, Traffic & Contacts (`publicrows/domain-prospect-profile`) Actor

One row per domain from your list: technology stack, estimated search traffic, domain rank, backlinks, registration age and the role e-mails, phones and social profiles the site publishes. Four licensed DataForSEO sources joined, nothing scraped. $30 per 1,000 domains, $10 without technology.

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

## Pricing

from $7.00 / 1,000 domain profiled (without technology)s

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

## Domain Prospect Profile – Tech, Traffic & Contacts

One row per domain from your list: technology stack, estimated search traffic, domain rank, backlinks, registration age and the role e-mails, phones and social profiles the site publishes. Four licensed DataForSEO sources joined, nothing scraped. $30 per 1,000 domains, $10 without technology.

### Who this is for

Agencies and sales teams qualifying a prospect list, SEO teams sizing a set of competitors, and AI agents that need one trustworthy profile of a company's website: paste the domains, get one row each with the stack it runs, the traffic it earns, the authority it has, how long it has existed and how to reach the business.

### Sample output

```json
{
  "domain": "apify.com",
  "domain_rank": 577,
  "location_code": 2840,
  "language_code": "en",
  "row_key": "apify.com|2840",
  "source_url": "https://dataforseo.com/apis/domain-analytics-api",
  "search_traffic_est": 59673.63,
  "organic_traffic_est": 59673.626341230454,
  "organic_keywords": 34368,
  "paid_traffic_est": 0,
  "paid_keywords": 0,
  "domain_created": "2009-06-02T17:14:10.000Z",
  "domain_expires": "2035-06-02T17:14:10.000Z",
  "registrar": "Amazon Registrar, Inc.",
  "tld": "com",
  "backlinks": 1420667,
  "referring_domains": 10872,
  "referring_main_domains": 8402,
  "dofollow_backlinks": 398006,
  "backlinks_updated": "2026-09-05T11:21:34.000Z",
  "site_country": "US",
  "site_language": "en",
  "ecommerce_platforms": null,
  "cms": null,
  "analytics_tools": "[\"Leadfeeder\",\"Linkedin Insight Tag\"]",
  "tag_managers": null,
  "crm_tools": "[]",
  "marketing_automation": "[]",
  "live_chat": "[]",
  "advertising_tools": null,
  "cdn": "[\"Amazon CloudFront\",\"Amazon S3\"]",
  "javascript_frameworks": "[\"Next.js\",\"React\"]",
  "technology_stack": "{\"content\":{\"search_engines\":[\"Algolia\"]},\"servers\":{\"cdn\":[\"Amazon CloudFront\",\"Amazon S3\"],\"web_servers\":[\"Next.js\"],\"paas\":[\"Amazon Web Services\"]},\"other\":{\"miscellaneous\":[\"HTTP/3\"]},\"analytics\":{\"analytics\":[\"Leadfeeder\",\"Linkedin Insight Tag\"]},\"web_development\":{\"javascript_frameworks\":[\"Next.js\",\"React\"],\"web_frameworks\":[\"Next.js\"],\"static_site_generator\":[\"Next.js\"]}}",
  "site_emails": "[\"support@apify.com\"]",
  "site_phones": null,
  "social_urls": "[\"https://twitter.com/apify\",\"https://www.linkedin.com/company/apify\",\"https://www.youtube.com/apify\"]",
  "site_last_visited": "2026-11-16T22:49:15.000Z"
}
```

### What you get

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

| Field | Type |
| --- | --- |
| `domain` | string, always present |
| `domain_rank` | number |
| `location_code` | number, always present |
| `language_code` | string, always present |
| `row_key` | string, always present |
| `source_url` | string |
| `search_traffic_est` | number (joined from a companion supplier request; null if that request fails) |
| `organic_traffic_est` | number (joined from a companion supplier request; null if that request fails) |
| `organic_keywords` | number (joined from a companion supplier request; null if that request fails) |
| `paid_traffic_est` | number (joined from a companion supplier request; null if that request fails) |
| `paid_keywords` | number (joined from a companion supplier request; null if that request fails) |
| `domain_created` | datetime (joined from a companion supplier request; null if that request fails) |
| `domain_expires` | datetime (joined from a companion supplier request; null if that request fails) |
| `registrar` | string (joined from a companion supplier request; null if that request fails) |
| `tld` | string (joined from a companion supplier request; null if that request fails) |
| `backlinks` | number (joined from a companion supplier request; null if that request fails) |
| `referring_domains` | number (joined from a companion supplier request; null if that request fails) |
| `referring_main_domains` | number (joined from a companion supplier request; null if that request fails) |
| `dofollow_backlinks` | number (joined from a companion supplier request; null if that request fails) |
| `backlinks_updated` | datetime (joined from a companion supplier request; null if that request fails) |
| `site_country` | string (joined from a companion supplier request; null if that request fails) |
| `site_language` | string (joined from a companion supplier request; null if that request fails) |
| `ecommerce_platforms` | string (joined from a companion supplier request; null if that request fails) |
| `cms` | string (joined from a companion supplier request; null if that request fails) |
| `analytics_tools` | string (joined from a companion supplier request; null if that request fails) |
| `tag_managers` | string (joined from a companion supplier request; null if that request fails) |
| `crm_tools` | string (joined from a companion supplier request; null if that request fails) |
| `marketing_automation` | string (joined from a companion supplier request; null if that request fails) |
| `live_chat` | string (joined from a companion supplier request; null if that request fails) |
| `advertising_tools` | string (joined from a companion supplier request; null if that request fails) |
| `cdn` | string (joined from a companion supplier request; null if that request fails) |
| `javascript_frameworks` | string (joined from a companion supplier request; null if that request fails) |
| `technology_stack` | string (joined from a companion supplier request; null if that request fails) |
| `site_emails` | string (joined from a companion supplier request; null if that request fails) |
| `site_phones` | string (joined from a companion supplier request; null if that request fails) |
| `social_urls` | string (joined from a companion supplier request; null if that request fails) |
| `site_last_visited` | datetime (joined from a companion supplier request; null if that request fails) |

Each row joins four licensed DataForSEO sources: domain rank from the Backlinks API, search traffic estimates from DataForSEO Labs for the chosen country, registration dates, registrar and backlink counts from the WHOIS database, and, with `includeTechnology` on, the technology stack and published contact details from the Domain Analytics Technologies API. Nothing is scraped by the actor.

Traffic figures are estimates of monthly visits from Google search (`search_traffic_est` sums organic, paid, featured-snippet and local-pack traffic), not total site visits. WHOIS fields are empty for domains the WHOIS database has not indexed (young or very small sites); technology fields are empty when the supplier has not crawled the site.

`site_emails` keeps role addresses only (info@, sales@, support@ and similar); personal mailboxes found on a site are dropped before the row is written. `site_phones` and `social_urls` are what the site itself publishes.

Enter domains without https:// or www: the WHOIS and technology sources index the registered domain, and a www. prefix would miss their rows.

### Pricing

Pay per domain: $0.03 each with details ($30.00 per 1,000), or $0.01 each ($10.00 per 1,000) with `includeTechnology` off. The first 10 rows of every run are free; a 20-domain test therefore costs $0.35.

### 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 Backlinks, DataForSEO Labs, WHOIS and Domain Analytics APIs, 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:// or www (example.com). Up to 1,000 domains travel in one batch; the traffic, authority and age lookups are three requests per batch.
- `location`: Country whose Google results the traffic estimates are based on.
- `language`: Language of the searches behind the traffic estimates.
- `includeTechnology`: Look up each domain's technology stack and the role e-mails, phone numbers and social profiles published on the site (one supplier request per domain, slower, and the row is charged at the technology price). Off = rank, traffic, backlinks and domain age only, at the base price.
- `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. 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:// or www (example.com). Up to 1,000 domains travel in one batch; the traffic, authority and age lookups are three requests per batch.

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

Country whose Google results the traffic estimates are based on.

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

Language of the searches behind the traffic estimates.

## `includeTechnology` (type: `boolean`):

Look up each domain's technology stack and the role e-mails, phone numbers and social profiles published on the site (one supplier request per domain, slower, and the row is charged at the technology price). Off = rank, traffic, backlinks and domain age only, at the base price.

## `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. 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\nshopify.com\nwikipedia.org\ngithub.com",
  "location": "2840",
  "language": "en",
  "includeTechnology": true,
  "sandbox": false,
  "maxItems": 1000
}
```

# Actor output Schema

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

Dataset items, one per domain (domain, domain_rank, location_code, language_code, row_key, source_url, search_traffic_est, organic_traffic_est, organic_keywords, paid_traffic_est, paid_keywords, domain_created, domain_expires, registrar, tld, backlinks, referring_domains, referring_main_domains, dofollow_backlinks, backlinks_updated, site_country, site_language, ecommerce_platforms, cms, analytics_tools, tag_managers, crm_tools, marketing_automation, live_chat, advertising_tools, cdn, javascript_frameworks, technology_stack, site_emails, site_phones, social_urls, site_last_visited). 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
shopify.com
wikipedia.org
github.com`,
    "location": "2840",
    "language": "en",
    "maxItems": 1000
};

// Run the Actor and wait for it to finish
const run = await client.actor("publicrows/domain-prospect-profile").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
shopify.com
wikipedia.org
github.com""",
    "location": "2840",
    "language": "en",
    "maxItems": 1000,
}

# Run the Actor and wait for it to finish
run = client.actor("publicrows/domain-prospect-profile").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\\nshopify.com\\nwikipedia.org\\ngithub.com",
  "location": "2840",
  "language": "en",
  "maxItems": 1000
}' |
apify call publicrows/domain-prospect-profile --silent --output-dataset

```

## MCP server setup

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

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/wHMFnWbfRkZbJR3PD/builds/534pCZzFSvsVC4lWV/openapi.json
