This article uses Korean text as its example. Google sets no character limit for meta descriptions or titles. Its Search Central documentation says there is no limit on length, and that results are truncated as needed, typically to fit the device width. So figures such as “160 characters” or “60 characters” are not rules; they are rough guesses meant to avoid truncation. This article separates what the documentation says from what it does not, and shows how to measure your own text with Geuljasu.
AI-generated image
What the documentation says
We checked two Google Search Central documents on 2026-10-30. Each shows its own last-updated date (Snippets 2026-04-20, Title links 2025-12-10).
| Item | What the document says | What it does not say |
|---|---|---|
| Meta description | No limit on length. In results it is truncated as needed, typically to fit the device width | At how many characters it is cut |
| title element | No limit on length. The title link is truncated as needed, typically to fit the device width. It advises avoiding unnecessarily long or verbose titles | At how many characters it is cut |
Neither document gives a cut-off in characters. “Device width” means the space on screen, not a character count, so text with many wide characters, such as Korean, may be cut sooner than text with narrow ones. Because the documents give no number, this article does not state one either.
Why measure length anyway
Putting the key point first keeps the meaning intact even if the end is cut. The values below are for two Korean example texts, counted by Geuljasu with spaces included, then without spaces, then as UTF-8 bytes.
| Text | With spaces | Without spaces | UTF-8 bytes |
|---|---|---|---|
| Title example (Korean, about using a counter for cover-letter length and the with/without-space difference) | 42 | 30 | 100 |
| Description example (two Korean sentences about checking cover-letter, SMS and social limits with a counter) | 88 | 68 | 208 |
Bytes are for reference only. A Korean character is 3 bytes in UTF-8, but bytes have nothing to do with truncation in search results. The Byte Counter is for places limited by bytes, such as text messages.
Check that the key point comes first
Paste text into Character Limit Trimmer and lower the limit step by step to see how the opening reads. Cutting the title example to 25 characters (spaces counted) leaves its main topic intact, which is the part before the ”|”. Cutting it to 30 stops partway through the part after the ”|”. The description example cut to 60 characters ends just after the first sentence plus the first two words of the second (“공백 포함”, meaning “with spaces”), so the first sentence has to carry the key point. These numbers are not Google’s real cut position; they are practice for asking whether the text still reads when cut.
Cautions
- “Meta description 160 characters” is not an official rule. It is a rough figure used by tools and guides and may change.
- The documents do not say whether spaces count. This article shows the with-spaces value by default.
- Do not pad text with repeated keywords. The documentation also advises avoiding unnecessarily long or verbose titles.
FAQ
Does a truncated meta description lower rankings? The documents checked here do not describe any link between truncation and ranking. Treat it only as a matter of how text is displayed.
What if my text looks different in results? The two documents checked here are not enough to name a cause. Shorten the text, put the key point first, and check the results again.
Are spaces counted? The documents give no rule. Compare the counts with and without spaces in the Word Counter and use the more conservative value.