What is a SERP Preview?
A SERP preview renders your title, URL and description the way a search result looks, so you can see how much of each line survives. It exists because Google truncates by rendered width rather than by character count: a title of 55 wide capitals can overflow the space that 70 narrow lowercase letters fit into.
The limits are measured in pixels. Google cuts a title at roughly 580 px on desktop and 920 px on mobile, and a description at about 920 px desktop and 680 px mobile. This tool estimates the width of each glyph in em units and approximates the real rendering closely enough to predict where the ellipsis lands — which is the practical question, since text after the cut is not read.
The page URL matters too. Google shows a breadcrumb-style line above the title, built from the path segments, and a URL of slug words separated by hyphens is rendered with spaces. That line is one of the few parts of a result you fully control, so it is worth reading before publishing.
How to preview a Google search result
- Type the title tag. The tool reports its approximate pixel width and flags whether it fits on desktop, on mobile only, or neither.
- Paste the page URL to see the breadcrumb line. Hyphens become spaces and path segments become the steps of the trail, so a keyword-heavy slug reads better than an ID.
- Optionally enter the site name to be appended, which is how most sites build a title — this changes the width and therefore whether it truncates.
- Write the meta description and watch the same measurement run against it. The target is under about 920 px on desktop and 680 px on mobile.
- Compare the desktop and mobile panels. A description that fits comfortably on desktop regularly truncates on a phone, and the mobile panel is the one with less room.
SERP Preview limits and rules
| Item | Limit |
|---|---|
| Desktop title | Truncated at roughly 580 px, which is about 55–60 characters of average English text |
| Mobile title | About 920 px — on mobile the title wraps to two lines, so it holds more |
| Desktop description | About 920 px, roughly 155–160 characters |
| Mobile description | About 680 px, roughly 110–120 characters |
| Measurement | Estimated from per-glyph advance widths, not rendered in Google's own font |
| Breadcrumb | Derived from the URL path with hyphens shown as spaces, as Google displays it |
| Dates and ratings | Not previewed — Google inserts these from structured data or page content |
| Site name line | Shown above the URL on mobile, as Google does for recognised brands |
| Rewriting | Google rewrites about a fifth of titles and most descriptions, so the preview is a guide, not a guarantee |
| Not covered | Rich results such as FAQ, breadcrumb and product snippets, which use their own layouts |
When to use it
- Writing a title tag and description before publishing, so the whole sentence is shown rather than trailing off into an ellipsis.
- Checking whether a long headline still fits once the site name is appended — the commonest cause of an unexpected truncation.
- Reviewing an existing page that gets impressions but few clicks, and finding the description is cut before the reason to click.
- Repairing URLs produced by a CMS, where hyphens and meaningful path segments read far better in the breadcrumb line than a numeric ID.
- Comparing a title against its mobile rendering, which is where most traffic now comes from and where the space is tightest.
Is it private?
Everything runs inside your browser. Your text and files are never uploaded, never stored and never seen by anyone else — including me. You can use the tool with the network tab open and watch no request leave the page. Closing the tab erases the input.
Frequently asked questions
Around 55–60 characters for the desktop limit, or roughly 580 pixels. Character count is only a proxy — the width depends on the letters used, since m and w are far wider than i and l. The pixel estimate here is the more reliable figure.
No. Google rewrites a significant share of titles when it judges the page content or a query to be better served by an alternative, and it frequently generates its own description from a passage on the page. A well-written description is still worth having, because it wins in the cases where it is used.
Under about 920 pixels on desktop and 680 on mobile, which is roughly 155 characters and 120 characters of ordinary English text respectively. There is no ranking benefit to a longer one; the only purpose is the click.
Because that is what Google's results show. Path segments are displayed as a breadcrumb with hyphens replaced by spaces, so /tools/converters/unit-converter reads as nhrepon.com › tools › converters › unit converter. Hyphen-separated slugs are therefore the right choice for readability in the result.
Not directly — Google has said for years that the meta description is not a ranking factor. It influences the click-through rate, which is why it is worth the effort, and a strong description is often the difference between two results competing for the same query.
Related tools
Written and maintained by Md. Nur Hossain Repon.