Dispatch
What Is a Meta Description? Writing Snippets That Earn the Click
A meta description is an HTML tag, <meta name="description" content="...">, that gives a short summary of a page's content. You don't see it on the page itself; it lives in...
On this page
- How Google decides what to show
- Length: there’s no fixed limit, just a fitting problem
- Why your description sometimes doesn’t appear at all
- AI Overviews are changing the picture further
- Writing descriptions that actually earn clicks
- Scaling descriptions across large sites
- Testing and measuring what actually works
- The practical takeaway
- Related posts:
A meta description is an HTML tag, <meta name="description" content="...">, that gives a short summary of a page’s content. You don’t see it on the page itself; it lives in the <head> of the HTML. Its main job happens somewhere else entirely: in the search results page, where it often (though not always) becomes the gray summary text shown under your blue title link.
Meta descriptions are not a ranking factor. Google has never claimed they are, and there’s no mechanism by which writing a better one would move you up the results page. What they do influence is click-through rate: whether someone scanning a results page chooses your listing over the nine others competing for the same attention. That distinction matters because it changes what “good” means. You’re not writing for an algorithm here. You’re writing for a person deciding, in about two seconds, whether your page is worth a click.
How Google decides what to show
Google does not always use the description you wrote. According to Google’s own guidance on writing meta descriptions, the company generates the snippet shown in search results using a combination of your meta description, the visible content of the page, and other signals, choosing whichever combination it judges most relevant to the specific query someone typed. If your hand-written description is vague, duplicated across pages, or simply doesn’t match what a searcher typed, Google may pull a more relevant excerpt straight from your page content instead.
This means a meta description functions less like a guaranteed display and more like a strong suggestion. Writing one well increases the odds Google uses it. It doesn’t guarantee it.
Length: there’s no fixed limit, just a fitting problem
Google’s documentation is explicit on this point: “There’s no limit on how long a meta description can be, but the snippet is truncated in Google Search results as needed, typically to fit the device width.” There is no official character cap. What actually happens is a pixel-width constraint: Google allots a certain amount of horizontal space to the snippet, and however many characters fit in that space is what displays, with everything past that cut off.
Because pixel width depends on character shape (a row of “i”s takes less room than a row of “w”s), there’s no single character count that maps perfectly to “will it fit.” That said, the SEO industry has converged on practical shorthand based on observing how snippets typically render: roughly 150 to 160 characters tends to display in full on desktop, while mobile result cards are narrower and tend to truncate earlier, often somewhere in the 105 to 120 character range. Treat these as rough planning targets based on typical rendering, not as values Google has published or guaranteed.
| Surface | Practical character guideline (industry shorthand, not an official Google limit) |
|---|---|
| Desktop | ~150-160 characters |
| Mobile | ~105-120 characters |
| Either, if truncated | Google generally cuts at a word boundary and adds an ellipsis rather than chopping mid-word |
A description that runs long doesn’t get penalized. It just gets cut off, sometimes mid-sentence, which is the practical reason to front-load your most important point rather than save it for the end.
Why your description sometimes doesn’t appear at all
Beyond rewriting your description, Google can also choose to show no snippet, or a heavily restricted one, in specific situations: if you mark a page with a nosnippet meta tag, if you use max-snippet:[number] to cap snippet length, or in some cases when Google determines no part of the page is a good match for a given query. These are documented controls, not guesses, in the same Search Central snippet guidance, and they’re worth knowing about even if you rarely use them, since they explain why a page you optimized carefully might still show a Google-generated snippet on some queries and your own description on others.
AI Overviews are changing the picture further
Search is also testing ways to summarize results using AI rather than displaying a static snippet at all. Search Engine Land has reported that Google is testing AI-generated descriptions for search snippets, in some cases replacing the page-owner’s meta description entirely with a Gemini-generated summary, marked as AI-generated, and in other cases generating an AI summary on top of the existing snippet logic. The same reporting points out that, in practice, Google was already frequently choosing not to use a site’s literal meta description text even before this testing; what’s changing is the mechanism doing the rewriting, not the fact that Google has always retained discretion over what displays. The practical implication for now: a well-written meta description still functions as an input signal Google can draw on, but it is one input among several, and that’s increasingly true rather than less true as AI-generated summarization spreads across search results.
Writing descriptions that actually earn clicks
With the mechanics out of the way, the writing itself comes down to a short list of habits that consistently separate descriptions people click from descriptions people skip past:
- Lead with the specific value, not a restatement of the title. If the title already says “Best Running Shoes for Flat Feet,” the description shouldn’t just repeat that idea in different words. It should add something the title couldn’t fit: a number of options compared, a key consideration, a concrete detail.
- Match the actual intent behind the query, not a generic description of the page topic. A description for a “how to” page should signal that it answers the question; a description for a product page should signal what’s actually for sale and at roughly what price point, if that’s honestly relevant.
- Use one true, concrete detail when you have one. A real number, a real timeframe, a real feature beats vague claims like “comprehensive guide” or “everything you need to know,” which describe nothing and could sit under any page on the internet.
- Write unique copy for every page. Google’s own guidance specifically warns against generic, boilerplate, or duplicated descriptions, since they fail to differentiate one page from another in results and tend to get overridden by Google-generated alternatives.
- Avoid keyword stuffing. Google’s documentation explicitly discourages filling a description with “long strings of keywords,” which reads poorly to humans and doesn’t help relevance the way a real, descriptive sentence does.
- Skip manufactured urgency you can’t back up. Generic calls to action (“Click here now!”) read as filler. A specific, honest reason to click reads as information.
Scaling descriptions across large sites
Hand-writing a unique meta description for every page works fine at the scale of a blog or a small service site. It breaks down fast on an e-commerce catalog with tens of thousands of SKUs or a directory site with thousands of listing pages. At that scale, most sites use templated descriptions built from structured page data, pulling in the product name, category, and a real attribute such as price range or material, rather than hand-writing each one.
The risk with templates is that a poorly built one produces descriptions that are technically unique in their data fields but functionally identical in structure, which still reads as repetitive to a searcher scanning several of your listings in a row. A workable template inserts enough real, page-specific detail (not just a swapped product name) that two descriptions from the same template don’t read as interchangeable. For local or location-based pages, the same principle applies: a service area or city name belongs in the description when it’s genuinely relevant to that page, not pasted into every page on the site regardless of relevance, which functions as a weaker version of the keyword-stuffing problem above.
Testing and measuring what actually works
Google Search Console’s Performance report is the practical tool for this. It shows impressions, clicks, and click-through rate broken out by page and by query, which lets you find pages with relatively high impressions but a click-through rate that’s noticeably below comparable pages, a useful signal that the snippet (title, description, or both) may be underperforming relative to its ranking position.
There’s no official Google guidance on how long to wait before judging whether a description change worked. As a practical matter, the more impressions a page accumulates per day, the faster you’ll have a statistically meaningful comparison; lower-traffic pages need proportionally longer to produce a reliable signal. Treat “a few weeks” as a common, reasonable starting point precisely because it’s a rule of thumb practitioners use to gather enough impression volume, not because Google has set that window as a minimum.
A workable testing habit: change one variable at a time (the description, not the description and the title simultaneously), record the date of the change, and compare a similar trailing window before and after rather than eyeballing a single day’s numbers.
The practical takeaway
A meta description has exactly one job: convince someone scanning a results page that your link is the one worth clicking. It doesn’t move rankings, and Google may rewrite or ignore it depending on the query and on what AI-generated summarization is testing at any given time. What stays in your control is writing something specific, honest, and genuinely differentiated for each page, sized to fit comfortably within the rough character ranges that tend to survive truncation, and checked periodically against real Search Console data rather than written once and forgotten.