The Short Answer
Write meta descriptions between 50 and 160 characters, and aim for 130 to 155. Google sets no hard limit and simply cuts long descriptions to fit the screen, but Bing Webmaster Tools flags descriptions it considers too long or too short, and a description that is cut off in results loses its last, often most useful, words. Measure the description in the finished page, not in the template that writes it, and make your build refuse anything outside the range. The same applies to titles: 60 characters or fewer for the full rendered title, suffix included.
The one sentence version
Keep every description between 50 and 160 characters, put the useful part first, and let the build fail rather than trusting anyone to count.
What Google Actually Says
Google's documentation on snippets is clearer than most advice written about it. There is no limit on how long a meta description can be. Snippets in results are truncated as needed, typically to fit the device width. And the snippet is created primarily from the page content itself; Google uses your meta description when it describes the page more accurately than text taken from the page would.
So for Google, length is not a rule you can break. It is a question of what survives truncation and whether your description is good enough to be chosen at all. Google also asks for descriptions that are unique to each page, and says programmatic generation is appropriate on large, database driven sites, as long as the results are readable and varied.
| Question | Google's answer |
|---|---|
| Is there a maximum length? | No limit; snippets are truncated to fit the device |
| Will my description always be shown? | No; snippets come primarily from page content |
| When is the description used? | When it describes the page more accurately than page text |
| Can descriptions be generated? | Yes, on large sites, if readable and varied |
| Same description on many pages? | Not helpful; use page level descriptions |
What Bing Flags
Bing is stricter in practice. Its Webmaster Tools reports a meta description that is too long or too short as an SEO issue, page by page. We could not find exact thresholds in Bing's own documentation, and third party guides disagree on the lower bound. What we can report is what Bing flagged on our own sites.
| What shipped | Length | What Bing did |
|---|---|---|
| 21 new pages on one site, 29 October 2026 | 164 to 205 characters | Flagged as too long |
| Directory listings, checked 2 November 2026 | 161 to 192 characters (39 pages) | Over our 160 limit |
| Other pages on the same directory | up to 265 characters (46 pages) | Over our 160 limit |
| Our rule since | 50 to 160, written to 130 to 155 | Build fails outside the range |
The first row taught us the lesson. Those 21 pages were built carefully, with every other check passing, and the descriptions were written by a generator that had no length rule at all. Bing's inspection tool showed the warning on the first page someone opened. Since then every page builder we run measures the description and fails outside 50 to 160 characters.
Bing matters more than its search share suggests
ChatGPT search leans on Bing's index and Copilot is built on it. A page Bing considers sloppy is a page those assistants meet with the same flags attached.
Why 130 to 155 Characters
The range is a margin, not magic. Under about 130 characters a description rarely says enough to earn a click; it states the topic and stops. Over about 155 it risks being cut on narrower screens, and the cut usually removes the part that makes someone choose your result: the number, the outcome, the reason. Between the two there is room for one complete promise.
Lead with the answer
Put the specific result, number or outcome in the first 100 characters, where every screen shows it.
One promise per description
Describe what the page gives the reader, not everything it contains.
Match the page exactly
A description that promises more than the page delivers earns a click and loses the reader.
| Weak description | Problem | Better approach |
|---|---|---|
| A list of every topic the page covers | Reads as keywords, says nothing specific | Name the one result a reader gets |
| The site tagline on every page | Identical across pages | Write a page level sentence |
| A sentence that ends in an ellipsis | Cut by the generator | Write to length, never trim mid sentence |
| Over 160 characters of detail | Truncated, flagged on Bing | Keep the strongest detail, drop the rest |
Titles Follow the Same Rule
The title tag has the same failure mode, and it is easier to miss because titles are often built in two layers. On a directory site we run, the listing template capped titles at 54 characters, comfortably under 60. The site layout then appended a brand suffix of 15 characters. Each layer was correct on its own, and 207 of the 265 listing titles rendered at more than 60 characters.
Give one layer ownership
Let the page build the complete title, suffix included, instead of each layer adding its own part.
Keep the suffix only when it fits
On that site 58 titles kept the brand suffix and the rest dropped it.
Use the space for the useful detail
47 titles got back a detail the old cap had cut, the one a reader compares on.
Measure the rendered string
Read the final title out of the built page and check it is 60 characters or fewer.
Search results show the site name separately, so dropping a brand suffix from a long title costs little. A cut off title that loses its most useful words costs more.
A Build Check That Refuses Bad Lengths
Rules written in a guide are forgotten. Rules enforced by the build are not. The check we now run on every site measures the final page, after every template and layout has done its work, and fails the build when a title or description is out of range.
Build the page as it will ship
Render the full HTML, with layouts, suffixes and defaults applied.
Extract the final strings
Read the title tag and the meta description out of the rendered page.
Measure in characters
Count characters, not words or pixels, so the rule is the same everywhere.
Fail outside the range
Titles 10 to 60, descriptions 50 to 160. Print the page and the length that failed.
Check the open graph copies too
Social titles and descriptions should match the main ones, or at least obey the same limits.
This takes minutes to write and saves the kind of cleanup that touches hundreds of pages. It belongs alongside the other checks in our technical SEO checklist, and it is the same habit that catches structured data problems before Search Console does, as in our guide to fixing review snippet errors.
Descriptions on Generated Pages
Most overlong descriptions are not written by people. They come from templates that join a variable to a fixed phrase. On the directory site, each listing description was a sentence built from the listing's own data followed by the same closing phrase on every page, and that closing phrase pushed 39 descriptions to between 161 and 192 characters. The page specific part was fine. The boilerplate broke it.
Put the variable part first
The page specific facts carry the meaning, so they go at the front where nothing can cut them.
Make boilerplate optional
Add a fixed closing phrase only when the whole description still fits in 160 characters.
Never cut mid sentence
If a variable is too long, choose a shorter field or a shorter sentence pattern, not an ellipsis.
Test with the longest real values
Run the template against the longest names and numbers in your data, not the average ones.
The proposed fix for those 39 listings is exactly the second step: drop the closing phrase when it would take the description over the limit. It removes the warning without touching the part of the description that is specific to each page.
How to Audit an Existing Site
Before fixing anything, measure everything. Fetch every address in your sitemap, read the title and description out of each page, and sort by length. Look for clusters, because a cluster of identical lengths or identical endings points at a template, and a template fix repairs hundreds of pages at once. Then sort the out of range pages by traffic, so the ones that earn are handled with the most care and the ones that earn nothing are fixed first.
| Audit output | What it usually means | Where to fix |
|---|---|---|
| Many pages at the same overlong length | One template with fixed text | The template |
| Titles all ending in the same brand phrase | A layout suffix | The layout or title owner |
| Empty or very short descriptions | A missing field in the data | The data source or a fallback rule |
| A few scattered long ones | Hand written pages | Each page, by traffic |
Fixing Pages That Already Rank
New pages should obey the rule from day one. Old pages that already rank deserve more care. A description change does not change the page content, and Google often writes its own snippet anyway, so the ranking risk of a better description is small. But a title change on a ranking page can shift how it matches searches. Treat them differently.
| Page | Description over 160 | Title over 60 |
|---|---|---|
| New page | Fix before shipping | Fix before shipping |
| Old page, little traffic | Fix | Fix |
| Old page that ranks and earns clicks | Fix carefully, keep the meaning | Change only with a reason, then watch for four weeks |
On the directory site the long blog titles and the 46 long descriptions are still waiting for exactly this decision, because those pages already rank. The listing titles were fixed the same day they were found, because they were generated and earned little. Prioritise by traffic, not by the length of the warning list. A warning list sorted by severity tells you what a tool noticed; the same list sorted by clicks tells you where a mistake costs you money, and that is the order to work in.
Descriptions and AI Answers
Assistants rarely quote your meta description. They read the page. But the description still does two jobs in the age of answers. It is often the text a search engine shows beside your link when an assistant cites you inside a results page, and it is one more place where a machine reads a summary of what the page claims. A precise description that matches the opening of the page reinforces the same facts, which is the habit our guide to writing for AI extraction recommends for every summary on a page.
Common Mistakes
Counting in the template
Layouts, suffixes and defaults add characters after the template is done.
Trimming with an ellipsis
A generator that cuts at 160 produces half sentences. Write to length.
One description for many pages
Identical descriptions are unhelpful and get replaced by page text.
Writing for length, not meaning
A description that fits but says nothing specific still loses the click.
The Bottom Line
Google will not punish a long description, it will just cut it. Bing will flag it. Write 130 to 155 characters with the useful part first, keep titles to 60 characters measured on the finished page, and make your build refuse anything else. Then spend the time you save on what the description promises, because the most precisely sized description in the world still has to describe something worth clicking.