Using Gloty
The dashboard
Gloty → Overview is the screen you land on and the one worth learning to read: it answers "is this working, and how far along is it?" in about five seconds.
The headline numbers
Three stats across the top describe the state of your queue.
| Stat | Counts | What a high number means |
|---|---|---|
| Translated | Finished translations, shown against the total expected — source strings multiplied by target languages. | Good. When it approaches the total, your site is substantially multilingual. |
| Pending | Rows discovered but not yet translated. | Work in progress. It should fall steadily; if it does not, check cron and quota. |
| Out of date | Translations whose source text has changed since they were produced. | You have been editing content. Re-queue these when you are ready to spend the quota. |
"Translated" is counted across all languages. The total it compares against is strings × target languages, so on a two-language site the denominator is roughly double your source string count. That is deliberate — it is the amount of translation work your site actually represents.
Supporting stats
Translation status
The pipeline panel follows one cohort of strings through the system. Reading left to right tells you where work is piling up:
- Collected Discovered on your site.
- Queued Waiting to be sent.
- Sent Dispatched and awaiting results.
- Translating Being worked on.
- Done Delivered and serving.
- Out of date Source has since changed.
| If work piles up at | Look at |
|---|---|
| Queued | Dispatch is not running — usually WP-Cron. See Troubleshooting. |
| Sent or Translating | Results are not coming back. Check for stuck jobs and a blocked webhook on Gloty → Sync. |
| Collected, with nothing moving on | Connection, license, or quota. The issues list below will say which. |
Language progress
A per-language breakdown of how much is translated. Use it to decide which language is ready to promote — and to spot a language you enabled and then forgot. Your source language is not listed, because it needs no translation.
Health warnings
Gloty runs live checks against your own site and surfaces anything wrong here, ranked with errors first. Each has a direct action link, so you can go straight to the screen that fixes it. The full list of checks — connection, license, quota, stuck jobs, failed jobs, stalled cron — is documented in Troubleshooting.
A quota notice appears once you pass 80% of your monthly characters, well before anything stops working.
An empty issues list is meaningful. It means the connection, license, quota, cron, and job queue all checked out. If translations still are not appearing with a clean bill of health, the cause is almost always a page cache rather than Gloty.
Getting started checklist
Until you have finished setting up, the dashboard shows a short checklist — choose your languages, scan your content, translate — with each step linking to the screen that completes it. It disappears once the work is done, and it agrees with the setup wizard rather than tracking its own separate idea of progress.
Recent translations
The last handful of rows to change, with their original text, translation, language, status, and timestamp. It is the quickest way to confirm results are genuinely landing — if the timestamps are recent, the pipeline is alive. For anything more than a spot-check, use Gloty → Translations, which has search, filters, and editing.
A quick daily read
- Any errors in the issues list? Fix those first.
- Is Pending falling? If it is flat, dispatch is not running.
- Is Out of date climbing? You have edited content that needs re-queuing.
- Are the Recent translations timestamps fresh?
- Is quota comfortable for the rest of the period?