Meta description checker. Length, CTA, truncation.
Paste a meta description or a full HTML head. The tool runs seven checks: character length, pixel-width truncation against mobile + desktop SERP limits, action-verb presence, CTA strength, primary-keyword mention, sentence count, and unique-vs-page-body comparison.
Seven meta-description checks in one paste. Drop a description (or a full HTML document; we'll extract the meta name="description") and the tool runs length, pixel-width, action-verb, CTA, primary-keyword, sentence-count, and trailing-period checks. Pure browser code.
Plain text works. Full HTML works — we extract the meta tag automatically.
Sources used by this tool
- Google Search Central — snippet guidance
- Pixel width measured via HTML5 Canvas API (Arial 14px, the SERP body font).
- Truncation thresholds: 920 pixels mobile, 990 pixels desktop.
- Action-verb list: 80 high-intent English imperatives (start, get, build, download, book, learn, etc.).
All checks run in JavaScript on your device. No fetch, no log.
What the checker measures.
Length sits in a 120-155 character sweet spot. Below 120, you waste the snippet real estate users see in the SERP. Above 155, the description truncates with an ellipsis on most viewports. Mobile cuts off around 920 pixels (~120 chars), desktop around 990 pixels (~160 chars). Hit the middle.
Pixel width is the actual constraint. We measure the rendered width using the browser's canvas API (Arial 14px, the SERP body font). The 920-pixel mobile threshold is what mobile-first indexing uses — and mobile is the canonical rendering for ranking, so the mobile gauge is the one to optimize against first.
Action verb presence tells you whether the description has CTA energy. Descriptions that read like a passive summary ("This page is about...") draw lower CTR than descriptions that tell the user what they can do ("Get a free quote", "Book a call", "Try the calculator"). The checker scans against an 80-word imperative-verb list and reports any matches found.
Primary keyword position matters because Google bolds matching terms in the rendered snippet, drawing the eye. Keyword in the first half of the description gets bolded close to where the user is reading; keyword at the end is past the natural skim point. Front-load.
Sentence count is a readability proxy. One long compound sentence is hard to skim; four short ones are choppy. Two or three sentences hits the readability sweet spot — a one-sentence claim followed by a one-sentence proof or CTA reads cleanly in a SERP.
Trailing punctuation is small but signals intentional writing. Descriptions that end mid-sentence look truncated even when they fit. Always end on a period (or, sparingly, an exclamation point or question mark).
Generic phrases like "learn more" and "click here" are the lowest-CTR copy patterns in the SERP. Specific is better: "Read the 8-minute guide" beats "learn more"; "Run the audit in 30 seconds" beats "find out". The checker flags 7 generic phrases for replacement.
Six questions users ask.
What is the ideal meta description length?
Target 120-155 characters. Below 120, you waste the SERP real estate users see. Above 155, the description truncates with an ellipsis on most viewports. Mobile cuts off around 920 pixels (~120 chars), desktop around 990 pixels (~160 chars). The pixel-width gauge below the form measures rendered width using the browser's canvas API.
Does Google use my meta description?
Sometimes. Google rewrites meta descriptions roughly 60-70% of the time based on the user's query, pulling matching text from the page body when it judges that more relevant. A well-written description survives untouched on branded queries and on queries closely matching the page's primary keyword. For long-tail variants, Google tends to compose its own snippet.
Should every page have a meta description?
Yes for high-intent pages: home, primary service pages, top blog posts, top product pages. For long-tail blog archives or category pages where Google would compose better snippets per query anyway, hand-writing meta descriptions adds little value. The 80/20 rule: write meta descriptions for the 20% of pages that drive 80% of organic traffic.
What CTAs work in meta descriptions?
Action verbs that match the user's intent: 'Get a free quote', 'Book a 30-minute call', 'Download the guide', 'Try the calculator'. Avoid generic 'Learn more' — it doesn't tell the user what they'll get. The strongest CTAs are specific (named action + named outcome) and time-bound when honest ('Quote in 48 hours', 'Free for 30 days').
Can I paste full HTML?
Yes. The tool extracts the <meta name="description" content="..."> attribute automatically when it sees a full HTML head. Useful when copying from a CMS export or a templated page where you want to verify the rendered output.
Does this tool log my input?
No. All checks run in JavaScript on your device. Nothing is sent to Digital Heroes servers. No signup, no email, no analytics beacon includes the description content.
Three mistakes we see most.
Roughly 8 out of 10 meta descriptions we audit get rewritten by Google before they ship to the SERP, because the page-author wrote for a length target instead of a click target. Google's snippet documentation is explicit that the description is a hint, not a guarantee, and that Google overrides whenever the description does not answer the query.
Mistake 1, writing for length not benefit: teams pad descriptions to hit "155 characters" because a checklist told them to. The result reads like a sentence that ran out of momentum at character 80 and got dragged to 155. MDN's meta element reference documents the attribute but never prescribes a length; the real constraint is whether the snippet rewards the click. Front-load the benefit in the first 100 characters, treat 150 as a soft ceiling, and let the description stop when the value-proposition is complete.
Mistake 2, duplicating across pages: CMS-templated descriptions ("Premium { product.category } from Acme. Free shipping over $50.") read identically across 2,000 product pages. Google treats this as low-effort and silently rewrites, often pulling the first paragraph of body copy. The checker on this page flags duplication across a sitemap when run in batch mode. The fix is dynamic interpolation of a unique benefit per page, not just the product name.
Mistake 3, primary keyword buried past character 100: when the query term appears late in the description, Google's snippet-generation often crops the front and bolds a fragment from later in the page or even from anchor text on referring sites. Google's docs note that snippet relevance to the query is the primary override trigger. Put the primary intent term in the first 100 characters, then the differentiator.
When to actually use this: before publish on every new page, during quarterly sitemap audits (run in batch mode against your XML sitemap), after major SERP rank changes (Google may have rewritten your description; check what it now shows in Search Console performance reports), and whenever click-through rate drops without a position change. Pair with our SEO service if managing 500+ pages where templating discipline is the work.
Related Digital Heroes services + reading: See our SEO service for production-grade snippet strategy, plus our Title Tag Checker and SERP Preview Generator. Sibling tools: Open Graph Preview and Keyword Density Checker.
Title + meta + preview.
SERP Preview Generator
See snippet rendered live mobile + desktop.
Title Tag Checker
Length + pixel-width + 8 best-practice checks.
Meta Tag Generator
Full HTML head + OG + Twitter previews.
Structured Data Validator
JSON-LD validator for 8 types.
Headline Analyzer
Score H1s on emotion, power-word use, balance.
SEO service
Title + meta + content optimization.
Published · Last updated .