Meta Description Length: The Character Band and the Pixel Cut Behind the Snippet

There is no fixed character limit - and that is the point

People ask for a magic number. There is none, because Google renders the description in the font and container of that particular results page and clips it when it runs out of horizontal space. Writable ranges shift with the device, the language, the width of the characters used (a run of capital Ws eats space far faster than lowercase i or l), and even the query, since bolded matching keywords are wider.

So optimise for a range and a structure, not an exact count: front-load the one or two ideas you most want seen inside roughly the first 120 characters, keep a natural full sentence there, and let the rest extend to about 155 if it adds value. If it gets cut mid-thought, at least the important part already showed.

Pixel width, not characters, decides the cut

Because the limit is spatial, the practical goal is "fit inside the box". The table below gives the commonly observed bands; use them as a starting target, then judge by how the page actually looks in a SERP preview, not by the count alone.

Measuring is easy and free: paste your draft into the character counter and read the character count including spaces. Counting characters is a proxy - the pixel reality varies - but staying inside the bands above keeps you comfortably in range.

Does the meta description affect rankings?

Google has stated for years that the meta description is not used in its ranking algorithm. What it does influence is click-through rate, and a compelling description that matches search intent can lift clicks - and more relevant clicks can indirectly help performance. Keyword stuffing does not buy ranking here; it just makes the snippet look spammy and gets the description rewritten or ignored.

Treat the field as advertising for the specific page: state what the page offers, who it is for, and one differentiator, in the searcher's own words.

Writing a description Google will actually show

Google replaces a hand-written description with a chunk of page text whenever it thinks the on-page content answers the query better. You cannot fully control that, but you can make yours more likely to survive:

Match the intent, be specific. A generic "Welcome to our site" is almost always rewritten. Name the concrete outcome the page delivers.

One description per page. Duplicate descriptions across many pages look templated; write per page, or let some fall back to auto-generated text.

Write to end within the safe zone. A complete, natural sentence inside ~120 characters is more likely to be shown than a long list that gets clipped mid-way.

Do not stuff. Repeat keywords and you invite Google to ignore you and pick its own snippet.

Draft and check the whole block with the meta tag generator, which assembles a title and description together so you can see them side by side.

When Google ignores yours and writes its own

Google may override your description in a handful of normal situations: your text does not match the query, the page looks newly created or thin, the description duplicates another page, or the query is a question that the page body answers more directly. A structured answer near the top of the page (which is exactly what the answer-first format does) gives Google good, quotable sentences to pull from - so a page that reads clearly often earns a better auto-snippet than a page whose only optimisation was the meta tag. Run any individual page through the meta analyzer - it checks one URL or pasted HTML at a time - to see whether that page's description is missing, thin or overlong.