Free tool · On-page SEO
Free SERP snippet preview
To preview a search snippet, check where the title and description get cut in pixels rather than characters, because a capital M is more than three times the width of a lowercase i. Type a title and description below to see both rendered and cut for desktop and mobile, measured with your browser's own text metrics.
Free, and the measurement happens in your browser. The conflict check against your deployed tags needs a free sign-in.
Desktop preview
example.com
Your title will appear here
Your meta description will appear here, cut where Google would cut it.
- Title
- 0 / 580 px
- Description
- 0 / 990 px
0 characters · 580px to spare
0 characters · 990px to spare
Widths estimated: your browser did not expose text metrics. Characters are sorted into width classes by shape and scaled linearly with font size. It distinguishes a narrow title from a wide one; it is an approximation and not a substitute for measuring the font.
The budgets are widely observed, not published by Google. Google states no pixel limit for either field and has changed the rendering more than once, so treat the cut point as a guide rather than a rule.
AEO depth layer
See the live snippet conflict check
The live snippet conflict check is computed from your own page and costs nothing to run. We ask for a free account because the expensive tools on this shelf stay free, and because it lets us tell you when your result changes. No card, no trial clock.
- The title, meta description, og:title, og:description and h1 actually deployed on your page, beside the draft you just wrote.
- A title that disagrees with its own og:title, which tells a search result and a shared link two different things about the same page.
- Whether the deployed tags fit the budget at all, measured server-side on what your server really returns rather than on what you meant to ship.
Signing in saves the details you entered above so we can follow up about your results. See our privacy policy for what we keep and why. The SERP Snippet Preview result you already have stays free either way. Privacy policy.
The budgets, and where they come from
Google publishes no pixel limit for a title or a meta description. It never has, it renders differently by device and sometimes by query, and it has changed the rendering more than once. Every figure below is what the SEO community has measured from real results. They are a guide, and any tool showing you one as an official limit is telling you something it cannot know.
| Field | Budget | Source |
|---|---|---|
| Title, desktop | 580px | widely observed, not published by Google |
| Title, mobile | 920px | widely observed, not published by Google |
| Description, desktop | 990px | widely observed, not published by Google |
| Description, mobile | 1300px | widely observed, not published by Google |
Why a character count cannot answer this
Letters are not the same width. These are the width classes the fallback estimate uses, as a ratio of the font size, which is why two titles of identical length can render more than 30% apart.
| Class | Ratio | Characters |
|---|---|---|
| hairline | 0.22 | ijl|!.,;:'`’ |
| narrow | 0.28 | ftI()[]{}/\-–␣ |
| medium | 0.5 | abcdeghknopqrsuvxyz0123456789?"*^~+<=>$ |
| wide | 0.62 | ABCDEFGHJKLNOPQRSTUVXYZ&#%@ |
| widest | 0.78 | mw |
| widestCaps | 0.88 | MW |
These are not advance widths read from the Arial font file, and no claim is made that they match Google's rendering exactly. In a browser, canvas measureText gives a real measurement of the actual rendered font. The tool uses that when it is available and shows both numbers.
How this compares to a typical preview tool
Where the usual tools are equal, the table says so.
| Capability | This tool | Typical preview tool |
|---|---|---|
| Desktop and mobile rendering | Yes | Yes |
| Pixel width rather than character count | Yes | Usually |
| Real browser text measurement | Yes | Estimated table |
| Says which method produced the number | Yes | No |
| Labels the budget as observed, not published | Yes | Presents it as a limit |
| Cuts at a word boundary like Google | Yes | Often mid-word |
| Publishes its width classes for inspection | Yes | No |
| Warns that Google rewrites titles anyway | Yes | Rarely |
| Conflict check against your deployed tags | Yes, with a free account | No |
What is in the live snippet conflict check
A preview shows what you are about to ship. The conflict check shows what is already there, which is a different and often more surprising thing.
- The title, meta description, og:title, og:description and h1 the page actually returns, beside the draft you just wrote. A draft that differs means the change was never deployed.
- A title that disagrees with its own og:title. A search result and a shared link then describe the same page two different ways, and nothing on the page will tell you.
- Whether the deployed tags fit at all, measured on what your server really returns rather than on what you meant to ship.
One caveat worth repeating: Google rewrites titles when it judges another one a better match, so fitting the budget makes a snippet eligible rather than certain. Once the tags are right, the h1 checker measures how far your heading and title actually agree, the keyword density checker maps whether your term appears in the slots that count, and the AI visibility checker asks whether an answer engine names you at all.
How to preview a Google search snippet
Step 1
Write the title you want, then look at where it cuts
The cut point matters more than the character count. A 55 character title full of capitals and Ms can overflow while a 65 character one of narrow letters fits.
Step 2
Check mobile as well as desktop
The budgets are substantially different, and mobile is where most search traffic is. A title tuned only for desktop is tuned for the minority case.
Step 3
Put the important words first
Whatever the budget, the safest assumption is that the tail of a title may not be shown. Front-load the phrase you want read, and put the brand at the end.
Step 4
Then check what is actually deployed
The conflict check reads the tags your server really returns and compares them with your draft, including the og:title. A page whose title and og:title disagree describes itself two different ways.
When you outgrow this tool
A preview shows what a snippet could look like. Connect Search Console and Linkeddit shows which of your titles actually earn clicks, and which earn impressions and nothing else.
The preview is free and complete on its own. Linkeddit is what you use once the snippet is written and the question becomes which of your titles actually earn clicks rather than impressions.
FAQ
SERP Snippet Preview questions
What the pixel budgets are and are not, why Google rewrites titles anyway, and how accurate a preview can honestly be.
How long should a title tag be?
Long enough to say what the page is, short enough not to be cut, and the second half is a pixel question rather than a character one. Google publishes no limit, and the widely observed cut is around 580 pixels on desktop, which is roughly 55 to 60 characters of ordinary prose but can be 45 of capitals or 70 of narrow letters. The practical rule that survives every rendering change: put the words that matter first.
Why does Google rewrite my title?
Because it judges another title a better match for the specific query, which it does routinely and has confirmed doing. It draws from your h1, your on-page headings, anchor text pointing at the page, and the title tag itself. This is why a preview tool is a drafting aid rather than a guarantee: fitting the budget makes your title eligible to be shown, not certain to be. Titles get rewritten most often when they are keyword-stuffed, boilerplate across many pages, or badly mismatched with the page content.
Is there an official pixel limit for titles and descriptions?
No. This is the part most snippet tools present as settled fact and it is not. Google has never published a pixel budget for either field, has changed the rendering more than once, and renders differently by device and sometimes by query. The numbers this tool uses are what the SEO community has measured from rendered results, and every one of them is labelled that way in the interface rather than in a footnote.
How accurate is the pixel measurement?
In a browser, exact for the font your browser renders: it uses canvas text metrics, which is a real measurement rather than a guess. Where those are unavailable it falls back to an estimate that sorts characters into width classes by shape, and it tells you which one it used. What no tool can be accurate about is Google's own rendering on someone else's device, which is why the budget is the soft part of this, not the measurement.
Does the meta description affect rankings?
Not directly, and it has not for many years. It affects whether someone clicks, and Google replaces it with its own extract from the page whenever it thinks that answers the query better, which is often. Writing one is still worth it for the queries where it is used verbatim, but treating it as a ranking lever is a misallocation of effort.
What is in the layer that needs an account?
The conflict check. It fetches the page and shows the title, meta description, og:title, og:description and h1 actually deployed, beside the draft you just wrote. It flags a title that disagrees with its own og:title, which means a search result and a shared link describe the page differently, and it flags a draft that has not been deployed at all. It costs nothing to run and no model is involved.
How is this different from other snippet preview tools?
It measures rather than estimates where the browser allows, tells you which of the two happened, and refuses to present the pixel budget as an official limit. Most of the category shows a confident green tick against a number Google has never published. It also cuts at word boundaries the way Google does, instead of truncating at a character count and calling it a preview.
More free tools
Every tool on the shelf is free, with no card and no trial. Most need no account at all. See all free tools.
Check up to 25 descriptions at once and find the duplicates, which is the one problem you cannot see a page at a time.
Word and phrase frequency with the denominator stated, plus an honest note that density is not a ranking factor.
Flesch scores with every count they are derived from, long sentences listed, and passive voice shown as clauses you can overrule.
Thirty-five checks worth a hundred points, with every weight and every threshold printed before you enter a URL.