Meta Description Too Short, and the 68 Character Case
The clearest meta description too short case we have is a roofing company in Georgia. Its description reads, "Roofing and insurance specialists serving our local Georgia community."
That is 68 characters. It is one complete sentence, it says what they do and where they do it, and our check flags it as too short because the floor is 70.
Two characters. That is the entire difference between a finding and no finding, and it is worth knowing before you rewrite a sentence that was already doing its job.
What the check measures
Our band runs from 70 to 160 characters. Below 70 is flagged short, above 160 is flagged long, and both findings exist because the two failures cost you something different.
A long description gets truncated, so the end of your sentence never appears. Google shows an ellipsis and the reader loses whatever you put last, which is usually the reason to click.
A short one is not truncated. It is smaller than the space available, and the finding exists because a description that fills its space has more room to persuade. The card's own text says this plainly, that a short description reads as an oversight and not a deliberate choice. That is the whole claim. There is no ranking effect, the finding costs three points, and it is rated low.
When a meta description too short is worth fixing
Where the description is a stub and not a sentence. "Welcome to our website" is fourteen characters, says nothing about the page, and gives a reader no reason to pick it over the result above. The fix is to write what the page offers and who it is for.
Both descriptions we found in our own store were sixty-eight characters and one was fifty-nine. Neither was a stub. That is a small sample, and it is the honest picture of how this finding arrives, which is usually as a boundary case on a page somebody already wrote a sentence for.
Where the page is competing for a query that matters and the description is doing no work. That is where the extra ninety characters buy something real, because the description is the only part of the search result you control.
Where you wrote it years ago and the business has moved on. That is worth a minute regardless of what the count says.
When it is not worth acting on
Where the description is a finished sentence and the count is the only complaint. The roofing example is that case. Padding it to clear a threshold produces worse copy, not better, and a description written to satisfy a character count reads like one.
The count cannot tell a short sentence from a thin one. That judgement is yours, and the report gives you the number and not the verdict.
There is a second reason to leave a good short description alone. Every rewrite risks losing the one thing it does well, and a description that already names the service and the area is doing the two jobs that matter. Expanding it with the third and fourth thing is where the padding starts, and padding is visible to a reader in a way that a character count never is.
What fills the band
Seventy to 160 characters is roughly one or two sentences, and the useful measure is not the character count but whether the description answers the question somebody typed. What the page offers, and what makes it different from the other nine results on the screen.
Where you are expanding one, the second sentence is usually the specifics. Not "we offer roofing services" but the thing that distinguishes you, the certification, the guarantee, the area you cover. That is the part a reader needs before they choose between you and the result above.
The three ways a description fails
We raise three separate findings here and they are worth telling apart. A missing description means the search engine writes the snippet for you, which is the guide on that finding. A long one means the end never shows. This one means there is less than there could be, which is the mildest of the three and the only one where doing nothing is often the right answer.
Where you want the mechanically opposite case, the guide on descriptions that run long covers what truncation cuts and how Google chooses the cut point.