Similarweb Traffic Crawler
Pricing
from $0.25 / 1,000 results
Similarweb Traffic Crawler
Collect public Similarweb traffic estimates in bulk with fast HTTP requests, including rankings, engagement, traffic sources, countries, keywords, competitors, and AI referrals.
Pricing
from $0.25 / 1,000 results
Rating
0.0
(0)
Developer
yeekal
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Similarweb Traffic Scraper: Website Traffic, Rankings & Competitors
Collect public Similarweb traffic estimates for one website or up to 200 domains per run. This Apify Actor is optimized for parallel collection, fast turnaround, and predictable resource usage.
Enter domains or URLs and receive one normalized Dataset item per successful website. Results are ready for export to JSON, CSV, Excel, or an automated Apify workflow.
Data you can collect
Available fields depend on what Similarweb publishes for each domain.
| Data | Output field | Common use |
|---|---|---|
| Estimated monthly visits | visits, monthlyVisits | Compare reach and traffic trends |
| Global, country, and category rank | globalRank, overview | Qualify and benchmark websites |
| Bounce rate, pages per visit, visit duration | engagement | Evaluate audience quality |
| Direct, search, social, referral, ads, and AI traffic | trafficSources | Analyze acquisition channels |
| Leading countries | topCountries | Identify important markets |
| Top search keywords | topKeywords | Support SEO and content research |
| Similar websites | competitors | Discover alternatives and market peers |
| AI referral data | aiTraffic | Track traffic from AI assistants |
Why use this Actor?
- Process up to 200 domains in one run.
- Process domain jobs concurrently for faster batch completion.
- Normalize full URLs, international domains, casing, and duplicates.
- Retry temporary failures automatically.
- Skip failed domains in the Dataset and log a concise error code for monitoring.
- Return compact normalized records without duplicating the upstream payload.
Input example
{"domains": ["google.com", "facebook.com", "youtube.com", "github.com", "microsoft.com","amazon.com", "wikipedia.org", "baidu.com", "apify.com", "bing.com"],"proxyConfiguration": {"useApifyProxy": true,"apifyProxyGroups": ["RESIDENTIAL"],"apifyProxyCountry": "US"},"maxConcurrency": 10,"maxRetries": 2,"requestTimeoutSecs": 30,"includeRaw": false}
Input parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
domains | string array | Required | Domains or URLs to analyze. Maximum 200 values per run. |
proxyConfiguration | object | US residential proxy | Standard Apify proxy configuration. Residential proxies are recommended for reliability. |
maxConcurrency | integer | 10 | Simultaneous domain requests. Range: 1-50. |
maxRetries | integer | 2 | Retries after temporary failures. Range: 0-5. |
requestTimeoutSecs | number | 30 | Timeout for each request. Range: 5-120 seconds. This is not the total Actor run timeout. |
includeRaw | boolean | false | Include the complete source response for troubleshooting. Increases Dataset size and storage usage. |
Each domain is processed independently. Concurrency controls how many domain jobs can run at the same time.
Output example
{"domain": "example.com","status": "ok","fetchedAt": "2026-08-06T08:00:00.000Z","snapshotDate": "2026-06-01","visits": 123456,"globalRank": 1234,"overview": {"siteName": "example.com","title": "Example","category": "business","countryRank": { "rank": 500, "countryCode": "US" },"categoryRank": { "rank": 20, "category": "Business" }},"engagement": {"bounceRate": 0.42,"pagesPerVisit": 3.7,"timeOnSiteSeconds": 185.4},"monthlyVisits": {"2026-04-01": 118000,"2026-05-01": 121000,"2026-06-01": 123456},"trafficSources": {"direct": 0.41,"searchOrganic": 0.35,"referrals": 0.12},"topCountries": [{ "countryCode": "US", "country": "United States", "share": 0.48 }],"topKeywords": [],"competitors": [],"aiTraffic": null,"request": {"attempts": 1,"elapsedMs": 620,"httpStatus": 200,"proxyUsed": true,"proxyCountry": "US"}}
If every attempt fails, the Actor logs the domain, a concise error code, and retry count, then omits that domain from the Dataset. Failed domains do not create Dataset items; when the Actor is priced per result event, they do not trigger a result event.
In the Apify console, Traffic results is a table view that selects summary fields such as visits and rank. All fields shows the complete JSON item. Both views use the same Dataset; API calls and Dataset exports return the complete item, not only the Traffic results columns.
Performance and proxy settings
The default concurrency is ten and the allowed range is 1-50. Use 10 for small batches and 50 for 100-200-domain batches when the account can sustain the parallel workload. More concurrency reduces elapsed time but does not reduce the number of domains submitted.
US Apify Residential Proxy is recommended for reliability. You can provide another standard Apify proxy configuration when your workflow requires a different region or pool.
Retries are handled per domain with backoff, while other domains continue processing. A failed domain does not block the rest of the batch.
Results are normalized into compact records so downstream exports and workflows do not need to handle a duplicated source payload.
How it works
- Normalize and deduplicate the submitted hostnames.
- Schedule domain jobs concurrently.
- Collect the available traffic, ranking, engagement, and referral metrics.
- Retry temporary failures with backoff.
- Normalize traffic, rank, geography, keyword, competitor, and AI referral fields.
- Write one success record per successful domain to the default Dataset.
Recommended configurations:
- Small batch: 10 domains,
maxConcurrency: 10,maxRetries: 2,requestTimeoutSecs: 30. - Large batch: 100-200 domains,
maxConcurrency: 50,maxRetries: 1-2,requestTimeoutSecs: 30.
Submitting multiple domains in one run is generally faster and more economical than starting one run per domain because Actor startup and proxy setup are shared. Keep batches at or below 200 domains so failures, retries, and run timeout remain easy to monitor.