Google SERP Simulator

How it works

1. Take the title, meta description and URL you type — or fetch a page's <title> and <meta name="description"> through the SSR checker's endpoint (raw HTML, no JavaScript, nothing stored)
2. Measure the width of each field in pixels with the browser's canvas, in the font Google renders: Arial 20px for the title, 14px for the description and URL breadcrumb
3. Desktop: cut the title on a word boundary when it exceeds 600 px; cut the description when it exceeds 920 px in total or two lines of 600 px, and add the ellipsis
4. Mobile: wrap at 348 px and cut the title after 2 lines and the description after 3 lines
5. Build the breadcrumb Google shows from the URL: origin, then each path segment separated by ›; prefix the description with today's date when the date option is on
6. Report findings: missing or cut fields, character counts against the usual 30–60 (title) and 70–160 (description) guidance, a word repeated in the title, capitals or a query string in the URL, and whether the search query's words appear in the title, description and URL

About search snippets and how Google truncates them

A search snippet is the three lines Google shows for your page: the site name and breadcrumb URL, the blue title, and the grey description. Google composes it from your title tag, your meta description and the page itself — and it truncates each part not by character count but by pixel width. A title of 55 characters in narrow letters fits; the same count in wide capitals does not. This simulator measures your text in the same font and size Google uses and shows where the cut lands, on desktop and on mobile, so what you see here is what a searcher sees.

The limits are observations of the live google.com layout as of September 2026, not a published rule: about 600 px for a desktop title on one line, about 920 px (roughly two lines) for a desktop description, two lines of title and three lines of description on mobile. Google changes these from time to time, so the constants live in one place in the tool and are updated when the layout changes. Character counts are shown alongside as the familiar guide — around 30 to 60 characters for a title and 70 to 160 for a description — but the pixel width is the number that decides.

Google rewrites titles and descriptions more often than most people expect. It shortens titles that overflow, replaces ones that repeat the brand or the same words, and generates its own description when the meta description is missing, too short or does not match the query. The findings list points at the patterns that most often trigger a rewrite — a cut title, a repeated word, a missing description — without claiming to predict what Google will do; the preview shows your text as written, which is the version you control.

Two optional inputs make the preview more realistic. A search query bolds its words in the description, the way Google highlights matching terms, and the findings tell you whether those words appear in the title, description and URL at all. The date toggle prefixes the description with today's date the way Google does for articles and dated pages, which costs about 15 characters of the description's budget — worth seeing before you write to the limit. Everything runs in your browser; the only server request is the optional fetch of a live page, which returns the page's title and description and stores nothing.

Frequently asked questions

How long should a title tag be?

Long enough to say what the page is, short enough not to be cut: on desktop that means up to about 600 pixels, which is roughly 50 to 60 characters in mixed-case Latin text and fewer in capitals or wide scripts. The simulator shows the exact width of your title and the character where the cut would land. There is no penalty for a longer title — Google simply shows less of it, or rewrites it.

How long should a meta description be?

Google shows about 920 pixels of description on desktop, roughly 150 to 160 characters, and around three short lines on mobile. Anything beyond is cut with an ellipsis. Descriptions are not a ranking factor; they influence whether people click. Write for the reader, keep the key message in the first 100 characters, and check the mobile preview, which cuts earlier.

Why does the tool measure pixels instead of characters?

Because Google does. Characters differ in width — an "i" is a third of a "W" — so two titles of identical length can fit or overflow. The tool draws your text on a hidden canvas in the font and size Google renders (Arial 20 px for titles, 14 px for descriptions) and reads the width back. Character counts are shown as a rough guide only.

Will Google show my title and description exactly like this?

Not always. Google rewrites a title when it overflows, repeats words, is missing, or does not describe the page well, and it often generates a description from page content when it thinks a passage matches the query better. The simulator shows your text as written and flags the patterns that most often trigger a rewrite; it cannot predict Google's choice for a given query.

What does the search query field do?

Google bolds the words of the query where they appear in the description, which draws the eye. Enter the query you want the page to rank for and the preview bolds its words the same way; the findings also tell you whether each word appears in the title, description and URL — a fact about your text, not a recommendation to stuff keywords.

Can I load the title and description from a live page?

Yes. Paste a URL in the field at the top and the tool fetches the page through the same endpoint as the SSR checker: it reads the raw HTML without running JavaScript, extracts the <title> and <meta name="description">, fills the fields and discards the page. If the page builds its title with JavaScript, the fetched value is what a crawler sees on first fetch — which is worth knowing too.

Is anything I type stored?

No. The preview and all measurements happen in your browser. The optional page fetch sends only the URL to our server, which returns the extracted fields, sets no-store and keeps no log.