Reference
Frequently asked questions
Short answers, with links to the page that covers each topic properly.
Getting started
What do I need to run Gloty?
WordPress 6.4 or newer, PHP 8.1 or newer, and outbound HTTPS from your server. Gloty is built to run well on ordinary shared hosting, including sites without a persistent object cache. See Getting started.
Do I need my own AI API key?
No. Translation runs through the Gloty service using the engine your plan allows, so there is no key to obtain, store, or rotate. Pick a specific engine — or leave it on Automatic — under Settings.
How long does the first translation take?
It depends on how much content you have and how healthy your cron is. At default settings a site clears roughly a couple of hundred strings a minute once dispatch is running. A small site is done in minutes; a large store takes hours. You can raise the dispatch batch size to speed it up.
Content and quality
Will it overwrite my original content?
No. Translations are stored in Gloty's own tables and served dynamically. Your posts, pages, and products in the WordPress core tables are never modified.
Can I fix a bad translation?
Yes. Edit it on Gloty → Translations. The row is then marked Manually edited and machine sync will never overwrite it.
How do I stop my brand name being translated?
Add it to the glossary as Never translate. It stays verbatim in every language, the fix applies immediately to strings already translated badly, and it costs no quota.
What happens when I edit a page that is already translated?
The existing translations are marked stale and keep being served, so visitors never see a page revert to your source language. Genuinely new text is queued and translated automatically; rewritten text keeps its old translation until you re-queue the stale rows, so you decide when to spend the quota.
Does it translate images or PDFs?
No. Gloty translates text in your HTML output and your WordPress content. Text baked into an image is pixels, and attached documents are not processed.
URLs and SEO
What do my URLs look like?
Your source language keeps its existing URLs. Each other language
is served under a prefix — /de/, /fr/. A
query-parameter mode exists as a fallback. See
Languages & URLs.
Are slugs translated?
Not yet — /de/about-us/ keeps the source slug.
Translated slugs are planned for a future release; they are
deliberately deferred because getting them wrong breaks links and
rankings.
Will Google see my translated pages as duplicate content?
No, provided the hreflang annotations are in place — and they are,
by default. Each page is self-canonical and declares every
alternate language plus x-default. See
SEO.
Does it work with Yoast SEO or Rank Math?
Yes. Gloty translates their meta output rather than emitting its own, so you never get duplicate tags.
Performance
Will it slow down my site?
Rendering a translated page involves no remote calls — translations are read from your database, in a single bulk query per page. The heavy work happens in the background. See How Gloty works.
Does it work with my caching plugin?
Yes, and it purges the right URLs. LiteSpeed Cache, WP Rocket, W3 Total Cache, WP Super Cache, Cache Enabler, WP Fastest Cache, and SiteGround caching are handled automatically; each language-prefixed URL is purged, not just the canonical permalink. Custom and CDN caches can hook the purge actions.
WooCommerce
Does it translate my store?
Yes — product titles, descriptions, attributes and variation options, cart item names, checkout fields, order email subjects and headings, and breadcrumbs. See WooCommerce & builders.
Why is my Cart or Checkout still in English?
Those blocks render in the browser with JavaScript, so their text never appears in the HTML Gloty reads. Gloty installs the matching WordPress language packs to fix this. If a string has no community translation in the pack, it stays in English.
Does it convert currency?
No. Gloty translates text; prices, tax, and shipping stay under WooCommerce's control. Pair it with a multi-currency plugin if you need per-market pricing.
Plans and data
How is usage counted?
In characters of source text sent for translation, counted per target language. Identical text is translated once and reused, and glossary matches cost nothing. Serving pages is always free. See Plans & billing.
What happens if I run out of quota?
New translation work pauses until you upgrade or the period resets. Your already-translated pages keep serving normally — the site does not revert to the source language.
Can I use one license on several sites?
Yes, up to your plan's site limit. Each activated site uses one slot; deactivating releases it. Deactivate before migrating or cloning a site so you do not spend two slots on one live site.
What happens to my translations if I cancel?
They stay in your database and keep being served. You lose the ability to translate new content, not the translations you already have. This is the practical difference from a hosted translation SaaS.
Where is my content sent?
Only the source strings being translated leave your site, and only while a batch is in flight — they go to the Gloty service, which passes them to the translation engine for your plan. Translations are stored in your database; no visitor data is ever sent. See What leaves your site.
Migration and removal
Can I move from another translation plugin?
Gloty does not import from other plugins. It discovers your content itself, so the practical path is to run a content scan and translate fresh, review the output, then retire the old plugin. Keep both active only briefly — two plugins rewriting the same URLs will conflict.
What happens if I deactivate the plugin?
Background jobs stop and translated pages stop being served. All your data is preserved and everything resumes on reactivation.
What happens if I delete it?
The uninstaller drops Gloty's tables, deletes its options, and releases the license slot. That is irreversible — back up first if there is any chance you will return.
Still stuck?
Check Troubleshooting, then Gloty → Overview, which runs live health checks against your own site and usually names the problem directly.