📱 Device target
Mobile uses tighter pixel limits — Google cuts the title sooner on narrow screens.
📝 Title tag
📝 Meta description
🏷️ Brand (optional)
Used to warn when your brand will be truncated out of the SERP title.
🖥️ Desktop SERP preview
Rendering at the ~600px / ~990px desktop SERP pixel budget. Pixel widths are estimates.
📱 Mobile SERP preview
Rendering at the ~580px / ~680px mobile SERP pixel budget. Pixel widths are estimates.
⚠️ Warnings
- • {{ w.message }}
- • {{ w.message }}
💡 Suggestions
- • [{{ s.field }}] {{ s.message }}
Paste a title and a meta description on the left to see the SERP preview, pixel widths, truncation, and suggestions.
ℹ️ About Title & Description Length Checker
Why Google truncates by pixel width, not by character count
Search results render in a proportional font where each character has a different width.
An eight-character title made of WWWWWWWW is roughly three times wider
than an eight-character title made of iiiiiiii — both are eight characters, but only one
of them fits inside Google's title pixel budget.
This tool estimates the rendered width of your title tag and meta description against Google's measured pixel limits, previews how the SERP snippet will actually display, and flags the most common length, brand-truncation, and emoji-penalty issues before you publish.
SERP pixel limits
- Title (desktop) — ~
600px, roughly 50–60 characters in Arial 18px bold. - Title (mobile) — ~
580px; mobile screens are narrower and Google leaves room for the favicon and site name. - Description (desktop) — ~
990px, roughly 150–160 characters in Arial 13px. - Description (mobile) — ~
680px, often only 120–130 characters before truncation. - These numbers are widely-cited Moz / RankRanger measurements from 2022–2023. Google does not publish them, so treat the budgets as approximations — a 10–20px buffer is sensible.
What this tool checks
- Character + word counts for both fields.
- Estimated pixel width using a hardcoded Arial-glyph width table (per character).
- Truncation point — the exact character index at which Google likely cuts the snippet.
- SERP preview — desktop and mobile renderings of the title link, the URL line, and the description as Google would display them.
- Brand-suffix detection — if your title is something like
"Page Title | My Brand"and is too long, the tool flags that the brand will be cut. - Emoji / special-character penalty — emoji and non-ASCII characters render wider than ASCII letters and eat extra pixels.
- 0–100 score per field combining all of the above.
- Cross-field suggestions — too short, too long, brand truncated, CTA cut off.
Practical use cases
- Pre-publish QA — paste your draft title and meta description, see exactly what Google will display.
- Brand-name protection — ensure your brand isn't getting truncated from the title link.
- Rich-result readiness — Google's "rich results" treatment requires reasonable title + description metadata.
- A/B title variants — compare two drafts side-by-side by pasting one at a time.
- Mobile-first SERP audits — mobile truncation is stricter; the device toggle lets you check both surfaces.
Output fields
- Character length — total characters including spaces and punctuation.
- Pixel width — estimated rendered width using the bundled Arial width table.
- Pixel limit — Google's measured budget for the current device.
- Truncation point — character index at which the snippet is cut. If equal to the total length, nothing is truncated.
- Truncated text (with ellipsis) — exactly what the user sees in the SERP.
- Within limits — boolean shortcut for "ship it".
- Score — 0–100 composite of length, truncation, brand visibility, and emoji-width penalty.
- Warnings — specific severity-tagged messages per field.
Related references
- Google: Control your title links in search results — official guidance on how the title link is built and when Google rewrites it.
- Google: Control your snippets in search results — meta description usage and rewrite behaviour.
- Moz: Title Tag — community reference on title length practice and the ~600px pixel rule.
- Wikipedia: Meta description — historical context and HTML reference.
Limits and privacy
- Inputs are capped at 10,000 characters per field. Above that, the analyzer refuses to start.
- The same TypeScript module runs in the browser and behind the API endpoint (Module-First pattern). Browser results are byte-identical to the API output.
- Analysis runs locally in the browser — your title and description never reach a server unless you call the API endpoint explicitly.
- Pixel widths are estimates based on Arial glyph metrics. Real-world SERP rendering varies slightly by browser, device pixel ratio, and Google's own A/B experiments. Treat results as a strong signal, not a guarantee.
API Usage Example:
POST /api/tools/seo/title-description-length-checker
Content-Type: application/json
{
"title": "Title & Description Length Checker | Online Cyber Tools",
"description": "Check SEO title and meta description length, pixel width, and Google SERP preview.",
"brand": "Online Cyber Tools",
"brandSuffix": " | Online Cyber Tools",
"device": "desktop"
}