← All articles

September 20, 2026 · 6 min read

How to write meta descriptions that get the click, not just the rank

Meta descriptions don't affect rankings, but they decide who clicks. Here's how to write and test ones that actually move CTR.

How to write meta descriptions that get the click, not just the rank — cover illustration

On a recipe page that already ranked in position four, changing the meta description from a generic restatement of the title to a specific promise — cook time, review count, and a concrete detail about the method — took click-through rate from 3.1% to 5.4% over the following month, with the ranking position unchanged the entire time. Nothing about relevance or authority moved. Only the pitch did.

It's ad copy, not a summary

A meta description sits next to nine other blue links, each one making its own case for the click. Restating the article's content wastes the one chance you get; the description's entire job is convincing someone to pick your result instead of a competitor's. That means leading with a specific benefit, number, or outcome rather than a bland recap of the title.

Character limits are pixel-based, not fixed

Google renders descriptions by pixel width rather than a strict character count, truncating differently across devices and having changed its display length more than once. The practical approach is to front-load your real message into the first 120 characters so it survives truncation everywhere, treating anything past 155-160 as a bonus that might not render on every device.

Specific beats clever, every time

"The ultimate guide to home coffee brewing" tells a searcher nothing they didn't already know from the title. "Pour-over, French press, and AeroPress compared: grind size, ratios, and brew time for each" gives them a concrete reason to believe the page answers their exact question. Named methods, numbers, and timeframes consistently beat superlatives in CTR comparisons.

Match tone to the intent behind the query

A page targeting "how to remove wine stains" should sound like a quick-fix promise — a specific household item and a claim it still works after the stain dries. A page targeting "wine stain remover comparison" should sound like a buyer's guide instead, naming what was tested and against what. Using the same tone for both intents leaves clicks unclaimed on one of the two.

Approximating an A/B test without dedicated tooling

Search Console won't split-test descriptions for you, but you can get close: change the description, note the date, and compare average CTR for that exact query across a matched time window before and after — same weekday range, similar seasonality. Give it at least two to three weeks of stable impressions before drawing any conclusion, since day-to-day CTR on a single query is noisy.

Duplicate descriptions quietly cost clicks across a site

Template-generated descriptions repeated across dozens of near-identical pages are one of the most common and easiest issues to find. Export your URLs and descriptions with a crawler and sort for duplicates; anywhere two pages share an identical description, at least one of them is getting no differentiation in the results at all.

Seasonal specificity beats a static evergreen line

A description referencing the current year, an active offer window, or a timely detail — "updated for 2026 filing deadlines" — reliably earns more clicks than a description that reads the same as it did two years ago, because it signals current relevance in a results page full of possibly outdated competitors. Revisiting your top pages by impressions once a quarter and refreshing stale-sounding lines is worth the small recurring effort.

Local queries need the location up front

For anything targeting a geographic query, leading with the city or neighborhood in the first few words measurably outperforms burying it at the end, since someone scanning results for local intent is pattern-matching on location before anything else. "Emergency plumber in Leeds, same-day callout" beats a generic trust-building line every time it's been tested against one.

Mobile truncates sooner than you'd guess

On a typical phone screen, Google frequently shows fewer characters before cutting off than it does on desktop, and since most search traffic for most niches is mobile now, writing for the shorter mobile truncation point is the safer default rather than optimizing for the desktop view first.

Opening with a number versus a question

A number up front ("3 ways," "12-minute fix") sets a concrete, checkable expectation. A question up front ("Struggling to remove wine stains?") mirrors a searcher's own internal frustration and can outperform numbers specifically for problem-aware queries. Testing both formats on the same page rather than assuming one wins universally is the only reliable way to know which fits a given query.

Where to place your brand name

Putting your brand name at the end of the description, after the actual pitch, lets the value proposition lead while still building recognition for repeat searchers. Leading with the brand name on a first-time query spends precious early characters on something a new visitor doesn't yet recognize as meaningful — costly real estate in a truncation-sensitive first 120 characters.

Common questions

Does the meta description tag affect rankings directly? No — Google has confirmed it isn't a ranking factor, though the CTR it produces can indirectly correlate with performance through engagement signals.

Will Google always use what I write? No, Google frequently rewrites the snippet, especially when it judges a body passage a better match for the specific query; a strong description improves the odds without guaranteeing it's used.

Should every page have a unique description? Yes, particularly for category and product pages — duplicate descriptions provide no differentiation and Google may auto-generate its own for some of them regardless of what you wrote.