SERP Snippet Preview

See how your title, URL and description look in Google on desktop and mobile, with character and pixel counters that mark the exact truncation point.

Enter search result details

Search preview

Desktop result

Fits preview
example.com
Your page title will appear here
Your meta description will appear here

Mobile result

Fits preview
example.com
Your page title will appear here
Your meta description will appear here

Search engines may rewrite titles and descriptions. This preview is an estimate, not a guarantee of how a result will appear.

What a SERP snippet is made of

A Google result has four parts: the favicon and site name, the blue title, the breadcrumb URL line and the grey description. The title normally comes from your title tag, the breadcrumb from your URL and breadcrumb markup, and the description from your meta description whenever Google decides not to rewrite it.

Google measures this text in pixels rather than characters, so a 60-character title built from narrow letters can fit while a 55-character title full of wide capitals is cut. The counters above the preview show both numbers, so you can see which one is about to overflow.

How to preview a snippet

  1. Type or paste the page title and watch the blue line: desktop keeps it to one line, mobile allows up to two.
  2. Add the page URL. The protocol is dropped and every path segment becomes a breadcrumb, the way Google renders it.
  3. Paste the meta description and check the grey lines: two on desktop, three on mobile. The counter turns amber the moment you pass the budget.
  4. Copy the title or description back into your page, or send them to the meta tag generator to produce the finished head tags.

Snippet preview examples

Title that fits

A 52-character title such as SERP Snippet Preview — Check Titles Before They Get Cut
One desktop line and two mobile lines, both marked Full text shown

Title that gets cut

A 95-character title that keeps going with extra keywords appended to the end
Desktop stops after the first line with an ellipsis and the badge switches to Truncated

Description with an ellipsis

A meta description longer than 160 characters
Desktop stops at the end of line two with an ellipsis, while mobile fits one more line before cutting

UrsaKit vs metatags.io, SISTRIX and Seobility

DimensionUrsaKitmetatags.ioSISTRIXSeobility
PriceFree, no sign-upFreeFree tool inside a paid suiteFree
Desktop and mobileBoth, side by sideGoogle card plus social cardsOne previewLength verdict only
Pixel measurementYes, measured on a canvasCharacter countsYesNo
Truncation shownYes, with the ellipsis in placeNoNoNo
Breadcrumb URLPath split into segmentsRaw URLRaw URLRaw URL
LocalesEnglish, Chinese, SpanishEnglishEnglishEnglish
FAQ

Frequently asked questions

Is this SERP snippet preview free?

Yes. It runs entirely in your browser, needs no account and has no limit on how many titles you check.

Do I have to paste my page URL?

No. The title and description previews work on their own; the URL field only fills in the breadcrumb line above them.

Does Google truncate by characters or by pixels?

By pixels. Google renders the title and description at specific font sizes and cuts whatever overflows, so a title of narrow letters can survive past 60 characters while wide capitals are cut earlier. That is why this tool shows both counters.

How long should a title and meta description be?

Aim for roughly 50 to 60 characters, about 580 to 600 px, for the title, and 120 to 155 characters for the description. The counters flag titles under 30 or over 60 characters, and descriptions under 110 or over 160.

Why does Google sometimes show different text?

Google can rewrite the title and description to match the query, and it may pull the description from the page body when it judges that more relevant. The preview shows your own text, so read it as the best case rather than a guarantee.

How accurate is the mobile preview?

It reproduces the mobile result width and line counts with the browser text engine. The exact pixel budget shifts with device width, so use it to catch obvious overruns rather than as a screenshot.

All Tools