SERP Snippet Preview

Why pixels decide it, and characters do not

A search result is laid out in a fixed-width container. Text fills the line and then stops, which means the cut lands wherever the pixels run out rather than at a particular letter.

Character counts are a convenient proxy because most English sentences average out to a similar width. The proxy breaks in the cases that matter most:

• Wide characters. Capitals, W, M and the numeral 0 are far wider than i, l and t. A title in title case can overflow while the same length in sentence case fits.
• Brand suffixes. A pipe, two spaces and a brand name is often 12 to 15 characters of pure overhead, appended after the part you wrote and measured.
• Dates and bylines. Google prefixes some results with a date, and the prefix eats snippet width that your description had already claimed.
• Non-Latin scripts. Character limits mean almost nothing outside English, where one character can occupy the width of two or three Latin ones.

The limits worth writing against

Google publishes none of these and changes them without notice, so treat them as working figures rather than as a specification. They are what this preview measures against.

The first 60 characters of a title do more work than everything after them. They are what survives truncation on both layouts, what a rewritten title usually preserves, and what a reader scanning ten blue links actually processes.

What Google does with your tags after you write them

Neither field is a promise. Google rewrites titles when it judges yours a poor fit, and it generates most descriptions from page text that matches the query. Google's own documentation lists what triggers the swap.

A rewritten title is not a penalty and not a bug to chase. It is a signal that the version you wrote answered the query less clearly than a sentence already sitting on your page.

How to preview a Google snippet

Six steps. The fourth is the one that turns a length check into a click-through check.

1. 01

   Paste the title and description you are testing

   Use the strings exactly as they will ship, brand suffix included. A title that fits at 52 characters can fail at 52 characters once a pipe and a nine-letter brand name are appended, because the measurement is pixels rather than letters.

2. 02

   Check desktop first, then switch to mobile

   The two layouts truncate differently. Desktop gives the title one line of roughly 600 pixels; a phone gives it two shorter lines and shows a third line of snippet. A title that survives one often dies in the other.

3. 03

   Read the pixel readout, not the character count

   The readout shows the measured width against the width of the line. Wide letters cost more than narrow ones, so a title full of capitals and Ms will cut earlier than one of the same length in lowercase.

4. 04

   Enter the query you want the page to win

   Matched terms are bolded in the preview the way Google bolds them. Bold text at the start of a snippet is what a scanning reader lands on, so seeing the bolding is closer to a click-through test than reading the string in a spreadsheet.

5. 05

   Front-load the part you cannot afford to lose

   Whatever renders in the first 60 characters survives every layout Google tries, including the rewritten ones. Put the promise there and the qualifier after it, rather than opening with the brand or a category label.

6. 06

   Rewrite until nothing important sits past the cut

   Truncation is only a problem when it eats meaning. A snippet that trails off mid-sentence after the point has landed reads as continuation rather than as a mistake, and it costs you nothing.

Once the wording is settled, the tags still have to reach the page. The meta tags generator writes the full head block including Open Graph and Twitter cards, and the meta tag checker reads back what a live URL is serving right now.

What this preview shows

Frequently asked questions