SERP Snippet Preview

Simulate how your title and meta description are likely to render in Google on desktop and mobile, with real line wrapping and grapheme-safe measurement. Compare wordings side by side, import a live page, and see what could make Google rewrite your title.

Variants

Result context and rendering model

Query highlighting is illustrative only: Google bolds terms it considers related as well, and picks the snippet text for the query, so a real result may share none of this wording. Bold text is also wider than the text that was measured, so a highlighted line can run slightly past the modelled column. The favicon is a placeholder tile, never the real one: fetching a site's favicon here would tell that site who is using this tool.

devdome.com devdome.com › tools
Free SERP Snippet Preview Tool for Google Titles | DevDome

Preview your Google snippet with grapheme-safe measurement and real line wrapping. Compare title variants for desktop and mobile before you publish.

Modelled on a wide desktop result: a roughly 600 px text column, one line of title at 20 px and about two lines of snippet at 14 px. Google has never published these numbers and they move with layout changes.

An approximation of one common layout, model version 2026-07-26. Anything cut here is cut by this simulation, not by Google. Google builds the title link and the snippet automatically, from the title tag, headings, other page text, links to the page and Open Graph, and it can change them per query. This preview is an approximation of one common layout, not a guarantee.

Stars, FAQ rows, sitelinks and breadcrumb names are rich results built from structured data, not from these two tags, so none of them can appear here. Check your structured data separately, and read every tag in the head with the Meta Tag Checker.

Variant comparison

Every variant measured against both device models, so you can see which wording survives in the narrowest layout. Widths are single-line measurements of your text; the range is where this model expects shortening to begin.

A share link carries your drafts in the URL fragment, which browsers never send to a server, so the text stays between you and whoever you send the link to. Exports and drafts never leave this browser either.

 

Title rewrite risk

Google replaces title links it considers half empty, boilerplate, obsolete, keyword stuffed or inaccurate. These checks look for evidence of each category and name it. Nothing here predicts what Google will do, and a check that had nothing to read says so instead of passing.

How this preview measures your snippet

Google does not count characters. Your text is laid out in a font at a size inside a column of a certain width, and whatever does not fit is cut. This tool does the same thing: it measures your exact text with canvas rendering in the chosen font, wraps it inside a container of the modelled width, then clamps it to the number of lines that layout shows. Measurement works on grapheme clusters, so an emoji, a flag or a letter with combining accents is never cut in half, and text with no spaces (Chinese, Japanese, Korean) wraps between characters the way a browser wraps it.

What it cannot do is promise the result. Google's own documentation says title links and snippets are generated automatically, from the title tag, headings, other page text, links pointing at the page and structured data, and that snippets are usually built from page content that matches the query. So the numbers here are a range with a version date (2026-07-26), not a limit, and the rewrite-risk section tests the things Google documents as reasons it replaces a title rather than guessing a score.

Use it when writing new pages, when Google keeps replacing a title you like, or when tightening descriptions before a content refresh. Then track which titles actually earn clicks: DevDome Analytics shows pageviews and real human visitors per page.

Written against Google's documentation: title links · snippets

Title and meta description FAQ

Is this exactly what Google will show?

No, and no tool can be. Google generates the title link and the snippet automatically: the title link can come from your title tag, a visible heading, other text on the page, Open Graph tags or even the text of links pointing at the page, and the snippet is usually assembled from page content that answers the search someone typed. This tool simulates one common layout so you can see roughly where text runs out of room, compare wordings, and check the things that make Google replace your title. Treat the pixel numbers as a range, not a rule.

How long should a title tag be in 2026?

Google publishes no character or pixel limit. In the desktop layout this tool models, titles start being shortened somewhere around 540 to 600 pixels of rendered width, which is roughly 50 to 60 average Latin characters. Width is what matters, not count: a title full of W and M runs out of room far earlier than one full of i and l. Front-load the words that matter so a shortened title still reads correctly.

How long should a meta description be?

Around 150 to 160 characters is the usual advice and matches the roughly two lines the desktop layout here shows. Mobile shows a narrower column over more lines. Google frequently ignores the description entirely and builds the snippet from page text that matches the query, so treat the description as your preferred opening rather than as guaranteed copy.

Does Google truncate by characters or pixels?

By rendered width. Text is laid out in Google's own font at its own size in a column of a certain width, and what does not fit is cut with an ellipsis. That is why two titles of identical character count behave differently. This tool measures your text with canvas rendering in the same font family and size it draws, then wraps it inside a container of the modelled width, which is closer to what a browser does than any character count. It is still an approximation: we do not know Google's exact column width, and it changes.

Why did Google rewrite my title?

Google documents the cases: titles that are half empty or generic, titles repeated as boilerplate across a site, obsolete titles naming an old year, titles stuffed with repeated keywords, and titles that do not match what the page is actually about. The rewrite-risk check on this page tests your title against each of those categories, and when you import a URL it compares the title tag with the page H1, the other prominent headings and og:title, because those are the sources Google can pull a replacement from.

Why is my snippet different from my meta description?

Because the snippet is query-dependent. Google mostly builds snippets from the part of the page that answers the specific search, so the same page shows different text for different queries, and a description that does not mention the query terms is often skipped in favour of page copy that does. Enter a query in the preview to see which words would be bolded, and treat that view as illustrative only.

Does mobile really give titles more room?

No, and the old version of this tool got this wrong. Mobile does not give a title a longer single line: it gives it a narrower column and lets it wrap onto a second line. That means the same title can survive on mobile and be cut on desktop, or wrap into a worse-looking two lines. Both previews here wrap inside a real container instead of measuring one long line, which is why they disagree.

Do meta descriptions affect rankings?

Not directly. The meta description is not a ranking factor, but it influences whether people click a result, and the snippet is effectively your advert in the search results. A specific, honest description within the visible range wins clicks from higher-ranked but blander results.