Meta description length checker

This checker counts the characters in your draft, compares the total with the recommended 120–160 range, and clearly marks descriptions that are too short or at risk of truncation. It gives writers, editors, and SEO teams a fast, consistent check without rewriting the copy or making subjective claims about ranking performance. Run it here or automate the same deterministic test through the API.

Understand what the checker measures

Paste the exact meta description you plan to publish. The checker counts Unicode characters, which means a visible emoji or another character outside the basic multilingual plane counts once rather than as two internal code units. It then compares that total with the recommended minimum of 120 characters and maximum of 160 characters. A result inside that inclusive range is marked recommended. A shorter result is marked too short, while a result above 160 is marked too long and receives a truncation-risk flag. The response also says how many characters are needed to reach the minimum or how many exceed the maximum. Those distances make revisions easier because you can see the size of the change required without repeatedly counting by hand. The tool does not inspect HTML, fetch a webpage, judge writing quality, or promise how a particular search engine will display the snippet. It performs one transparent length check on the text you provide.

Use the range as an editorial signal

The 120–160 range is a practical writing target, not a guarantee that every search result will show every character. Search engines may build a different snippet from page content, vary the displayed space by device or query, and truncate copy according to rendered width rather than a simple character total. Treat a too-long result as a useful warning that important words near the end may not appear. Move the page’s clearest benefit, topic, or action toward the beginning before cutting secondary detail. When a description is too short, add specific information that helps a searcher distinguish the page instead of padding it with repeated keywords. A description inside the range still needs to be accurate, readable, and aligned with the page. This checker deliberately separates the objective measurement from editorial judgment: it tells you whether the count fits the chosen range, while your team remains responsible for relevance, tone, truthfulness, and a natural reason to click.

Build a repeatable publishing check

For a single page, paste the final draft and review the status before publishing. For a content pipeline, send each proposed description through the API and store the returned character count, status, and truncation-risk value with your editorial checks. You can block empty input, route short descriptions back to a writer, and flag long descriptions for review without changing their text automatically. Because the algorithm has no network calls, randomness, or time-dependent behavior, the same input produces the same result in a browser, build process, or continuous integration job. Keep the submitted text identical to the value placed in the page’s meta tag; leading and trailing spaces are counted when present because they are part of the supplied string, although an input containing only whitespace is rejected as empty. Recheck descriptions after localization because character counts change across languages. This English capability measures any Unicode text, but it does not translate copy or substitute locale-specific editorial guidance.