Meta Title & Description Length Checker
Check meta title and description length in pixels as well as characters, so you can see whether Google will truncate them. Shows a live desktop and mobile preview and flags the exact point where the text is cut.

Character counts are a rough guide. Google truncates on pixel width, which is why a title full of capital letters gets cut at 48 characters and one full of lower-case letters survives to 65. Paste your title and description to see both measurements and where the cut lands.
What this tool does
Type a meta title and meta description and you get four numbers: characters and approximate pixel width for each, measured separately for desktop and mobile. A live preview shows where the ellipsis would appear.
Pixel width is the measurement that matters. Google renders the title link in a proportional font, so WWW occupies roughly three times the space of iii. A 60-character title made of wide characters overflows; a 68-character one made of narrow characters often does not. Counting characters alone gives you false confidence in both directions.
A worked example
Take two titles of identical length:
AI Workflow Automation Services for Small Business Owners— 57 characters, comfortably inside the desktop limit.WHOLESALE MACHINERY MANUFACTURING & WAREHOUSE MANAGEMENT— 56 characters, and it overflows, because every letter is a capital.
The tool shows the second one crossing the threshold and marks the point where Google would truncate it, so you can move the important words to the front rather than trimming from an arbitrary position.
Rough limits to work to
| Element | Desktop | Mobile |
|---|---|---|
| Title pixel width | about 580px | about 550px |
| Title characters | 50–60 typical | 45–55 typical |
| Description pixel width | about 990px | about 900px |
| Description characters | 150–160 typical | 110–130 typical |
Treat these as guide rails, not rules. Google states plainly that it may rewrite a title link when it judges the page's own title a poor match for the query, and that snippets are generated per query rather than lifted verbatim.
Where people go wrong
Padding a description to hit exactly 160 characters. Length is not a ranking factor. A tight 120-character description that answers the query beats a padded 160-character one that trails off into keyword soup.
Writing for the counter instead of the click. The title's job is to earn the click from a results page full of competitors. Front-load the differentiator.
Ignoring the brand suffix. If your template appends | Brand Name, that is 15 or more characters of every title spent identically. Measure the rendered title, not the part you typed into the CMS.
Assuming the description will be used at all. Google frequently generates a snippet from body copy instead. Google's own snippet documentation explains the controls you actually have — max-snippet, data-nosnippet and nosnippet — and it is worth knowing them before blaming the description.
Forgetting that titles get rewritten. The guidance in Google's title link documentation is specific: a title that is boilerplate, keyword-stuffed or wildly mismatched with the page invites a rewrite.
FAQ
Are the pixel widths exact?
They are a close approximation. Exact rendering depends on the font Google serves, the device, and the user's zoom level, none of which can be measured from your side. The approximation is calibrated against the characters that actually cause trouble — capitals, wide letters and punctuation — and is reliable enough to tell an overflowing title from a safe one.
Why does my mobile preview cut earlier than desktop?
Less horizontal space. Mobile results run to roughly 550px for the title, which is why a title that fits neatly on desktop can lose its last two or three words on a phone.
Does description length affect rankings?
No. It affects click-through rate, which affects traffic. That is worth optimising for on its own terms without pretending it is a ranking signal.
Should every page have a unique description?
Every page you care about ranking, yes. Duplicated descriptions across a template make it more likely Google generates its own snippet, and you lose the control you were trying to exercise.
Next steps
Once the lengths are right, check how the whole result looks with the SERP preview tool, and run the page through the SEO Meta Tag Analyzer to catch missing canonicals and Open Graph tags. If you are producing pages at volume, the Content Brief Generator builds the outline before you write the meta.
Publishing content on a schedule? How to Automate Social Media Posting covers the distribution half of the job.
Want a technical SEO audit rather than a character count? Book a discovery call.

Want this built against your real numbers?
A 30-minute call to scope the workflow, agent, or automation you actually need.
More seo tools
All tools301 Redirect Rule Generator
Turn a list of old and new URLs into redirect rules for Apache htaccess, Nginx, Cloudflare or Netlify. Detects redirect chains and loops before you deploy them, and handles bulk migrations from a pasted list.
Canonical Tag Generator
Generate a correct rel=canonical tag from any URL. Normalises the scheme, strips tracking parameters, resolves trailing slash and case issues, and warns about the canonical mistakes that quietly deindex pages.
Content Brief Generator
Generate a complete SEO content brief from any keyword — ready to hand to a writer
Google SERP Preview Tool
See how your page will look in Google results on desktop and mobile before you publish. Renders the title link, breadcrumb URL and snippet with realistic truncation, and highlights query terms the way Google bolds them.
Hreflang Tag Generator
Build a complete, reciprocal hreflang set for a multilingual page and export it as link tags, an HTTP header block or XML sitemap entries. Validates language and region codes and adds x-default automatically.
Keyword Clustering Tool
Group any keyword list by search intent and topic — ready for content planning
Have a workflow that's burning hours every week?
Bring me one real bottleneck. I'll tell you whether it's worth automating, and what it would take.