How to Write a Meta Description That Gets Clicks

The meta description is the only piece of SEO copy that is unambiguously advertising. It does not rank you. It does not get crawled for signals. Its entire job is to convince a person who is already looking at ten blue links that yours is the one worth the click. Treated as a checkbox, it produces the beige summaries that Google routinely overwrites. Treated as ad copy with a 160-character budget, it is one of the few on-page changes that can lift traffic without moving a single ranking position.

This post covers how to write one that survives contact with a real results page. For the wider context of how the description fits with title tags, robots directives, canonicals, and social markup, see The Complete Guide to Meta Tags.

The real length constraint

The commonly quoted figure is 155 or 160 characters. It is a useful approximation and a slightly misleading one, because Google truncates snippets by rendered pixel width, not by counting characters. A description built from narrow characters survives longer than one full of capitals and wide letterforms.

The practical numbers as they stand in 2026:

• Desktop: roughly 920 pixels, which works out to about 150-160 characters in Google's snippet font for typical English prose.
• Mobile: noticeably tighter, often cutting near 120 characters, and varying with device width and whether Google decides to show extra elements like a date prefix.

Two consequences follow. First, a date stamp on a post consumes part of your budget before your copy starts — an article showing "Aug 7, 2026 —" gives up roughly a dozen characters. Second, and more importantly, the first clause has to work alone. Write so that the description still makes a complete, persuasive statement if it is cut at 120 characters. Everything after that is a bonus that desktop users get.

The corollary is a floor as well as a ceiling. Descriptions under about 70 characters look thin in the results page and leave persuasive space unused. If you cannot say something useful in 100 characters, the problem is usually that the page's value proposition is not clear yet.

What Google rewrites, and why it does not mean give up

Studies over the last several years have consistently found that Google replaces the supplied meta description on somewhere between half and two-thirds of queries. This gets cited as evidence that writing them is pointless. It is not.

Google rewrites when it believes a passage from the page body answers the specific query better than your general-purpose summary. That is a good outcome — it is dynamic, per-query relevance you could not have written for in advance. What matters is that your description is the default it works from, and it is what appears when the query is broad, navigational, or brand-led — often the highest-intent traffic you get.

It is also read verbatim in places that never rewrite anything: RSS readers, some site-search implementations, several link-preview surfaces, and any platform that falls back to <meta name="description"> when Open Graph tags are missing. That fallback path is one of the quieter reasons a shared link looks wrong, alongside the image problems covered in why your link preview image isn't showing.

Rewrites cluster around a few causes worth fixing:

• The description duplicates the title almost word for word.
• It is templated boilerplate repeated site-wide.
• It is keyword-stuffed and reads like a list.
• It describes the site rather than the page.

If a specific page is being rewritten consistently on its main query, those four are the checklist.

Formulas that hold up

Good descriptions are not creative writing. They are structured, and a handful of patterns cover most page types.

The value-plus-proof pattern, for informational content:

Compress images without visible quality loss. Side-by-side comparison of WebP, PNG, and JPG at five quality levels, with file-size numbers for each.

The first sentence is the promise; the second is the evidence that you can deliver it. It works truncated because the promise lands first.

The specificity pattern, for how-to content:

Set up a canonical tag in six lines of HTML. Covers absolute URLs, self-referencing canonicals, and the three mistakes that make Google ignore the tag entirely.

Concrete numbers ("six lines", "three mistakes") outperform vague quantifiers because they signal the page has actual boundaries rather than being a general essay.

The qualifier pattern, for commercial pages:

Free browser-based PDF merger. Combine up to 50 files, reorder pages by drag, and export without uploading anything to a server.

Price, limits, and constraints up front. This filters out the wrong clicks, which is desirable — a bounce from a mismatched expectation helps nobody.

Across all three, the moves that matter are the same: front-load the differentiator, use active verbs, include the primary term naturally so it bolds against the query, and end with the reason this page beats the other nine. Avoid the openers that waste your first fifteen characters — "In this article, we will", "Learn everything about", "Welcome to our guide on". They are pure cost.

Common failures

Leaving the CMS default in place. The single most common problem on real sites. A theme that emits the site tagline as the description on every page has effectively given every URL the same snippet.

Writing it last. A description drafted after the article is written tends to summarise what got written rather than argue for why it is worth reading. Draft the title and description before the body and you will usually find the article itself gets sharper.

Duplicating across near-identical pages. Paginated archives, filtered category views, and location pages with a single word swapped all produce the same snippet at scale. Either template a genuinely differentiated description with real variables in it, or omit the tag and let Google generate one per page.

Ignoring the truncation point. A description with the call to action at character 158 is a description whose call to action mobile users never see.

Mismatching the page. Overselling produces a click and an immediate return to results. The description is a filter as much as a hook.

Fitting it into a workflow

The description does not work alone. It sits under a title tag that is fighting its own pixel-width limit, and the two need to complement rather than repeat each other. A title that says "Meta Description Length: The 2026 Guide" should be followed by a description that adds something — the mobile cutoff, the rewrite rate — not one that restates it.

A short pre-publish loop catches nearly everything:

1. Draft the title and description before the body copy.
2. Run the description through the Meta Description Optimizer, which previews the rendered SERP snippet at both desktop and mobile widths so you can see exactly where the cut lands rather than counting characters and hoping.
3. Check the title alongside it with the Page Title Optimizer to confirm the pair reads as one unit.
4. Generate the full head block with the Meta Tag Generator.
5. After deploy, view source on the live URL and confirm the tag rendered — frameworks that inject metadata client-side can serve an empty <head> to crawlers.

All of these run entirely in your browser. Draft headlines and unpublished URLs are never sent anywhere.

The short version

Write 140-160 characters that still work if cut at 120. Lead with the differentiator, include the primary term naturally, and end with a reason to click. Make every page's description genuinely different. Accept that Google will rewrite many of them and write well anyway — because the ones it does not rewrite are usually the queries that matter most, and because half the internet outside search reads the tag exactly as you wrote it.