You write a perfect meta description. It says everything it needs to say, reads naturally, and lands exactly on message. Then Google truncates it mid-sentence in the search results, and the version readers actually see ends on a word like "and" or "the," which looks broken and undermines the click you were trying to earn.
Every Platform Has a Different, Unforgiving Budget
Meta descriptions get cut around 155 to 160 characters. Tweet-length posts on most platforms cap around 280 characters, but a post with a link or image attached effectively has less room once the platform reserves space for the preview card. SMS messages split into multiple segments past 160 characters, silently costing more to send and sometimes arriving out of order. Push notifications on mobile often truncate around 40 to 50 characters before the rest gets hidden behind a "more" tap most users never make.
None of these limits are the same number, and none of them are configurable. Writing copy without checking against the specific platform's limit means gambling that your sentence happens to fit, which it usually doesn't once you're actually trying to say something specific.
Why Word Count and Character Count Aren't the Same Problem
A sentence with twelve short words can run shorter than a sentence with eight long ones. Writers who think in word count alone consistently misjudge how much room they actually have, because character count is what every platform's limit is actually measured in, not word count. "The quick fix works" is nineteen characters longer than "It just works," despite both being reasonable four or five word phrases.
This gap matters most in constrained fields: title tags, meta descriptions, subject lines, button labels. A word count that looks reasonable in a document can still blow well past a character-based limit once you count every space and punctuation mark.
Reading Time Matters for a Different Reason
Reading time estimates, usually calculated from average words-per-minute reading speed, matter less for hard platform limits and more for setting reader expectations. Publications that display an estimated reading time, a pattern popularized in part by platforms like Medium, give readers a reason to commit to an article instead of bouncing on an unknown time investment. Getting that estimate roughly right, and writing to a length that matches what the format implies, keeps the promise you're implicitly making at the top of the page.
Checking Before You Draft, Not After
The most reliable fix is checking your target platform's limit before you start writing the constrained copy, not after you've already written something you love and now have to butcher to fit. Know the number, write toward it, and treat going over as a signal to cut rather than something to solve by removing spaces or abbreviating words into gibberish.
EvvyTools' Word & Character Counter tracks both word count and character count live as you type, along with an estimated reading time, so you can see exactly where you stand against a platform's limit before you're staring at a truncated preview after the fact.
Meta Descriptions Deserve Extra Care
Search engine snippets are the single highest-stakes character limit most writers deal with regularly, because a truncated meta description is often the entire reason a page gets skipped over in results. Google's own guidance, covered extensively through resources like Google Search Central, doesn't guarantee it will even use your written meta description over an auto-generated snippet, but writing a tight, complete sentence within the character budget gives it the best odds of being used as-is.
Subject Lines Have Their Own Hidden Cutoff
Email subject lines get truncated differently across devices, mobile inboxes show noticeably fewer characters than desktop clients before cutting off with an ellipsis. A subject line that reads perfectly on a laptop screen can lose its punchline entirely on a phone. Testing a subject line's length against the tightest common limit, rather than the most generous one, avoids that mismatch across devices.
Social Platforms Keep Moving the Goalposts
Character limits aren't static even within a single platform. Post length caps, preview card text length, and how much of an attached link's title gets shown have all changed multiple times across major social platforms over the past several years, usually without much advance notice to the people writing copy for them. A limit you memorized a year ago might already be wrong.
This is part of why checking a draft's character count against the current limit, rather than relying on memory of what the limit used to be, matters more than it might seem. Platforms like LinkedIn have adjusted preview truncation more than once, and copy tuned to an old limit can end up either wastefully short or awkwardly cut off after a change nobody on the writing team noticed happened.
Button and Label Copy Has the Tightest Budget of All
Interface copy, button labels, form field hints, navigation items, often has the least forgiving character budget of anything a writer touches, because it also has to survive translation into other languages that may run longer for the same meaning. A button that says "Continue" in English can become notably longer in German or French, and a label written right up against its pixel budget in English has no room left once localization expands it.
Product and UX writers dealing with this constraint regularly build in deliberate slack, writing shorter than the technical limit allows specifically to leave room for translation expansion later. That's a character-count discipline that goes beyond just checking a single number, it's planning for the number to effectively shrink once the copy travels beyond its original language.
Building the Check Into Your Draft Process
Add a length check as a fixed step before anything goes out, the same way a spell check became automatic years ago. It takes seconds and catches a failure mode that's otherwise invisible until the copy is already live and already truncated somewhere you can't easily fix after the fact.
The same "check before you publish" instinct applies to headlines, not just character-constrained fields. EvvyTools' breakdown of what makes a headline score well covers the other half of this problem, why some headlines get skipped even when they technically fit the space they're given.
Email Has Its Own Set of Nested Limits
Email adds a wrinkle most other formats don't have: a subject line limit, a preheader text limit, and often a sender name limit, all rendering differently across Gmail, Outlook, and mobile mail apps simultaneously. A subject and preheader combination tuned for desktop Gmail can read completely differently once it hits a mobile inbox with a narrower preview pane, sometimes cutting off the preheader entirely and leaving just the subject line to do all the work.
Marketers who test across multiple clients before sending a campaign catch this kind of mismatch before it goes out. Testing after the fact, once a campaign has already landed in ten thousand inboxes with an awkwardly truncated preheader, is a much more expensive way to learn the same lesson.
A Small Habit, Applied Consistently
None of this requires new software knowledge or a workflow overhaul. It requires knowing the actual limit for wherever your copy is going, and checking against it before you consider the draft finished. Do that consistently and the "why did this get cut off" problem mostly disappears.
The counter is one of several free writing checks EvvyTools runs entirely in the browser, worth bookmarking if character limits keep tripping up your copy.
Top comments (0)