WordPress Translation Plugin 403 Errors: Cause and Fix
If your wordpress translation plugin shows 403 Forbidden errors or “automated requests” pages instead of translated posts, the plugin is being blocked by the translation service it relies on. This article explains why that happened to us in 2007, how to avoid it, and which translation plugins to use for a multilingual WordPress site today.

Quick answer: Old translation plugins fetched pages from the free Google Translate website on the fly, and Google blocked the repeated requests as automated traffic, which caused 403 errors. Plugins that scrape a free web service will always break sooner or later. Use a maintained plugin that stores translations or uses an official translation API with your own key.
Table of Contents
Why our WordPress translation plugin showed 403 errors
In early 2007 I installed the Global Translator plugin, which automatically translated every page on QuickOnlineTips into 8 languages using the free Google translation service. It worked for a while, and then all the translated pages started showing 403 Forbidden errors.
Repeated queries from visitors and search engine bots were being blocked by Google as possible spam or virus traffic. Instead of a translated page, the plugin received Google’s “We’re sorry” page, which said the query looked similar to automated requests from a computer virus or spyware.
I found that caching is essential for translation plugins to cut down the number of requests. I went from 12 hours to 24 hours of caching, and that worked for some time, but then every page was back to 403 errors. I checked several other blogs using Global Translator and Angsuman’s Translator Pro (a $30 plugin), and the problem was universal.
Plugin updates with smarter caching helped for a while, as we reported in updated WordPress translator plugins fix 403 errors. But the real problem stayed: these plugins depended on scraping a free web page that was never meant to be used as an API.
How to fix 403 errors from translation plugins
- Check where the 403 comes from. Open a translated page and look at the error. If it is a page from the translation service, the service is blocking you. If it is your own server’s error page, check your security plugin, firewall or host for blocked requests.
- Stop scraping free translation pages. Remove old plugins that fetch translations from public web pages without an API key. They are unmaintained and will keep breaking.
- Use an official API with your own key. Modern plugins connect to paid machine translation APIs with your account and key, so requests are allowed and billed properly.
- Store translations, don’t fetch them on every visit. Choose a plugin that saves translated content in your database or its own service, so pages load without calling a translation engine each time.
- Clear your caches after switching plugins, so old error pages aren’t served from cache.
Best WordPress translation plugin options today
These well-known plugins create real multilingual sites with separate URLs for each language, which search engines can index:
- WPML (external site, opens in new tab): a long-running paid plugin for translating posts, pages, menus and themes, with manual or automatic translation.
- Polylang (external site, opens in new tab): a popular plugin with a free version for manual translation and a paid Pro version.
- TranslatePress (external site, opens in new tab): lets you translate pages visually from the front end, with optional automatic translation.
- Weglot (external site, opens in new tab): a hosted translation service with a WordPress plugin, priced by word count and languages.
If you only want visitors to read your site in their language without separate SEO pages, browser translation in Chrome, Edge and Safari often does the job for free. See our guide to free website translation options for more choices.
Machine vs human translation
Automatic translation is fast, but it can read awkwardly. For your most important pages, have a fluent speaker review the machine translation. It improves quality for readers and avoids thin, low-value pages in search results.
FAQ
Why does my translation plugin show a 403 Forbidden error?
Either the translation service is blocking your site’s requests as automated traffic, or your own server or firewall is blocking them. Check which error page you see to find the cause.
Is Global Translator still available?
We haven’t confirmed a maintained version today, so treat it as an old plugin and use a current, maintained translation plugin instead.
Does caching fix translation 403 errors?
Caching reduces requests and can delay the errors, but it doesn’t fix the root problem if the plugin scrapes a free service without an API key.
Which WordPress translation plugin is free?
Polylang and TranslatePress both offer free versions for manual translation, with paid upgrades for automatic translation and extra features.
Subscribe to our weekly tech newsletter
New tech guides, free tools and 2-minute fixes, once a week.
🎁 100 Tech Terms ebook comes free with every subscription.
Unsubscribe anytime. See our privacy policy.







Two years later and it seems we are having the same problems, I hope someone can tell us how this was fixed
Thanks
I used global translator, but it leads to 403 forbidden error from google.
I guess it has raised too much translation request to google.
Is there a new fix for it?
—
Kevin
Yes you are right, exactly the problem I’m having right now. It seem like google might implement “API” base request for their services very soon.
Any solution for “others” plugins for wordpress.