SERP Preview

See exactly how a title and description will appear in Google, measured in pixels the way Google measures them rather than in characters.

Processed on your device — no upload

termiva serp --desktop
Where
example.com › page
Your page title appears here
And the description below it, which is what decides whether anyone clicks.
Title268 / 580pxfits
Description482 / 920pxfits

Google measures the cut in pixels, not characters. A “60 character” rule is a pixel budget restated for one alphabet — wide letters blow through it early, and Arabic harakat cost nothing at all despite adding to any character count.

title 268pxdescription 482pxverdict fitsnothing uploaded

How to use it

  1. Type or paste the title, description and URL.
  2. Switch between desktop and phone.
  3. Rewrite anything the meter says will be cut.

How it works

A search result is three lines: the title tag, the URL, and the meta description under it. Google calls the whole block a snippet, and a tool that draws one before you publish gets looked for under several names — SERP simulator, Google preview, snippet tester. They are the same question asked once: is any of this going to be cut?

Google decides where to truncate a result by pixel width, not by character count. The budget is roughly 580 pixels for a title and 920 for a description on a desktop result, and less on a phone. Each character here is given a width in ems and the line is added up, so what you see is a measurement rather than a count.

Why the character rule fails. Illinois libraries and MMMMMMMMM WWWWWWWW are both eighteen characters, and the second is more than twice as wide. Every "keep it under 60 characters" guide is a pixel budget restated for one alphabet at one average letter width. It is right on average and wrong on the titles that matter, which are the ones near the edge.

Arabic is where it fails hardest. A character count includes the harakat — the fatha, damma and kasra sitting above and below the letters — and those have no advance width at all. They stack on the letter before them. So a vowelled Arabic title reads as far over the limit and is cut short by whoever wrote it, when the rendered line was never close to the edge. This measures the marks at zero, which is what the renderer does.

The tight band exists on purpose. A line within 5% of the budget is reported as having no room left rather than as a pass. The estimate has error in it, Google re-renders in its own font on its own device, and a single word added later pushes it over. Reporting 578 against 580 as safe is how a page ships truncated.

A worked example

The cut is shown, not described. When a line goes over, the preview shows what actually survives — broken on a word boundary with an ellipsis, the way Google does it — so you can see whether the part that gets cut was the part carrying the meaning. A title truncated after the brand name is a different problem from one truncated after the verb.

Try the case that catches Arabic writers. Put in دمج ملفات PDF بلا رفع and then the same line fully vowelled. The character count changes by roughly half; the pixel measurement does not move. One of those two numbers is what Google acts on.

A short description is a wasted one. The tool flags a description under about 40% of the budget, because that space is free and it is the line deciding whether anyone clicks. Ranking third with a description worth reading beats ranking first with a generic one, and click-through feeds back into position.

What this cannot promise. Google rewrites titles it judges a poor match for the query, and does so on roughly a third of results. Fitting the budget stops your title being cut. It does not stop it being replaced. The two are different failures and only the first is under your control.

To write the tags themselves once the wording is settled, the meta tag generator produces the head block with Open Graph and Twitter cards included. To check what a page already carries, paste its source into the meta tag analyser.

Questions

Why pixels and not characters?

Because that is what Google measures. Two eighteen-character titles can differ in width by more than double, so a character limit is right on average and wrong exactly at the edge, which is the only place the limit matters.

What are the actual limits?

About 580px for a title and 920px for a description on desktop, and roughly 490px and 680px on a phone. Google has never published them; these are the widely measured values and they move occasionally.

Is the measurement exact?

No, and it does not claim to be. It sorts a line into fits, no room left, or will be cut, which is the decision you are making. An exact answer needs Google’s own font metrics and its own renderer.

Why does my Arabic title measure less than I expected?

Harakat take no width — they stack on the letter before them. A character count includes them, so a vowelled Arabic line looks far longer than it renders. The measurement counts them at zero, as the renderer does.

Will Google use the title I write?

Often, but not always. It rewrites titles it considers a poor match for the query on a large share of results, usually pulling from an h1 or the site name. Fitting the budget prevents truncation, not replacement.

Does the description affect ranking?

Not directly — Google has said so repeatedly. It affects click-through, and click-through affects how much traffic a given position earns, which is a real effect by a different route.

Why is a nearly-full line a warning?

Because the estimate has error, the render is not identical, and content grows. A line at 578 of 580 is one word away from being cut, and it will get that word eventually.

Does anything I type get sent anywhere?

No. The measurement is arithmetic running in this page. An unpublished title is often the most sensitive thing on a marketing site and there is no reason for it to leave your machine.

Why does the preview not force a direction?

Because an Arabic result runs right to left in Google as well. Forcing either direction would show you a layout you will never actually meet. Only the URL line is isolated, since a Latin host inside an Arabic line is the one part the bidi algorithm visibly reorders.

Is SERP Preview free to use online?

Yes — free, with no account, no daily limit and no watermark. It runs online in your browser, and because the work happens on your own device it keeps working offline once the page has loaded.

Reading