When something is wrong

A string stays in the source language

Look under WPGlotty → Strings first. Missing text has not been collected: check exclusions and translate="no". WPGlotty also collects text JavaScript adds after the page loads. For text loaded through admin-ajax.php, list the plugin’s action under Settings, Translation settings, Translate AJAX actions.

If it is listed but untranslated, it is queued or has failed. Check the status screen to see which.

Nothing is being translated at all

Check these four things in order: an active licence, available credits or a paid plan, a provider key unless using credits, and WordPress cron. If WordPress cron is disabled, check its replacement system cron is running. Check Automatic translation is not Off and neither your monthly budget nor the site’s monthly word limit has been reached. After a TranslatePress import, check your languages are switched on. Translation status shows notices for these issues.

The translation is right but reads badly

Start with the translation style, tone of voice and glossary rather than changing models. Adjust these, then use Translate everything again for that language. Click any remaining awkward wording on the page to correct it. Your manual corrections stay unchanged.

Visitors see the old text

A page cache may be showing old text. WPGlotty clears supported caches, but it may not be able to clear your server’s cache. Clear it manually to check whether this is the cause. If so, connect it using the purge filters.

The licence says it cannot be reached

WPGlotty keeps the last licence response and continues working. If the warning lasts more than a day, check whether your site can reach wpglotty.com. A firewall blocking outgoing HTTPS also blocks requests to your translation provider.