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-countSEOmeta-descriptioncontenttext-toolsTutorial

Counting before you publish a meta description or a 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. It includes the meta-description-155, twitter-280 and sms-160 presets, aligned with product limits. Everything stays in the browser. The other text tools sit on the Text & Markdown tools hub. For site-wide performance, cross-check the web performance checklist 2026 and the link between speed and SEO in why fast sites rank better.

Meta description 155-character preset, with a progress bar and an under-or-over indicator

Counting 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 text 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 and 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 (remove them before pasting into the CMS)

Forgetting that CMS-appended "…" counts toward the limit

Paste from Word with invisible non-breaking spaces

A meta truncated mid-word in the SERP means a lower CTR even with decent rankings.

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

Google may rewrite meta; an overlong title loses the end (secondary keyword or brand).

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 characters

Descriptions under 100 characters are too vague for FastMinify's editorial floor

Counting HTML entities as one visual character

Run one pass at preset 155 for Google, one at 280 for social and a custom limit of 60 for the title: three pastes, three green indicators.

Words or characters, and the rule of each SEO field

Meta description, in characters rather than words

Google often truncates displayed meta descriptions around 155–160 characters, depending on snippet width. Bing and Ahrefs audits often flag anything 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, which is what the default preset measures.

Title tag and H1, two fields and two budgets

The SEO <title> tag is truncated in Google results at around 60 characters on desktop, and sometimes earlier on mobile because of 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, so use a custom limit or watch the character counter.

Open Graph, Twitter and article body

Social cards (og:description, twitter:description) often reuse the 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 about 200 words per minute, adjustable. To structure a long README or post, chain the Markdown TOC generator on the same hub.

Numbers to know before you write

The usual limits at a glance

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 characters max (preset): truncate at a word boundary and add “…” rather than cutting mid-word.

Meta description: target 155 characters, floor 100, hard limit around 160, preset meta-description-155

Title tag: about 50–60 characters, with a custom limit of 60 in the word counter

Tweet or X post: 280 characters, preset twitter-280

SMS preview: 160 characters, preset sms-160

Blog article: count words and reading time, since there is no single SERP ceiling

Exactly what the word counter counts

The tool uses the same logic as src/lib/word-counter.ts. Words are whitespace-separated tokens after trimming, sentences are split on .!?, and paragraphs are blocks separated by blank lines. Preset limits follow charCountMode (with or without spaces). The input ceiling is the same as the other text tools in this group: 64 KiB of UTF-8.

Words: split on whitespace after trimming, with 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 and red limit bar, with amber from 80% of the preset

Empty input: zeros everywhere, no error

From meta description to tweet with the word counter

Write a meta description under 155 characters

Open the word counter, select the preset Meta description (155) under Character limit, keep charCountMode on “with spaces” and paste your draft. The bar turns red on the first character past 155. Tweak until the indicator is green or amber (green below 80%, amber from 80 to 100%, red when over).

meta-description-155 preset aligned with site META_DESCRIPTION_MAX_LENGTH

Copy the final version into your CMS or front matter

Read it aloud: 155 characters come to roughly 22 to 28 English words, depending on vocabulary

No server upload, with live updates as you type like the other text tools

Neighbor hub tool: beautify Markdown to format product docs before counting

A 60-character title and a 155-character 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.

First pass, a title with a custom limit of 60

Choose Custom as the character limit, enter 60 in Custom limit, and count characters with spaces. Example: “Online JSON Minifier | FastMinify” (33 characters) leaves room for a brand suffix.

Second pass, a meta with the 155 preset

Switch to meta-description-155 and rewrite without repeating the title verbatim. Add the intent (free, in the browser, no upload) in one sentence.

Third pass, an optional tweet

Use twitter-280 for a launch post: more room, more direct tone. The counter does not publish anything, it only sizes the text.

Reading time for a blog article

Paste the article body (without YAML front matter). The panel shows words and ~X min read at your WPM (default 200). It helps align readingTime fields in the editorial calendar. Recalculate after each translation pass, because German is often shorter than French for the same content.

WPM from 150 to 300, with 200 as the default, matching the FastMinify blog convention of about 200 words per minute

Sentences and paragraphs as a structure 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), Hugo front matter and the metadata export of Next.js: most expose a character counter. Check whether it counts with spaces and whether it includes an automatic 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 limits

Other tools count words and characters, so 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, with no account. It is not a full SEO audit, since 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.

Count your meta description now

Word counter Markdown TOC generator CSV to Markdown table Text & Markdown hub

Use preset 155 for meta, a custom 60 for title and 280 for social: three passes

Count characters with spaces unless your CMS explicitly differs

Recalculate reading time for each language (FR/EN/DE/ES)

Do not confuse LLM tokens and SERP characters

Trim and proofread, because trailing spaces count in the limit bar

Share this article

Share this article:

HTTP/2, HTTP/3 and Minification: Is Minification Still Worth It?

HTTP/2 and HTTP/3 change how files travel, not how big they are. Measured sizes, compile times and bundling tests show what minification still saves.

22.10.202615 min read

Unix Timestamps: Convert Epochs and Avoid Time Zone Mistakes

Convert a Unix epoch to a readable date and back, tell seconds from milliseconds, and avoid time zone, JWT and clock change traps, all in your browser.

19.10.202618 min read

Cron Expressions: Read the Syntax and Calculate the Next Runs

Read a cron expression field by field, check its next runs in UTC or local time and avoid traps with steps, time zones and dialects, all in your browser.

16.10.202618 min read