Documentation
Gloty documentation
Gloty makes a WordPress site multilingual: it discovers every
translatable string on your site, translates it in the background,
and serves the results from your own database under clean
language URLs like /de/ and /fr/.
These pages cover the plugin end to end — installing it, choosing languages, running the first translation, refining the output, and the hooks and endpoints available if you want to extend it.
Applies to Gloty 1.15 and later. Features added in a specific release are marked inline. Your installed version is shown at the top of Gloty → Overview in wp-admin.
New here? Start with these
- Getting started Requirements, install, and the five-minute setup wizard through to your first translated page.
- How Gloty works The capture → translate → serve pipeline, and why your pages never wait on a translation API.
- Languages & URLs Source and target languages, URL structure, and how visitors move between language versions.
What Gloty does
hreflang with x-default,
per-language canonicals, translated titles and meta, Open
Graph, JSON-LD, and sitemap alternates.
The short version
- 1 · Discover Gloty finds translatable strings as pages render and during a content scan.
- 2 · Queue New strings are stored as pending rows in your database.
- 3 · Translate A background job sends batches to the Gloty translation service.
- 4 · Serve Results come back, get cached locally, and appear on your language URLs.
Browse by task
- The dashboard Read the Overview screen: what the counts mean and where work is stuck.
- Scanning & sync Run a content scan, dispatch translations, and read the job queue.
- Managing translations Filter, edit, protect, re-queue and delete individual translations — including the visual editor.
- Glossary Keep brand and product names exactly right in every language.
- SEO hreflang, canonicals, metadata, sitemaps, and Yoast / Rank Math compatibility.
- WooCommerce & builders Products, cart, checkout, emails, and page builders like Elementor and Divi.
- Settings reference Every option on the Settings screen, what it does, and its default.
- Plans & billing Character quota, site limits, translation engines per plan, and managing your subscription.
- Troubleshooting Nothing is translating, translations look stale, cron is stalled, quota is exhausted.
- Developer reference Filters, actions, REST endpoints, database tables, and configuration constants.
Requirements at a glance
| Requirement | Minimum | Notes |
|---|---|---|
| WordPress | 6.4 | Tested up to 6.7. |
| PHP | 8.1 | On older PHP the plugin deactivates itself and shows a notice rather than breaking the site. |
| Outbound HTTPS | Required | To reach the Gloty translation service in the background. Never during a page render. |
| WP-Cron or a real cron | Recommended | Drives background dispatch. Without it, translations only move when you click Translate now. |
| Permissions | manage_options |
Needed to open the Gloty admin screens and the visual editor. |
Getting help
The Troubleshooting page covers the problems we see most often, and Gloty → Overview surfaces live warnings about your specific site (connection, quota, stalled cron, failed jobs). If something is still wrong, include your Gloty version, WordPress version, PHP version, and a screenshot of the Overview screen when you contact support.