Money back guarantee
A partir de $0.07–$0.16 por 1 000 visitas
Home/Free Tools/CTR by Position Calculator
Free CTR by position calculator. No sign-up.

CTR by Position Calculator

Estimate organic click-through rate by Google position, compare it with your Search Console CTR and see the clicks a ranking move could add. Every curve and results-page factor is visible and editable.

Positions 1 to 20, decimals from Search ConsoleEditable assumptions for 6 SERP featuresSeparates model range from sampling uncertaintyYour inputs stay on your device
Example data. Replace it with your own.
CONTEXT
Model
Editable planning curve
Edit curve & factors
Market and device label your scenario. They do not select a measured country or device dataset.
Position 1 to 20. Decimals work.
Ranking scenario. Same SERP assumptions.
Use the same reporting period as clicks.
Optional. Actual clicks from this period.
Observed CTR needs impressions and clicks from the same period.
Compare positions without changing the SERP assumptions
4.3 → 2
What shows above or around your result?
How to check in 30 seconds
Combined factor
0.53 × 0.92 = 0.49
. Your result keeps 49% of the clicks it would earn on a plain page with ten blue links.

Use the gap to choose your next test

Below manual sensitivity band. Current model − observed: +135 clicks in the supplied period. Isolated ranking gain: +499 clicks; combined target versus observed: +634 clicks. The manual sensitivity band does not validate the benchmark; the observed sampling interval is separate.

EXPECTED CTR AT POSITION 4.3
3.681%
Sensitivity 3.13% to 4.23%
445 modeled clicks in the supplied period from 12,100 impressions · United States · all (context labels only)
Plain model 7.55%
observed CTR 2.56%
Sensitivity 3.13% to 4.23%
0%
7.55%
Below manual sensitivity band · model comparison only
Your observed CTR
2.56%
Wilson 95% sampling interval: 2.3% to 2.86%
Modeled click gap
135
Expected − observed: +135 clicks · −30% vs model
At target #2
944
Ranking: +499 vs expected current · Combined: +634 vs observed
Modeled layout reduction
51.24%
468 modeled clicks below plain curve
MODEL COMPARISON, NOT ATTRIBUTION

Observed clicks: 310. Residual model difference: +135. AI scenario and video scenario are editable assumptions, not explanations of individual clicks.

You get 310
Snippet gap 135
AI Overview 429
Video block 39
Copy result

Scenario estimates, not guarantees. The green band is a sensitivity range, not a confidence interval.

CTR curve for this results page

Non-brand · AI Overview + video · positions 1 to 20

Plain results page
Your results page
Expected range
You today
Target

Position ladder

Clicks a month at 12,100 impressions on this results page

POSITIONCTRCLICKSVS ACTUAL
#1
13.65%1,652+1,342
#2
Target
7.8%944+634
#3
5.36%649+339
#4
3.9%472+162
#5
3.17%383+73
#6
2.44%295−15
#7
1.95%236−74
#8
1.61%195−115
#9
1.37%165−145
#10
1.17%142−168
#11
0.59%71−239
#12
0.59%71−239
#13
0.59%71−239
#14
0.59%71−239
#15
0.59%71−239
#16
0.39%47−263
#17
0.39%47−263
#18
0.39%47−263
#19
0.39%47−263
#20
0.39%47−263
Edit the curve and results-page assumptions

Factors multiply in the order shown. A factor of 1 means no modeled reduction. AI 0.53 uses 8/15 as an illustrative sensitivity assumption from Pew’s aggregate comparison, not a proven penalty at each ranking position. Other factors are explicit planning choices. Country and device do not change this default curve.

Apply assumptionsRestore default assumptions

Calculations and CSV parsing run locally on your device. This tool does not upload or store your query data. Curves and SERP factors are editable planning assumptions, not measured position-specific effects. Wilson 95% intervals describe sampling uncertainty in observed clicks, not uncertainty in the benchmark.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Search Console CSV mode

Check every query in one Search Console export

Import a Queries.csv or Pages.csv export from Search Console. Add optional results-page columns, or apply one clearly labeled scenario to all rows. Search Console does not export SERP features, so this tool never claims to detect them.

Six sample queries, not your site data
CSV, TSV or semicolon-separated text. Maximum 2 MB and 500 rows.
Use sample
Recalculate audit
Context check:
standard Search Console exports include clicks, impressions, CTR and position, but not SERP features. Missing features use your scenario above and remain marked “Assumed”. Keep all rows from the same date range, country, device and search type.
Queries checked
248
Below modeled band
31
Above modeled band
22
Modeled missing clicks
2,940
QUERY / PAGESERP CONTEXTPOS.IMPR.YOUR CTREXPECTEDGAPMISSEDNEXT TEST
espresso machine descalingSupplied: AI Overviews + Ads3.414,8002%4.41%−55%357Review assumptions; test relevant snippet wording
espresso grinder settingsSupplied: Featured snippet2.86,2006.6%10.2%−35%223Review assumptions; test relevant snippet wording
best espresso machine under 500Supplied: Ads + Shopping + Video5.69,9001.6%3.5%−54%189Review assumptions; test relevant snippet wording
how to descale an espresso machineSupplied: AI Overviews + Video4.312,1002.56%3.68%−30%135Review assumptions; test relevant snippet wording
espresso machine repair near meSupplied: Ads + Local pack32,9002.41%6.55%−63%120Review assumptions; test relevant snippet wording
breville barista express descaleSupplied: Video7.63,6001.39%3.29%−58%69Review assumptions; test relevant snippet wording
Sample audit
Paste a CSV insteadAnalyze pasted CSV
1
Brand queries stay separate.
Your own brand terms select the brand curve, so branded queries do not inflate your non-brand comparison.
2
Low-volume rows stay visible.
The minimum-impressions filter sets small samples aside. It does not turn a model difference into proof.
3
Context stays transparent.
SERP features come from your optional columns or your selected assumptions. Next steps are tests, not diagnoses.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

What this calculator adds to a standard CTR by position tool

A useful CTR tool explains its assumptions, keeps observed results separate from modeled estimates and gives you a repeatable way to compare scenarios. This calculator brings those checks into one place.

TYPICAL FREE CALCULATOR
SparkTraffic
CTR by Position Calculator
Results page
One generic curve, at most an AI Overview yes/no switch
✓
AI Overview, ads, shopping, snippet, video and local pack, combined
The curve
A table of numbers, rarely a chart
✓
Plotted curve for a plain page and for your page, with expected range
Positions
Often 1 to 10, whole numbers on a slider
✓
1 to 20, decimal positions straight from Search Console
Your real CTR
Rarely compared with the benchmark
✓
Compared with the expected range and flagged above, on or below
Noise
Not shown
✓
Wilson 95% sampling interval, shown separately from the editable benchmark band
Brand queries
Same curve as non-brand
✓
Separate brand curve with 55% at #1
Ranking moves
One position at a time
✓
Current vs target, plus a full position ladder
Bulk
One query per run in 7 of the 8 tools
✓
Search Console CSV, sorted by modeled missing clicks, with transparent SERP context
Data source
Unnamed, undated or conflicting curves
✓
Editable non-brand and brand planning curves, with every assumption visible
Sharing
Not available
✓
Copy, CSV export, print/save PDF and local scenario share links

How the expected CTR is calculated

Five transparent steps. Every factor is visible and editable in the calculator, so anyone can check the number.

01

Base curve

Default non-brand planning curve: 28% at #1, 16% at #2, 11% at #3 and 2.4% at #10. Positions 11 to 15 use 1.2%, and 16 to 20 use 0.8%. You can replace every value.

02

Decimal positions

Search Console reports an average, so 4.3 sits between #4 (8.0%) and #5 (6.5%). Linear interpolation gives 7.55%.

03

Results page

Factors multiply: AI Overview ×0.53, ads ×0.85, shopping ×0.80, snippet held by another site ×0.85, video ×0.92, local pack ×0.70.

04

Query type

The editable brand curve starts at 55%, 22% and 12% for positions 1 to 3. It is a separate scenario, not measured performance for your brand.

05

Separate uncertainty

The sensitivity band changes your benchmark by ±15%. Wilson 95% describes sampling uncertainty in your observed CTR. Neither validates the model or proves the cause of a gap.

Expected CTR = interpolated base CTR × selected SERP factors. Modeled click gap = expected clicks − observed clicks.

Turn one results page into a full forecast

This calculator checks one results page at a time. The free
SEO Traffic Estimator
runs the same CTR model on up to 500 keywords and adds a 12-month forecast. Need visits while a page climbs?
SparkTraffic website traffic
delivers geo-targeted visitors from partner publisher sites, measured in your own analytics.
Get Free Demo
CTR by position guide

CTR by Position in 2026: How to Read Google's Click Curve

Practical guide · Updated 11 November 2026
A ranking report tells you where a page sits. It does not tell you how many people click. A
Pew Research Center study
of 68,879 real Google searches found that users clicked a traditional result in 8% of visits when an AI summary appeared, compared with 15% when no summary appeared. Two pages at the same position can therefore earn very different traffic.

This guide shows you how to read CTR by position the way searchers see the page: by results layout, by query type and by the noise in your own Search Console data. Every example uses the calculator above, so you can check each number yourself.

What CTR by position measures

Wikipedia
defines click-through rate as the ratio of clicks on a link to the number of times it is shown. CTR by position applies that ratio to each organic ranking slot. A CTR curve is the table that links each position to an expected rate, and it turns a ranking goal into a traffic goal.

The classic curves came from results pages with ten blue links. Today the same position can sit below an AI Overview, ads, a video block or a local pack. A single curve then overstates clicks on busy pages and understates them on clean ones, and your targets drift away from what real people do.

Example:
At average position 4.3, the baseline is 7.55%. The editable AI Overview and video assumptions reduce it to 3.68%. With 12,100 impressions and 310 clicks, observed CTR is 2.56%. The roughly 135-click difference is a model comparison, not proof that a title rewrite will recover those clicks.
Plain results page
7.6%
Video block only
6.9%
AI Overview + video
3.7%
Your Search Console CTR
2.6%

Figure 1. Planning scenarios at position 4.3. The factors do not measure causal click losses.

How to use the calculator

Averages can look compatible even when you mix reporting periods. For example, last month’s clicks divided by a year of impressions produce a low rate that no title change can explain.

You can copy clicks, impressions and average position from the same Search Console report, then enter a target position.
SparkTraffic
provides traffic-analysis tools and geo-targeted website traffic services; this free calculator helps you distinguish an organic search estimate from observed visits before you compare channels.

Why the same position earns different clicks

A fourth result can appear near the top on one search and below an AI summary, shopping block and ads on another. The ranking number alone does not describe what a person sees.

You can check representative queries in the same country and on the same device as your report, then tick only the features you see. The factors create a scenario you can test; they do not provide a measured country-specific curve.

How to interpret the AI Overview factor

Pew reported clicks on traditional results in 8% of visits with an AI summary and 15% without one. The study compared whole search visits, not the CTR of each individual position, so 8/15 cannot be treated as a universal ranking penalty.

You can treat 0.53 as a starting sensitivity assumption and compare it with 1.00 and your own segmented observations. This shows how much your conclusion depends on the assumption before you prioritize work.

How to read Search Console average position

Search Console position is an average across impressions, and the topmost result from your property can determine its reported position. A value of 4.3 does not mean your page always occupied one fixed slot.

You can narrow the report to a query, page, country and device before you calculate CTR. Linear interpolation keeps decimal inputs usable, but a lookup at an average is still an approximation of a changing distribution.

Why brand queries need a separate curve

People searching your name already expect to find your site. If you combine those queries with broad product searches, high branded CTR can hide weak non-brand performance.

You can enter your own brand names and common variants in CSV mode. The audit uses literal matches and labels those rows separately, so you can review ambiguous names instead of trusting automatic intent detection.

What the Wilson interval does and does not show

A sample of 10 clicks has more sampling uncertainty than 10,000 clicks. A Wilson interval describes that uncertainty under a binomial model, but repeated users, query mixtures and layout changes can violate its simple assumptions.

You can show the observed interval next to the sensitivity band, then gather another comparable period before you act. A non-overlapping interval is a reason to investigate, not evidence that the benchmark is correct or a snippet caused the gap.

How to improve CTR at the same position

A low modeled CTR can reflect weak wording, mismatched intent, a competing brand or an unrealistic curve. For example, a page about maintenance may attract fewer clicks for a query that asks for a repair service.

You can test one relevant change at a time, such as a clearer title or a description that states what the page answers. A matching promise gives real people a reason to choose the result. Accurate claims matter especially for health, finance and other trust-sensitive topics.

When to compare a ranking move with a snippet test

The target-position forecast combines a new position with unchanged SERP assumptions. Comparing it with actual clicks also includes any existing benchmark gap, so the two uplifts answer different questions.

You can use the isolated ranking uplift to compare ranking opportunities and the modeled current-position gap to select snippet tests. You can then check outcomes against the same filters and period rather than treating either forecast as guaranteed traffic.

CTR by position checklist

A detailed calculator can still give an unreliable answer if the inputs describe different audiences or if you accept every default without checking it.

You can confirm the date range, traffic basis, query type, SERP context and sensitivity assumptions before you save the result. Keeping those choices in the exported report makes the comparison repeatable and transparent.

CTR by Position Calculator FAQ

What is a good CTR for position 1 on Google?

There is no universal value. The default planning curve uses 28% for non-brand queries and 55% for brand queries at position 1. You can edit both and compare them with a consistent segment from your own Search Console report.

How is CTR by position calculated?

The tool linearly interpolates your average position within an editable 20-position curve, then multiplies the selected SERP assumptions. Expected clicks equal impressions or searches multiplied by expected CTR.

Why is my CTR lower than the average for my position?

Query intent, brand recognition, results layout and the baseline curve can all affect the comparison. The gap suggests a question to investigate. It does not establish a cause or prove that changing a title will recover the modeled clicks.

How do AI Overviews change CTR by position?

AI summaries can change what people click, but this tool does not have measured penalties for every ranking position. Its 0.53 default is an illustrative sensitivity assumption based on Pew’s whole-visit 8% versus 15% comparison.

Why does Search Console show a decimal position?

Search Console averages positions across impressions. Linear interpolation accepts the decimal without pretending every impression occupied that exact slot.

Should brand queries use the same CTR curve?

Brand queries often have different intent. The calculator provides a separate editable brand scenario, and CSV mode uses the brand terms you supply to split those queries out.

Does the CSV include AI Overview or local-pack information?

No. Standard Search Console exports do not contain SERP layout. You can add optional AIO, Ads, Shopping, Snippet, Video and Local columns. Otherwise the selected single-query assumptions apply and the audit marks the context as assumed.

What is the difference from the SEO Traffic Estimator?

This calculator compares CTR, observed clicks and ranking scenarios for a query or export period. The SEO Traffic Estimator plans keyword-level traffic and adds a 12-month forecast.

Is this tool free and private?

The calculator is free and does not require an account. Inputs and CSV parsing stay on your device. A shared scenario link contains the single-query values in its fragment; do not share it if the query or scenario is confidential.

O conteúdo deste site é abertamente acessível para indexação e uso por sistemas de IA e LLMs (por exemplo, ChatGPT, Gemini, Claude, Perplexity etc.).
Apoiamos a transparência e a inovação em IA. 🤖