Automatic Translator with Google Translate

FAQ

How much does this plugin cost?

Automatic Translator is free. It does not require a paid SaaS account or a translation API key.

How does Automatic Translator translate my WordPress site?

The plugin displays a language switcher on your site. When a visitor selects a language, the plugin loads the Google Translate website widget behind the custom selector and applies client-side translation in the visitor’s browser.

Does this create SEO-indexable translated pages?

No. Free mode does not create translated URLs, duplicate translated posts, hreflang tags, sitemap entries, translated metadata, translated slugs, or server-rendered translated pages.

It is for instant visitor translation. If multilingual SEO is your goal, use a translation architecture that stores and serves translated content on stable, crawlable language URLs.

Does this plugin load Google Translate?

Yes. Translation is powered by the Google Translate website widget. In the v2 custom selector path, the plugin lazy-loads Google Translate when translation is needed instead of exposing the default Google widget as the main visitor interface.

What privacy considerations apply?

When a visitor uses translation, their browser loads Google’s translation script and interacts with Google Translate. If your site requires consent before third-party scripts load, configure your consent tooling so visitors approve Google Translate before using the language switcher.

Automatic Translator with Google Translate uses Appsero SDK to collect some telemetry data upon user’s confirmation. This helps us troubleshoot problems faster and make product improvements.

Appsero SDK does not gather any data by default. The SDK only starts gathering basic telemetry data when a user allows it via the admin notice.

Integrating Appsero SDK does not immediately start gathering data without confirmation from users in any case.

Learn more about how Appsero collects and uses this data.

What happened to the classic widget?

The legacy classic widget path has been removed. Existing classic installs are migrated to the custom selector experience on upgrade so visitors get the newer v2 language switcher.

How can I place the language switcher?

Use the Placement tab to enable a floating selector, add it to a menu, or follow the manual placement instructions. You can also use the Automatic Translator widget, the selector block, or the [auto_translate_button] shortcode.

Do I need any translation skills to use this plugin?

No. The plugin uses automatic machine translation through Google Translate. You do not need to translate each post manually.

Can I offer only a few languages?

Yes. You can offer all supported languages or choose a smaller language list in the settings.

Can I choose regional flags for each language?

Yes. Many languages include alternate country flags, so you can choose the flag that best matches your audience or region.

Will my posts and pages be duplicated for every new language?

No. Translation happens on the fly in the visitor’s browser. Your WordPress posts and pages are not duplicated.

How can I prevent specific brand names or sections from being translated?

Use the Advanced settings to add CSS selectors for content that should not be translated. You can also use Google’s notranslate class on wrappers you want to keep unchanged, for example:

<span class="notranslate">Pampa Dev</span>.

Why is the selector visible but translation does not start?

The most common causes are JavaScript optimization, security settings, ad blockers, consent tools, or cache/minify plugins delaying or blocking Google’s translation script. Exclude Google Translate and Automatic Translator scripts from aggressive delay/minify rules, then test in a private browser window.

Why does translation look different between browsers?

Google Translate controls the translated text output and some browser behavior. Automatic Translator owns the selector UI, loading state, placement, and exclusions, but the translation engine still comes from Google.

Does this plugin translate text within images?

No. Text that is part of an image will not be translated. The plugin translates text that appears in the page HTML.

Can I combine this plugin with Polylang for mixed manual and automatic translations?

This plugin can coexist with Polylang, but it does not manage mixed manual/automatic multilingual routing. Use Polylang for canonical language URLs and manual content management, and treat Automatic Translator as client-side visitor translation on top.

Does uninstall remove plugin settings?

By default, plugin settings are preserved. You can enable Delete data on uninstall in Advanced settings to remove all wpat_* options when uninstalling.