Settings reference
Every option on Gloty → Settings, what it changes, and what it defaults to. Language and URL options live on the Languages screen; SEO options on the SEO screen.
Translation
Translation engine
Changed in 1.18.0 There is no engine setting. Which engine translates a batch is decided by the Gloty service rather than stored on your site, so it can change without a plugin update. Translation runs on OpenAI, with Google Gemini as the automatic fallback if OpenAI is unavailable.
Every plan uses the same engines — engine access is not a paid-tier perk. Google Translate and DeepL are no longer used: the AI engines produce comparable or better results on the context Gloty sends, as each string travels with the role it plays and its surrounding document.
Earlier versions offered a Translation provider dropdown (Automatic, Google Translate, DeepL, OpenAI, Google Gemini) gated by plan. That setting is gone. If you had chosen an engine, no action is needed: the saved choice is no longer used, and nothing you have already translated changes or is re-translated.
New content is translated automatically
Publishing always queues translations — there is nothing to switch on. Saving a post or updating a term registers its text and creates a pending row for every active target language; the background job then picks those up on its next run.
Changed in 1.18.1 Earlier versions showed an Auto-translate on publish toggle that defaulted to off. It never gated anything — translation happened either way — so it described the opposite of the actual behaviour and has been removed rather than left to mislead.
If you want to control when characters are spent, the effective levers are the dispatch batch size below, and dispatching manually from Gloty → Sync.
Dispatch batch size
How many strings are sent to the translator per batch. The background job runs about once a minute when WordPress cron is healthy and sends several batches each run, so a higher value clears a backlog faster. 100–250 suits a large initial translation; drop back afterwards if your host is sensitive to long-running requests.
The screen also shows when background dispatch last ran, and warns you if it looks stalled.
Cache translations
Reuse stored translations for identical text instead of re-sending it. Leave this on — turning it off means paying to translate the same sentence repeatedly. It exists for debugging translation output.
Exclusion selectors
.notranslate, .skip-translationA comma-separated list of CSS selectors whose contents Gloty leaves alone. Anything inside a matching element is neither captured nor translated.
.notranslate, .skip-translation, #site-credit, code, .brand-nameGood candidates:
- Code samples and technical output.
- Author credits, legal notices, and signatures.
- Third-party widgets that handle their own localisation.
- Brand-heavy regions such as a logo strip.
Keep the defaults.
Adding class="notranslate" to any element is the
quickest way to protect a one-off region without editing this
setting at all.
Visitor redirection
Auto-redirect by browser language
On their first visit, send visitors to the language version matching their browser preference, when you offer that language. Applied once per visitor and remembered with a cookie, so a manual choice from the switcher always wins afterwards. Search engine crawlers are never redirected, and only plain page views are affected.
Enable it once your target languages are substantially translated — see Languages & URLs.
Language switcher
| Setting | Options | Default |
|---|---|---|
| Style | Dropdown, Inline links, Flags only | Dropdown |
| Position | Top left, Top right, Bottom left, Bottom right, Manual (shortcode / widget only) | Bottom right |
| Show flags | On / Off | On |
Placement options, the shortcode, the widget, the footer list, and the CSS hooks are covered on the Language switcher page.
Settings that live elsewhere
| Setting | Where |
|---|---|
| Source language, target languages, activation | Gloty → Languages |
| URL strategy (subdirectory or query parameter) | Gloty → Languages |
| hreflang, metadata, sitemap alternates, JSON-LD | Gloty → SEO |
| Glossary terms | Gloty → Glossary |
| License key, plan, usage, subscription | Gloty → Billing |
| Scan mode and dispatch controls | Gloty → Sync |
Advanced tuning
A few behaviours are deliberately not exposed as settings, to keep the screen calm. They are available to developers as filters — see the developer reference:
| Filter | Controls |
|---|---|
gloty_dispatch_batches_per_tick |
Batches sent per background run (default 5). |
gloty_manual_dispatch_batches |
Batches sent by Translate now (default 20). |
gloty_capture_output |
Whether page HTML is scanned for new strings. |
gloty_translate_output |
Whether captured text is injected into the page. |
gloty_rewrite_output_links |
Whether the links-only rewrite pass runs. |