Meta description length: no limit, only truncation
Google sets no limit on how long a meta description can be; it truncates the snippet as needed, typically to fit the device width. That is the wording of Google's own documentation on snippets, last updated on and checked on . What matters is how much of a description survives the cut, and that depends on the screen.
Where the cut falls
The cut falls at a width, measured in pixels on the screen that shows the result, so the same description can end in different places on a phone and on a desktop. Characters are a rough proxy for that width and no more.
Letters differ in width. A line of wide letters such as W and M fills the space sooner than a line of narrow ones such as i and l, so two descriptions of identical character count can be cut at different words. A counter that reports 150 characters says nothing about which of those characters a reader will see.
Crawlers estimate the width for you. Screaming Frog's SEO Spider, for example, flags descriptions over 985 pixels and over 155 characters, and its documentation describes the pixel figure as an estimate that tries to match the latest truncation points, which Google adjusts frequently. As checked on , those are the flags it raises. Treat any such figure as a reading of today's screen, with the date it was taken.
A working target
Aim for roughly 120 to 155 characters. On a phone the important part stays visible, and on a desktop the description fills its lines without running long. This is a target for writing, not a limit: nothing breaks above it, and nothing is rewarded for landing inside it.
The range is only useful alongside a preview of the actual text. Two descriptions of the same length can be cut at different words, so the check that settles it is reading the snippet as it will be shown, in a preview that renders the width, before the page is published.
Put the point first
Truncation removes the tail, so the tail is where anything optional belongs. The opening words carry what the page is and why somebody would choose it; detail that only helps a reader who has already decided can sit at the end and be lost without harm.
Compare two descriptions for the same product page on example.com:
- "Welcome to our store, where we have been helping customers since 2010. Browse the Atlas 40 backpack, a 40-litre bag with a laptop sleeve."
- "Atlas 40: a 40-litre travel backpack with a padded laptop sleeve and side access. Fits most cabin-bag limits. Free returns."
The second survives any reasonable cut. The first spends its opening on words that would fit on every page of the shop.
Checking what is actually shown
The description you wrote and the snippet a reader sees are two different texts, so the check has to look at the second. Search for the page in Google, by a query it should answer or by its address, and read the result as it appears; repeat on a phone, since the narrower screen cuts sooner.
For more than a handful of pages, a crawler does the measuring. Screaming Frog's SEO Spider shows each description with its estimated width and a snippet preview; standalone previews such as Portent's SERP Preview Tool and the Mangools SERP Simulator render a single description the same way. Their widths are estimates of today's screen, which is why a live result remains the final word.
When the description is not shown at all
A description of perfect length is still a suggestion. The engine can choose text from the page instead, usually when the written description does not match the query or says nothing specific, and length does not change that. The parent section on meta tags covers why that substitution happens and what makes it less likely.
How to write one
Describe this page, not the site
The description competes with nine other results that are broadly about the same subject. Something true and specific about this page beats a sentence that could sit on any of them.
Lead with what distinguishes it
Where several pages differ in one attribute, that attribute belongs at the front. Pages that share the same description are a separate problem, covered under duplicated titles and descriptions.
Write plainly
A description is read in a second by somebody scanning a list. Short sentences and concrete nouns survive that reading; slogans do not.
Say what the click leads to
Where the page lets a reader do something, such as compare plans, download a file or book a slot, name that action in the description. A reader choosing between results wants to know what happens next, and a specific verb answers that faster than an adjective.
Keep it true to the page
A description that promises what the page does not deliver earns a click and a quick return, and it is also the kind the engine is most inclined to replace.
Where nobody wrote one
Large sites rarely have a description on every page; the ones nobody got to are filled with whatever the engine assembles. Filling those gaps from what each page says, without touching the descriptions you wrote, is what meta titles and descriptions written where missing covers.
FAQ
How long should a meta description be?
There is no required length: Google sets no limit and cuts the snippet to fit the screen. A working target of roughly 120 to 155 characters keeps the important part visible on a phone and fills the lines on a desktop. Check the actual text in a preview, because width depends on the letters, not only on their count.
Does Google cut by characters?
No. It truncates the snippet as needed, typically to fit the device width, so the cut is a matter of pixels on a given screen. Character counts are a convenient approximation, and two descriptions of the same count can be cut at different words because wide letters take more room than narrow ones.
Is a long description penalised?
Nothing in Google's documentation describes a penalty for length. A long description is simply cut where the screen runs out, so the cost is that readers may not see its end. That is why the point belongs at the front and anything optional at the back.
Should I count characters or pixels?
Write against a character target, because it is easy to keep in your head, and check against pixels, because that is where the cut falls. Crawlers and snippet previews estimate the width for you; treat their figures as a reading of today's screen, since the truncation point moves.