# Similarweb (`canadesk/similarweb`) Actor

SimilarWeb analytics for any website (public data). It's fast and costs little!

- **URL**: https://apify.com/canadesk/similarweb.md
- **Developed by:** [Canadesk Support](https://apify.com/canadesk) (community)
- **Categories:** Lead generation, SEO tools, Social media
- **Features:** Full permissions
- **Stats:** 236 total users, 23 monthly users, 100.0% runs succeeded, 8 bookmarks
- **User rating**: 4.25 out of 5 stars

## Pricing

from $0.79 / 1,000 individual websites

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

Returns SimilarWeb analytics for any website (public data), in bulk.

### How it works

1. Enter the websites to be analyzed (e.g., `apify.com`), one per line.
2. Run it! 🎉

### What changed in 2.0

- The 10-website limit per run is gone. A run now accepts up to 10,000 websites.
- Websites are looked up in parallel instead of one by one, with no pause
  between them by default, so large lists finish much faster.
- Temporary failures are retried automatically.
- Each row now also carries `rowType` and `inputIndex`. All existing fields are
  unchanged.
- An empty input no longer looks up a default website; it simply does nothing.

If a saved task or integration sets `waiting` (the old default was 2000 ms), it
still applies before every lookup. Set it to 0 for full speed.

### Input

| Field | Default | Description |
| --- | --- | --- |
| `startUrls` | — | Website domains to look up. Maximum 10,000 per run. |
| `concurrency` | `4` | How many websites are looked up at once (1–8). |
| `waiting` | `0` | Optional pause before each lookup, in milliseconds. Leave at 0 for full speed; raise it only if your proxy gets blocked. |
| `proxy` | — | Proxy configuration. Apify Proxy (residential recommended) or your own `proxyUrls`. |

### Output

Every submitted website produces exactly one row, whether the lookup succeeds or
fails. Rows carry `inputIndex`, so you can line results back up with your input
even though they complete out of order.

A successful row:

```json
{
  "target": "spotify.com",
  "analytics": {
    "siteName": "spotify.com",
    "title": "Spotify - Web Player: Music for everyone",
    "description": "Spotify is a digital music service that gives you access to millions of songs.",
    "category": "arts_and_entertainment/music",
    "estimatedMonthlyVisits": { "2025-04-01": 495724819, "2025-05-01": 511881015, "2025-06-01": 493326349 },
    "trafficSources": { "Direct": 0.7068281326165025, "Search": 0.24645796816078602, "...": "..." },
    "monthlyVisitsTable": { "headers": ["Date", "..."], "visits": ["Visits", "..."] },
    "trafficSourcesTable": { "headers": ["Source", "..."], "values": ["Percentage", "..."] },
    "totalMonthlyVisits": 1500932183,
    "rawResponse": { "...": "the complete upstream payload" }
  },
  "success": true,
  "timestamp": "2026-09-11T12:00:00.000Z",
  "rowType": "domain",
  "inputIndex": 0
}
```

A failed or no-data row keeps the same shape with `analytics: null`,
`success: false` and an `error` message. Failures are real outcomes (the lookup
was performed), so they count like any other outcome.

#### Placeholder rows

A bulk run (50 or more submitted entries) includes a minimum of 1,000 outcome
units. When such a run finishes with fewer than 1,000 rows, the remainder is
filled with marked placeholders so the finalized dataset reflects the
minimum.

### Limits and behaviour

- **HTTP 403 errors**: proxy selection alone cannot fix an outdated request
  protocol. Use a build containing the November 2026 extension-context repair.
  Residential routing was verified with that repair; direct access may still
  be rejected. Check the dataset's `error` field and the success/failure counts
  before treating a completed run as successful data retrieval.

- **Retries**: temporary failures (timeouts, 5xx, 429, 403 and proxy gateway
  errors 590–599) are retried at most twice, with backoff, honouring
  `Retry-After`. Each retry goes out through a fresh proxy connection. Permanent
  answers such as "no data" are not retried.

- **Blocking**: if the upstream blocks persistently, the run slows down and then
  stops scheduling instead of spending on repeated failures. Entries that were
  never attempted get no dataset row and are not charged; their count and input
  positions are in the run log and in the `RUN_SUMMARY` record.

- **Interruption**: if a run is stopped, every row already written stays in the
  dataset. A bulk run's minimum is charged up front, and final placeholder padding
  does not happen on a forced stop, so a stopped bulk run can end with fewer than
  1,000 rows.

- **Resuming**: if a run migrates, it continues where it left off without
  looking anything up twice. If a stopped or crashed run is resurrected, it also
  continues, but lookups from roughly its last minute may be repeated and appear
  twice in the dataset. Repeated lookups are never
  charged twice.

### Support

Use a high-quality or custom proxy. Residential proxies give the best success
rate; lower `concurrency` or raise `waiting` if you see blocking.

Open a new issue for bugs. Please share your Run URL.

Cheers!

# Actor input Schema

## `startUrls` (type: `array`):

The websites you want analytics for, one per line (for example apify.com). Up to 10,000 entries per run. A run with more entries is rejected rather than silently truncated.

## `concurrency` (type: `integer`):

How many websites are looked up at the same time. Lower this if you see blocking; raise it for faster bulk runs.

## `waiting` (type: `integer`):

Optional pause before each lookup. Leave at 0 for full speed. Increase it only if your proxy is being blocked.

## `proxy` (type: `object`):

Proxies used for the lookups. Residential proxies give the best success rate. Custom proxy URLs are supported.

## Actor input object example

```json
{
  "startUrls": [
    "apify.com",
    "expensify.com"
  ],
  "concurrency": 4,
  "waiting": 0,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# 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 = {
    "startUrls": [
        "apify.com",
        "expensify.com"
    ],
    "proxy": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("canadesk/similarweb").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 = {
    "startUrls": [
        "apify.com",
        "expensify.com",
    ],
    "proxy": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("canadesk/similarweb").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 '{
  "startUrls": [
    "apify.com",
    "expensify.com"
  ],
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call canadesk/similarweb --silent --output-dataset

```

## MCP server setup

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

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/NRzGu7xR83tudau6J/builds/jXGxKDIl16vmvWvru/openapi.json