What low CTR means
Click-through rate is the proportion of search impressions that become clicks. It varies by position, query type, device, brand familiarity and the surrounding results. A low number is not automatically a problem. A page at position 17 should not be judged by the same expectation as a page at position 2.
The useful question is narrower: is this page appearing for a query it can satisfy, and does its title and description make that promise clear?
Find the right page first
In Search Console, open Performance, choose a recent 28-day range and view Pages. Sort by impressions. Look for URLs with enough data to inspect, an average position that is not being hidden by a handful of unrelated queries, and search intent the page can genuinely satisfy. There is no single impression threshold that works for every new or established site.
Imagine a guide receives 600 impressions for “Search Console weekly review” at an average position of 8, but earns 4 clicks. That is a reason to inspect the queries and result promise—not proof that the title is broken or that a rewrite will earn a particular number of clicks.
For a quick first shortlist, export the Pages table and use the free Search Console opportunity finder. It sorts your CSV in the browser; it does not upload it, inspect query intent or replace Search Console.
Read the query pattern before rewriting
Open the page's Queries view and group phrases by intent: learning (“how do I”), comparison (“best tool for”), diagnosis (“why is”) or action (“download”, “template”, “app”). Compare that intent with the page's first screen. If searchers want a workflow and see only a pitch, add the workflow. If they want a tool and see only theory, make the relevant next step visible.
Check whether a good query is being diluted by loosely related impressions. Page-level CTR combines different queries, positions, devices and result layouts. The aggregate percentage can hide a page that performs well for its intended search and poorly for accidental variants.
Choose the fix that matches the evidence
- Relevant query, unclear promise: make the title more specific to the task and audience.
- Good title, weak opening answer: improve the first paragraph and the section that should satisfy the search.
- Mixed or wrong intent: clarify the page's subject and add relevant internal links; do not stuff in every phrase.
- Far-back position or very few impressions: a title tweak may not be the priority. Improve usefulness and discovery, or wait for more data.
Make one change at a time
Write down a hypothesis first: “This title names the product but not the job this page solves.” Then change the smallest element that can test it. Keep the page accurate, preserve what already helps visitors, and avoid changing the title, opening, URL and links all at once.
Measure the follow-through
Wait for a comparable period and enough impressions to make the comparison useful. Review clicks, impressions, CTR, position and query mix together; note seasonality, promotions, site changes and major result-page changes. Record the edit date and what would count as a useful outcome before inspecting the next graph. A CTR change alone does not prove that a title edit caused it.
Rank for Mac connects Search Console evidence with local page review and a change record. The public Yuzool case log separates documented work from measured outcomes.
Prefer a walkthrough? Watch the 30-second Rank demo, then compare the feature set and $39 one-time price.