Website Traffic Estimator for 100 Domains in Bulk

Estimate organic website traffic for 100 domains in a single run (up to 1000 supported). Paste a list of domains and get one decision-ready row each: current organic traffic, a 12-month history, MoM and YoY change, a normalized 0–100 traffic index, and where the domain ranks inside your own list.

Built for SEO agencies, market analysts, and sales-intelligence teams who benchmark competitor or prospect websites at portfolio scale — not one domain at a time in a browser tab. Data comes from a licensed traffic-estimation API, so there is no scraping, no proxies, and no anti-bot loop.

What does the Website Traffic Estimator do?

Give it a list of domains. For each one, the estimator pulls the current organic-traffic estimate and the monthly historical series, then computes the portfolio metrics — a 0–100 index normalized across your set, the rank and percentile of each domain within the list, and month-over-month and year-over-year deltas with a riser / decliner / flat flag. One domain in, one row out — it answers, at scale, how much organic traffic each domain gets, how it is trending, and how they compare.

Why use the Website Traffic Estimator

• 100 domains per run — up to 1000 supported. One list in, one clean row per domain out — no per-domain clicking, no spreadsheet assembly.
• Historical series, not just a snapshot. Every domain carries a monthly history array (up to 12 months), so you see the trajectory.
• Portfolio comparison built in. rank_in_set, percentile, and a 0–100 traffic_index place every domain against the others in the same run — instant benchmarking within your list.
• Movement flags. mom_delta_pct, yoy_delta_pct, and a trend of riser, decliner, or flat show which domains are gaining or losing organic traffic.
• Risers & decliners view. A ready-made dataset view filters out flat domains so you can hand your team just the movers.
• Pay per domain, cache free. $0.15 per delivered row on the Free plan, down to $0.10 on Gold and above; a domain checked in the last 24 hours is served from cache and costs nothing beyond the one-time run start.

How to check website traffic in bulk

1. Open the Actor and paste your domains into the Domains field (one per line). Enter bare domains — the protocol, www., and any path are stripped to the root automatically, and duplicates are removed, so two variants of the same site count as one row.
2. Optionally set the Location (numeric code, default 2840 = United States) and Language (two-letter code, default en). One market per run.
3. Run the Actor. It checks the 24-hour cache first, then fetches current and historical traffic for every new domain in a single batch, and computes the in-set metrics.
4. Open the Overview dataset view for the at-a-glance list: domain, organic traffic, 0–100 index, in-set rank, and trend.
5. Switch to the Risers & decliners view to see only the domains whose trend is not flat, then sort by the MoM column to find the biggest movers.
6. Export to JSON, CSV, or Excel, or pull results from the API and feed them into your own SEO or sales dashboard. Re-run every ~30 days to keep the portfolio current.

Minimal input:

{
  "domains": ["notion.so", "figma.com", "example.com"]
}

What data you get per domain

One dataset row = one domain. Every row always carries the same 14 keys (nothing missing, no raw provider payload leaks through). Example row:

{
  "domain": "notion.so",
  "location_code": 2840,
  "language_code": "en",
  "etv_organic": 152340,
  "traffic_index": 100,
  "rank_in_set": 1,
  "percentile": 100,
  "history": [
    { "month": "2025-08", "etv_organic": 141200.0 },
    { "month": "2025-12", "etv_organic": 147880.2 },
    { "month": "2026-07", "etv_organic": 152340.5 }
  ],
  "mom_delta_pct": 3.65,
  "yoy_delta_pct": null,
  "trend": "flat",
  "not_found": false,
  "source": "primary",
  "checked_at": "2026-07-24T09:14:02.371Z"
}

Field	Type	What it tells you
domain	string	The normalized root domain (echo of input)
country	no	Market for the estimate — pick a country from the dropdown (92 supported markets). Defaults to United States.
location_code	no	API only (hidden in the UI): numeric market code that overrides the Location picker — handy for scripted runs and saved tasks.
language_code	no	Language of the estimate — leave on "Market default" to use the country's primary language (Germany → German).
etv_organic	number | null	Estimated monthly organic traffic value; null when the domain has no metric
traffic_index	number 0–100 | null	Traffic normalized against the top domain in the fetched set
rank_in_set	integer | null	Rank by organic traffic within your list (1 = highest)
percentile	number | null	Percentile position within your list (100 = highest)
history	array | null	Monthly series [{month, etv_organic}], oldest to newest; null when not fetched
mom_delta_pct	number | null	Month-over-month change, percent; null when the baseline is zero, missing, or the series is too short
yoy_delta_pct	number | null	Year-over-year change, percent (month vs month-12); null when the series is under 13 months
trend	string | null	riser, decliner, or flat from the MoM delta; null when the delta is null
not_found	boolean	true = the domain had no metrics; still a delivered, billed row
source	string	Data provenance: primary, historical-degraded, or bulk-only
checked_at	ISO 8601	When this observation was taken

Traffic index, ranking, and trend explained

The comparison metrics are computed within the set of domains you submit, so they benchmark your list against itself:

• traffic_index normalizes organic traffic to 0–100 against the highest-traffic domain in the run (the top domain scores 100).
• rank_in_set orders domains by organic traffic (competition ranking on ties), and percentile gives that position on a 0–100 scale.
• trend reads the MoM delta with a ±5 percentage-point noise band: inside the band is flat, at or above it is riser, below is decliner — so representation noise is not reported as real change.

Domains with no organic value fall outside the ranking (those fields are null), so a not-found domain never distorts the benchmark.

Input parameters

Field	Required	Notes
domains	yes	Your list of domains (1–1000). Each yields one row. Normalized to the root and de-duplicated before fetching.
country	no	Market for the estimate — pick a country from the dropdown (92 supported markets). Defaults to United States.
location_code	no	API only (hidden in the UI): numeric market code that overrides the Location picker — handy for scripted runs and saved tasks.
language_code	no	Language of the estimate — leave on "Market default" to use the country's primary language (Germany → German).

Run this Actor via the Apify API or the Apify MCP server (mcp.apify.com), so AI assistants can trigger a bulk traffic check straight from a domain list.

How much does the Website Traffic Estimator cost?

Billing uses Apify's pay-per-event model. You pay per delivered row, not per input domain and not per upstream call.

Event	When	Price
Run start	Once per run	$0.10 (flat, one-time)
Domain estimated	Per delivered row	$0.15 per domain (Free plan) → $0.10 on Gold+

The per-domain price is flat across every Apify plan. You are never charged for:

• Cache hits — a domain estimated in the last 24 hours is served from cache and bills nothing beyond the one-time run start.
• Failures — a domain whose data could not be fetched is skipped and never billed.

A not_found result is a delivered answer and is billed as one domain — knowing a domain has no organic-traffic metric is a result. On Free accounts the run stops before the first paid call once your plan limit is reached, so you are never charged beyond your balance.

Website Traffic Estimator vs Similarweb and manual checks

	This actor	Similarweb-style SaaS	Manual per-site checks
Bulk 100 domains (up to 1000)	Yes, one run	Enterprise tier only	No
Monthly history per domain	Yes, up to 12 months	Yes	Tedious
In-set ranking and 0–100 index	Yes	No	No
Risers / decliners flag	Yes	Manual	No
Cost model	From $0.10 per domain, cache free	Monthly seat	Your time
API + MCP access	Yes	Limited	No

For a domain-authority and backlink-strength snapshot instead of traffic, pair this with the Domain Authority Checker below. This estimator is the traffic-and-history angle: monthly series plus portfolio comparison across a submitted set, rather than a single authority score.

How the estimator stays reliable

• Cache (24h): identical domains within 24 hours are served free, with the original observation time preserved.
• Deterministic metrics: the same inputs always produce the same index, rank, and deltas. The contract version is part of the cache key, so a field change cleanly invalidates old entries.
• Graceful degradation: if only part of the batch resolves, the row is still delivered and source records how (primary, historical-degraded, or bulk-only). Each call retries transient errors up to three times with backoff.
• Plan-limit guard: on Free accounts the run stops before the first paid request when the forecast exceeds your plan limit — nothing is charged beyond your balance.

What this actor does not do

• It does not scrape websites or search engines — estimates come from a licensed traffic API.
• It does not report exact, audited visitor counts — organic traffic figures are model-based estimates.
• It does not measure paid, referral, direct, or social traffic in v1 — organic only.
• It does not track domains over time on its own — it is stateless; re-run it to refresh.
• It does not support per-domain geo or language targeting — one market and language per run.

FAQ

How many domains can I check at once?

Up to 1000 domains per run (100 is the typical batch) — one billed row each, except free cache hits and failures.

What is the traffic index?

A 0–100 score that normalizes each domain's organic traffic against the highest-traffic domain in the same run, so you can compare your list at a glance.

Why is yoy_delta_pct often null?

Year-over-year change needs the exact point from 12 months earlier. The window is about 12 months, so that baseline is often unavailable — null means "series too short", not zero change.

Do cache hits cost anything?

No. A domain estimated within the last 24 hours is re-delivered from cache and never billed beyond the one-time run start.

How often should I run it?

About every 30 days keeps a portfolio current, since organic-traffic estimates move slowly month to month. You can also run it via the Apify API or the MCP server.

Related actors

Pair this with the rest of the doesaiknow suite for a fuller SEO and competitive-intelligence view:

• Domain Authority Checker — bulk domain-authority and backlink-strength snapshot, when you need authority rather than traffic.

See the doesaiknow publisher page for more companion actors.

Legal & support

• This actor reports model-based organic-traffic estimates for the domains you provide. Data is sourced from a stable, licensed vendor API, not from scraping, proxy rotation, or anti-bot circumvention. It stores no personal data.
• Output is provided as-is for competitive-intelligence and SEO purposes. Traffic estimates are point-in-time model figures, not guarantees of actual visitor counts.
• You are responsible for using the output in line with the terms of the platforms you operate on and applicable law in your jurisdiction.
• Questions or a bug? Open an issue on the Actor's Issues tab, or see the API tab for integration details.

SEO keywords

website traffic estimator, website traffic checker, bulk website traffic, check website traffic, similarweb alternative, competitor website traffic, site traffic estimator, website analytics API, organic traffic estimate, domain traffic checker, traffic estimation API, bulk domain analysis, website traffic API, competitor traffic analysis, organic traffic checker, traffic benchmarking, website traffic comparison, domain traffic estimate, monthly traffic history, traffic trend tracker, SEO traffic tool, portfolio traffic analysis, estimate website visitors, traffic index.

Built by doesaiknow.