Traffic Estimate
developer/v1/domain/traffic-estimateEstimates traffic metrics for a domain including monthly visits, global rank, and traffic tier based on multiple data signals.
What It Does
Aggregates traffic signals from five independent sources — Tranco global ranking, Cloudflare Radar DNS popularity, Open PageRank link authority, WebsiteLaunches site authority, and Chrome UX Report real-user data — to estimate monthly visits and traffic tier. Cross-validates ranking sources for higher confidence.
Why It's Useful
Traffic estimates help evaluate domain value, competitive positioning, and market opportunity without requiring access to analytics. Useful for competitor research, M&A due diligence, and sales prospecting.
Use Cases
Competitive Intelligence
Estimate competitor traffic to understand market share and identify growth opportunities.
Benchmark your traffic against competitors without their analytics.
Domain Acquisition
Evaluate traffic potential when assessing domains for purchase.
Make data-driven acquisition decisions based on traffic value.
Sales Prospecting
Qualify leads based on their website traffic to prioritize outreach.
Focus sales efforts on prospects with meaningful web presence.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
domain | string | Required | The domain to estimate traffic forExample: example.com |
Response Fields
| Field | Type | Description |
|---|---|---|
domain | string | The estimated domain |
dataAvailability | string | Signal availability: sufficient (ranking data), limited (secondary signals only), or insufficient (no meaningful data) |
estimatedMonthlyVisits | object | Estimated monthly visits range (min, max, midpoint) |
trafficTier | string | Traffic tier: very-high, high, medium, low, or minimal |
score | number | Composite traffic score (0-100) factoring tier and confidence |
grade | string | Letter grade derived from score (A+ through F) |
confidence | number | Estimation confidence (0-100) based on number and agreement of independent signals |
signals | array | Data signals used: tranco, cloudflare-radar, openpagerank, websitelaunches, crux (source, signal, value) |
audienceProfile | object | CrUX quality weights per device (mobileQualityWeight, desktopQualityWeight, splitType) or null — reflects LCP performance quality, not traffic volume |
Code Examples
curl "https://api.edgedns.dev/v1/domain/traffic-estimate" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d "domain=example.com"const response = await fetch(
'https://api.edgedns.dev/v1/domain/traffic-estimate?domain=example.com',
{
headers: {
'Authorization': 'Bearer YOUR_API_KEY'
}
}
);
const data = await response.json();
console.log(data);import requests
response = requests.get(
'https://api.edgedns.dev/v1/domain/traffic-estimate',
headers={'Authorization': 'Bearer YOUR_API_KEY'},
params={
'domain': 'example.com'
}
)
data = response.json()
print(data)Read the full Traffic Estimate guide
Why it matters, real-world use cases, parameters, response fields, and how to call it from Claude, ChatGPT, or Gemini via MCP.
Read the guide →Related Endpoints
External References
Learn more about the standards and protocols behind this endpoint.
Try This Endpoint
Test the Traffic Estimate endpoint live in the playground.