Title is very short
title_too_shortShort answer
The title has fewer than 20 characters ("Pricing", "About"). Google has no minimum, and a short title that says exactly what the page is works fine. Expand it only if it fails to describe the page or to match what people search for.
Why it matters
Short titles tend to be generic, and generic titles are rewritten by Google and skipped by searchers. "Pricing" is fine for a pricing page; "Guide" is not for a 3,000-word guide. This rule is informational.
How Glimana detects it
The rule fires for an indexable page whose title is shorter than 20 characters.
How to fix it
- Find the affected pages in Glimana. Open Issues › Title is very short. 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.
Add the topic and, where it helps, the brand: "Pricing — Glimana" instead of "Pricing", "Hreflang: the complete setup guide" instead of "Hreflang". Target the main query the page already ranks for: the page's queries are listed on the Pages screen, and the title should contain the words people actually search.
Edit the SEO title in the plugin's snippet box. One-word titles usually come from pages created with a short slug-like name ("Contact", "About") and a title template without the site name; add
%%sep%% %%sitename%%to the template in Yoast › Search Appearance or Rank Math › Titles & Meta.Edit "Page title" under Search engine listing. For collections, include what the collection contains ("Women's running shoes" rather than "Running"); for pages, add the shop name through Online Store › Preferences.
Build titles from the page's main heading plus a short qualifier and the brand. Do not use the route name or a database label as the title.
-
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 is longer than the minimum width. 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 is longer than the minimum width.