---
title: "English labels on GTranslate-translated pages"
description: On pages translated by GTranslate, most of your site appears in the selected language, but some HomeRunner labels, such as calendar buttons and small…
url: "https://homerunner.io/docs/why-do-some-homerunner-labels-like-calendar-buttons-and-small-ui-text-stay-in-en/"
updated: "2026-10-26"
category: Theme and design
---

# English labels on GTranslate-translated pages

On pages translated by GTranslate, most of your site appears in the selected language, but some HomeRunner labels, such as calendar buttons and small interface text, stay in English.

**Why this happens.** Three separate layers produce these labels, and each needs its own fix. From the front end they all look the same, so you may need to check each one.

**Calendar month and weekday names.** These come from WordPress core, not the HomeRunner plugin. Without the WordPress core language pack for a language, these names fall back to English on translated pages. Install the core language pack for every language GTranslate serves. Go to **Site Language** settings and add each locale, or ask support to run the core language install for you.

**HomeRunner JavaScript labels.** HomeRunner's own JavaScript labels are translatable per site using Loco Translate (text domain: **homelocal**). Add the missing strings for each language and save. If a stale cached translation file is shadowing the new one, support can check and clear it.

**Labels from a custom site plugin.** Labels set by a custom site plugin through WordPress script translations can be broken by the GTranslate proxy itself. The proxy machine-translates the keys of the inline translation data, so the lookup no longer matches and the English source text shows instead. Marking the script as 'notranslate' does not prevent this. The fix is a site-level adjustment that protects the translation data from the proxy. Contact HCS support to enable it for your site.

Still stuck? [Contact the HomeRunner team](https://homerunner.io/contact/) with your site address and what you tried, and we take it from there.