SimilarWeb Traffic & Rank Scraper | from $2.40/1K
Pricing
from $2.33 / 1,000 domain-traffics
SimilarWeb Traffic & Rank Scraper | from $2.40/1K
Extract website traffic data from SimilarWeb: global rank, category rank, monthly visits, bounce rate, pages/visit, traffic sources breakdown, and top countries. Clean JSON output via the undocumented SimilarWeb data API — no SimilarWeb account required.
Pricing
from $2.33 / 1,000 domain-traffics
Rating
0.0
(0)
Developer
Vitalii Bondarev
Maintained by CommunityActor stats
0
Bookmarked
117
Total users
18
Monthly active users
17 hours
Issues response
8 days ago
Last modified
Share
SimilarWeb Traffic & Rank Scraper
Extract comprehensive website traffic intelligence from SimilarWeb for any domain — no SimilarWeb account required, no API key needed. Perfect for SEO agencies, growth marketers, competitive analysts, and market researchers who need bulk traffic data without a $600/month SimilarWeb subscription.
Features
- Global rank — SimilarWeb worldwide rank (e.g. #47 for github.com)
- Category rank — rank within the site's primary category (e.g. #2 in News & Media)
- Country rank — rank in the site's primary country with country code
- Monthly visits — average monthly visits over the last 3 months (absolute count)
- Engagement metrics — bounce rate, pages per visit, average visit duration in seconds
- Traffic sources breakdown — shares for Direct, Search Organic, Search Paid, Social Organic, Social Paid, Referrals, Mail, Display Ads, GenAI, Affiliate
- Top countries — up to 5 top countries with traffic share percentages
- Monthly visit history — last 3 months of visit counts with exact dates
- Bulk processing — scrape hundreds or thousands of domains in one run
- URL normalization — accepts bare domains or full URLs, strips www automatically
- Graceful error handling — small/untracked sites get an error record instead of crashing
How to Use
- Open the actor and paste a list of domains into the Domains field.
- Use bare domains (
airbnb.com) or full URLs (https://www.airbnb.com/rooms/). - Leave proxy settings at the default (Apify RESIDENTIAL) — required for SimilarWeb.
- Click Start and results appear in the dataset within seconds per domain.
Example input:
{"domains": ["airbnb.com","booking.com","vrbo.com","tripadvisor.com"]}
Pricing & Cost Estimate
This actor uses Pay Per Result pricing. You are charged per domain successfully delivered. Each domain costs $0.0049 (i.e. $4.90 per 1,000 domains).
| Volume | Cost |
|---|---|
| 100 domains | ~$0.49 |
| 1,000 domains | ~$4.90 |
| 10,000 domains | ~$49.00 |
| 100,000 domains | ~$490.00 |
For reference: a SimilarWeb Professional subscription costs $600+/month and limits you to a fixed quota. With this actor you pay only for what you scrape.
The actor runs on Apify RESIDENTIAL proxy — compute and proxy costs are covered by Apify's PPE model and billed to your Apify account (not to you via an external service).
Input Reference
| Field | Type | Description |
|---|---|---|
domains | string list | Domains or URLs to look up. Required. |
proxyConfiguration | proxy | Proxy settings. Default: Apify RESIDENTIAL. Do not change. |
maxConcurrency | integer | Parallel fetches, 1–10. Default: 3. Keep at 3–5 to avoid rate-limiting. |
Output Reference
Each domain produces one record:
{"domain": "airbnb.com","global_rank": 169,"country_rank": 78,"country_rank_cc": "US","category": "travel_and_tourism/accommodation_and_hotels","category_rank": 3,"category_rank_name": "Travel_And_Tourism","monthly_visits_avg": 107846142,"avg_visit_duration_sec": 407.03,"pages_per_visit": 13.92,"bounce_rate": 0.309,"traffic_sources": {"direct": 0.45,"search_organic": 0.25,"search_paid": 0.05,"social_organic": 0.08,"social_paid": 0.02,"referrals": 0.07,"mail": 0.03,"display_ads": 0.01,"gen_ai": 0.005,"affiliate": 0.005},"top_countries": [{"cc": "US", "share": 0.55},{"cc": "GB", "share": 0.10},{"cc": "CA", "share": 0.08}],"estimated_monthly_visits": [{"month": "2026-02-01", "visits": 95000000},{"month": "2026-03-01", "visits": 110000000},{"month": "2026-04-01", "visits": 107846142}],"is_small": false,"scraped_at": "2026-06-07T12:00:00Z","error": null}
Fields are null when SimilarWeb has no data for a domain (new or very small sites). The error field explains why — null means success.
Use Cases
SEO agencies — audit competitor traffic channels, benchmark client sites against industry leaders, identify high-traffic targets for link building.
Growth hackers — validate market size before entering a niche, measure traffic share of competing products, track share-of-voice over time.
Market researchers — rank industries by total traffic, identify the top 100 sites in any category, build traffic-weighted media lists.
Sales intelligence — prioritize outreach lists by website traffic size, qualify inbound leads, validate company web presence.
Other Actors
Looking for more SEO and traffic data tools? Check out our other actors in the SEO_TOOLS and MARKETING categories on Apify Store.
FAQ
Does this require a SimilarWeb account? No. The actor uses SimilarWeb's undocumented data API that powers their browser extension. No login required.
Why do some domains return null values?
SimilarWeb only tracks sites with meaningful traffic. New domains, very niche sites, or sites with fewer than ~5,000 monthly visits often have no data. The error field will say "small site" for these.
How fresh is the data? SimilarWeb updates their estimates monthly. The data reflects the most recent month available in their system.
Can I scrape a million domains?
Yes — increase your Apify memory limit and set maxConcurrency to 5. Expect ~1–2 seconds per domain. For very large runs, split into batches of 10,000.
Is this legal? This actor accesses publicly available data from a public API endpoint. Use in accordance with SimilarWeb's Terms of Service and applicable laws. Do not use scraped data to build a competing data product.
Support: Open an issue in the actor's Issues tab or contact us via Apify's messaging system.
More scrapers from our toolkit
Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:
- Google Search (SERP) Scraper
- ASO Keyword Tracker
- Google News Scraper
- App Store Scraper
- Google Play Scraper
Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.
Usage statistics
This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.
Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.
Only these fields are recorded:
- schema version, Actor name and build number;
- UTC start and finish hour (not a precise timestamp);
- run duration, number of results and time to the first result, each as a coarse range;
- whether the result was empty, the end status, and an error type from a fixed list;
- memory setting and counts of charged events;
- names of the input fields you set, never their values;
- the selected option for input fields that offer a fixed list of choices (for example a sort order).
We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.
Additional fields (Phase 2)
This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.
The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.
Run-outcome signals (v2)
To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:
- the result limit you asked for (a range, when the input has one) and what share of it was delivered;
- results delivered per input item you listed (a range);
- output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
- how the run was started (console, API, schedule, webhook, another Actor);
- how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
- if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
- a short code made from the names of the input fields you set, never their values.
Repeat-run fingerprint (v2)
When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.