Your site serves the original language even though Universally is set up. Work through these in order: the first three checks cover most cases, and caching is the single most common cause once setup is correct.
Check the basics first
- Check the project's Domain matches the site you are browsing. Open General Settings and compare it with the address bar. A site with the wrong domain serves every page in the source language and reports no error at all. Only the bare and
www.forms are interchangeable: a staging host, a different subdomain, or an old domain after a move is rejected. - Visit a translated URL directly, such as
/es/followed by a page path, rather than waiting for a redirect. If that page is translated, the problem is the switcher rather than translation. See The switcher is not visible. - Confirm a target language is enabled. Open the project and choose All Languages. If the list is empty, nothing can be translated.
- Run the connection check. Open the project's API Settings. For a WordPress project it checks your site live and reports one of four results: plugin connected, plugin not detected, site unreachable, or plugin out of date. Use Check again after a fix, and update the plugin if it reports an old version.
The plugin is active but nothing is translated
Cause. The API key is missing, wrong, or was never saved.
Fix. Copy the key from the project's API Settings screen and paste it into the plugin, then save. A key that was pasted with a trailing space fails the same way as a wrong key.
See Find your API key.
Only some pages are translated
Cause. The page is excluded, or nothing on it has been translated yet.
Fix. Check the project's Translation Rules screen. Two settings take content out: a path under Exclude Pages is served in the source language deliberately, and an Exclude CSS Selectors entry removes the elements it matches along with everything inside them. .notranslate, class="no-translate" and translate="no" in your own HTML do the same thing.
See Translation rules.
It worked, then stopped
Cause. The plan's word total is exhausted, so new text is no longer being translated.
Fix. Check usage on the dashboard. Pages translated before the total ran out keep serving; new or changed text waits until you have words again, either by adding a word add-on or by moving to a larger plan. If you have a card on file, the move may already have happened automatically.
See Usage limits.
The page is translated when logged in but not for visitors
Cause. A cached copy of the original page is being served.
Fix. Clear your site cache, then your CDN cache, then your browser cache, in that order. A page-caching plugin or a CDN will keep serving the version it stored before Universally was connected.
See Caching and CDNs and Clear cache and refresh translations.
Still stuck
Email [email protected] with the site URL, the translated URL you tried, and which language. See Get support.