Debug: upstream API calls (click to expand)
| URL | Estimated Traffic |
Domain |
|---|
How it works
The Top Pages Finder queries our keyword index for every page on the submitted domain that ranks for at least one keyword in Google, models the estimated organic traffic for each page, sorts the result by traffic descending, and returns the top N rows.
Per-page traffic estimation. For each page, we look up every keyword it ranks for, multiply each keyword's monthly search volume by a position-weighted click-through-rate curve, and sum the results. This is the same methodology the Website Traffic Checker uses for whole-domain estimates, applied at the page level.
Single mode processes one domain synchronously and returns results in a few seconds. Bulk mode queues up to 20 domains and processes them asynchronously, so you can keep working while the job runs.
Canonicalization with fallback. Before the main fetch we resolve example.com vs www.example.com via the link-graph. If the chosen variant turns out to have too many pages for the upstream to enumerate (a known edge case for very large sites), we retry once with the opposite variant before declaring per-input failure. This recovers a real class of inputs that would otherwise fail.
Plan caps.
- Top pages per domain: 100 on the Free plan. Gold and Platinum both deliver up to ~1,000 (the upstream ceiling).
- Domains per bulk submission: 20.
- Daily-jobs budget: 100.
Known limitations.
- Organic search only. Pages that get most of their traffic from paid ads, social, email, or direct visits won't appear at the top of this list. For example, a viral social-media campaign page may have very high visit counts but low organic traffic, and rank poorly here.
- Google only. Bing / DuckDuckGo / Yandex / Baidu rankings don't contribute.
- Upstream depth ceiling. The underlying API caps responses at around 1,000 rows per domain regardless of plan, so very large sites with deep long-tail traffic can't all be returned.
- Index freshness. Newly-launched pages take a few days to several weeks to enter our index. Recent traffic spikes may not be reflected yet.
- Tie-breaking on traffic ties. When two pages have nearly identical modeled traffic, ordering between them is essentially arbitrary. Don't over-interpret tiny differences in row position.
What the columns mean
- URL
- The specific page on the domain that's ranking. Click to open the page in a new tab; cross-link icons let you immediately inspect the URL in Organic Ranking Checker, Backlinks Checker, Website Traffic Checker, etc.
- Estimated Traffic
- Modeled monthly organic-search visits to this specific page. Computed from position-weighted CTRs on every keyword the page ranks for. The headline column, and the default sort.
- Total Keywords
- Count of distinct keywords the page ranks for in Google. A page with a tighter keyword footprint that ranks well for high-volume terms can out-earn a page with broader-but-mediocre coverage, so read this alongside Estimated Traffic.
- Domain (bulk mode only)
- Which of your submitted domains this page came from. Useful when running several competitors at once: filter or sort to compare the top-page profiles side-by-side.
Frequently asked questions
How do I find the top pages of a website?
Enter the domain (e.g. example.com) and click Find Top Pages. We return up to 100 of the domain's highest-traffic pages from organic Google search on the Free plan, ranked by estimated monthly traffic, with the total keyword count for each. Bulk mode lets you run up to 20 domains at once.
How is "top page" defined here?
"Top" means highest estimated organic-search traffic from Google. We rank every page on the domain that's in our keyword index by the position-weighted click-through traffic it should receive from the keywords it ranks for, then return the top N rows. This is the same metric the Website Traffic Checker uses to score whole domains, applied per-page so you can see which specific URLs are pulling the traffic.
How do I get a list of all pages on a website?
This tool returns the highest-traffic pages, not every page. The full inventory of a domain's URLs lives in the site's sitemap.xml (if they publish one) or has to be crawled. Free crawlers like Screaming Frog (up to 500 URLs) or open-source Scrapy work for that. The advantage of this tool over a crawl is that you get the traffic ranking for free, no crawl needed, which is usually what you want when researching a competitor.
Why are the same number of pages returned regardless of plan?
Our upstream caps top-pages responses at around 1,000 rows per domain regardless of any depth parameter, which means the plan ladder is a soft cap rather than the actual upstream limit. The Free plan returns up to 100 rows; Gold and Platinum both return up to 1,000 (the upstream ceiling). For most domains the long tail is already covered in the first few hundred rows so this isn't a real constraint.
Why is a page I know is high-traffic missing?
Three common reasons. First, our index covers organic-search traffic only; pages that get most of their visits from paid ads, email, or direct traffic won't rank high here. Second, the page may be very new and not yet indexed in our dataset (Google takes days; we re-index periodically). Third, the page may be ranking for keywords with no measurable search volume (e.g. branded micro-niches), which means we can't model its traffic even though it's receiving visits.
Can I use this on my own site to find which pages drive my traffic?
Yes, and it's a useful cross-check against Google Search Console's "Top pages" report. The two views should mostly agree on which URLs are your top earners. Differences usually mean: (a) we're missing keywords that are surfacing for you locally but aren't in our country-specific index, or (b) GSC is missing traffic that comes through ranking variations we capture (e.g. ranking for keyword variations that GSC consolidates).
What is the most visited page on the internet?
Google.com's homepage by a wide margin (everyone's default search start), followed by major social-media sites (Facebook, YouTube, Twitter/X, Instagram) and the homepages of large news / e-commerce sites. For the long-tail "most visited within a niche" question, run this tool against the niche's top domain and you'll see the breakdown.
Why does each input count as a job toward my daily cap?
The daily-jobs cap counts at the submission level, not the row level: one bulk submission of 10 domains counts as 1 job, not 10. The cap is shared with no other tool in the project (the Top Pages Finder has its own bucket), so the number you see in the quota banner is your full top-pages daily budget. For domain-level traffic estimates without the per-page breakdown, the Website Traffic Checker is cheaper from a quota perspective.