★ FREE TOOL · RUNS IN YOUR BROWSER

SERP Preview Tool.
Pixel width,
not character count.

Google truncates titles and descriptions by how wide they render, not by how many characters they contain. Paste yours below to see where the cut falls on desktop and mobile. Nothing is sent anywhere — the whole tool runs in this page.

Your snippet

51 characters · ~477px of ~580px
Google shows a breadcrumb path rather than the raw URL, so short readable paths display better than parameter strings.
157 characters · ~948px of ~1840px
rankedtag.com › serp-preview-tool

SERP Preview Tool: Check Your Title and Description

See how your title tag and meta description render in Google results, with truncation estimated by pixel width rather than character count. Free, no sign-up.

An estimate, not the real renderer. Google adds and removes elements per query and rewrites titles and descriptions when it judges another option more useful.

Why pixel width, and not character count

Almost every piece of advice on title length is given in characters, and almost all of it is wrong at the edges. Google renders results in a proportional typeface, so the space a title occupies depends on which letters are in it. A title of 60 narrow lowercase characters can fit comfortably where a title of 50 characters in capitals will not.

The practical consequence is that two titles of identical length can behave completely differently, and that a brand name full of capitals eats considerably more of your budget than its character count suggests. The preview above estimates width using a per-character table rather than counting, which gets much closer to where the cut actually falls.

It remains an estimate. Nothing outside Google can be exact, because the rendering depends on the user’s device, the exact font loaded, and what else Google decides to show for that query. The aim is to be usefully closer than a character count, not to be the renderer.

Writing a title that survives

Put the distinguishing words first. If the end is at risk of truncation, the end should carry the least important information. A brand name at the front costs you the same width on every page you own, which is why most sites put it at the end.

Describe the page, do not list keywords. Google overrides titles it judges unhelpful, and keyword stacking is one of the more reliable triggers. A title that reads like a sentence a person wrote is both more likely to survive and more likely to be clicked.

Make it unique. Duplicate titles across a large page set are a common site-wide problem and they make it harder for a search engine to distinguish those pages. Templates are fine when the variables actually differentiate the result.

Match the page. A title that promises something the page does not deliver earns a click and loses the visitor, which is worse for you than not ranking. The return to the results page is a behaviour you can see in your own analytics if you look for it.

The description is an advert you are not paying for

Meta descriptions have not been a ranking factor for a long time, and a lot of teams stopped writing them carefully as a result. That is a mistake of a different kind: the description frequently decides which of ten adequate results gets the click, and clicks are the entire point of the ranking you worked for.

Google rewrites descriptions often, usually by lifting a passage from the page that matches the query more closely than your written one. This is not a failure. It means the page contains a better answer for that query than the summary did, which is a reasonable outcome. Writing a good description is still worth it for the cases where yours is used.

The most effective descriptions answer the implied question and set an accurate expectation of what the page contains. The least effective repeat the title in slightly different words and add a list of keywords nobody reads.

What changes when an AI answer sits above the result

An assistant answer does not display your title or description at all, so their direct role shrinks on queries that resolve to a generated summary. Their indirect role does not. A clear, specific title is one of the signals that helps any system work out what a page is about, and the discipline of saying what something is in very few words is the same discipline that produces quotable content.

The practical advice is unchanged, with a shift in emphasis. Informational queries are where AI answers appear most and where the click is least reliable, which is an argument for weighting your attention towards the commercial and comparison pages where the click still happens and still converts. Those are the titles worth labouring over.

If you want the fuller version of that argument, we have written it up in SEO vs GEO and in AI SEO vs traditional SEO.

FAQ

Titles and descriptions, asked and answered.

Want the rest of the page checked?

Send the domain. The founder runs the 52-check review personally and replies within 48 hours, including when the answer is that your titles are not the problem.

Apply for review ↗

Think in pixels rather than characters. Google truncates titles at roughly 580 pixels on desktop and less on mobile, and pixel width varies enormously by character: a title full of capitals and wide letters truncates far earlier than one of the same character count in lowercase. Around 50 to 60 characters is a useful rule of thumb, but the preview above is more reliable than the rule.

Roughly 140 to 160 characters is the working range, and again the real limit is width. Google frequently rewrites descriptions anyway, often pulling a passage from the page that matches the query better. A good description is still worth writing, because when it is used it is doing the job of an ad you did not pay for.

Not directly. Google has said for many years that it is not a ranking factor. It affects click-through rate, which is the reason to care about it. A description that answers the implied question and sets an accurate expectation earns clicks that a keyword-stuffed one does not, and it reduces the immediate return to the results page that follows a mismatch.

Because it decides the title it shows, and it will override yours when it judges another option more useful for the query, often using an H1 or a prominent heading. The usual causes are titles that are too long, stuffed with keywords, repeated across many pages, or that do not describe the page accurately. Writing a concise, specific, unique title reduces the chance of being rewritten.

Yes, and duplicate titles are one of the more common site-wide problems we find. Identical titles across many pages make it harder for search engines to tell those pages apart and increase the chance of being overridden. On a large catalogue or a multi-location site, templates are fine, provided the variables genuinely differentiate the result.

Less directly than they do for a results page, because an assistant answer does not display them. They still matter indirectly: a clear, accurate title helps a model understand what a page is about, and the same discipline that produces a good title, saying what the page actually is in few words, produces content that is easier to quote.

No, and nothing can be. It estimates pixel width using a character-width table based on the font family Google renders results in, which gets close but is not the real renderer. Google also adds or removes elements per query, including dates, sitelinks and favicons, and rewrites titles and descriptions when it chooses. Treat it as a good approximation, not a guarantee.

Yes, because Google shows a breadcrumb-style path rather than the raw URL. Short, readable, logically nested paths display better than long parameter strings, and a clear path communicates structure before anyone reads the title. It is a small effect on its own and a visible one in a crowded set of results.