Troubleshooting
TranslatePress Automatic Translation Not Working: Causes and How to Fix It

Short answer
TranslatePress automatic translation usually stops because the setting is off, the Google or DeepL API key is invalid or restricted, billing is inactive, the daily character limit is reached, or cached pages stop the plugin from running. Test your credentials on the Automatic Translation tab first.
Key takeaways
- Check Settings > TranslatePress > Automatic Translation first.
- Google keys need the Cloud Translation API enabled and billing active.
- Referrer-restricted keys often fail because requests come from your server.
- Pages translate when first visited in the new language, not all at once.
- Clear page and CDN caches so translated URLs reach WordPress.
Why is TranslatePress automatic translation not working?
TranslatePress automatic translation usually fails because it is switched off, the API key is invalid or restricted, billing is not active on the translation account, a daily character limit is reached, or cached pages never trigger a translation.
TranslatePress can translate your site by hand or with a machine translation engine. Automatic translation depends on several moving parts: the plugin setting, the engine, your API key or license, and your site's caching.
Common symptoms include:
- Pages in the second language still show the original text
- Some strings translate and others do not
- Translation worked for a while, then stopped
- An error appears when you test your API credentials
The steps below follow the order TranslatePress itself uses, so you can work down the list and stop when it starts working.
Is automatic translation turned on?
Go to Settings > TranslatePress, open the Automatic Translation tab, and check that automatic translation is enabled and an engine is selected.
It sounds obvious, but it is the first thing to rule out. After updates or migrations, settings can reset. The TranslatePress automatic translation documentation shows the current layout of this tab.
On the same tab, confirm:
- The translation engine is the one you have credentials for
- The API key or license field is filled in
- The languages you added in the General tab are supported by that engine
Save the settings even if nothing changed. Saving can refresh stored values that were left in a bad state.
Is your translation engine set up correctly?
Each engine needs its own credentials: Google Translate needs a Cloud API key with the Translation API enabled, DeepL needs a DeepL API key, and TranslatePress AI needs an active license with credits.
TranslatePress supports several engines, and what is available depends on your plan. Check the current plan details on the TranslatePress site, since options change over time.
| Engine | What it needs |
|---|---|
| Google Translate | Google Cloud project, Cloud Translation API enabled, billing active, API key |
| DeepL | DeepL API plan and key, plus a TranslatePress plan that includes DeepL |
| TranslatePress AI | A license that includes AI credits |
For Google, follow the official TranslatePress guide to generating a Google Translate API key. Google's Cloud Translation documentation explains billing and quotas.
For DeepL, see the TranslatePress DeepL add-on documentation. A DeepL API key is not the same as a DeepL web or app subscription, so check you created an API key.
Is the API key restricted or blocked?
Keys with the wrong restrictions are rejected, because TranslatePress calls the engine from your server, so browser-based referrer limits often block it.
In Google Cloud, open the credentials page and check the key's application restrictions. Referrer restrictions are meant for keys used in a visitor's browser. TranslatePress sends requests from your web server, so those requests may not carry the referrer the key expects.
Safer choices are restricting the key to the Cloud Translation API and, if your host has a fixed outgoing IP address, restricting by IP. If you are unsure, check TranslatePress's key guide for its current recommendation.
Also confirm billing is active on the Google Cloud project. A key on a project with billing disabled is refused even when everything else is right.
Have you hit a character limit?
TranslatePress has a daily character limit setting, and engines have their own quotas, so translation stops once either limit is reached for the day.
On the Automatic Translation tab, look for the setting that limits machine translation characters per day. It protects you from big bills, but a low value can stop translation partway through a large site.
Raise the limit if your budget allows, or let the site translate over several days. Check your engine's usage dashboard too. Google Cloud and DeepL both show usage and quota limits.
TranslatePress also offers an option to log machine translation queries. Turning it on for a short time helps you see whether requests are being sent at all.
Does automatic translation only run when a page is visited?
Yes, TranslatePress translates a page when it is first loaded in the new language, so pages nobody has visited in that language stay untranslated.
This surprises many site owners. Adding a new language does not translate every page in one go. Each page translates the first time someone, or something, opens it in that language.
To speed things up, visit your key pages in each language yourself. For larger sites, crawling the translated URLs, such as with a sitemap-based crawler, triggers translation across many pages.
Existing manual translations are not overwritten. If you translated a string by hand earlier, automatic translation leaves it alone.
Could caching stop automatic translation?
Yes, if a cached copy of the translated URL is served, WordPress never runs, so TranslatePress never gets a chance to translate the page.
This often happens when you add a language on a site with page caching or a CDN. The cache may hold an untranslated copy created before automatic translation was set up.
Fix it in this order:
- Clear your caching plugin
- Clear your host's server cache
- Purge your CDN
- Visit the translated page in a private window
Our guide on how to clear cache in WordPress lists where each cache lives.
If you use Cloudflare, our Cloudflare cache rules guide explains how cache rules can affect translated URLs.
Why do some strings stay untranslated?
Strings stay in the original language when they come from images, JavaScript-loaded content, excluded selectors or text that was manually translated as the original.
Check these cases:
- Text in images. Machine translation cannot read text inside images. Use the translation editor to swap the image per language.
- Dynamic text. Content loaded after the page loads may need TranslatePress's dynamic translation option to stay on.
- Excluded strings. Under the advanced settings, some selectors or paths may be excluded from translation.
- Gettext strings. Theme and plugin strings may already have their own translation files.
Open the page in the TranslatePress visual editor and click the string. If it shows as translatable, add the translation by hand. If it does not appear, it is likely loaded by a script or excluded.
How do you test the API connection?
Use the test option on the Automatic Translation tab, which sends a sample request to the engine and shows the response, including any error message.
TranslatePress provides a way to test API credentials from the settings screen. Read the response carefully. Messages about billing, invalid keys or forbidden requests tell you which of the earlier sections applies.
If the test fails with a connection error rather than an API error, your host may block outgoing requests. Ask your host whether your server can reach the engine's API.
For PHP errors behind the scenes, turn on the WordPress debug log. Our guide on how to read the WordPress debug log explains what to look for.
What should you do if nothing works?
Update TranslatePress and its add-ons, test with other plugins deactivated, and contact TranslatePress support with your test results and engine details.
Plugin conflicts are less common here, but optimization plugins that rewrite HTML can interfere. Test on a staging copy with only TranslatePress active. Our guide on fixing a plugin conflict walks through the method.
If you are new to the plugin, our guide on how to use TranslatePress in WordPress covers setup from scratch.
When you contact support, include your plan, the engine you use, the exact error text from the API test, and whether translation ever worked.
Frequently asked questions
Is TranslatePress automatic translation free?
The plugin offers automatic translation with Google Translate in its free version, but Google charges for API usage beyond its free allowance. DeepL and TranslatePress AI depend on your plan. Check both vendors' pricing pages for current terms.
Why does TranslatePress translate only some pages?
Automatic translation runs when a page is first loaded in the new language. Pages nobody has opened in that language stay untranslated. Visit them yourself or crawl the translated URLs to trigger translation.
Will automatic translation overwrite my manual translations?
No. TranslatePress keeps strings you translated by hand. Automatic translation only fills in strings that have no translation yet, so your edits stay safe.
Why does my Google API key not work in TranslatePress?
The key may be on a project without billing, missing the Cloud Translation API, or restricted by HTTP referrer. Requests come from your server, so check restrictions and enable the API and billing.
Can I limit how much TranslatePress spends on translation?
Yes. Use the daily character limit on the Automatic Translation tab, and set budgets or quotas in your Google Cloud or DeepL account. Both help you avoid unexpected charges.
Sources
- Automatic translation TranslatePress
- Generate Google Translate API key TranslatePress
- DeepL automatic translation add-on TranslatePress
- Cloud Translation documentation Google Cloud
- TranslatePress plugin WordPress.org Plugins
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


