Skip to content
Part of: How-to format
General

Meta title and meta description length: what actually fits

Keep meta titles at 50-60 characters — Google's real cutoff is about 600 pixels of width on desktop. Keep meta descriptions near 155 characters for desktop and 120 for mobile. Both truncate with an ellipsis. Front-load keywords, write a unique title and description for every page, and expect Google to rewrite weak ones.

Shreyas Bagal·Sep 12, 2026·6 min

Keep meta titles at 50-60 characters — Google's real cutoff is about 600 pixels of width on desktop. Keep meta descriptions near 155 characters for desktop and 120 for mobile. Both truncate with an ellipsis. Front-load keywords, write a unique title and description for every page, and expect Google to rewrite weak ones.

Key takeaways

  • Keep meta titles at 50-60 characters — the real desktop limit is about 600 pixels, so wide letters cost more.
  • Write meta descriptions to about 155 characters for desktop and put the payoff in the first 120 for mobile.
  • Google rewrites titles that stuff keywords, duplicate across pages, or mismatch the content — often substituting the H1.
  • Meta descriptions aren't a direct ranking factor, but bolded query matches make them your best free ad.
  • Give every page a unique title and description, and never let the cutoff land mid-promise.
Meta title and meta description length: what actually fits
On this page

Data

Keep meta titles between 50 and 60 characters and meta descriptions under 155 for desktop — about 120 if mobile matters more to you. Google truncates both with an ellipsis, and the real title cutoff is roughly 600 pixels of width, so wide capital letters cost more room than narrow ones.

Google doesn't publish official character limits for titles and descriptions — the numbers everyone uses are the points where truncation kicks in on real results pages. That distinction explains most of the weird behavior: why one 62-character title survives while another dies at 58, and why your carefully written description sometimes never shows at all. Here are the working numbers, then how to write text that survives them.

The reference table

ElementSafe lengthHard limitNotes
Meta title50-60 characters~600 pixels wide on desktopWidth-based: W and M cost far more than i and l; ALL CAPS truncates soonest
Meta description (desktop)150-155 charactersNo fixed cap — cuts by widthTruncated text ends in an ellipsis
Meta description (mobile)~120 charactersNo fixed capMobile cuts sooner; put the payoff in the first 120
H1 (for comparison)No limitGoogle often swaps it in when it rewrites a title

Two things to notice before the details. Every limit here is a display limit, not an indexing one — Google reads your full title and description however long they run; it just won't show all of them. And "safe length" assumes average-width Latin text: numerals, thin letters, and short words buy you slack, while long capitalized words spend it fast.

Meta title length: 60 characters is really 600 pixels

Google truncates title links at about 600 pixels of width on desktop, not at a character count. Characters are just the convenient proxy, and at average letter widths, 50-60 characters is where most titles cross the pixel line. The proxy bends at the extremes: a title full of narrow letters like i, l, and t squeezes in more characters than one stacked with W's and M's, and an ALL-CAPS title hits the wall soonest of all, because capitals are wide.

The practical rule: draft to 50-60 characters and front-load. Put the keyword in the first 30 or so characters so that even a clipped title keeps its meaning and its relevance signal. Treat anything over 60 as a rewrite candidate rather than an automatic failure — character 63 sometimes survives — but never bet the keyword or the promise on the back end of a long title.

Meta description length: 155 on desktop, 120 on mobile

Desktop results typically show up to about 155 characters of description before the ellipsis; mobile often cuts near 120. Same principle as titles — the cut is width-based, so these are working numbers, not contracts.

Write so the first 120 characters stand alone: a complete thought, keyword included, no cliffhanger. Characters 120 through 155 are the bonus zone — supporting detail, the soft call to action, material you can afford to lose on a phone screen. The failure mode to avoid is the mid-promise cut: "Get 20% off when you…" reads worse than no description at all, because it advertises that nobody checked.

Treat the 120 mark as a discipline rather than a second limit to obsess over. If the sentence that matters is complete by then, the desktop-only bonus zone becomes pure upside instead of a gamble — and the same description works everywhere without maintaining two versions.

Google rewrites titles it doesn't trust

A perfectly sized title still isn't guaranteed to display, because Google rewrites titles it judges unhelpful. The reliable triggers:

  • Keyword stuffing. "Cheap Flights | Cheap Airfare | Cheapest Flight Deals" is a rewrite waiting to happen.
  • Boilerplate duplicates. The same title pattern across hundreds of pages tells Google your titles carry no page-specific information, so it goes looking for some.
  • Mismatch. The title promises something the page doesn't actually cover.

When Google rewrites, it most often pulls from your H1 or another prominent heading — one more reason the title tag and the H1 should tell the same story, even when they're worded differently. You can't opt out of rewrites. You can only remove the triggers, and clean, accurate, unique titles are the ones that get left alone most.

Descriptions don't rank you — they sell the click

Google has said the meta description isn't a direct ranking factor, and writing one like ranking copy misses what it's actually for. The description is the free ad under your title: its whole job is to win the click from whatever position you already hold, and a lifted click-through rate is worth real traffic even when rankings don't move an inch.

Two mechanics make a description work harder. First, Google bolds the words in a snippet that match the query — include the phrase you're targeting and your snippet gets visual emphasis the generic text around it doesn't. Second, for long-tail queries Google frequently ignores the meta description entirely and pulls a passage from the page that matches the search better. That's normal, not a penalty; your handwritten description shows mostly for your head terms, which is exactly where the polish pays off.

How to write a title that survives

A shape that keeps working: primary keyword + concrete differentiator + brand if it fits.

  • Draft at 50-60 characters with the keyword in the front half
  • Make it unique — no other page on the site should share it
  • Match the H1's substance so the pair reinforces instead of contradicting
  • Add one specific that earns the click: a number, a year, or the format — "template," "checklist," "calculator"

"Invoice template for freelancers (free, no signup)" beats "Free Invoice Template Download Invoice Templates" on every axis that matters: it fits, it's honest, and it won't trip a rewrite.

The brand suffix is the usual casualty of the 60-character budget. Keep it on pages where recognition wins the click — the homepage, category hubs, anything head-term competitive — and drop it on long-tail posts where every character has a job. A " | Brand" tail typically costs eight characters or more; make them earn their place page by page. A meta title generator drafts variants pre-sized to the limit, which beats trimming by feel and recounting every edit.

How to write a description that survives

One sentence of substance, one soft push. Name what the page delivers with a concrete detail — a count, a price, a timeframe — include the target phrase once for the bolding, and end with a low-pressure next step: "see the full table," "try the free tool." Skip throat-clearing like "On this page we will discuss…", which spends 30 of your 155 characters saying nothing the title didn't. A meta description generator produces sized drafts you can edit against the actual page instead of composing in the abstract.

Three ways to waste a snippet

These three mistakes account for most wasted snippets, they're all findable in a crawl, and each one is fixable in an afternoon:

  1. The same description sitewide. Google treats boilerplate descriptions as no information and substitutes page text — you've silently unpublished your own copy on every URL at once.
  2. Cutting mid-promise. Write to the safe lengths and verify with a character counter before shipping; the ellipsis should never land inside your main clause.
  3. Stuffing. A comma-separated keyword pile earns nothing extra from Google and reads as spam to the person deciding whether to click. One natural use of the phrase gets you the bolding; the rest of the space belongs to persuasion.

Snippet limits are the gentle cousin of paid-platform caps — if you also write ad copy, the Google Ads character limits reference applies the same discipline with a much stricter referee.

Ready to put this into practice?

Open a formatter

Spotted an error? Email hello@boldlytype.com — we update guides quarterly and welcome corrections.

Frequently asked questions

Latest questions readers ask us about this topic.

What happens if my meta title is too long?

Google cuts it off with an ellipsis once it passes roughly 600 pixels of width on desktop — usually somewhere past 60 characters. Truncation alone doesn't hurt rankings, but it can swallow your keyword or your promise, and long stuffed titles invite Google to rewrite the whole thing.

Is the meta description a ranking factor?

No — Google has said meta descriptions aren't a direct ranking factor. They still matter because they're the sales copy under your title in the results: a specific, well-matched description earns more clicks from the position you already hold, and Google bolds the searcher's query words inside it.

Why does Google keep changing my meta description?

Because it decided page text matches the query better, which happens constantly for long-tail searches. Your written description shows mostly for your main keywords. You can't force Google to use it — you can only make it the strongest option for the queries you care about by matching them closely.

How do I check my title and description lengths?

Count characters before you publish: 50-60 for titles, up to 155 for descriptions, with the first 120 doing the real work for mobile. A character counter is the fastest check — paste, read the number, trim. For titles, also eyeball width: capitals and W's eat pixels much faster than thin letters.

Should the meta title match the H1?

They should agree in substance — same topic, same promise — without matching word for word. The title tag is written for a 60-character slot on a results page; the H1 has the whole page to work with. If the two diverge in meaning, Google often swaps your title out for the H1.

The sub-questions readers ask next — answered, with where to go.

LinkedIn's post box — used for feed posts, comments, your headline and your About section — is plain text with no formatting toolbar and no markdown, so there's no bold button. The workaround the whole creator economy uses is Unicode bold: type your line, convert it to bold Unicode characters (𝗯𝗼𝗹𝗱) in a generator, then paste it back and the emphasis sticks, because the style is baked into the characters themselves. Bold only the hook — the part that shows before the “…see more” cut-off — to earn the click, and keep the rest plain so the post stays skimmable. Two caveats matter: Unicode text isn't read by LinkedIn's search and is announced poorly by screen readers, so never bold the keywords, names or hashtags you want found or read aloud. For true rich text (headings, lists), use LinkedIn's separate 'Write article' editor instead.

Format a LinkedIn post

Instagram's native composer collapses the line breaks you type, which is why captions paste in as one dense block — it's worst when you post from the web or through some schedulers. The reliable fix is to compose the caption with the spacing you want and paste it back with the breaks preserved, rather than relying on invisible-character hacks (blank Unicode characters can break Instagram's search and are read poorly by screen readers). Write the caption with your intended breaks, generate the spaced version, and paste it into the caption field. Put your strongest hook on line one, since that's the part that shows before the 'more' cut-off in the feed. Keep paragraphs short — two or three lines — so the caption stays skimmable on a phone, where almost everyone reads it.

Open the line-break tool

Yes — WhatsApp is the exception among messaging and social apps because it has its own built-in markup that it renders for everyone. Wrap text in *asterisks* for bold, _underscores_ for italic, ~tildes~ for strikethrough, and triple backticks for monospace; the symbols disappear and the styling shows. So you usually don't need Unicode characters on WhatsApp at all. Reach for a Unicode formatter only when you want a style WhatsApp's markdown doesn't cover — small caps or script for a Status, say — or when you're writing one message to post across several apps that don't share WhatsApp's syntax (Instagram, X and Threads strip these symbols and show them literally). For everyday bold and italic inside WhatsApp itself, the native markup is the better and more accessible choice.

Format for WhatsApp

Because that editor is plain text and strips anything it doesn't parse. Markdown (*bold*), HTML tags and rich-text styling only render where the platform explicitly supports them — paste them into Instagram, X/Twitter or a LinkedIn post and you see the raw asterisks, or nothing at all, because those boxes have no formatting engine. Unicode styling works differently: the bold or italic look is baked into each character (a Unicode bold 'A' is its own code point), so it survives any plain-text field and travels with a copy-paste. That's the whole reason Unicode 'fancy text' formatters exist. The trade-off is accessibility — because they aren't ordinary letters, screen readers can mis-read them and in-app search may not match them — so use Unicode for short emphasis, not for body copy or anything that must be searchable.

Generate paste-proof styles

Related in this series

See all in How-to format

Explore the topic cluster

More tools and guides across this topic cluster.

Get the next post.

Craft notes on writing for the internet. One short email, every other week. No spam.

Keep reading