ToolsThatRank / measured data

First party measurement

CTR by position calculator

Type one page's average position, impressions and clicks from Search Console. You get its click through rate beside the rate that pages in the same position band recorded on our own 52 properties. On that fleet the 1 to 10 band recorded 7.1 times the rate of the 51 to 100 band.

One operator's sites, not an industry benchmark. Every rate here was read from Search Console properties we own. For a curve drawn from many sites, see Backlinko's CTR study (read 2026-10-10).

Average position 1 to 10 0.5559% 4,299 clicks on 773,293 impressions
Average position 51 to 100 0.0780% 54 clicks on 69,190 impressions
Whole fleet, 90 days 6,228 clicks from 1,436,949 impressions across 52 properties

Read 2026-10-10 from the Search Console searchAnalytics/query endpoint. Window 2026-07-10 to 2026-10-07. Each rate is the band's clicks divided by the band's impressions.

By Michael Lip. ToolsThatRank sells the pipeline that produced this page. The calculator is free and needs no signup.

Your row

Compare one page with its band

Open the Pages tab of the Search Console Performance report and pick one page. Copy its average position, impressions and clicks. An example row is loaded. Replace it with your own.

Enter an average position, impressions and clicks, then press Calculate.

The numbers you type stay in your browser. Nothing is fitted between bands. A decimal position is rounded first, the same rule the dataset uses, so 20.5 reads as 21. A position outside 1 to 100 returns no reading.

The measurement

Every band, with the counts behind it

A band measures pages by their average topmost position across all their queries. It is therefore not the same measurement as a published CTR at rank curve, and the two should not be compared.

One property, belikenative.com, supplies 64.14% of the fleet's impressions (921,701 of 1,436,949). So each band is shown twice, once for all 52 properties and once with that property removed. Read them together.

CTR by average position band. Read 2026-10-10.
Band All 52 properties Largest property removed
CTRImpressionsClicksPages CTRImpressionsClicksPages
1 to 100.5559%773,2934,2992,0090.8587%184,3511,5831,315
11 to 200.3297%319,7051,0548460.7942%74,536592418
21 to 300.3440%208,1357164140.3825%162,613622293
31 to 500.1671%109,5481836310.2100%54,774115548
51 to 1000.0780%69,190544850.0817%59,97949465

Read 2026-10-10 from the searchAnalytics/query endpoint, window 2026-07-10 to 2026-10-07. CTR is clicks divided by impressions inside the band, shown to four decimals. Pages is the number of page rows in the band.

Where the curve does something unexpected

Pooled, the 21 to 30 band (0.3440%) sits above the 11 to 20 band (0.3297%). With the largest property removed the order is the usual one, 0.7942% then 0.3825%. Every band also reads higher with that property removed. We report the shape and do not explain it, because this export measured no cause.

Why these rates differ from our position bands page

Our position bands page reads 34 properties over 2026-05-15 to 2026-08-12. This page reads 52 properties over 2026-07-10 to 2026-10-07. The two windows overlap from 2026-07-10 to 2026-08-12. The rate in every band differs between the two pages. They are two separate readings of a small fleet, and neither corrects the other.

Method

How we measured this

We measured these bands on 2026-10-10 against the Google Search Console Search Analytics API, method searchAnalytics/query, with read only access, on the 52 verified properties in the operator's account. The window is 90 days, 2026-07-10 to 2026-10-07, and ends three days before the read date. All 52 properties returned data.

Route one

Query grouped by page. Search Console returns one average position per page for the window. We round it to a whole number, put the page in the band that holds it, then sum clicks and impressions inside the band.

Route two

Query grouped by page and date. Each page's position is rebuilt as the impression weighted mean of its daily rows, then banded the same way. The export records the same impressions, clicks and page count as route one in all five bands.

The rate

Pooled. The band's clicks divided by the band's impressions, not a mean of page rates. A page with many impressions moves the rate more than a page with few.

Filters

No minimum impression filter was applied. 4,385 of the 4,386 page rows fall in a band. The export marks no property as cut short by the row limit.

Band sums and property totals do not match

The five bands sum to 1,479,871 impressions and 6,306 clicks. The same window read at property level gives 1,436,949 impressions and 6,228 clicks, and the sum of the daily rows gives the same two figures. The band sums are 2.99% and 1.25% higher. Search Console counts impressions by page differently from impressions by property, and its report overview says totals can differ between the two. We print both and adjust neither. The 64.14% share uses the property totals. The band rates use the page rows.

What the checks cannot catch

Both routes call the same API, so their agreement cannot catch an error on Google's side. A separate script recomputed every figure on this page from the saved export before release. That checks our arithmetic. It does not check the export step. Query text is never collected or published, and no per property file is published.

The calculator divides a band's clicks by its impressions without rounding. It rounds only what it displays, to four decimals.

Limits

What this cannot tell you

It cannot tell you what CTR your page should have. A band rate is what our pages recorded, pooled, in one window. A different window gives different numbers, as the two band pages on this site show.

The sample is one operator's fleet, and most of it is small. 12 of the 52 properties recorded no click in the window, and 13 recorded 20 or more. Among those 13, property CTR ran from 0.0814% (40 clicks on 49,160 impressions, average position 21.01) to 25.0000% (37 clicks on 148 impressions, average position 9.7). A band rate hides a spread that wide.

A page's average position mixes every query the page appears for, so two pages in one band can face different queries. CTR also says nothing about why a click happened or whether it was useful. A band is an average over many pages, not a target.

Related readings on this site are the position bands page for the earlier window, the CTR comparison calculator for two periods, and the average position calculator.

ToolsThatRank sells the pipeline that produced this page.

No ranking, traffic, or revenue outcome is promised.

The operator sells the software described here and owns every site in the dataset.

These figures come from one operator's properties, not from a representative sample of the web.

Search Console is authenticated, so readers cannot recheck the private source readings without access.

Figures are read on the stamped date and change as Search Console reprocesses data.

Michael Lip

Made by Michael, one person and a lot of coffee.

If ToolsThatRank has helped you, you can buy me a coffee. It honestly makes my day, and I read every note that comes with one.