Why Your Position 1 CTR Sits at 7% Instead of 28%

Written by

in


A position 1 ranking used to be worth something like 40% of the clicks on a page. That number is now closer to 7%, and the gap between what you were promised and what you’re getting is probably the whole reason you’re reading this.

Your CTR is lower than average for your position because the “average” you’re comparing yourself to was built for a search results page that doesn’t exist anymore, your query mix includes branded and generic terms you haven’t separated, or your title and snippet aren’t doing enough work to earn the click once a searcher actually sees your listing. Usually it’s some combination of all three.

What benchmark CTR should your ranking position hit?

The old answer was clean. Position 1 got roughly 27.6% of clicks, position 3 got about 11.0%, and by position 10 you were down to 2.4%, according to a benchmark study cited by Software Toolbox. That curve has been the industry reference point for years. Plenty of rank trackers and SEO dashboards still quote it as if it’s gospel.

It isn’t anymore, at least not on its own.

First Page Sage’s tracking shows blended position 1 CTR dropped from 39.8% to 7.1% in the space of a year, an 82% decline that the report calls the largest year-over-year movement it has recorded in nine years of publishing. That’s not a gradual drift. That’s a step change tied to a specific event: Google made its AI-generated answer the default response to a search query rather than an optional layer above the results. The ten blue links stopped being the default feature of the page.

So which number should you use? Neither one in isolation. The 27.6%-at-position-1 figure is still a reasonable yardstick for queries where Google isn’t inserting an AI answer, a shopping carousel, or a heavy knowledge panel. The 7.1% figure reflects what’s actually happening across a broader, blended set of queries where those features now show up constantly. If your query triggers an AI response above your listing, benchmark yourself against the lower number. If it doesn’t, the older curve still applies reasonably well.

A person types on a laptop displaying data charts on the screen

Here’s a worked example. Say you rank position 3 for “industrial humidity sensor” and your Search Console data shows a 4% CTR over the last 90 days. Against the 11.0% position-3 benchmark, that looks like a serious problem. Your 4% might be close to the realistic ceiling for that specific query right now, not evidence that your title tag is broken.

That distinction matters because it changes what you fix. A genuine title problem gets solved by rewriting the title. An AI-answer problem gets solved, if it gets solved at all, by targeting a different angle of the query that doesn’t get swallowed by the AI box.

There’s also a separate, adjacent number worth knowing if you run paid alongside organic: the industry-wide average CTR for Google search ads sits at 3.17%, while display ads average 0.46%, Indeed reports, citing WordStream data. That’s useful context precisely because it shows how different paid and organic click economics are. Comparing your organic CTR to an ad benchmark, or vice versa, tells you nothing. They’re different behaviors from different intents.

One thing worth checking before you panic over any benchmark gap: average position itself is often fractional and blended across devices, countries, and SERP features, which means a reported “position 3” might represent a mix of position 1 results on mobile and position 6 results on desktop for the same query. Pull the data apart by device before you trust the position number at all.

AI answers and snippet mismatches depress organic CTR

Segment your branded and generic queries before you do anything else with your CTR data. This is the single highest-use move in this whole conversation, and it’s also the one most teams skip because it takes an extra ten minutes in a spreadsheet.

Branded queries, someone searching your company name directly, convert at CTRs far above any generic benchmark because the searcher already knows what they want and you’re the obvious click. Software Toolbox’s guidance points out that branded product queries sit far above the curve, and mixing them with generic queries hides weak non-branded performance. If your site gets decent branded search volume, your blended average CTR can look perfectly healthy while your actual acquisition queries, the ones bringing in people who’ve never heard of you, are quietly underperforming.

Pull your Search Console data, filter for queries containing your brand or product names, and look at the rest separately. Does the generic-query CTR still clear the benchmark for its average position? If not, you’ve found the real problem, and it was sitting there disguised by your branded traffic the whole time.

The trade-off here’s time, not difficulty. Segmenting queries properly means tagging or filtering potentially hundreds of search terms, and if your product names overlap with generic industry language, the split won’t be perfectly clean. Do it anyway. An approximate split beats a blended average that tells you nothing actionable.

Once you’ve separated the signal, the second decision is whether an AI answer is sitting on top of your result before you decide your title is the problem. Check manually; Search Console doesn’t flag this for you directly. Search a sample of your underperforming queries and note whether Google’s AI response, a featured snippet, or a “people also ask” block appears above your organic listing. If it does, your expected CTR for that position drops regardless of how good your title is.

This is the part that’s genuinely unfair about ranking signals right now. CTR has never been a direct Google ranking factor on its own, but it does communicate relevance and quality signals over time, according to Backlinko’s explanation of CTR. A page that earns consistent clicks sends a positive signal that can support rankings for specific keywords. Which means a query where an AI answer is eating your clicks can create a slow, quiet drag: lower CTR, weaker relevance signal, harder time holding or improving the ranking you already earned.

What do you actually do about it? Not much, directly. You can’t turn off Google’s AI answer layer. What you can control is which queries you’re optimizing titles and content for in the first place. If a query reliably triggers an AI Overview that fully answers the searcher’s question, that query is probably never going to deliver strong organic CTR again, no matter how good your snippet is. Redirect title and content optimization effort toward adjacent queries, more specific long-tail variants, comparison questions, or anything requiring a deeper answer that an AI box is less likely to fully resolve.

The mistake most teams make here’s treating every low-CTR query the same way: run an A/B test on the title tag, tweak the meta description, wait a month, repeat. That works fine for queries where the problem actually is a weak title. It wastes a month for queries where an AI answer or a featured snippet is the real ceiling. Check which situation you’re in first.

To prioritize where to spend that effort, open your WordPress Search Console report if you’re on that platform, Insights → Reports → Search Console, and look at the view that lists search terms alongside impressions, clicks, CTR, and average position together, as Monsterinsights describes. That combined view is built specifically to help you decide which pages are worth fixing first, rather than guessing. A high-impression, low-CTR page ranking well is your highest-value target; a low-impression page isn’t worth the hour.

One more practical note: the value of fixing this compounds. A 1 to 2 percentage point CTR lift on a page already getting 10,000 monthly impressions adds hundreds of extra visits a month, per Monsterinsights’ own figures. That’s not a reason to chase every page. It’s a reason to start with your highest-impression pages first, since the same percentage gain is worth more there.

If you want a structured way to keep tracking this month over month rather than re-pulling reports from scratch, our guide on performance tracking tools walks through the setup.

What it is not

A low CTR relative to position isn’t the same thing as a ranking problem. Your position is earned by relevance, authority, and technical signals Google evaluates before the click ever happens. CTR measures what happens after the searcher already sees you, which is a separate and later decision point.

It’s also not a fixed, single target. There’s no official body-defined number for what “good CTR” means at any position; the benchmarks you see from Software Toolbox, First Page Sage, or Advanced Web Ranking are observational studies of aggregate search behavior, not a standard Google publishes or enforces. Treat them as a comparison point, not a pass/fail line.

And it’s not interchangeable with Quality Score, even though the two get confused constantly. Quality Score is Google Ads’ own rating of ad relevance and landing page experience for paid campaigns, evaluated against other advertisers bidding on the same search over the last 90 days, per Google’s own documentation. Expected CTR is one input into Quality Score for ads. It has nothing to do with your organic listing’s click rate. If your team runs both organic and paid, keep these conversations separate; a low organic CTR tells you nothing about your Ad Quality Score, and vice versa.

When it matters

This matters most if you’re managing pages that rank well, positions 1 through 5, but aren’t delivering traffic that matches that position. That gap is where budget and effort get wasted silently. A page stuck at position 8 with a weak CTR is a minor leak. A page at position 2 with a CTR that’s half the expected curve is a major one, because the impression volume at that position is usually far higher.

It also matters more for commercial and informational queries that are prone to AI Overviews or featured snippets, think “how to,” “what is,” and comparison-style searches. If your content strategy leans heavily on that kind of query, expect your realistic CTR ceiling to be lower than it was two years ago, and plan your traffic projections accordingly rather than being surprised by it every quarter.

It matters less if your traffic comes mostly from branded search or highly specific, long-tail technical queries where AI answers rarely have enough information to fully satisfy the searcher. Those queries tend to hold up closer to the older benchmark curve.

Frequently Asked Questions

What counts as a “good” CTR for my industry?

There’s no universal good number, because CTR depends on position, query type, and whether an AI answer or rich result is competing for the click. The closest thing to a reliable number is your own site’s historical CTR by position, measured in Search Console over a consistent period, compared against itself over time rather than against a generic industry average.

Does a low CTR hurt my rankings directly?

Not directly. CTR isn’t a ranking factor Google applies on its own, according to Backlinko’s reporting. It functions as a relevance and quality signal that can support ranking improvements over time when it’s consistently strong, and the reverse holds for consistently weak CTR relative to expectation.

How do I know if an AI Overview is suppressing my CTR?

Search the query manually and check whether Google’s AI-generated answer appears above the organic results. Search Console doesn’t label this for you in the standard report, so a manual spot-check across your underperforming queries is currently the only reliable method.

Should I separate branded and non-branded queries before benchmarking?

Yes, every time. Branded queries convert at CTRs well above any generic benchmark and will inflate your blended average, masking weak performance on the generic queries that actually drive new customer acquisition, as Software Toolbox notes.

Is it worth rewriting titles for every low-CTR page?

No. Rewrite titles for pages where the low CTR is a title or snippet problem; a page competing against an AI Overview that fully answers the query won’t recover much from a better title alone. Check what’s actually sitting above your listing on the SERP before deciding which fix applies.


Don’t let a healthy ranking report hide a traffic problem you haven’t looked at yet. Pull your Search Console data this week, split branded from generic, and check which of your top pages are losing clicks to AI answers rather than weak titles, because the two problems need completely different fixes and treating them as one will waste your next quarter. If you’d rather have that audit and the content fixes handled for you, book a call with our team at Keyworth and we’ll walk through what’s actually costing you clicks.

About the author

Abayomi Adenekan

Abayomi Adenekan

SEO Specialist, 10+ years

Abayomi “Yomi” Adenekan built Keyworth. He has spent over ten years in growth marketing, SEO, and product. He began as a web developer and email marketing specialist, moved into paid media managing $13M a year in ad spend, and now leads growth at a podcast incubator with 1,300+ creators. He also runs Dynareach, his own SEO, web development, and branding agency. He holds an M.Sc. in Data-Driven Marketing from Universidade NOVA de Lisboa and lives in Lisbon.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *