---
title: Booking text not translating with WPML or GTranslate
description: "Some text in the booking experience stays in the original language even though your translation plugin, such as WPML or GTranslate, is set up. **Why this…"
url: "https://homerunner.io/docs/why-don-t-some-homerunner-booking-strings-translate-even-with-my-translation-plu/"
updated: "2026-10-26"
category: Theme and design
---

# Booking text not translating with WPML or GTranslate

Some text in the booking experience stays in the original language even though your translation plugin, such as WPML or GTranslate, is set up.

**Why this happens.** These parts of the booking experience render their text in JavaScript after the page loads, and a few strings come directly from the HomeRunner API. A translation plugin that works on the server-rendered HTML (such as WPML string translation or GTranslate) never sees those strings, so they stay untranslated. This is expected behavior for server-side translation plugins.

**Language prefixes in URLs.** If your translation plugin adds a language prefix to URLs (for example /en/ or /fr/), it can also rewrite the widget's asset and config URLs to that prefixed path, which breaks the widget.

**What you can do.** Getting these strings into each language takes site-level handling that the HomeRunner team sets up for you. With this setup, the booking widget is passed your active locale so dates format correctly per language. The dynamically rendered booking strings (calendar labels, checkout notices, price-breakdown terms, the "no results" message) are swapped per language after they render. The URL rewriting is corrected as part of the same setup. Contact HomeRunner support with the list of languages your site uses, and support configures this for you.

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