Traffic Estimate: a beginner's guide
Estimate domain traffic and popularity
Traffic estimates: how the major SEO tools make their numbers up (and what to trust)
Traffic estimates are educated guesses about how many visitors a website actually gets per month. The estimates come from third-party tools like SimilarWeb, Semrush, Ahrefs, and Sparktoro, and they are the numbers that get quoted constantly in sales calls, investor pitches, and competitive teardowns. The important fact about traffic estimates is that none of these tools have access to the website's actual analytics. They are all estimating from external signals, and the estimates can be wildly different from reality.
You should care because traffic estimates are how the marketing world talks about competitor size, even though they are inherently imprecise. A salesperson telling you that "competitor.com gets 2.4 million visits per month" is quoting a tool's estimate, not a measured number. Sometimes that estimate is within 20% of reality. Sometimes it is off by a factor of 5 in either direction. Knowing how the estimates are produced — and how much to trust them — is the difference between using the data well and being misled by it.
The four sources every traffic-estimation tool draws from:
Clickstream data. Most tools buy anonymized browsing data from browser extensions, ad networks, and ISPs. This is the single biggest source of their estimates. The quality varies dramatically depending on how representative the panel is for the audience you care about.
Search visibility. Tools estimate organic traffic by checking which keywords a domain ranks for, the rank position, and the average click-through rate at that position. This works well for content sites, less well for sites driven by direct, social, or paid traffic.
Public signals. Some tools incorporate signals like Alexa rank, the size of the backlink profile, social-media engagement, and the number of pages indexed.
Statistical modeling. All the tools then run their raw data through proprietary models that smooth out noise and fill in gaps. The model is the secret sauce, and it is also why two tools can disagree by a factor of three on the same domain.
Three questions a traffic-estimation check answers:
Roughly how big is this competitor compared to me?
Is the competitor's traffic trending up or down over the last 6–12 months?
Where is the traffic coming from — search, direct, referral, social, paid?
The cost of taking traffic estimates literally is making decisions based on numbers that might be off by 5x. The right way to use them is as directional signals for trends and comparisons, not as ground-truth measurements. If three tools all show a competitor's traffic doubling over six months, the trend is probably real. If one tool says 2 million visits and another says 200,000, the absolute number is unknowable. Use them for comparison and trends; never quote them as if they were measured.
The Traffic Estimate endpoint, in plain language
In one sentence: Estimate domain traffic and popularity
Estimates traffic metrics for a domain including monthly visits, global rank, and traffic tier based on multiple data signals.
Don't worry if some of the words above are still unfamiliar — there's a plain-language glossary at the bottom of this page, and most of the terms link to their own beginner guides if you want to learn more.
What is actually happening when you call it
Here's what's actually happening behind the scenes when you call this endpoint:
Aggregates traffic signals from five independent sources — Tranco global ranking, Cloudflare Radar DNS (Domain Name System) 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.
If you're using an AI assistant through MCP, you don't need to understand any of the technical details — the assistant calls the tool and translates the result for you.
Why this specific tool matters
Let's skip the marketing fluff and answer the only question that actually matters: why should you, a real human with a real to-do list, care about the Traffic Estimate tool? Here's the plain-English version, written the way you'd hear it from a friend who happens to do this for a living.
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.
Picture this in real life. Imagine a product manager. Here's the situation they're walking into: Estimate competitor traffic to understand market share and identify growth opportunities. Without the right tool, that person would be stuck copy-pasting between five browser tabs, reading documentation written for engineers, and crossing their fingers that the answer they cobble together is correct. With the Traffic Estimate tool, the same person gets a clear answer in seconds — no spreadsheets, no guessing, no waiting for someone on the infrastructure team to free up.
Three questions this tool answers in plain English. If any of these have ever crossed your mind, the Traffic Estimate tool is built for you:
Are search engines actually able to crawl, understand, and recommend my pages?
What is the single biggest fix I could make today to climb in Google?
How does my site compare against the technical SEO checklist that the top results all pass?
You can either click the tool and get the answer yourself, or ask your AI assistant — connected through MCP (Model Context Protocol) — to ask the question for you and translate the answer into something you can paste into Slack.
Who gets the most out of this. Marketers, content writers, freelancers running client sites, founders trying to grow without paying for ads, and SEO specialists running monthly health checks. If you see yourself in that list, this is one of the EdgeDNS tools you should bookmark today.
What happens if you skip this entirely. Skip it and search engines quietly stop sending you traffic and you don't find out until the next quarterly review. That's why running this check — even once a month — is one of the cheapest forms of insurance you can give your domain.
Available on the developer plan. The technical details: `GET /v1/domain/traffic-estimate`.
When would I actually use this?
If you're still on the fence about whether the Traffic Estimate tool belongs in your toolbox, this section is for you. Below you'll meet three real people — a product manager, a domain investor, and a sales development — facing three real situations where this tool turns a stressful afternoon into a five-minute task. Read whichever story sounds closest to your week.
Story 1: Competitive Intelligence
Imagine you're a product manager. Estimate competitor traffic to understand market share and identify growth opportunities.
Why it matters: Benchmark your traffic against competitors without their analytics.
Story 2: Domain Acquisition
Imagine you're a domain investor. Evaluate traffic potential when assessing domains for purchase.
Why it matters: Make data-driven acquisition decisions based on traffic value.
Story 3: Sales Prospecting
Imagine you're a sales development. Qualify leads based on their website traffic to prioritize outreach.
Why it matters: Focus sales efforts on prospects with meaningful web presence.
Common situations across teams. Beyond the three stories above, here are the everyday workplace moments when people across the company reach for the Traffic Estimate tool — or one of the tools right next to it in this category. If any of these are on your calendar this month, that's your sign:
Before launching a new page, site, or campaign — to catch the dumb mistakes.
During a quarterly SEO health check.
When organic traffic suddenly drops and you need to find out why.
When pitching a new client and you need an audit deck in under an hour.
If you can see yourself in even one of those bullets, the Traffic Estimate tool will pay for itself the first time you use it.
Still not sure? Here's the easiest test in the world. Open Claude, ChatGPT, Gemini, or any other AI assistant connected to the EdgeDNS MCP server and ask, in your own words: "Is the Traffic Estimate tool useful for my job?" The assistant will look at the tool, ask you a couple of follow-up questions about what you're trying to accomplish, and give you a straight answer in plain English. No commitment, no signup forms, no jargon.
The easiest way: just ask your AI assistant
If you've connected the EdgeDNS MCP server to Claude, ChatGPT, Gemini, Cursor, or any other AI assistant, you don't need to write any code. Just ask in plain English:
"Use the Traffic Estimate tool to check example.com and explain anything that looks wrong in plain language."
The AI will figure out which tool to call, fill in the right parameters, run it, and then explain the result back to you. No copy-pasting between tabs. No reading raw JSON. No memorizing endpoint names.
MCP (Model Context Protocol) access is free on every plan, including the free tier. One API key works for both REST and AI — you do not have to choose.
The technical way: call it from code
If you're a developer and want to call the endpoint from a script or your own application, here's the simplest possible example. Replace the placeholder API key with the real one from your dashboard.
# Replace edns_live_YOUR_KEY with your real API key from the dashboard
curl -H "Authorization: Bearer edns_live_YOUR_KEY" \
"https://api.edgedns.dev/v1/domain/traffic-estimate?domain=example.com"What you need to provide
There's just one piece of information you need to provide. The table below explains exactly what it is and what a real value looks like.
| Field | Type | Required? | What it means | Example |
|---|---|---|---|---|
domain | string | Yes | The domain to estimate traffic for | example.com |
What you get back
When you call this tool, you'll get back a JSON object with the fields below. If you're talking to it through an AI assistant, the assistant reads these for you and explains them in plain language — you don't need to memorize them.
| Field | Type | What you'll see in it |
|---|---|---|
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 |
Words you might be wondering about
If any words on this page felt like jargon, here's a plain-language version. Click any linked term to read a full beginner-friendly guide.
DNS (Domain Name System) — The internet's address book. When you type a website name, DNS turns it into the actual numeric address computers use to find each other.
Need Programmatic Access?
Automate domain intelligence with 100+ API endpoints and a free MCP server for AI integration.