SERP Snippet Preview, Explained

After reading this you will know why Google measures your title and description in pixels, how to predict where your snippet gets cut, and how to write titles that survive the cut on both desktop and mobile.

What a SERP snippet preview shows

A search result on Google is built from three parts: a clickable title in blue, a green or gray URL line, and a gray description below it. A SERP snippet preview reconstructs that block from text you type, so you can see the exact result before you publish the page.

The catch that trips up most people: Google does not cut your title after a fixed number of characters. It cuts by pixel width. The letter W is roughly ten times wider than the letter i in the same font. A 60 character title made mostly of W and M can overflow, while a 65 character title full of i, l and t fits with room to spare.

Consider two titles, both 55 characters:

• Will Warm Winter Weather Worry Wheat Farmers Widely? renders around 610 px and gets truncated.
• Little tips to fit slim titles inside tight limits renders around 400 px and fits easily.

Same length, very different fate. That is the whole reason a pixel-accurate preview exists.

When to use it, and when not to

Use a preview whenever you write or edit a page title (<title>) or meta description. That covers new articles, product pages, landing pages, and any page where the search snippet is the first thing a person reads about you.

Do not treat the preview as a promise. Google rewrites titles on a large share of results. Independent studies from 2021 put the title rewrite rate above 60 percent for some query types. Google rewrites a title when it thinks yours is unhelpful: too long, keyword-stuffed, identical across many pages, or a poor match for the query. The preview improves your odds of showing what you wrote. It does not lock it in.

The pixel-width model

The width of a rendered string is the sum of the widths of its characters, plus the small gaps between them. In a proportional font each character has its own advance width. A rough model looks like this:

Here W_{\text{total}} is the total pixel width, n is the number of characters, c_i is the i-th character, and w(c_i) is that character's advance width in the render font at the render size. Google draws desktop titles in roughly 20 px Arial and descriptions in roughly 14 px Arial.

Truncation is a threshold rule. Let L be the pixel limit. Google keeps whole words until adding the next word would exceed L, then appends an ellipsis:

Because the cut lands on a word boundary, your visible title depends on where your words fall, not just the raw width. A single long word near the limit can cost you eight or ten visible characters.

A worked example with the demo data

Load the tool's demo defaults and you get a title, a URL and a description. Walk through how the desktop title width is estimated. Assume the demo title is SERP Snippet Preview Tool, which is 25 characters including spaces.

How character width shapes the limit

Because widths vary, the number of characters you can fit inside 580 px is a range, not a constant. The chart below shows how many characters of a single repeated letter fit inside the desktop title budget.

Real English text averages close to 8 px per character in 20 px Arial once you mix cases and spaces. That gives a practical target of about 580 / 8 ≈ 72 characters, but you should aim lower, near 60, to leave headroom for wide words and to survive minor layout changes.

Reading and interpreting the result

When you look at a preview, check four things in order.

Title fit

Stays under about 580 px on desktop and about 480 px on mobile. If it truncates, move the words that matter most to the front so they survive the cut.

Description fit

Stays under about 920 px, which is roughly 155 to 160 characters of ordinary text. Mobile shows fewer lines, so front-load the sentence that earns the click.

Front-loaded meaning

The first 40 to 50 characters of the title should stand alone. On mobile and in rewrites, the tail is the part most likely to disappear.

Truthful match

The snippet should describe the page. A description that overpromises raises clicks but also raises the bounce back to search, which does you no favor.

Common mistakes

Counting characters instead of pixels is the classic error. A "58 character" title full of wide letters overflows while the counter says you are safe. Trust the pixel measurement.

Padding the description to hit 160 characters is another. Length is not the goal; a clear 120 character description that matches the query beats a padded 160 character one. Google truncates the excess anyway.

Testing only desktop is the third. Mobile titles have a smaller budget, around 480 px, and most searches happen on phones. A title that fits desktop at 560 px will be cut on mobile. Preview both.

The last mistake is assuming the preview is final. Because Google rewrites titles on a large fraction of results, write a clear, honest, well-scoped title and treat the preview as a strong first draft of what searchers will see.

Related tools

The preview handles the search result. When you also need the underlying tags and the social cards, use the Meta Tag & Open Graph Generator, which produces the <title>, meta description and Open Graph markup and previews the Google, Facebook and X cards together.

Related tools

Meta Tag & Open Graph Generator

Generate meta tags and preview the Google, Facebook and X cards.

Keyword Density Checker

Word and phrase frequencies of any text, with stopword filter.

Redirect Chain Checker

Follow every hop: 301s, 302s, loops and chain length.

UTM Campaign URL Builder

Build tagged campaign URLs with correct encoding.

robots.txt Tester

Test which URLs a robots.txt blocks, rule by rule.

Page Size & Request Analyzer

Page weight, request counts and the heaviest resources.