Review a title and description before publishing
Measure a draft with controlled font stand-ins and compare desktop and mobile editing guidance without treating it as a Google display prediction.
SERP Snippet & Truncation Checker
Free, no signup. Measure title and description widths with consistent font stand-ins and compare them with configurable preview guidance. Google does not publish a fixed pixel cutoff and may rewrite either field.
Compare title variants
Score up to two alternatives beside the title above. Scores are directional writing heuristics, not CTR predictions.
Example data — replace with your own
Runs entirely in your browser — nothing you paste is uploaded or stored. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.
Desktop
example.com
Title
Desc
Mobile
example.com
Title
Desc
Google can choose or reshape title links and snippets based on the search context. Treat every configured width and status here as editing guidance, not a display guarantee.
What this result means ↓| # | Title | Desktop title | Mobile title | Desktop desc. | Mobile desc. | Impressions | Flags |
|---|
Your file is parsed locally in your browser and never uploaded. Flags marked "rewrite risk" are patterns that tend to trigger Google rewrites — hints, not verdicts.
Sample report Illustrative example — use the checker above for a live measurement
Say you enter this title and description for a page on acme.example:
…and the desktop preview returns:
- The title exceeds this product's desktop preview setting. It measures 642px against the configured 580px width; the simulation fades the remainder after "Enterprise." See what PASS/WARNING/ERRORS mean for how the thresholds work.
- The description only warns. 874 of 920px remains within the configured mobile preview width but close enough to review — treat it as a product cue, not a display prediction.
- The practical edit is front-loading. Put the distinct part of the title first and
consider a shorter draft, e.g.
Technical SEO Audits for Enterprise Sites | Acme, then re-check. - For the writing rules behind these numbers, see the title tag and meta description guides.
How to use it
- Type or paste your title tag and meta description into the Single check form. A live character count sits under each field.
- Add the page URL so the preview shows a realistic domain, favicon, and breadcrumb.
- Read the two previews — Desktop and Mobile — side by side. Text beyond the configured preview width is faded, and each has a guidance badge.
- Check the width meters under each preview for the measured width against the selected preview setting; toggle Dark SERP or Copy shareable link as needed.
- Got a site export? Switch to the Bulk (CSV) tab, map your columns, and check every row at once with a downloadable results CSV.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Rate this tool
This checker measures title-tag and meta-description widths with consistent font stand-ins and compares them with configurable preview settings. Read the title tag and meta description guides for the writing rules behind the numbers.
What the results mean
Every field gets a pixel width and a status colour on the meter, rolled up into a badge per device:
- PASS (green) — the text fits comfortably within this product's configured preview band for that device.
- WARN (amber) — the text is past the product's warning threshold but remains inside its configured preview width.
- ERRORS (red) — the text exceeds the configured preview width; the faded tail shows the portion outside that product setting, not where Google is guaranteed to cut it.
| Rating | Desktop title | Mobile title | Character count |
|---|---|---|---|
| Pass | ≤ 480 px | ≤ 700 px | A rough secondary check |
| Warn | 481–580 px | 701–920 px | Measure rendered pixels |
| Fail | > 580 px | > 920 px | Never decide by characters alone |
In the Bulk tab, each row also carries text flags:
- missing title / missing description — the field is empty in that row.
- duplicate title — the exact title appears on more than one row in the file.
- rewrite risk — product heuristics for patterns worth reviewing, such as all-caps titles, very short titles, keyword repetition, boilerplate prefixes, or emoji. They do not predict a rewrite.
How it works
Everything runs client-side. The tool draws your text onto an off-screen HTML canvas and calls
measureText with controlled web fonts — Arimo (metrically compatible with Arial)
for desktop, Roboto for mobile — to get a consistent rendered pixel width. Because measurements depend
on the font, the tool waits for document.fonts.ready before computing, so numbers come
from the real metrics rather than a fallback face.
A binary search finds the longest prefix that fits the configured preview width, which drives the faded tail in the simulation. The product settings live in one small config file and carry a last verified date that hides itself once it goes stale.
Features
- Consistent measured-width title and description previews using Arial- and Roboto-metric web fonts.
- Separate desktop and mobile simulations with consistent font stand-ins, single-line vs. wrapping titles, and configurable per-device preview widths.
- Live faded-width preview plus a measured-width meter and guidance badge per field.
- Favicon-style site marker, site name, and breadcrumb rendered from the URL you enter; Dark SERP toggle.
- Shareable links that encode your title/description/URL in the URL fragment.
- Bulk CSV/TSV mode with column mapping, duplicate + rewrite-risk detection, and results export — all parsed locally.
Limitations
Google can pick and reshape snippets and title links based on search context, so the configured preview widths are editing guidance, not published limits or display guarantees. The tool only shows a verification date after live-SERP calibration, and hides stale dates. The previews are a faithful mock, not a live pull from Google; they don't fetch your page, render rich results (sitelinks, ratings, dates), or reflect personalisation. The "rewrite risk" flags are heuristics that flag patterns Google tends to rewrite, not verdicts.
Frequently asked questions
Why measure title tags in pixels instead of characters?
Google does not publish a fixed pixel cutoff for title links or snippets, and it may rewrite either field. Proportional text still means an “m” takes more space than an “i.” This tool uses consistent Arial-compatible and Roboto font metrics to compare drafts with configurable preview widths; the result is guidance, not a guarantee of Google’s display.
How many pixels wide can a title tag be before it truncates?
Google does not publish a fixed cutoff. This tool currently uses configurable 580px desktop and 920px mobile preview settings, with a warning band below each one. Those values are product guidance, not Google limits or a prediction of where a real result will be shortened or rewritten.
Will Google always show the meta description I write?
No. Google primarily creates snippets from page content and may use the meta descriptionThe meta description is an HTML head tag — `<meta name="description" content="…">` — that suggests a short summary of the page for the search snippet. It's not a Google ranking factor, and Google rewrites it the majority of the time, but a good one can still lift click-through. when it better describes the page for a search. Treat every width result and rewrite-risk pattern here as editing guidance, not a rule or display prediction.
What are the mobile and desktop previews showing me?
Two side-by-side mock listings — desktop (Arial-metric font) and mobile (Roboto-metric font) — with your URL, title, and description compared with configured preview widths. Text beyond a product setting is faded, and a meter reports measured width with a guidance badge.
Can I check a whole site export at once?
Yes. The Bulk (CSV) tab takes a Screaming Frog, Sitebulb, or CMS export, lets you map the title/description/URL columns, and checks every row in your browser. It flags drafts beyond the configured preview widths, duplicate titles, and heuristic rewrite-risk patterns, then lets you export the annotated results as CSV. The file is parsed locally and never uploaded.
Feature requests for Serp Snippet Checker
Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
Where this tool helps
Common use cases
Compare title alternatives against one query
Score up to three candidates with transparent writing heuristics and optional competing titles while keeping the score distinct from CTR or ranking performance.
Audit a crawl or CMS export in bulk
Map title, description, URL, and optional joined GSC columns, then check every row locally for configured width statuses and review cues.
Find duplicate, missing, and rewrite-risk patterns
Surface exact duplicate titles, empty fields, all-caps, very short, repeated-keyword, boilerplate-prefix, and emoji hints without claiming Google will rewrite them.
Prioritize review with joined impression evidence
Use optional impressions and CTR to rank rows that also cross a configured width, then export the annotated evidence for editorial follow-up.
Watch the full workflow
SERP Snippet & Truncation Checker walkthrough
Read the transcript
SERP Snippet & Truncation Checker
This beginner walkthrough explains what a search snippet is, checks one fictional title and description, compares desktop and mobile previews, tests alternative titles, audits six fictional rows from a local C-S-V, explains every important flag, and downloads the finished review file.
Step 1
A search snippet is the title, page address, and description people may see in search results. This tool lets you preview a draft before publishing. It measures the title and description with consistent font settings, compares them with the tool’s desktop and mobile guidance, and shows when text extends past those settings. Everything runs in your browser.
Step 2
Google does not publish one fixed pixel cutoff for every result. It can also replace a supplied title or description with text from the page. So this preview is editing guidance. It helps you compare drafts consistently, but it cannot guarantee exactly what Google will show, where a real result will be shortened, or whether changing the text will improve rankings or clicks.
Step 3
Use Single check when you are writing one page, comparing a few title ideas, or reviewing how a result may look on desktop and mobile. Use Bulk C-S-V when you have a crawl or content-management export and want to find long, missing, repeated, or suspicious drafts across many pages. Optional impression data can help you decide which rows to review first.
Step 4
For one page, enter the title tag, meta description, and page U-R-L. You can also add comma-separated search terms. The preview bolds simulated matches for those terms and includes that bold styling in the measurement. Character counts are shown too, but pixel width is more useful because wide letters take more room than narrow letters.
Step 5
Select Try an example. The tool fills a clearly labeled fictional Acme page, including a long title, a long description, a page address, and two search terms. The browser waits for the controlled fonts before measuring. The result gives us realistic problems to interpret without using customer data or claiming that this is a live Google result.
Step 6
On desktop, the title measures six hundred eighty-five pixels against this product’s five hundred eighty pixel setting. The description measures one thousand one hundred forty-two against nine hundred twenty. Both fail the configured guidance, so the tail is faded. That faded area means outside this tool’s setting. It is not a promise that Google will cut the real result at that exact word.
Step 7
The same text behaves differently in the mobile model. The wrapped title measures five hundred forty-one pixels against nine hundred twenty and passes. The description measures one thousand one hundred thirty-six against six hundred eighty and fails. This is why a single character rule can be misleading: the font, device treatment, and actual words all affect the measured width.
Step 8
The example receives a title-writing score of sixty-one out of one hundred. The tool notes that it includes a useful qualifier and the chosen keyword. This score is a transparent writing checklist, not an estimate of click-through rate, ranking, traffic, or revenue. Use the reasons to improve a draft, then choose language that accurately matches the page.
Step 9
Open Compare title variants to place two alternatives beside the current title. You can also paste titles already appearing for the same search. Here, one alternative leads with the keyword and keeps a brand suffix, while another uses a useful qualifier. The scores help explain differences, but the biggest number is not automatically the best choice. Accuracy and search intent still come first.
Step 10
Dark S-E-R-P changes the mock result to a dark theme so you can inspect both appearances. Copy shareable link stores the current draft and comparison fields in the link, which is useful for review. These controls change how the draft is reviewed; they do not fetch Google, load the real page, add rich results, or simulate personalization.
Step 11
For many pages, switch to Bulk C-S-V and choose a crawl or C-M-S export. This fictional six-row file contains U-R-L, title, description, impressions, and click-through-rate columns. It is parsed locally in the browser and never uploaded. The tool does not sign in to Search Console or fetch performance data on its own.
Step 12
Before running, confirm which columns contain the title, description, and U-R-L. This file maps Title one, Meta Description one, and U-R-L automatically. Impressions and C-T-R are optional. They help sort affected pages by supplied evidence, but they do not change whether a title or description passes the configured width guidance.
Step 13
Select Check all rows. The browser measures every title and description with the same model, counts exact duplicate titles, keeps missing fields visible, and adds deterministic hints for writing patterns worth reviewing. The result is an annotated inventory. It does not rewrite pages automatically, and none of the flags is a final editorial decision.
Step 14
All six rows were checked. One title exceeds the desktop setting, while none exceeds the mobile title setting. One description exceeds the desktop setting and three exceed the mobile setting. The file also contains two duplicate titles and two rewrite-risk hints. These totals show the size of the review queue; they do not tell us that every flagged field must be changed.
Step 15
Worst truncation offenders sorts affected rows using the impressions already present in this file. The long guide leads with twelve thousand five hundred impressions. Two service pages follow with eight thousand two hundred and six thousand one hundred. This helps allocate review time, but it does not prove that the current title or description caused the supplied click-through rate.
Step 16
Rows two and three contain the same exact title, so both receive a duplicate-title flag. The pages have different U-R-Ls, descriptions, impressions, and click-through rates. The flag proves only that the title text repeats inside this file. It does not prove keyword cannibalization, tell us which page should rank, or decide which title should change.
Step 17
The title S-E-O receives a very-short rewrite-risk hint. Another row is flagged for all caps and repeated meaningful words. The last row has no title and is marked missing title. Its measured width is zero, but that does not make the empty field a useful pass. Rewrite-risk means inspect the draft and page context. It does not predict that Google will replace the text.
Step 18
Export results C-S-V downloads a header plus the six analyzed rows. This verified file preserves every U-R-L, source title, source description, measured width and status, supplied performance field, and review flag. Keep it with the original export so an editor can understand why each row surfaced and reproduce the review later.
Step 19
Pass means the text fits comfortably inside the product’s configured band. Warning means it is beyond the warning threshold but still inside the configured preview width. Fail means it crosses that width. These labels support consistent editing. A pass does not guarantee Google will use the text, and a fail does not prove exactly where Google will shorten or replace it.
Step 20
For one page, enter the draft, U-R-L, and relevant search terms. Compare desktop and mobile, then test clearer alternatives. For a site export, verify the mapping, run the local audit, inspect the highest-value affected rows, and export the handoff. Before editing, read the real page and confirm its purpose, audience, and search intent.
Step 21
The checker uses controlled font stand-ins and product settings, not a live Google result. It does not model every device, rich treatment, experiment, language behavior, or personalized search context. Google may build different text from the page. After a careful edit, publish through the normal review process, then use Search Console and real result checks to learn what actually happened.
Use the preview to improve drafts. Use real evidence to decide.
Use the measurements to find drafts worth reviewing, not to promise a specific Google display. Save the exported evidence, confirm what each page is meant to rank for, make the clearest useful edit, and then watch Search Console and real results after publication.
Common issues & how to fix them
- Error Search title is missing Fix: Add a unique, descriptive HTML title that names the page’s primary topic and matches its visible content.
- Warning Search title is likely to truncate Fix: Rewrite the title so its measured pixel width fits the preview, placing the distinctive topic before lower-priority branding.
- Error Meta description is missing Fix: Add a page-specific meta description that accurately summarizes the content and gives searchers a reason to choose the result.
- Warning Meta description is likely to truncate Fix: Shorten the meta description until it fits the tool’s pixel-width limit, preserving the main benefit and differentiator near the start.
- Warning Search title is unusually short Fix: Add accurate, distinctive page context while keeping the title concise and aligned with the visible content.
- Warning Meta description is unusually short Fix: Add a concise page-specific summary and value proposition, while recognizing that Google may rewrite the snippet.