Word and Character Count for SEO: Meta Descriptions, Titles and Social Snippets

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.

09.09.2026
9 min read
Share this article:
word-count
SEO
meta-description
content
text-tools
Tutorial

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.

Meta description 155-character preset — progress bar and under/over badge
With or without spaces — useful when your CMS counts differently
Estimated reading time (WPM 150–300) for articles and landing pages
Twitter/X 280 and SMS 160 presets for social snippets
100% local — marketing copy never leaves the tab

Common meta, title and counting mistakes

Mixing up words and characters

"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.

Counting words for a meta description instead of characters
Ignoring trailing spaces (trim before CMS paste)
Forgetting that CMS-appended "…" counts toward the limit
Paste from Word with invisible non-breaking spaces
Duplicating title, H1 and meta

Three identical fields waste the snippet and do not help users pick your result.

Title = H1 = meta word for word
Repeating only the keyword with no user benefit
Meta that does not describe the page (keyword stuffing)
Title too long because the brand is duplicated twice
Ignoring mobile and social

Desktop SERP and Twitter cards do not share the same usable width.

Testing length only on a desktop preview
Reusing og:description without retesting at 280 char.
Descriptions under 100 char. — too vague for FastMinify's editorial floor
Counting HTML entities as one visual character

Words or characters: each SEO field has its own rule

Meta description: characters, not words

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.

Title tag and H1: two fields, two budgets

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.

Open Graph, Twitter and article body

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

Quick limits cheat sheet

These are practical guides, not SERP display promises. Google often rewrites the displayed snippet even when your tag is perfect.

Before

Discover how to optimize your website to improve organic search rankings and attract more qualified visitors using proven SEO techniques you can apply starting today.

After

155 char. max (preset) — truncate at a word boundary + "…" rather than mid-word.
Meta description: target 155 char., floor 100, hard ~160 — preset meta-description-155
Title tag: ~50–60 char. — custom limit 60 in word-counter
Tweet / X: 280 char. — preset twitter-280
SMS preview: 160 char. — preset sms-160
Blog article: count words + reading time — no single SERP ceiling
What FastMinify's counter measures exactly

The 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).

Words: whitespace split after trim — no stemmer or specialized CJK handling
Characters with spaces: JavaScript input.length (UTF-16 code units)
Characters without spaces: length after removing \s
Green / amber / red limit bar — amber from 80% of preset
Empty input: zeros everywhere, no error

Word counter workflow: from meta to tweet

Write a meta description under 155 characters

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).

meta-description-155 preset aligned with site META_DESCRIPTION_MAX_LENGTH
Copy the final version into your CMS or front matter
Read aloud — 155 char. ≈ 20–25 English words, varies by vocabulary
No server upload — live debounce like other text tools
Neighbor hub tool: beautify Markdown to format product docs before counting
Scenario — 60 char. title + 155 char. meta for a landing page

You ship a tool page with a tight SEO title and a descriptive meta. Two passes in the same tab.

1

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.

2

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).

3

Pass 3: optional tweet

Preset twitter-280 for a launch post — more room, more direct tone. The counter does not publish; it only sizes.

Reading time for a blog article

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.

WPM 150–300 — 200 default, matching FastMinify blog convention (~200 words/min)
Sentences and paragraphs: structure sanity check
Do not confuse blog reading time display with meta 155 preset
Long posts: Markdown TOC for navigation
CSV → README table: CSV to Markdown table

Bake limits into your stack

CMS and meta fields

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

// Next.js App Router — FastMinify-aligned target import { clampMetaDescription } from '@/lib/meta-description' export const metadata = { title: 'Online JSON Minifier — FastMinify', // ~32 char. description: clampMetaDescription( 'Minify JSON in the browser. No upload, API presets, one-click copy.' ), // clamps to 155 char. at word boundary + … }
Alternatives and honest limits

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.

Preset 155 for meta, custom 60 for title, 280 for social — three passes
Count characters with spaces unless your CMS explicitly differs
Recalculate reading time after each locale (FR/EN/DE/ES)
Do not confuse LLM tokens and SERP characters
Trim and proofread — trailing spaces count in the limit bar
Share this article
Share this article: