glimanaDocs Open Glimana →

Issue guide · Content

Site name appears more than once in the title

SeverityInfo
CategoryContent
ScopePer page
EffortSmall
Verified byRe-crawl after you mark the task done
Rule keytitle_site_name_repeated

Short answer

"Acme Blog | Acme" — the brand twice, the topic squeezed. Usually a title template that appends the site name to a title that already contains it. Keep the brand once, at the end.

Why it matters

Titles are truncated to fit the device; every repeated word pushes the descriptive words off the edge. Google also tends to rewrite titles it judges repetitive. This is informational — it does not affect the health score.

How Glimana detects it

Glimana counts occurrences of each brand name (site settings and the detected site name) in the title and fires when one appears more than once.

How to fix it

  1. Find the affected pages in Glimana. Open Issues › Site name appears more than once in the title. 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.
  2. Apply the fix on your platform.

    Remove %sitename% from the template for post types whose titles already carry the brand, or stop adding the brand to post titles by hand.

    Theme titles are usually {{ page_title }} – {{ shop.name }}; do not add the shop name to the resource's own title.

    Append the brand in one place in the layout, never in both the page and the layout.

  3. 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.

  4. 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 site name appears once in the title. 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 site name appears once in the title.

Sources