# Similarweb Scraper — AI Traffic, $0.80/1K (`meka.im/similarweb-scraper`) Actor

Get Similarweb traffic, rankings, keywords, countries, channels, and AI referral insights for $0.80 per 1,000 domains. Compatible with the leading Actor's 19 core fields, with additional AI data. No API key; no charge for domains without data.

- **URL**: https://apify.com/meka.im/similarweb-scraper.md
- **Developed by:** [Meka.im](https://apify.com/meka.im) (community)
- **Categories:** Marketing, Business, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.80 / 1,000 delivered domains

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

Similarweb traffic and AI referral intelligence for **$0.80 per 1,000 domains with data**.

- **19 core fields validated 100%** against a leading Similarweb Actor on 105 domains
- Additional AI referral totals, assistant shares, trends, and prompt insights
- No charge for invalid, failed, duplicate, or no-data domains
- No Similarweb API key required

Paste a list of domains. Get monthly visits, global and country rankings, engagement, the traffic-source split, top countries, top keywords, and which AI assistants are sending visitors, as a flat table you can export to CSV, Excel, JSON or a warehouse.

### Quick start

1. Put your domains in the **Domains** field.
2. Click **Start**.
3. Export the Dataset, or read it with the API calls below.

```json
{
  "domains": ["stripe.com", "nytimes.com", "openai.com"],
  "maxDomains": 1000
}
```

### Input

| Field | Type | Default | Notes |
|---|---|---|---|
| `domains` | array of strings | required | Hosts, bare or as full URLs. Scheme, path, query, port, credentials, trailing dot and case are all cleaned |
| `maxDomains` | integer | 1000 | Upper bound on unique domains in one run, 1 to 5000 |
| `maxConcurrency` | integer | 2 | How many batches of 16 run in parallel, 1 to 10. The upstream rate limit is the real ceiling, so raising this mostly adds waiting |

Valid, unique domains preserve their first-input order. Duplicate domains are processed once, and invalid inputs are skipped without charge.

Internationalized domains are used exactly as you type them. The source keeps separate records for a Unicode spelling and its ASCII form, and in a check on 2026-09-19 only the Unicode spelling carried a rank and real traffic. Submitting both spellings gives you two rows, because upstream they are two different records.

Every row carries `inputDomain` (what you typed) and `normalizedDomain` (what was queried).

### Output

One row per domain. Several numeric fields in the core set are strings; that is the shape existing pipelines already parse, so it is preserved rather than cleaned up.

#### Core fields

| Field | Type | Notes |
|---|---|---|
| `domain` | string | The queried host |
| `title` | string | `""` when the source has none |
| `description` | string | `""` when the source has none |
| `category` | string | Two-level, e.g. `finance/banking_credit_and_lending`. `""` when absent |
| `globalRank` | number or null | `null` for sites without one, including many subdomains and link shorteners |
| `countryRank` | object | `{ Country, CountryCode, Rank }`, each null when absent |
| `categoryRank` | string or null | |
| `visits` | string | Visits in the snapshot month. `"0"` is a real zero |
| `bounceRate` | string | 0 to 1 |
| `pagesPerVisit` | string | |
| `timeOnSite` | string | Seconds |
| `estimatedMonthlyVisits` | object | `{ "YYYY-MM-01": visits }`, three months |
| `trafficSources` | object | `SocialOrganic`, `SocialPaid`, `Mail`, `Referrals`, `SearchOrganic`, `SearchPaid`, `Direct`, `GenAi`, `Affiliate`, `DisplayAds`, each 0 to 1. A source the upstream did not report is `null`, not `0` |
| `topCountryShares` | array | `{ Country, CountryCode, Value }` |
| `topKeywords` | array | `{ name, esitmatedValue, cpc }`. The misspelled key comes from the source and is preserved so existing consumers keep working |
| `competitors` | array | Empty, see Limits |
| `isDataFromGA` | boolean | The site owner publishes its own analytics |
| `screenshot` | string | Source-hosted preview image |
| `snapshotDate` | string | The month the data describes |

#### Additional fields

| Field | Type | Notes |
|---|---|---|
| `inputDomain` | string | What you typed |
| `normalizedDomain` | string | What was queried after cleanup |
| `dataAvailable` | boolean | Whether the source has measurable traffic. `false` rows are written so your list stays aligned and are never charged |
| `keywordVolumes` | array | `{ name, volume }`, aligned with `topKeywords` |
| `aiTraffic` | object | See below |

`aiTraffic` carries `available`, `totalVisits`, `share` (0 to 1), `distributionBoundary`, `sources` and `prompts`. Each entry in `sources` is one AI assistant with `source`, `rank`, `share` and `monthlyHistory` (three months of `{ date, share }`). Unknown numbers are `null`, never `0`; a confirmed absence of entries is an empty array.

`aiTraffic.available` and `dataAvailable` are different states. A site can have plenty of traffic and no AI referrals at all.

Example row, trimmed:

```json
{
  "domain": "stripe.com",
  "title": "Link by Stripe: One-click payments",
  "globalRank": 312,
  "countryRank": { "Country": 840, "CountryCode": "US", "Rank": 226 },
  "visits": "133172721",
  "bounceRate": "0.5545453726745924",
  "estimatedMonthlyVisits": { "2026-06-01": 120792625, "2026-07-01": 129949921, "2026-08-01": 133172721 },
  "trafficSources": { "Direct": 0.4318, "SearchOrganic": 0.0596, "Referrals": 0.3898 },
  "topKeywords": [{ "name": "stripe", "esitmatedValue": 3087760, "cpc": 2.36 }],
  "competitors": [],
  "snapshotDate": "2026-08-01T00:00:00+00:00",

  "inputDomain": "stripe.com",
  "normalizedDomain": "stripe.com",
  "dataAvailable": true,
  "keywordVolumes": [{ "name": "stripe", "volume": 6120000 }],
  "aiTraffic": {
    "available": true,
    "totalVisits": 1607549,
    "share": 0.0136,
    "distributionBoundary": "<100M",
    "sources": [
      { "source": "grok.com", "rank": 1, "share": 0.4607,
        "monthlyHistory": [{ "date": "2026-08-01", "share": 0.4607 }] }
    ],
    "prompts": ["What are the steps to integrate a modern online payments platform…"]
  }
}
```

### Pricing

$0.80 per 1,000 delivered domains that carry data.

- A domain with no measurable traffic is written to the Dataset so your list stays aligned with your input, and it is not charged.
- Invalid entries, failed lookups and duplicate inputs are not charged.
- A resumed run does not refetch or recharge a domain already in the Dataset.

The run summary records `charged` alongside `delivered`, so you can reconcile the bill against the Dataset.

### Limits

Stated here rather than discovered later.

This Actor returns the traffic and AI insights available in the current public website snapshot. It does not provide every dataset available in Similarweb's paid platform.

Included: global, country and category rankings; monthly visits and three months of history; bounce rate, pages per visit and time on site; traffic share by country; the channel split; top keywords with estimated value and volume; AI referral totals, per-assistant shares with monthly history, and prompt text where the source exposes it; title, description and category.

Not included:

- **Similar sites and competitors.** `competitors` is an empty array; the public source does not return it.
- **Full keyword database**, incoming and outgoing referral lists, named social sources, ad networks and publishers.
- **Demographics**, audience interests and audience overlap.
- **Subdomain, folder and page-level traffic.**
- **Arbitrary country, device, channel or date-range queries.** Every row is the current monthly snapshot; `snapshotDate` says which month.
- **Long-term history.** `estimatedMonthlyVisits` holds three points.
- **App intelligence** and company or industry databases.

Two behaviours worth knowing: small sites, most subdomains and link shorteners often have `null` ranks even with hundreds of millions of visits; and a subdomain returns its own numbers, not the parent domain's.

### Compatibility

Designed as a compatible superset of the leading Similarweb traffic Actor's core dataset. The 19 core fields keep their original names, types and null rules, verified field by field against a live run of that Actor on 105 domains. Everything else is additive and sits alongside them, so an existing pipeline keeps working without changes.

### API and automation

Read the Dataset directly:

```bash
curl "https://api.apify.com/v2/datasets/DATASET_ID/items?format=csv&clean=true" \
  -H "Authorization: Bearer APIFY_TOKEN"
```

Start a run and wait for its Dataset in one call:

```bash
curl -X POST "https://api.apify.com/v2/acts/ACTOR_ID/run-sync-get-dataset-items" \
  -H "Authorization: Bearer APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"domains":["stripe.com","nytimes.com"]}'
```

Each run also writes an `OUTPUT` record to the key-value store with how many domains were requested, unique, skipped, duplicated, delivered, charged, delivered without data, and failed.

Schedules and webhooks work as with any Actor. Runs are independent, so a monthly schedule matches how often the underlying numbers change.

### FAQ

**Why is `visits` a string but `globalRank` a number?** Because that is the shape the reference Dataset publishes, and changing it would break consumers that already parse these columns. The types are pinned by tests.

**A domain returned a row with zeroes. Was I charged?** No. `dataAvailable` is `false` on that row, which means the source has no measurable traffic for that site. It is written so your list stays aligned and it is not charged.

**Why did I get fewer rows than domains I submitted?** Duplicates collapse to one row, and entries that cannot be a domain are skipped. The run summary reports `uniqueDomains`, `duplicateInputs`, `skippedInvalid` and `failed`.

**A site has traffic but `aiTraffic.available` is false.** That is a real answer: no AI assistant referrals were recorded for it. It is unrelated to `dataAvailable`.

**Why is the data a month old?** The source publishes monthly. `snapshotDate` tells you exactly which month each row describes.

**Can I get competitors or similar sites?** Not from this Actor. See Limits.

**My run stopped early.** If `stoppedOnBudget` is true in the run summary, the run hit the maximum charge you allowed. Raise the limit and start it again — already delivered domains are not refetched or recharged.

### Legal

This Actor is independently developed and is not affiliated with, endorsed by, or sponsored by Similarweb.

It reads a public endpoint. It does not sign in, does not use cookies or credentials, and does not reach anything behind a login. You are responsible for how you use the data, including any applicable terms and data-protection rules.

# Actor input Schema

## `domains` (type: `array`):

Websites to analyse. Accepts example.com, www.example.com or https://example.com/path — the host is extracted for you. Entries that cannot be a domain are skipped and never charged.

## `maxDomains` (type: `integer`):

Upper bound on unique domains processed in one run. Duplicates collapse to a single lookup and a single result.

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

How many batches of 16 domains run in parallel. The upstream rate limit is the real ceiling, so raising this mostly adds waiting.

## Actor input object example

```json
{
  "domains": [
    "stripe.com",
    "nytimes.com"
  ],
  "maxDomains": 1000,
  "maxConcurrency": 2
}
```

# Actor output Schema

## `websites` (type: `string`):

No description

## `runSummary` (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 = {
    "domains": [
        "stripe.com",
        "nytimes.com",
        "openai.com",
        "shopify.com",
        "coinbase.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("meka.im/similarweb-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 = { "domains": [
        "stripe.com",
        "nytimes.com",
        "openai.com",
        "shopify.com",
        "coinbase.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("meka.im/similarweb-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 '{
  "domains": [
    "stripe.com",
    "nytimes.com",
    "openai.com",
    "shopify.com",
    "coinbase.com"
  ]
}' |
apify call meka.im/similarweb-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,meka.im/similarweb-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/igmUwUudmDZMER1KN/builds/zKihQWpHfmXJxzYaO/openapi.json