Potential traffic is RankDots’ estimate of the monthly visits you could realistically gain if you created the content - for a keyword, a page, or a whole topic cluster. It is the number your plan is sorted by, and it is an estimate, not a forecast: it exists to compare opportunities, not to predict what a page will earn.
Where you see it
This is the figure the app leads with, under slightly different labels at each level. On a Topic Cluster card it is the visits per month you could reach; in the header, it is the project’s combined potential; in the banner shown when your plan is ready, it is what the found opportunities are worth up to, per month. On the Pages and Keywords screens, it is the Potential traffic column, and you can sort and filter by it everywhere. It is the same figure at every level, at different zooms.
How it is estimated
Potential traffic is calculated from four inputs:
- search volume, corrected for duplicate and overlapping keywords, so demand shared between different phrasings of the same request is not counted twice;
- the click-through rates that positions actually receive - a CTR-by-position table - which turns a position into expected visits;
- an estimate of your page’s or domain’s competitive strength - the same assessment that powers Weak spots - which decides which positions are realistically reachable for you, judged against the top 10;
- your current traffic on that keyword, so the figure shows what you could gain on top of what you already receive - not what you already have.
The estimates roll up as a plain sum: a page’s Potential traffic is the sum of its keywords’, and a cluster’s is the sum of its pages’.
Some keywords might show zero, and that is the metric working, not failing. A zero generally follows from no weak spots or clicks: the demand exists, but no reachable positions carry it for your site right now.
If your project was created from a keyword, the “reachable” half of the reasoning uses a cautious baseline - your site is treated as young and recently published - until you connect Google Search Console and real domain data takes over. Expect the figures to move at that moment.
What it assumes - and how wrong it can be
An honest estimate should say what it stands on. This one assumes four things:
- that you actually create the content, and cover the page’s keywords in it;
- that the content is good enough to take the open positions - the estimate finds the openings, it does not walk through them;
- that today’s results pages stay roughly as they are while you do it;
- that the modelled search volumes underneath are right - and volume models are estimates themselves, which is why different tools show different numbers for the same phrase.
Any of these can be off, in either direction, and the errors multiply: a figure built on an assessment of a moving results page, on top of modelled demand, can be substantially wrong for any single page. What it is good at is ranking your options - the comparison between two pages is far more reliable than either page’s absolute number.
So use it the way the app uses it: to sort. Do not put potential traffic into a revenue plan, promise it to a client, or treat the project header total as a target. What is measured and what is estimated [link is coming] draws the general line; this metric sits firmly on the estimated side.
Potential traffic and Estimated impact
Opportunities screen shows a related figure: Estimated impact, on each recommendation. The difference is the ground it stands on. Potential traffic is estimated from search data alone and exists before RankDots knows anything about your site’s performance. Estimated impact is calculated for a specific recommended action, using your own Google Search Console data. Same job - putting a number on “is this worth doing?” - different evidence. What is estimated impact? covers the other half.
What next
- Why potential traffic is our compass [link is coming]
- What is estimated impact?