Meta description is too long
description_too_longShort answer
The description is wider than about 920 px (around 155 characters), so the end is cut in results. No penalty; just put the sentence that sells the page first. Informational.
Why it matters
Like titles, snippets are cut to fit the result box. A long description whose first sentence is complete is fine; one that puts the point at the end loses it.
How Glimana detects it
Glimana measures the description's rendered width in Google's result font and fires above 920 px.
How to fix it
- Find the affected pages in Glimana. Open Issues › Meta description is too long. Every affected page is a row; open one to see the evidence Glimana recorded for it (the measured value, the offending element or the target URL). The same list sits on the task card under Tasks, and the page's own detail view under Pages shows its full signals.
-
Apply the fix on your platform.
Lead with the value and cut the preamble: the first 150 characters should already say what the page offers and why to click. Extra sentences beyond the 920 px limit are simply not shown; they do no harm, so this is a tidy-up, not an emergency.
Shorten the meta description in the SEO plugin's snippet box (the counter turns orange past the limit). If many pages are affected, the plugin is probably auto-generating descriptions from the first paragraph; set a template with
%%excerpt%%and write real excerpts for the pages that matter.Edit "Meta description" under Search engine listing on the product, collection or page. Themes that fall back to the product description (
{{ product.description | strip_html | truncate: 320 }}) should truncate at 160.Truncate generated descriptions at about 155 characters on a word boundary, or better, write them per page.
-
Publish and clear caches. Save and publish, then make sure the crawler will see the new version: WordPress — clear the page cache in your cache plugin and purge the CDN; Shopify — theme and content changes go live on save, but purge any CDN in front of the store; custom code — deploy and purge the edge cache. Check in a private window or with
curl -s https://your-domain/page | grep -i '<title\|canonical\|robots'that the live HTML has changed; Glimana reads what the server sends, not what your browser has cached. - Verify in Glimana. Open the task under Tasks and click Mark as done. The affected pages are queued for a verification crawl within a few hours, and the task closes when the description renders under 920 px. If the check still fails, the task returns to New with a note; when it passes, the task is listed under Resolved technical issues on Impact reports. To check sooner, use Re-crawl affected pages on the issue.
How the fix is verified
Re-crawl; the task closes when the description renders under 920 px.