# Meta description length, with examples that earn the click

Write for the snippet, not the tag. Aim for around 155 characters on desktop, shorter on phones. You still write it even when Google rewrites it, because a good snippet answers the search.

Updated 2026-09-13 · Source: https://porteur.ai/guides/meta-description-length

## How long should a meta description be

About 155 characters on desktop. Shorter on phones.

Write to be clear in about two short clauses. If it runs long, trim the second clause first. Avoid fluff and empty adjectives.

| Context | Practical target | Why |
| --- | --- | --- |
| Desktop results | Up to about 155 characters | Longer line length, more room before truncation |
| Phone results | Shorter than desktop, write for the first sentence | Narrower screen, snippets cut earlier |

> Google may show more or less than your tag. Treat 155 characters as a writing target, not a rule.

## Why write one if Google rewrites most

Because your tag guides the snippet when the query matches it. It also appears on social shares and internal tools. It sets the pitch you want seen.

Google often pulls a sentence from the page body. That is fine when the page is well written. It is poor when the page opens with fluff or a cookie wall.

So write a tag that answers the search in one line. Then make sure the same answer is in the first paragraph on the page. You cover both cases.

> Your tag does not boost rankings on its own. It earns clicks. Better click-through can grow traffic on positions you already hold.

## What a good meta description looks like

It answers the query in plain words. It names the product, the action, and one proof. It avoids brackets, emojis and sales fluff. It reads like a line of support, not a slogan.

- State the outcome first, then the feature that makes it true
- Use the searcher’s words once if they are natural
- Name one concrete detail: a limit, a file type, a time, a format
- Avoid empty words: simple, powerful, amazing, intuitive
- Do not repeat the title
- Do not stuff keywords

```html
<meta name="description" content="Create proposals in minutes with your logo and pricing. Works with PDFs and e‑sign. Start free on yourproduct.com." />
```

The fixed page should echo this in the first paragraph. That keeps the body snippet strong when Google rewrites it.

## Examples that earn the click

These examples fit around 155 characters and work on phones when trimmed. Adjust the nouns to your product. Keep the structure: outcome, detail, action.

/pricing

- Before: "Flexible pricing for every team. Choose the plan that suits you."
- After: "See plans and limits for teams of 1 to 50. Monthly and annual. Free trial on all tiers. Switch any time from your billing page."

/guides/getting-started

- Before: "Getting started with YourProduct. Learn the basics in this guide."
- After: "Set up YourProduct in 10 minutes. Connect your domain, invite your team, ship your first update. Screenshots for each step."

yourproduct.com/tools/title-and-meta-description-checker

- Before: "A free tool to check your titles and meta descriptions."
- After: "Preview your title and meta description as they appear on Google. Count pixels and characters. Paste a URL or text. Free and fast."

A product feature page, like "/features/calendar"

- Before: "Our calendar feature helps you stay organised."
- After: "Plan launches on a drag and drop calendar. Syncs with Google Calendar. Colour labels and due dates. Free on Starter."

A comparison page, like "/compare/yourproduct-vs-competitor"

- Before: "YourProduct vs Competitor. Which is better?"
- After: "YourProduct vs Competitor: pricing, limits and support side by side. We compare features that matter for startups and small teams."

> Test the after line as your on-page first sentence too. If it reads well there, you are safe when Google rewrites the snippet.

## Writing to the query, not the tag

Searchers see a query-led snippet. Your tag wins when it matches the words and the intent. Write different lines for different page types.

- Feature pages: outcome, key feature, one proof
- Guides: the task and what the reader will finish with
- Pricing: plans, a limit or allowance, billing cadence
- Comparison: the two names and what you compare
- Integrations: what it connects to and what it syncs

For a query like "meta description length", the snippet that earns the click is direct: "About 155 characters on desktop, shorter on phones. Examples that fit." That answers, then promises depth.

## Handling truncation on phones and long queries

Write the first 90 to 120 characters to stand alone. Put the payoff there. Anything after that is a bonus when space allows on desktop.

- Avoid starting with your brand name unless it is needed
- Keep numbers early: minutes, file types, limits, formats
- Remove filler clauses: "with ease", "designed for", "learn how to"
- Prefer a full stop over commas that pad the line

Long queries often trigger a body snippet that includes the matched words. Place those words once, naturally, in your first paragraph. That helps the rewrite read well and avoids keyword stuffing in the tag.

## How to add or fix meta descriptions

1. **Find your key templates** List your key page types. For a SaaS, start with home, pricing, features, integrations, docs hubs, top guides, login-free tools.
2. **Draft one line per type** Use the structures above. Keep under about 155 characters. Paste into a character counter to check. Read it out loud once.
3. **Put the line in the tag and on the page** Add the meta tag in the head. Mirror the same idea in the first paragraph so a rewrite still sells the click.
4. **Ship to staging and check** View source and verify one tag per page. Load the page with JS disabled. Confirm the description is present in the HTML.
5. **Go live and let it recrawl** Submit the URL in Search Console if you need it fresh. Expect the snippet to change with the query. Track clicks over 28 days.

```html
<head>
  <title>Pricing for startups and small teams</title>
  <meta name="description" content="See plans and limits for teams of 1 to 50. Monthly and annual. Free trial on all tiers. Switch any time from your billing page.">
</head>
```

> Use only one meta description tag per page. Duplicates confuse parsers and can be ignored.

## How to check meta descriptions in bulk

Crawl your site and export title, description and status code. Focus on live 200 pages that can rank. Ignore redirects, 404s and noindex pages in this pass.

- Sort by missing or empty descriptions
- Sort by length to catch very short and very long lines
- Group duplicates across different URLs
- Spot pages where the first paragraph does not match the tag

If your CMS supports it, expose description fields in your sitemap or an admin export. That lets you fix many at once without view source on each page.

Search Console can show which pages get impressions but few clicks. Pair that with your crawl to pick which descriptions to rewrite first. Start with pages on page one or two for their terms.

## Pages you can skip or handle differently

- Noindex pages: drafts, internal dashboards, admin routes
- Redirect targets: the snippet comes from the final URL, not the redirect
- Paginated lists: use a clear first paragraph and consider leaving the tag blank
- Very long docs: put the task and result in the opening paragraph, the body will likely be used

Avoid http meta refresh and JavaScript redirects on pages you want to rank. Use a server 301. If you must refresh, keep a proper canonical on the final URL and do not worry about the description on the jumping page.

## Measuring impact in Search Console

Use the Performance report. Switch to Pages, then add a filter for your edited URLs. Compare the last 28 days to the prior 28 days. Look at clicks and CTR, and keep an eye on average position shifts.

- Rising impressions with flat clicks: your snippet is weak or mismatched
- Flat impressions with rising clicks: your new line is working
- Falling clicks with falling position: not a snippet issue, look at content and links
- Big swings day to day: wait for a full 28 days before judging

Export the query list for each page. If the top queries changed, rewrite the description to match the new terms. Keep the page paragraph aligned with the tag so rewrites stay persuasive.

## Questions

### What happens if a meta description is over 155 characters?

Nothing breaks. Google may truncate it or ignore it and use the body instead. Put the payoff in the first sentence so it still works when cut on phones.

### What is the ideal character length for a meta description?

Aim for around 155 characters on desktop and shorter on phones. Treat it as a writing target, not a rule. Make the first 90 to 120 characters self contained.

### What should a meta description look like?

One clear sentence that answers the query. Outcome first, one concrete detail, then the action. Avoid fluff, emojis and brackets. Do not repeat the title.

### How many words should be in a meta description?

About 18 to 24 short words fits near 155 characters. Count characters, not words, because truncation depends on characters and how they render.

### Do I need a meta description on every page?

Add them on pages that can earn search clicks. For thin or paginated pages, a strong first paragraph can be enough. Avoid duplicates across many URLs.

### Do keywords in the meta description help rankings?

They do not act as a direct ranking factor. They help win clicks when they match the searcher’s words. Put them in naturally, once.

## Read next

- [Title tag length: what fits, what Google rewrites, and how to write one](https://porteur.ai/guides/title-tag-length): About 60 characters is a safe line. Learn pixels versus characters, why Google rewrites titles, and how to write titles that earn clicks.
- [On-page SEO checklist: the twelve things on the page](https://porteur.ai/guides/on-page-seo-checklist): The twelve page elements that move clicks and rankings, with examples you can copy to your own product pages today.
- [Search intent: what the results page tells you to build](https://porteur.ai/guides/search-intent): Learn the four intents, read intent from the results page, and fix pages that will never rank by changing their kind, not just the words.
- [The Search Console performance report, column by column](https://porteur.ai/guides/search-console-performance-report): Every column in the Google Search Console performance report explained with the traps that trip small sites, and how to act on each.
- [Landing page SEO: one page, one search, one promise](https://porteur.ai/guides/landing-page-seo): Give each landing page a target query, a clear promise, proof, and one CTA. Keep it from clashing with your home page. Steps and examples inside.
- [What a good SEO report contains, with an example](https://porteur.ai/guides/seo-report-example): See what a good SEO report contains, how it drives decisions, and a worked example on a product page you can copy for your next report.
- [Title and meta description generator](https://porteur.ai/tools/title-and-meta-description-generator): Paste a page URL or a search phrase and get five titles under 60 characters and five descriptions of 120 to 155, written from the page, lengths counted.
- [Search snippet](https://porteur.ai/glossary/search-snippet): What a search snippet is, where its text comes from, how to measure it, how to improve rich and featured snippets, and when to limit it.

Paste your URL to get a fast read on your titles and descriptions against the searches around them and three pages you compete with, free in about thirty seconds. Free check: https://porteur.ai/