Similarweb Traffic Scraper

Get Similarweb website traffic estimates, rankings, engagement, acquisition channels, keywords, geography and AI-referral data for up to 200 domains per run. Similarweb Traffic Scraper helps you benchmark competitors and enrich research lists without a Similarweb login or API key.

Coverage varies by website. Each result includes a status, coverage information and warnings so missing estimates are not confused with zero traffic.

Quick start

1. Enter a small list of domains or website URLs.
2. Click Start and wait for the run to finish.
3. Open the dataset to review the results and export them.

{
  "domains": ["apify.com", "openai.com"],
  "includeRawData": false
}

Website URLs are normalized to domains, and duplicate domains are removed. A run accepts at most 200 unique valid domains. IP addresses are unsupported and skipped with a warning. If a list contains only unsupported inputs, the run finishes with no results and no result charges; the run-start fee can still apply. Mixed lists continue processing valid domains.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose an example to start with a small, preconfigured input.

• Compare SaaS website traffic and channels — Review traffic, engagement and channel estimates for three websites.
• Monitor AI referral traffic across leading AI sites — Inspect available AI-referral estimates for OpenAI, Perplexity and Anthropic.
• Analyze SEO keywords and website traffic by country — Explore keywords and country estimates for Semrush, Ahrefs and Similarweb.

What you get

• Traffic and engagement: latest visits, bounce rate, pages per visit and average visit duration.
• Rankings and history: global, country and category ranks, plus available monthly visit history.
• Acquisition channels: direct, referral, organic and paid search, social, email, affiliate, display-ad and generative-AI shares.
• Countries and keywords: leading countries, their traffic shares and estimated visits, plus available organic keyword metrics.
• AI referrals: estimated visits, chatbot mix, history and top prompts when the source provides them.
• Website context: title, description, category, previews, favicon, snapshot date and coverage warnings.

Who is it for?

• SEO teams comparing search traffic, keyword opportunities and geographic reach.
• Market researchers benchmarking websites using the same source of estimates.
• Sales teams adding website-traffic signals to domain lists.
• AI and content analysts reviewing available AI-referral estimates across websites.

Input settings

Setting	API key	Default / purpose
Domains	domains	Required. Up to 200 domains or URLs.
Include source payload	includeRawData	false. Add source data without the static country catalog.
Automatic residential fallback	autoResidentialFallback	true. Existing automatic connection recovery. See field help.
Proxy configuration	proxyConfiguration	Proxy disabled. An enabled explicit configuration takes precedence.
Maximum concurrency	maxConcurrency	5, from 1 to 20 requested; effective source concurrency is capped at 5 for bounded memory.
Maximum retries	maxRetries	2, from 0 to 5.
Request timeout	requestTimeoutSecs	30 seconds, from 5 to 60.
Maximum run time	maxRunSeconds	270 seconds, from 35 to 270.

Customer Maximum cost and run-timeout settings also apply. The Actor uses the run's effective event prices, including the automatic run-start fee, to reserve affordable result windows. If a useful result cannot fit, it stops successfully with a warning, status message and RUN_SUMMARY.limitStop; collected rows remain available and unprocessed domains remain in the summary's remaining count. A timeout keeps a 30-second storage/shutdown reserve; allow at least 35 seconds for useful work (this is not a guarantee of source availability). Normal source failures still appear as errors, not limit stops. The independent 270-second processing cap is unchanged.

The Actor uses an isolated transport worker with at most five active source requests and 20-result scheduling windows. A timed-out or failed transport is closed before unfinished requests may use their remaining retry budget; already completed results are preserved. Large source responses and expanded results use private temporary files with bounded encode buffers rather than remaining in IPC or the billing journal. Large decode/normalization ownership is serialized while source requests retain their five-slot concurrency. Completed large rows are uploaded as their exact encoded JSON, preserving all output fields and save-before-charge fencing. Source responses above 4 MiB or excessive country/history expansions fail explicitly, never as silently truncated estimates. Shipping defaults remain 256 MiB and 300 seconds. Connection safeguards reduce unnecessary repeat work but cannot guarantee that an upstream service or proxy will accept every request.

Only the Actor-managed automatic residential fallback can reuse an exclusive session qualified by an already-needed useful response within 7.5 seconds. Each session is limited to two total uses and less than 60 seconds; failed, slow, malformed or no-data responses immediately discard it. Customer-configured proxies retain their existing rotation semantics. These safeguards do not add retries, raise timeout caps or guarantee recovery from blocking or proxy rejection. Safe timing summaries exclude proxy credentials, endpoints, IPs and session identifiers.

For a direct-only input, set autoResidentialFallback to false and leave proxies disabled. Detailed connection behavior and limitations are in the input-field help.

Output data

One record is saved per processed unique domain. ok means measurable traffic or rank data was returned. no_data means the source returned a valid response without measurable visits or ranks, or explicitly returned no public report (HTTP 204). For unavailable public reports, estimates remain null—not measured zero—and the warning explains the reason. error records describe source failures rather than traffic estimates. Blocking, quota responses, and public JSON with missing or zero traffic are not treated as an unavailable report.

Fields	Meaning
domain, status, snapshotDate	Requested website, result status and source snapshot date.
rankGlobal, countryRank, categoryRank	Available popularity rankings.
totalVisits, monthlyVisits	Estimated latest visits and monthly history.
monthlyTrafficTrend	Latest/previous source month and visits, absolute change and percentage change derived from the existing monthly estimates; no extra requests.
company	Optional public-report company name, founding year, headquarters country/city, nullable numeric employee/revenue bounds and currency. Missing values and extension/error rows remain null.
bounceRate, pagesPerVisit, timeOnSite	Engagement estimates. Duration is in seconds.
topCountries, topKeywords	Available country shares and keyword metrics.
directTraffic, searchOrganicTraffic, genAiTraffic	Examples of acquisition-channel shares.
aiTrafficVisits, aiTrafficShareChatgpt, aiTrafficShareHistory	Available AI-referral estimates and chatbot history.
dataCoverage, warnings, aiTopPromptsError	Coverage and interpretation caveats.
sourceEndpoint	extension or public_report provenance; public recovery errors identify the attempted public endpoint. Other error records may be null.

Share fields use a 0–1 scale. For example, 0.25 means 25%. Missing metrics remain null or empty rather than invented. The RUN_SUMMARY key-value record reports completed, no-data, error and remaining counts.

The following is the shortened example retained from the existing documentation, not a fresh measurement:

{
  "status": "ok",
  "domain": "apify.com",
  "snapshotDate": "2026-06-01T00:00:00+00:00",
  "dataCoverage": "full",
  "rankGlobal": 8801,
  "country": "US",
  "countryRank": 8256,
  "categoryRank": 247,
  "totalVisits": 4414475,
  "bounceRate": 0.3635451161685786,
  "pagesPerVisit": 7.312413594737495,
  "timeOnSite": 294.15710816692786,
  "directTraffic": 0.41454222509064287,
  "searchOrganicTraffic": 0.36619347801592966,
  "genAiTraffic": 0.03090505529728478,
  "aiTrafficVisits": 122413.785,
  "aiTrafficShareChatgpt": 0.6188700398406928,
  "warnings": [
    "Similarweb metrics are estimates and may differ from first-party analytics."
  ]
}

Monthly traffic trend

company contains source-supplied company details when available from the same public report, without extra requests. Fields are name, yearFounded, headquarterCountryCode, city, employees, revenue, and currency. Employee and revenue objects have nullable numeric min/max bounds; unknown upper bounds and currency are not inferred. Malformed or inverted bounds remain null. These details are not independently verified, and no company data is inferred from traffic. For example: {"name":"Example Ltd","yearFounded":2001,"headquarterCountryCode":"GB","city":"London","employees":{"min":10001,"max":null},"revenue":{"min":1000000000,"max":null},"currency":null}.

monthlyTrafficTrend derives only from Similarweb's existing EstimatedMonthlyVisits estimates. It accepts valid first-of-month YYYY-MM-01 source keys and reports their latest two months as YYYY-MM, retaining null for missing, malformed, negative or nonfinite visit values. Both changes require consecutive calendar months, valid nonnegative values and a positive previous denominator. Missing months, zero baselines and unavailable values produce null changes—not invented zeros or growth across a gap. Flat and negative growth are supported. percentChange is in percent units, unlike the share fields. Error rows have a null trend; no-data rows never fabricate growth. Existing history/aliases and billing are unchanged.

Illustrative arithmetic only, not a fresh website measurement: source estimates of 100 visits in December 2025 and 120 in January 2026 give:

{
  "monthlyTrafficTrend": {
    "latestMonth": "2026-01",
    "latestVisits": 120,
    "previousMonth": "2025-12",
    "previousVisits": 100,
    "absoluteChange": 20,
    "percentChange": 20,
    "source": "EstimatedMonthlyVisits",
    "isEstimate": true
  }
}

Existing output aliases

Records also include types_included, data_captured_at, globalRank, estimatedMonthlyVisits, countryShare, website_traffic_by_country, paidReferralsTraffic, redirect and snake-case keys inside AI/country history.

isDataFromGoogleAds is a legacy alias. The accurately named field is isDataFromGoogleAnalytics.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The apify-actor-start event is charged once when a run starts, including runs that return no results.

The result event is charged for each saved domain record with status ok or no_data. Diagnostic error rows do not trigger this event. A no-data result is not a free result.

Pricing update: Updated run-start pricing and volume discounts take effect on 13 November 2026. See the live Pricing tab for current and upcoming rates.

Tips for best results

• Start with two or three domains. Check coverage before submitting a larger list.
• Compare matching snapshots. Estimates from different months are not directly interchangeable.
• Review warnings first. Missing source coverage is not proof of zero traffic.
• Keep source payloads off unless needed. The standard fields are easier to review and export.

Limits and caveats

Similarweb metrics are modeled estimates, not first-party analytics. Smaller sites may have limited coverage, and AI prompts are not available for every domain.

This Actor does not provide WHOIS records, homepage keyword density or a supported Similar Sites lookup. It is not affiliated with or endorsed by Similarweb.

Source restrictions can prevent results. An explicit anonymous lookup quota response is saved as a nonretryable source_quota_exceeded error, not no_data. The Actor does not retry or switch proxy routes for that response; other domains continue normally. The source's quota allowance, scope and reset time are unknown. Generic rate-limit responses retain bounded recovery. Mixed runs retain useful records alongside diagnostic errors. If every domain encounters a source failure, the run fails. A time-limited run can leave domains unprocessed, so review RUN_SUMMARY before treating a batch as complete.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~similarweb-traffic-scraper/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"domains":["apify.com","openai.com"]}'

Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/similarweb-traffic-scraper').call({
  domains: ['apify.com', 'openai.com'],
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("fetch_cat/similarweb-traffic-scraper").call(
    run_input={"domains": ["apify.com", "openai.com"]}
)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

MCP and AI agents

You can ask your AI assistant to collect data with Similarweb Traffic Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Similarweb Traffic Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/similarweb-traffic-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Similarweb Traffic Scraper by Fetch Cat, or give it the identifier fetch_cat/similarweb-traffic-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Get the available website traffic estimates for Apify and OpenAI, then compare their engagement metrics.”
• “Collect AI-referral estimates for OpenAI, Perplexity and Anthropic, then summarize the chatbot shares that are available.”
• “Retrieve keyword and country traffic estimates for Semrush and Ahrefs, then organize the results for a spreadsheet.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Is this the official Similarweb API?

No. It is an independent scraper of publicly available Similarweb estimates. No Similarweb login or API key is required.

Why are some fields empty?

Similarweb coverage varies by domain and metric. Check status, dataCoverage, isSmall, warnings and aiTopPromptsError before interpreting an empty field as zero.

For Automatic runs of more than 50 domains with recovery enabled, the Actor checks public traffic reports first and uses extension extraction for reports that fail to provide verified data. This preserves extension availability for domains needing that alternative; large-batch results may have limited coverage. Smaller runs, configured proxies, direct-only runs and zero-retry runs retain extension-first behavior. When extension extraction fails and the existing request/deadline budget permits, the Actor may make one public-report recovery request. Successful extension records are preserved without this request. Explicit anonymous registration quotas are not retried through another extension proxy. Public recovery uses your configured proxy exclusively when supplied; otherwise it starts direct. If that public request receives a challenge (HTTP 202/403), Automatic may use one residential recovery request within the existing total request budget. After an observed direct public challenge, later public requests in the same run prefer that recovery connection instead of repeating the blocked direct route. Explicit Direct/fallback opt-outs remain direct-only; no extra request beyond the retry budget is added. Setting maxRetries to zero leaves no extra recovery request budget.

Public-report records carry sourceEndpoint: "public_report", dataCoverage: "limited", and a warning. They preserve available visits, ranks and engagement estimates in existing fields. Missing channel shares and AI details remain null/empty. Public graph percentages are not monthly visit counts: monthly histories and monthlyTrafficTrend remain empty/null. Desktop-only country estimates are omitted rather than mislabeled as all-device traffic. Public challenges, unverified or missing positive traffic data remain nonbillable errors, not no-data records. Public availability varies and a challenge may prevent recovery.

Are source errors charged?

Diagnostic error records do not trigger the result event. A valid no_data response does. The start event still applies.

Can I export and compare recurring results?

Yes. Export datasets as JSON, CSV or Excel, or retrieve them through the API. Save your input as a task if you want to reuse it. Comparing separate runs is a step for your own workflow, not a built-in change report.

Related Actors

• Semrush Domain Overview Scraper — Collect public Semrush domain-overview snapshots with available traffic, ranking and backlink metrics.
• Website Technology Stack Detector — Identify technologies used by a website.
• WHOIS / RDAP Domain Lookup — Look up domain registration information.
• Website Contact Finder — Find publicly listed contact information.
• Website Social Profile Finder — Discover linked social profiles.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥