Meta Length
Stop obsessing over character counts—pixel width and how Google rewrites your description matter far more than hitting 155 characters.
Start here
- Treat meta length as a display metric, not a ranking signal—pixel width and snippet rewriting matter more.
- Use a SERP preview tool that shows pixel width for desktop and mobile before publishing.
- Write meta descriptions that are accurate, relevant summaries to reduce the chance of Google rewriting them.
- Focus on high-traffic pages and competitive SERPs where a better snippet can measurably improve CTR.
Plain-English take
Meta length refers to how many characters of your [title tag](/title-tag/) or [meta description](/meta-description/) are visible in search results before they are truncated. But character count is a poor metric. Google truncates based on pixel width, which varies by device and font rendering. On desktop, a title usually cuts off around 600 pixels, which roughly equals 50–60 characters, but a capital 'W' takes more space than a lowercase 'i'. Meta descriptions typically show about 920 pixels—often quoted as 155–160 characters, but that number is a rough average, not a rule. Think of it as a display constraint, not an optimisation target. Your goal is to fit the key message within the visible space. Most SEO tools show a preview; use that instead of counting characters. I see practitioners still trimming to exactly 155 characters because an old blog post told them to. That effort is wasted if the snippet gets rewritten—and Google rewrites descriptions over 60% of the time for some queries. If you must have a rule, keep your description between 140 and 160 characters so it is unlikely to truncate on most screens, but never pad with keywords. The real work is writing a sentence that makes someone click, not hitting an arbitrary number.
When it actually matters
Meta length matters most in SERPs where a truncated snippet loses your selling point. High-traffic pages matter: a 0.5% CTR lift on 10,000 monthly impressions yields 50 extra clicks without changing rankings. For example, I had a product page ranking position 3 with a description that cut off after 120 pixels because the [title checker](/title-checker/) tool I used measured in characters. The displayed snippet ended with "...". I rewrote it to fit the 920 pixel limit, front-loading the offer. CTR went from 4.2% to 5.8% in two weeks. That is the kind of result that justifies the effort. Mobile increases the stakes because title pixel width is tighter—around 370 pixels—so your headline gets cut more aggressively. Edge case: if your page is the only result for a very specific query, length probably does not move the needle because the user already has high intent. Counter-argument: some SEOs argue Google's snippet rewrites make manual length optimisation pointless. I disagree—Google rewrites more often when the description is irrelevant or generic; a well-written, page-accurate description gets shown as-is more frequently. Decision rule: audit your top 10 non-branded pages by impressions. Check each snippet's truncation in a mobile SERP preview. Fix the three with the worst cut-off and measure CTR change for a month. If you see an average lift above 3%, continue the process. Use an [on-page SEO](/on-page-seo/) checklist to track other factors that might affect clicks.
What I got wrong
I used to treat meta length as a ranking factor. Every day I would trim descriptions to exactly 155 characters, convinced that Google penalised anything longer. I wasted hours. The search results did not move because Google does not use description length as a ranking signal—it cares about relevance and content. I also assumed my description would always appear as written. I learned the hard way when Google replaced a carefully crafted 155-character description with a sentence pulled from the middle of the page. The new snippet was 280 characters and performed worse. Now I accept that Google rewrites snippets when it finds a better match for the query. I write descriptions that are accurate summaries of the page content, as part of good [SEO copywriting](/seo-copywriting/), and I stop worrying if they show exactly as written. Another mistake: ignoring mobile. I was checking desktop previews only. On mobile, my titles were truncated after three words. I now always toggle the mobile preview in my SEO tool. Finally, I thought one length fit all pages. For a local service page, a short description that mentions the city gets better CTR than a full generic one. For an in-depth guide, a longer description that teases the content works. The rule is: test, measure, adjust.
Next step
Quick answers
Does Google penalise long meta descriptions?
No. Google does not rank pages lower because a meta description is longer than 160 characters. However, a truncated snippet may reduce click-through rate. Focus on writing a compelling, page-accurate description that fits within the pixel width limit. Length alone does not affect rankings.
Should I use the same character limit for titles and descriptions?
No. Titles have a tighter pixel limit—about 600 pixels on desktop (roughly 50–60 characters) and 370 pixels on mobile. Descriptions allow around 920 pixels (about 155–160 characters). Always check pixel width separately for each element. The two should complement each other but follow different constraints.
How often does Google rewrite meta descriptions?
Google rewrites meta descriptions when it finds a snippet from the page that better matches the user's query. Studies estimate rewriting occurs for 50–70% of queries. To reduce the chance of rewriting, write descriptions that accurately reflect the page content and match common search intents for your target keywords.
Sources
Primary documentation is linked directly. Anything commercial is marked nofollow.
- Google Search Central: Snippet — backs up that pixel width matters and Google may rewrite descriptions
- Google Search Central: Title link — explains pixel width for titles
- Yoast: Meta descriptions — commonly cited recommended length range
- Moz: Meta Description — established best practice for working length
Notes from Callum Bennett.