Content
SERP Snippet Preview
Preview your title and description in Google
Write a title tag and meta description and see them rendered as a desktop and a mobile result, measured in pixels rather than characters, with the truncation point marked and the space taken by the favicon, site name and date accounted for.
Get early accessWhat it returns
- A desktop and a mobile rendering of the title, the breadcrumb or URL line, and the description.
- The measured pixel width of each line against the width Google actually allows, with the cut-off point marked in the text.
- What the favicon, site name and any date prefix take away from the space left for the title.
- A plain warning when the text will be truncated, instead of a character count that passes and then truncates anyway.
When this matters
You rewrite forty titles in a spreadsheet, keep every one under the character count everybody quotes, ship them, and half still get cut mid-word. The reason is that the font is proportional: a title full of narrow letters fits comfortably where one full of wide letters does not, and a character budget cannot tell the two apart. Measuring the rendered width is the only check that matches what Google does.
How to answer this today
Site audit covers the version of this problem that scales: it crawls the site and reports titles and descriptions that are missing, duplicated, or long enough to be truncated, across every page at once. What it cannot do is show you a title you have not published yet, which is the one job this tool has.
Site auditWhy this is harder than it looks
Google rewrites the text
Titles are frequently replaced with the H1 or the site name, and the description shown is very often lifted from the body copy rather than the meta tag. A preview is an honest render of what you proposed, never a promise of what will appear.
The target keeps moving
The fonts, sizes and container widths Google uses change without notice, and every change moves the truncation point. A preview is only as current as the measurements behind it, so those measurements have to be dated and maintained.
Mobile is not one width
Mobile results differ by device width and pixel density, so a single mobile preview is a representative case rather than the case. The useful output is the margin you have, not a pass or fail.
The URL line is unpredictable
Google shows a breadcrumb built from the site structure more often than the raw URL, and that affects both the width and the way the result reads. Rendering the raw URL would make the preview look cleaner and less accurate.