How to Write Meta Descriptions That Earn Clicks
How to write meta descriptions that earn clicks: match the search term, lead with the benefit, and stay short enough that Google won't cut it off.
A meta description that earns clicks states the page's single clearest benefit or answer in the first sentence, includes the exact term a searcher typed, and stays short enough (roughly 150-160 characters on desktop) that Google's pixel-width truncation doesn't cut it off mid-word.
A meta description's only job is to get read in the two seconds someone spends scanning a results page, and either earn the click or lose it to the result above or below. Most advice about this stops at "keep it under 160 characters," which is true but incomplete. The length rule matters because of what happens if you break it, not because 160 is a magic number.
What Google actually does with it
Google's own developer documentation is specific on two points that change how you should write these. First, 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. Second, snippets are primarily created from the page content itself, meaning Google will discard your written description entirely and pull a different passage from the page when it judges that passage answers the search query better. Writing a meta description doesn't guarantee Google shows it.
Google also recommends creating descriptions that accurately describe the specific page, as opposed to using the same description across many pages. A reused, generic description gives Google every reason to override it.
Why the character count matters
The truncation isn't really measured in characters, it's measured in rendered pixel width. SEO crawler Screaming Frog has documented this directly: the CSS cutoff in Google's results sits at roughly 920 pixels, rendered in 13-pixel Arial, and Google cuts at a word boundary rather than mid-word. That's why two descriptions of the same character count can get truncated at different points: a line full of narrow letters (i, l, t) fits more text than one full of wide capitals. In practice this lands most desktop snippets around 150-160 characters before a word gets dropped, which is where the common "160-character" rule of thumb comes from. It's a proxy for pixel width, not a rule Google states directly.
A quick check on our own pages
We pulled the live meta descriptions straight off yabado.ai this session rather than guessing. Our homepage sits at 161 characters, right at the edge. Our GEO services page runs 174. Our GEO audit page is 205 characters, meaning Google is very likely truncating the back half of that sentence in real search results right now. The SEO for small business hub and the FAQ schema article both sit comfortably under 150. Checking your own live pages this way, not a template, is the fastest way to catch the ones quietly running long.
The practical rule
Lead with the single clearest benefit or answer in the first sentence, include the exact term a searcher would type, and keep the whole thing under roughly 155 characters so the ending survives truncation instead of getting cut mid-clause. Then accept that Google might swap it out anyway, and make sure the content right below your title tag can stand in as a snippet on its own merits.
Frequently asked
How long should a meta description be?
There is no hard character limit. Google's own documentation states there's no limit on how long a meta description can be, but truncates the displayed snippet to fit the device width, which in practice lands around 150-160 characters on desktop and closer to 120 on mobile before words start getting cut.
Does Google always use the meta description I write?
No. Google's documentation says snippets are primarily created from the page content itself, and it will swap in different text, sometimes a different sentence pulled from the page, when it decides that text answers the specific search query better than the written description does.
What should the first sentence of a meta description do?
It should state the page's clearest benefit or answer on its own, because that's the part most likely to stay visible if Google truncates the rest. A meta description that opens with a vague clause and saves the real value for the end risks having the useful part cut off.
Should every page have a unique meta description?
Yes. Google explicitly recommends creating descriptions that accurately describe the specific page rather than reusing the same description site-wide, since duplicate descriptions give Google no reason to prefer your written text over text it pulls from the page itself.
Does a good meta description help rankings directly?
No. Google's John Mueller said directly in a 2022 Search Central office hours, as reported by [Search Engine Journal](https://www.searchenginejournal.com/google-answers-if-meta-description-matters-for-rankings/449119/), that the meta description is 'primarily used as a snippet in the search results page, and that's not something that we would use for ranking.' He added that a good snippet still makes a page more interesting to click, which is a real business outcome even when it isn't a ranking signal.
More in SEO for Small Business
Internal Linking That Actually Moves Rankings
An internal linking strategy that works: link every page up to its pillar hub, across to related pages, and out to one page that converts.
Keyword Research When Half Your Traffic Is an LLM
How to do keyword research in 2026: the same volume and intent basics, plus a new filter for whether a click is even available anymore.
GBP Optimization That Survives AI Overviews
Google Business Profile optimization for 2026: what still wins the local pack and what it takes to also get cited in AI Overviews.
See how AI describes your brand
A free GEO audit takes about 90 seconds and tells you what ChatGPT, Claude, Perplexity and Gemini actually say about you.
Run a free GEO audit →Written by YaBaDo's AI agents and reviewed by a human before publishing. If you find something wrong, tell us and we will correct it.