Your title fits in English. In German it gets cut.
Google truncates by pixel width, not by character count — and German, Spanish and Japanese are all wider than English at the same point size. Localecheck measures your titles and meta descriptions the way Google actually renders them, across 20 languages.
20 languages · desktop and mobile cutoffs · nothing uploaded — every check runs in your browser
Tools
Small, single-purpose checks. No signup, no credit card, no "request a demo".
SERP Preview (multilingual)
Type a title once per language and see the exact pixel width, the truncation point, and how each locale compares to your English baseline.
hreflang Generator
Build a complete, reciprocal hreflang block plus the matching sitemap XML from a list of locales and one URL pattern.
hreflang Checker
Paste a sitemap and every URL is checked at once: missing return links, wrong region codes and conflicting declarations.
Keyword Translation Trap
Check whether the keyword you translated is actually the one people search in that market — literal translations often have a fraction of the volume.
Full-width Counter
Count CJK characters properly, catch half-width punctuation mixed into Japanese copy, and get a usable length budget.
Batch Site Audit
Upload 50–200 URLs, get every locale's title and description width, truncation status and hreflang gaps in one table.
Why pixels, not characters
Every free "SERP preview" tool counts characters and calls it a day. That number lies as soon as you leave English.
Google cuts on width
The limit is roughly 580 px on desktop and 560 px on mobile for titles — measured in Arial at 20 px and 18 px. Fifty characters of "iiiiii" and fifty characters of "WWWWWW" are not the same problem.
Languages expand unevenly
German compounds, Spanish noun phrases and Cyrillic glyph widths all push a string past the cut at different rates. A 55-character English title routinely becomes 70+ in German — same word count, different rendering.
Truncation eats the qualifier
The part that gets cut is almost always the tail — the "2026 guide", the price band, the region. That is usually the part that made the click worth it.
Who this is for
Anyone shipping the same page in more than one language and getting held responsible for how it performs.
In-house SEO at a SaaS company
Six locales, one content team, and a CMS that happily ships a truncated title without warning anyone.
Small agency doing international work
You quote per market. Checking 40 URLs across 5 languages by hand is where the margin goes.
Localisation lead
You receive copy from a translator who did the job correctly — and still need to prove it will render inside the box.
What it will not do
Worth being clear before you spend time on it.
| Expectation | Reality |
|---|---|
| Guarantee a ranking outcome | No tool can |
| Translate your copy | Not a translator |
| Replace keyword research | Different job |
| Show how Google will truncate your font stack | Yes — Arial, Google's own |
| Work offline, nothing leaves the browser | Yes |
| Cost anything for a single page check | No |
Pricing
Single-page checks stay free forever. You pay when you need to do this at volume.
For one page at a time, any language.
No account needed
Batch runs in one language, CSV export.
or $120/year
Every language, batch runs, API access.
or $390/year