How to Improve Google Search CTR With Better Titles and Descriptions

Google Search Console tells you how often your pages show up in search results and how often people actually click through. Those two numbers, impressions and clicks, sound simple, but the metric built from them, click-through rate (CTR), is one of the most misread numbers in SEO. Business owners often see a low CTR on a page, assume the title is "bad," rewrite it once, and never check whether it made any real difference. This guide walks through what CTR actually measures, how to find pages where a title and description change is genuinely worth making, and how to write and evaluate that change properly.

Impressions, clicks, and CTR: what each one actually tells you

An impression is counted whenever one of your pages appears on a Google search results page for someone's query, whether or not that person scrolls to it or clicks it. A click is counted when someone actually clicks through to your site. CTR is simply clicks divided by impressions, shown as a percentage. If your page had 1,000 impressions and 40 clicks, its CTR is 4%.

That distinction matters because impressions and clicks answer different questions. Impressions tell you whether Google considers your page relevant enough to show for a query. CTR tells you whether the people who saw it were persuaded enough by what they saw, your title, description, URL, and any extra result features, to actually visit. A page can have excellent impressions and rankings and still underperform on CTR, and that gap is exactly where title and description work pays off.

What "average position" really means

Search Console reports an average position for each page or query, and it's easy to misread this as "you rank #4." It isn't that. Average position is calculated across every single impression, for every query variant, every device, and every page of results that impression appeared on, then averaged. A page that ranks #2 for one search phrase and #9 for a related, higher-volume phrase might show an average position of #5, a number that doesn't describe either actual result. Position also moves with personalisation, location, and device, so the same query can rank differently for two different searchers at the same moment.

This matters for CTR analysis because position and CTR are related but not fixed to each other. Results near the top of the page generally attract more clicks simply because they're seen first and seen more often, but how much more varies a lot depending on the query. A branded search ("acme plumbing reviews") behaves very differently to a broad, comparison-style search ("emergency plumber near me"), and features like map packs, video results, or People Also Ask boxes can pull clicks away from organic results regardless of where you sit. Never read a CTR number without also looking at the position and the type of query it came from.

Using the Performance report properly

The Search Console Performance report is where all of this lives, and a few habits make it far more useful:

• Filter by page, then look at its queries. A single page usually ranks for dozens of query variants. Looking at the page's overall CTR without seeing which queries drive it can hide the real story.
• Compare similar time periods, not arbitrary ones. Use the date comparison feature to set like-for-like ranges, for example the same day-count before and after a change, ideally avoiding periods that include holidays, seasonal spikes, or unrelated site changes.
• Don't overreact to daily noise. Search Console data updates with a short delay and naturally fluctuates day to day, particularly for pages with lower impression volume. A dip or spike over two or three days is usually noise, not signal.
• Sort by impressions first, then CTR. This surfaces pages that already get meaningful visibility, which is where a title or description fix has an actual audience to work on.

If you haven't yet worked out which pages deserve attention at all, How to Find SEO Opportunities in Google Search Console covers how to scan the whole report for opportunities, of which low CTR is only one type.

Finding the real opportunity: good impressions, weak CTR

The pages worth your time are the ones with meaningful impressions, meaning Google already shows them to a reasonable number of searchers, but a CTR that's noticeably lower than similar pages at a similar position. A page with 30 impressions a month isn't a priority no matter how bad its CTR looks, the sample is too small to mean anything. A page with 2,000 impressions a month sitting at position 6 with a CTR well below what comparable pages get at that position is genuinely worth investigating.

Before changing anything, work out what the searcher actually wants. Look at the specific queries driving impressions to that page in the Performance report. If the queries suggest the searcher wants pricing and your title doesn't mention it, that's a clue. If the queries are highly local and your title is generic, that's another. The fix should respond to what real searchers are typing, not a guess at what sounds good.

Writing a clearer, more specific title

Google's own guidance on title links is consistent: write descriptive, concise text that's specific to the page, avoid vague titles like "Home" or "Services," and avoid repeating the same title or boilerplate across multiple pages. A few practical points for a business site:

• Be specific about what the page offers. "Boiler Repairs in Cheltenham" tells a searcher more, and matches more search intent, than "Services" or "Welcome."
• Keep brand and location context where it's relevant. If you serve a specific area, naming it in the title helps a local searcher confirm relevance at a glance. If your brand name carries trust or recognition, keep it, typically at the end, so it doesn't crowd out the descriptive part.
• Front-load the part that answers the query. Titles get truncated on some devices and result types, so put the most useful words first.

Google explicitly warns against keyword stuffing, repeating the same word or phrase multiple times in a title doesn't help the searcher and can make the result look spammy. One clear description of the page beats a title crammed with every variation of a keyword.

Writing a description that's compelling and honest

The meta description doesn't influence rankings, but it's the pitch that sits underneath your title and can be the deciding factor in whether someone clicks. Google's guidance on snippets describes a good meta description as an accurate, specific summary of the page, not a stuffed list of keywords, and stresses that every page should have its own unique one rather than reusing the same text sitewide.

Write it as a short, honest pitch: what the page covers, and why it's relevant to the person searching. Include a concrete detail if you have one, a service area, a specific offering, what makes the page useful, rather than a vague claim. Keep it tight, since Google truncates long descriptions to fit the space available, and there's no guaranteed length that always displays in full.

Avoid clickbait. A title that promises something the page doesn't deliver, an exaggerated claim, a question the content doesn't actually answer, might lift CTR briefly but increases the chance someone leaves immediately, which helps nobody. The goal is a title and description that accurately represent the page well enough that the right person clicks and stays.

Google may rewrite what you write

It's worth being direct about this: Google does not always display the exact title or description in your HTML. Its systems can and do generate a different title link or snippet from other content on the page, from heading tags, or from context Google considers more relevant to a specific query, and this happens for a meaningful share of results. This isn't a sign you did something wrong, it's normal behaviour. Writing a clear, accurate, specific title and description is still the right move, because it's the strongest signal you can give Google about what to show, but don't expect a one-to-one match between what you publish and what appears in every search result.

Give changes time, and don't keep tinkering

Two mistakes are common once a business owner starts editing titles: changing them too often, and judging the result too soon. Google needs to recrawl and reprocess a page before a new title or description can appear in results, and that doesn't happen instantly. If you rewrite a title, then rewrite it again a few days later because you're impatient, you never get a clean read on whether either version worked, and you make it harder for Google to settle on a stable version to display.

A reasonable approach: make one considered change per page, then leave it alone for at least three to four weeks before comparing performance, using the date-comparison view in the Performance report against an equivalent prior period. For lower-traffic pages, you may need longer to gather enough impressions to draw a real conclusion. Judge the change on CTR at a similar position and similar query mix, not on raw clicks alone, since traffic naturally varies for reasons unrelated to your title.

What a title change will and won't do

This is the point worth being clearest about: changing a title or description is not a ranking factor in the way it's often assumed to be. It will not, by itself, move a page up the results. What it can do is change whether someone who already sees your result decides to click it. Ranking and clicking are two separate problems, solved in different ways. If a page has genuine visibility, decent impressions at a reasonable position, but an underwhelming CTR, a better title and description is the right tool. If a page barely shows up at all, the problem is upstream of CTR, and no amount of rewording the snippet will fix it.

If the page's content itself doesn't match what the query is asking for, a title rewrite is a temporary patch at best. How to Improve an Existing Web Page Without Rewriting Everything covers how to strengthen the underlying page itself once you've confirmed the title and description aren't the whole story.