
Word and Character Count for SEO: Meta Descriptions, Titles and Social Snippets
Meta description 155 characters, title ~60, tweet 280: count words and characters in the browser with FastMinify's word counter — SEO presets, reading time, 100% local.
Why count before you ship a meta or title?
A meta description truncated in Google, a title cut off on mobile, or a tweet that loses its ending: these are length mistakes, not writing quality failures. Yet most CMS fields say "160 characters max" without clarifying whether spaces, punctuation or HTML entities count. FastMinify does not replace Search Console or a full SEO audit. The online word counter counts words, characters (with or without spaces), sentences, paragraphs and estimated reading time — with meta-description-155, twitter-280 and sms-160 presets aligned with product limits. Everything stays in the browser. The full cluster lives on the Text & Markdown tools hub. For site-wide performance, cross-check the web performance checklist 2026 and the speed ↔ SEO link in why fast sites rank better.
Common meta, title and counting mistakes
"My meta is 25 words, I'm fine" — Google truncates by characters/pixels. A long German compound or an ALL CAPS title burns budget fast.
Three identical fields waste the snippet and do not help users pick your result.
Desktop SERP and Twitter cards do not share the same usable width.
Words or characters: each SEO field has its own rule
Google often truncates displayed meta descriptions around 155–160 characters depending on snippet width. Bing and Ahrefs audits often flag beyond 160. FastMinify targets 155 (preset meta-description-155), with an editorial floor of 100 characters on this site to avoid descriptions that are too short. Count characters with spaces — that is what the default preset measures.
The SEO <title> tag is truncated in Google results around ~60 characters on desktop — sometimes less on mobile by width. It is not the same field as the visible page <h1>: you can keep a tight SERP title and a more descriptive H1 for users. FastMinify has no dedicated "title-60" preset — use a custom limit or watch the character counter.
Social cards (og:description, twitter:description) often reuse meta description — but not always. Twitter/X historically caps at 280 characters (tool preset). Article body is better reasoned in words and reading time: the counter estimates ~200 words/min (adjustable). To structure a long README or post, chain the Markdown TOC generator on the same hub.
Numbers to know before you write
These are practical guides, not SERP display promises. Google often rewrites the displayed snippet even when your tag is perfect.
Before
After
meta-description-155twitter-280sms-160The tool uses the same logic as src/lib/word-counter.ts: words = whitespace-separated tokens (trim); sentences = split on .!?; paragraphs = blocks separated by blank lines. Preset limits follow charCountMode (with or without spaces). Input ceiling: same as other text cluster tools (64 KiB UTF-8).
input.length (UTF-16 code units)\sWord counter workflow: from meta to tweet
Open the word counter, select preset Meta description (155), keep charCountMode on "with spaces", paste your draft. The bar turns red on the first character past 155. Tweak until the badge is green or amber (<80% green, 80–100% amber, over = red).
You ship a tool page with a tight SEO title and a descriptive meta. Two passes in the same tab.
Pass 1: title with custom limit 60
Preset Custom limit, enter 60, characters with spaces. Example: "Online JSON Minifier — FastMinify" (32 char.) — room for brand suffix.
Pass 2: meta with preset 155
Switch to meta-description-155, rewrite without repeating the title verbatim. One sentence on intent (free, browser, no upload).
Pass 3: optional tweet
Preset twitter-280 for a launch post — more room, more direct tone. The counter does not publish; it only sizes.
Paste article body (without YAML front matter). The panel shows words and ~X min read at your WPM (default 200). Useful to align readingTime fields in the editorial calendar — recalculate after each translation pass, because German is often shorter than French for the same content.
Bake limits into your stack
WordPress (Yoast, Rank Math), Next.js metadata, Hugo front matter: most expose a character counter. Check whether it counts with spaces and whether it includes an auto brand suffix. FastMinify fits the loop before CMS paste — especially when drafting in Markdown or a ticket.
Basic example
Other tools count words/characters — pick by privacy and SEO presets.
Conclusion
On-page SEO often starts with simple numbers: 155 characters to aim for a readable meta, ~60 for a title, 280 for a tweet — and words plus reading time for the body. The FastMinify word counter encodes those presets in the browser, no account. It is not a full SEO audit: Google can rewrite your snippet, and length alone does not rank. Combine local counting, clear copy and the rest of the 2026 performance checklist. Explore the text hub for Markdown TOC and CSV tables.
Related Articles

Deployment, Service, Ingress: structurally validate Kubernetes YAML before `kubectl apply` — browser-local check, no cluster or kubectl required.

A tour of FastMinify clusters, search intents and workflows — minify, DevOps, API and SVG tools, all in the browser, no account required.

Unreadable traces, missing maps: recover readable JS and CSS in the browser with unminify and beautify — formatting only, mangled names stay lost.