Labs

SERP Snippet Preview

See your title and description the way Google will show them — desktop and mobile — with pixel meters that tell you where the cut-off is.

Type a title or import a page
Snippet —
Device
Preview —
The Google result preview will appear here
Settings favicon from site · no pasted HTML
How It Works

How to Use SERP Snippet Preview in 3 Steps

1

Type or import

Enter a title, description and URL — or paste a live URL in Import from a live page and press Import to pull them from the page’s tags. Switch between Desktop and Mobile.

2

Watch the meters

Google cuts titles at about 600 px on desktop and 920 px on mobile, and descriptions at roughly 920 / 1,300 px — not at a character count. The meters measure your text in Google’s actual font sizes and show the cut with an ellipsis, exactly where it would appear.

3

Export

Download the preview as a PNG for a client deck or a ticket, or copy the final title and description. Then paste them into the Meta Tag Generator to produce the tags.

FAQ

SERP Snippet Preview — Frequently Asked Questions

Why pixels and not characters?

Google truncates by available width, so “WWW” uses far more room than “iii”. A 55-character title full of wide capitals can be cut while a 65-character title of narrow letters fits. The meters measure the real rendered width in Arial at Google’s sizes (20 px title, 14 px description) — the same method Google’s own tooling uses.

Will Google show exactly this?

Mostly. Google often rewrites titles (adding the site name, dropping boilerplate) and may pick a different snippet from the page when the description doesn’t match the query. The preview shows what your tags ask for; the limits are accurate as of 2026 but Google changes them from time to time.

How does the date work?

For articles Google prefixes the description with the publish date (“18 Oct 2026 — ”), which eats into the description’s width. Set a date to see the effect; the meter includes it.

Where does the favicon come from?

Your browser loads /favicon.ico from the host in the Page URL field — Toolity never fetches it. If the site has no favicon at that path, a globe icon is shown, which is also what Google does.

Why does fetching sometimes fail — and what is the relay?

Browsers block JavaScript from reading other websites directly (CORS). The tool first tries a direct request; when the site forbids it, the URL only is sent to a public read-only relay (allorigins.win, then codetabs.com) that fetches the page and returns its HTML. The relay sees the URL you typed, nothing else — Toolity has no server and keeps no record. If the relay is busy or the site blocks bots, paste the page source instead: that path is 100% local.

How do I use paste mode?

Open the page in your browser, press Ctrl/⌘+U (view source), select all, copy, and paste into the HTML box. Only the <head> is needed. Paste mode never contacts any server.