SERP Snippet Preview
Desktop
Mobile
Character counts are the wrong unit
Google truncates a result by how wide the text renders, not by how many characters it holds. Illinois and WWWWWWWW are both eight characters, and one is far wider on screen than the other. That is why two titles of identical length behave differently: one fits, the other ends in an ellipsis. Advice pinned to a character count is a rough proxy at best, and it fails hardest on strings heavy with capitals or heavy with narrow letters.
What the preview measures
Type a title, a URL and a meta description, and the tool draws a desktop and a mobile result and reports the measured width of each line as you type. That measurement is an approximation: it measures your text in your browser using a font close to the one Google uses, which is not Google's own rendering. Treat the working figures the industry quotes — around 600 pixels for a desktop title, around 920 for a desktop description — as observed convention rather than published limits. Google documents no fixed length for either, and it has changed snippet lengths before without notice.
Things that consume width faster than a character count implies:
- Capitals and wide glyphs: W, M, and uppercase words.
- A brand suffix repeated on every page, plus its separator and surrounding spaces.
- Non-Latin scripts. Devanagari, Arabic and CJK glyphs do not follow Latin rules of thumb.
- Punctuation-dense strings such as dates, SKUs and model numbers.
Google frequently rewrites what you wrote
The title in your markup is an input, not a guarantee. Google substitutes its own title link when it judges another string a better match for the query, drawing on the h1, another heading, or prominent on-page text — though it has said the title element remains the source for the large majority of results. Descriptions are replaced more readily, often with a body passage containing the searcher's words. The meta description is not a ranking factor; it only influences whether someone clicks.
How to act on the measurement
Put the distinguishing words first, so the snippet still makes sense after a cut. Do not pad a title to reach a target width, and do not amputate a useful description just to end inside a line — a sentence that runs over is fine if the first clause carries the point. Check both layouts, because they do not break at the same place and neither is reliably the stricter one: the mobile result is narrower but wraps over more lines.
Share this tool with friends
Free to use, no sign-up, works on any phone.
Frequently Asked Questions
Because the cut-off is a width, not a count. Capitals, wide letters such as W and M, or a long brand suffix can exceed the rendered width well before the string looks long by character count. Paste the exact title into the preview and read the measured width instead of counting characters. If the width is comfortably inside the usual working figure, the likelier explanation is that Google rewrote your title rather than truncated it.
Google publishes none, and its documentation gives no fixed length for either — snippets are truncated as needed. The figures most tools work to are roughly 600 pixels for a desktop title and roughly 920 pixels for a desktop description, both derived from observation rather than documentation, and mobile differs again. Treat them as a warning line, not a specification: Google has altered snippet lengths in the past and can do so without notice.
Google replaces the title link when it judges another string a better match for the query, usually drawing on the h1, another heading, or prominent on-page text — though it has said the title element is still the source for the large majority of results. Descriptions are swapped more readily, typically for a body passage containing the search terms. You cannot force your version; a clear, query-relevant, non-boilerplate title makes a rewrite less likely.
No. Google has said for years that the meta description is not a ranking factor. It matters for click-through: it is the line under your title, and a description that answers the query gets clicked more often than one padded with keywords. Google also rewrites descriptions often, so treat yours as the version you would like shown rather than the version guaranteed to appear. Write it for the person reading the results page.
In practice, no. Varying tags by user agent is possible but fragile and discouraged, and since mobile-first indexing Google crawls primarily with the smartphone agent, so a desktop-only variant may never be seen. What is worth doing is checking both renderings, because the measures differ and the same string does not break at the same point. Front-load the words that matter and the title still reads correctly wherever it is cut.
No. It renders what you type into the three fields, so you can test wording before it goes anywhere near a template. It does not request your URL, so it cannot tell you whether the tag is present on the page, whether the page is indexed, or what Google currently displays for that result — check those in Search Console or in a live search. The widths shown are a browser measurement of your text, not Google's rendering.