Title is long enough to be truncated in search results
title_too_longShort answer
The title is wider than about 580 px in Google's result font (roughly 60 characters), so the end will be cut off on most devices. There is no penalty and no length limit — Google says so explicitly — but what is cut is not read. Put the words that matter first; trim if the end carries meaning.
Why it matters
Google truncates titles to the width of the result, not to a character count; wide letters use more space than narrow ones, which is why Glimana measures pixels. The rule is informational: a long title that front-loads its meaning is fine. It matters when the distinguishing part (the product, the year, the location) sits at the end.
How Glimana detects it
Glimana renders the title text in the font metrics Google uses for desktop results and fires when the width exceeds 580 px. The evidence shows the measured width and the title.
How to fix it
- Find the affected pages in Glimana. Open Issues › Title is long enough to be truncated in search results. 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.
Put the distinguishing words first, drop boilerplate ("Welcome to", "Official site", "Home page"), and keep the brand last, separated by a dash or pipe. Glimana measures the rendered width in pixels (580 px limit), so there is no need to count characters: a title of 60 characters in narrow letters can fit while 50 wide ones do not.
Pattern that works for most pages: Primary topic — qualifier | Brand, for example "Hreflang return tags: how to fix them | Glimana".
Edit the title in the SEO plugin's snippet box below the editor; the preview bar turns orange when too long. If every title is long, the cause is the title template: Yoast › Search Appearance › Content types (
%%title%% %%sep%% %%sitename%%), Rank Math › Titles & Meta. Remove the tagline variable (%%sitedesc%%) from the template; that alone usually fixes hundreds of pages.Product and collection pages: edit "Page title" under Search engine listing at the bottom of the product/collection editor. Store-wide suffix: Online Store › Preferences › Title and meta description, and check
theme.liquidfor{{ page_title }} - {{ shop.name }}patterns that append the shop name twice.Generate the title from the page's own fields and append the brand once in the layout. Truncate at a word boundary if the source field is free text (product names from a feed, for example).
-
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 title renders under 580 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 title renders under 580 px.