Select a meaningful sample
Ask for page-level impressions, clicks, CTR and average position over a complete 28-day window. Use a practical impressions floor to avoid overreacting to tiny samples; it is a filter, not a Google benchmark.
Search Console · SEO diagnosis
Find low-CTR pages in Google Search Console
Start with pages earning enough impressions to evaluate, then compare their CTR with the queries, average positions and devices behind it. A low site-wide click-through rate does not, on its own, mean your page titles need rewriting.
14 days free · No credit card
Google Search ConsoleIllustrationCTR · illustrative page1.2%
12,000 impressions and 144 clicks. Position and query intent matter more than an arbitrary CTR target.
ImpressionsOrganic clicks
01 / Understand the signal
There is no universal 'good CTR' in Search Console
A page averaging position 15 usually has a different click opportunity from one averaging position 3. Brand queries, informational intent, rich SERP features and device mix can change the result too. Rather than label every page below 3% as weak, inspect query–page combinations with meaningful impressions and compare them with their own context.
02 / The analysis01 02 03
Identify CTR opportunities without chasing false positives
Segment by query and device
For the candidate pages, break the returned results down by query and optionally device. A page-level average can hide one high-impression query ranking far lower than another.
Check what is actually clickable
Review the live SERP, intent and displayed title for the main queries. Prioritize cases where impressions are substantial, position is competitive and the snippet or answer could genuinely be clearer.
03 / Worked example
The lowest CTR is not always the first page to optimize
These three fictional examples show why position belongs beside CTR and impressions. The figures are not ranking or CTR benchmarks.
| Example page | Impressions / clicks | CTR / avg. position | First check |
|---|---|---|---|
| /guides/mcp | 12,000 / 144 | 1.2% / 3.8 | Investigate high-impression queries and the displayed SERP. |
| /blog/seo-basics | 9,000 / 171 | 1.9% / 15.0 | Position likely explains much of the low CTR; inspect rankings first. |
| /pricing | 3,500 / 168 | 4.8% / 4.5 | Compare branded and non-branded intent before drawing conclusions. |
All URLs, queries and numbers in this table are fictional. They demonstrate the method, not actual performance.
Read the evidence
Check the query mix behind 1.2%
The /guides/mcp example has 12,000 impressions at a 3.8 average position: investigate how those impressions split across queries and devices. The 1.9% URL sits at position 15, where low CTR is less surprising. Average position is an aggregate, so neither row proves a bad title. Calculate CTR as clicks ÷ impressions; compare differences in percentage points, not relative percentage alone.
04 / Ready-to-copy prompts
Three prompts that make CTR actionable
An assistant can filter and group GSC performance. It cannot inspect the live SERP through AskGSC, so keep that as a separate manual check.
AskGSC offers read-only Google Search Console access through MCP: accessible properties, Search Analytics and period comparisons. Use the exact authorized property, not a guessed domain.
Explore all 18 Google Search Console prompts01Find the candidate URLs
For [PROPERTY], list pages over the last complete 28 days with at least [MIN_IMPRESSIONS] impressions, sorted by CTR ascending. Include clicks, impressions, CTR and average position. Highlight those with competitive positions; do not apply a universal CTR benchmark.
02Unpack a weak CTR
For [PROPERTY] and [PAGE URL], return query–page performance for the last complete 28 days. Identify the high-impression queries behind the page-level CTR, with each query's clicks, impressions and average position. Explain what still needs a live SERP check.
03Compare a title change fairly
For [PROPERTY] and [PAGE URL], compare two complete equal 28-day windows around [CHANGE_DATE]. Show CTR in percentage points, impressions, clicks and query mix. Describe changes, not the supposed effect of a title edit, unless other causes are ruled out.
05 / Decide what to do01 02 03
Three outcomes, three different SEO actions
Strong position, weak clicks
Inspect the actual search results and the query's intent. A clearer title or description can be worth testing, but Google may rewrite snippets.
Weak position, weak clicks
Do not start by changing every title. Work out whether the page answers the query and whether the ranking opportunity is real.
Mixed query intent
Segment the queries and devices. A blended page CTR can look bad when the URL appears for many peripheral searches.
CTR does not measure a snippet in isolation
Google can rewrite titles and snippets; SERP features, search intent and reporting mix influence CTR. AskGSC reports read-only Search Analytics data, not live SERP screenshots, A/B tests or title-edit attribution. Missing query rows must not be interpreted as zero.
06 / FAQ
Questions worth answering
What Search Console can and cannot tell you about this particular SEO problem.
01What is a good CTR in Google Search Console?+
There is no reliable fixed threshold for every query, page or position. Judge CTR alongside impressions, average position, query intent and device.
02Can GSC identify low-CTR keywords too?+
Yes. You can inspect query and page dimensions for candidates. This page covers both without claiming that every query with low CTR needs its own rewrite.
03Does changing a title automatically increase CTR?+
No. Google may choose a different displayed title, and demand or ranking can change at the same time. Use matching periods and review the live results.
Run it on your own data
Find the CTR problem before rewriting the title.
Put impressions, positions and queries in the same answer, then decide which pages actually justify a SERP review.
Review my low-CTR pages14 days free · No credit card