Google Translate Pro WP Plugin

01What GTranslate Pro Actually Does

Put simply: it reads your site’s HTML, pulls out the text, sends it through a translation engine, rebuilds the page in the target language, and stores that output in a cache. The next visitor who wants the same language gets the page instantly, with zero API calls.

It supports over 100 languages. You can use a free built-in provider with no API key, or connect your own Google Cloud Translation API key for enterprise-level reliability. Both options work with the same caching system.

It’s built for WordPress developers and site owners who want multilingual support without turning their site into a slow mess.

02The Caching System: Where the Real Value Is

Translation is slow by nature. Every API call takes time. If your page has 80 text segments and you’re calling the API for each page load, that adds up fast.

GTranslate Pro’s caching layer solves this completely. Here’s what happens from the moment someone visits a translated page:

After the first visit, every repeat request gets the cached version. For busy sites, this means your translation API is barely touched after the initial warmup.

Database Cache vs. Filesystem Cache

You can choose where translations are stored. Both work, but they have different strengths:

03Everything You Get Out of the Box

Here’s a quick overview of what’s included, from the basics to the more advanced stuff:

04Getting It Running: Installation

Installation is straightforward. You’ll need WordPress 5.8+ and PHP 7.4+ on your server.

# Navigate to the plugin folder
cd wp-content/plugins/GTranslate

# Install dependencies
composer install

05Configuring Your First Translation

Once activated, go to Dashboard → GTranslate. You’ll see five tabs: General, Languages, Translation, Display, and Advanced.

Step 1: Pick Your Translation Provider

Under the General tab, choose your provider:

• Free Built-in Provider: Works with no API key. Good for most blogs and small business sites.
• Official Google Cloud API: Requires an API key from Google Cloud Console. Better quality and more reliable for high-traffic sites. Billing must be enabled on your Cloud project.

// Switch provider via WordPress action
do_action('gtranslate_switch_provider', 'official');

// Or using the plugin instance
$plugin = \GTranslate\Plugin::instance();
$plugin->switch_provider('official');

Step 2: Set Your Source Language and Target Languages

Your source language is the language your site is written in (almost always English). Target languages are everything else you want to offer.

The Languages tab has a searchable multi-select with all 100+ options. You can hit “Select All” to enable everything, or pick specific languages for your audience.

Step 3: Choose Which HTML Tags to Translate

Under the Translation tab, you control which HTML elements get processed. The default set covers most cases:

p, h1, h2, h3, h4, h5, h6, span, button, a, li, td, th, label

If your site has simple content, you might only need p, h1–h6, and li. Removing tags you don’t need reduces the amount of work the plugin does per page.

06Adding the Language Switcher to Your Site

Visitors need a way to switch languages. GTranslate Pro gives you five placement options, and you only need one.

<!-- Default dropdown -->
[gtranslate_switcher]

<!-- Button group, no flags -->
[gtranslate_switcher style="buttons" show_flags="0"]

<!-- Flags only, no names -->
[gtranslate_switcher show_names="0" show_flags="1"]

$switcher = new \GTranslate\Language_Switcher(
    \GTranslate\Plugin::instance()->get_settings()
);

echo $switcher->render([
    'style'      => 'default',
    'show_flags' => true,
    'show_names' => true,
]);

What the Switcher Looks Like

Customizing the Switcher’s Look

The Display settings tab has a Custom CSS field. The switcher uses predictable class names so it’s easy to style:

/* Main container */
.gtranslate_widget {
    background: #1e293b;
    border-radius: 10px;
    padding: 8px;
}

/* Active / selected language */
.current-language {
    font-weight: 600;
    color: #6366f1;
}

/* Language option hover */
.language-option:hover {
    background: rgba(99, 102, 241, 0.1);
}

07Built-in API Protection: Rate Limits and the Circuit Breaker

If something goes wrong with your translation API, a naive plugin would keep hammering it indefinitely. That can get expensive fast, or get your key suspended.

GTranslate Pro has two layers of protection built in.

Rate Limiting

The default is 100 requests per minute. Once that limit is hit, the plugin queues requests and processes them in the next window. If the queue is full, extra requests are dropped gracefully. You can tune this from Advanced Settings → Requests per Minute.

The Circuit Breaker

This is the smarter protection. After 3 consecutive API failures, the circuit “opens” and stops sending requests for 60 seconds. After that timeout, it sends a test request. If it succeeds, normal operation resumes. If not, the circuit stays open longer.

08Excluding Pages and Elements You Don’t Want Translated

Not every page needs translation. Privacy policies, checkout flows, or pages with code examples are good candidates to exclude.

Exclude Pages by URL Pattern

Under Translation settings, add URL patterns one per line:

/privacy/
/terms/
/checkout/
/account/

Exclude Elements by CSS Selector

If a specific section of a page shouldn’t be translated, add its CSS selector:

.no-translate
#code-examples
.product-sku
.widget-title

Or Use the HTML Attribute Directly

<!-- This block won't be touched by the plugin -->
<div class="no-translate">
    SKU: ABC-1234
</div>

<!-- Or use a data attribute -->
<p data-translate="false">Preserved content</p>

Excluding from Code (via WordPress Filter)

add_filter('gtranslate_should_exclude_page', function($exclude, $uri) {
    // Exclude all URLs under /members/
    if (strpos($uri, '/members/') !== false) {
        return true;
    }
    return $exclude;
}, 10, 2);

09For Developers: Hooks and Custom Providers

GTranslate Pro is built around WordPress hooks, so you can tap into the pipeline at any point without editing plugin files.

Useful Filters at a Glance

// Modify which languages are available to visitors
add_filter('gtranslate_target_languages', function($langs) {
    return ['es', 'fr', 'de']; // limit to 3
});

// Modify translated content before it's sent to the browser
add_filter('gtranslate_translate_content', function($translated, $original, $lang) {
    return $translated; // post-process here
}, 10, 3);

// Do something after the user switches language
add_action('gtranslate_language_switched', function($new, $old) {
    // Log, track, or redirect
}, 10, 2);

// Run code after cache is cleared
add_action('gtranslate_cache_cleared', function($language) {
    // Purge your CDN, for example
});

Clear Cache for One Language

$cache = \GTranslate\Plugin::instance()->get_cache();

// Clear all cached translations
$cache->clear_all();

// Clear only Spanish translations
$cache->clear_by_language('es');

10Common Issues and How to Fix Them

Most problems have simple causes. Here are the ones that come up most often:

11Download