XeroWP
LocalizePilot – Multilingual & AI Translation

LocalizePilot – Multilingual & AI Translation

0/5 (0 ratings) — active installs Updated Sep 22, 2026
ai translationautomatic translationmultilingualtranslatetranslation
Download v1.0.5
LocalizePilot Dashboard & API with translation status, provider selection, API usage, fallback settings, and AI translation controls.

LocalizePilot Dashboard & API with translation status, provider selection, API usage, fallback settings, and AI translation controls.

LocalizePilot is a multilingual WordPress translation plugin for automatically translating posts and pages and managing each language version directly inside WordPress.

Choose a translation or AI provider, generate a language version, and edit the translated content directly in Gutenberg. Review and customize text, blocks, links, images, featured media, and other supported content without changing the original page.

LocalizePilot goes beyond basic automatic translation. Each language can have its own editable content, featured image, Gutenberg media, URL, translation status, and frontend language experience while remaining connected to the original WordPress post or page.

Use different banners, hero images, screenshots, product graphics, and CTA images for different languages, not just different translated text.

Translated content uses language-prefixed URLs such as:

/de/example-page/

/fr/example-page/

/ar/example-page/

Visitors can switch between equivalent language versions, while supported internal links can retain the selected language as they continue browsing.

Automatic & AI Translation

LocalizePilot supports multiple translation and AI providers:

  • TranslateX
  • Google Cloud Translation
  • OpenAI
  • Google Gemini
  • Anthropic Claude
  • Kimi
  • DeepSeek
  • Mistral AI
  • Groq
  • OpenRouter

Administrators can configure the selected provider, test the connection, set an optional fallback provider, and control daily automatic translation usage.

For supported AI providers, LocalizePilot includes controls for translation style, temperature, maximum output tokens, and custom translation instructions.

Automatic and AI-generated translations remain editable after generation.

Gutenberg Translation Editing

Each translated post or page can be opened and edited directly in the WordPress Gutenberg block editor.

Editors can customize:

  • Titles and excerpts
  • Headings and paragraphs
  • Gutenberg blocks
  • Buttons and links
  • Images and media
  • Featured images

Each language version can be adjusted independently without changing the original WordPress content.

Language-Specific Images & Media

LocalizePilot lets different language versions use different featured images and Gutenberg media.

You can customize visual content by language, including:

  • Promotional banners
  • Hero images
  • Product graphics
  • Screenshots
  • CTA graphics
  • Instructional images
  • Other Gutenberg media

For example, an English page can use one promotional banner while German, French, or Arabic versions use their own localized graphics.

This allows you to localize both translated content and visual experiences for different audiences.

Translation Workflow & Rules

LocalizePilot provides four translation statuses:

  • Automatic – generated by the selected provider
  • Edited – manually changed in Gutenberg
  • Reviewed – checked and approved
  • Needs Update – the source post or page changed after translation

Translation rules can also:

  • Translate supported attributes such as alt text, titles, placeholders, ARIA labels, and supported SEO descriptions
  • Keep supported internal links inside the selected language
  • Detect source-content changes
  • Refresh translated content when the source changes
  • Use stale translated cache when a translation provider is temporarily unavailable

These tools help editors manage automatic translations without losing control over reviewed or manually customized content.

Language Switcher & Multilingual URLs

LocalizePilot includes multiple ways to display a multilingual language switcher.

Use the shortcode:

[localizepilot_switcher]

or add the LocalizePilot Language Switcher Gutenberg block.

An advanced shortcode example is:

[localizepilot_switcher style="inline" labels="native" alignment="center"]

Switcher options can include:

  • Dropdown layout
  • Inline layout
  • Native language names
  • English language names
  • Language codes
  • Alignment
  • Additional CSS classes

An optional automatic header language switcher is also available.

LocalizePilot uses language-prefixed URLs while preserving the current page path when switching languages.

For example:

/de/blog/example-post/

can switch directly to:

/fr/blog/example-post/

Supported internal links can also preserve the selected language while visitors browse the website.

For example:

/about/

can become:

/de/about/

for a visitor browsing the German version.

External links are not changed.

Translation Cache & Performance

LocalizePilot includes built-in cache management for translated WordPress content.

Available functionality includes:

  • HTML translated-page cache
  • Gutenberg translation snapshots
  • WordPress object cache
  • Configurable cache lifetime
  • Cache directory and writable-status information
  • Rendered-page cache history
  • Gutenberg snapshot history
  • Expired-cache cleanup
  • Rendered-cache clearing
  • Snapshot clearing
  • Individual cache deletion
  • Cache size information

Cache history can display information such as:

  • Page URL
  • Cache type
  • Language
  • Translation provider or status
  • Visitor activity
  • Updated time
  • File size

Clearing generated cache files does not remove manually edited translations stored in WordPress.

When stale-cache fallback is enabled, LocalizePilot can serve an existing translated version when the selected translation provider is temporarily unavailable.

Multilingual Analytics

LocalizePilot includes optional first-party analytics for understanding visitor activity across language pages.

Reports can include:

  • Unique visitors
  • Page views
  • Repeat visits
  • Language pages
  • Languages viewed
  • Daily visitor trends
  • Daily page-view trends
  • Per-language page reports
  • Language filtering
  • Date-range filtering
  • Specific URL filtering

Analytics retention can be configured by the administrator.

The same visitor can be counted once for a specific language page in unique visitor reports while repeat visits remain available as page-view events.

Raw visitor IP addresses and raw user-agent values are not stored.

RTL Language Support

LocalizePilot supports right-to-left language configurations for languages such as Arabic.

This allows multilingual WordPress sites to provide appropriate language direction for RTL content.

Key Features

  • Automatic WordPress translation
  • AI translation with multiple providers
  • TranslateX and Google Cloud Translation support
  • OpenAI, Gemini, Claude, Kimi, DeepSeek, Mistral, Groq, and OpenRouter support
  • AI translation style and instruction controls
  • Optional fallback translation provider
  • Configurable daily automatic translation limit
  • Gutenberg-editable translations
  • Language-specific featured images
  • Language-specific Gutenberg media
  • Different banners, screenshots, hero images, and CTA graphics by language
  • Automatic, Edited, Reviewed, and Needs Update workflow statuses
  • Source-content change detection
  • Translation of supported attributes
  • Language-prefixed URLs
  • Same-page language switching
  • Localized internal links
  • Language switcher shortcode
  • Gutenberg language switcher block
  • Optional automatic header language switcher
  • RTL language support
  • Persistent Gutenberg translation snapshots
  • Rendered-page HTML cache
  • WordPress object-cache support
  • Cache management and history
  • Stale-cache fallback
  • First-party multilingual analytics
  • Unique visitor and repeat page-view reporting
  • Language, date, and URL analytics filters

External services

LocalizePilot uses only the provider selected and configured by a WordPress administrator. When a translation is generated, tested, refreshed, or required for a frontend page, including a normal page viewed by a logged-in visitor, the plugin may send titles, excerpts, block text, visible page text, supported attributes, source and target language codes, model settings, and custom translation instructions to that provider. The configured API key is sent only to the selected provider.

Each provider controls its own billing, retention, model training, quotas, regional availability, terms, and privacy practices. Review the selected provider’s policies before sending personal or sensitive content.

TranslateX

  • Service and documentation: https://translatex.com/api-documentation
  • Terms: https://translatex.com/terms
  • Privacy: https://translatex.com/privacy-policy

Google Cloud Translation

  • Documentation: https://cloud.google.com/translate/docs
  • Terms: https://cloud.google.com/terms
  • Privacy: https://policies.google.com/privacy

OpenAI

  • Documentation: https://platform.openai.com/docs
  • Terms and policies: https://openai.com/policies/
  • Privacy: https://openai.com/privacy/

Google Gemini

  • Documentation: https://ai.google.dev/gemini-api/docs
  • Terms: https://ai.google.dev/gemini-api/terms
  • Privacy: https://policies.google.com/privacy

Anthropic Claude

  • Documentation: https://platform.claude.com/docs
  • Terms: https://www.anthropic.com/legal/commercial-terms
  • Privacy: https://www.anthropic.com/legal/privacy

Kimi by Moonshot AI

  • Documentation: https://platform.kimi.ai/docs/api/overview
  • Terms: https://platform.kimi.ai/docs/agreement/modeluse
  • Privacy: https://platform.kimi.ai/docs/agreement/userprivacy

DeepSeek

  • Documentation: https://api-docs.deepseek.com/
  • Terms: https://cdn.deepseek.com/policies/en-UK/deepseek-open-platform-terms-of-service.html
  • Privacy and general terms: https://cdn.deepseek.com/policies/en-US/deepseek-terms-of-use.html

Mistral AI

  • Documentation: https://docs.mistral.ai/
  • Terms: https://legal.mistral.ai/terms/commercial-terms-of-service
  • Privacy: https://legal.mistral.ai/terms/privacy-policy

Groq

  • Documentation: https://console.groq.com/docs
  • Terms: https://console.groq.com/docs/legal/services-agreement
  • Privacy and legal policies: https://console.groq.com/docs/legal

OpenRouter

  • Documentation: https://openrouter.ai/docs
  • Terms: https://openrouter.ai/terms
  • Privacy: https://openrouter.ai/privacy/

Privacy and data removal

LocalizePilot stores settings and API keys in the WordPress options table, translation records in the WordPress posts and post-meta tables, daily usage counters in the options table, generated cache files under wp-content/cache/localizepilot/, and optional first-party analytics events in a dedicated WordPress database table.

When analytics is enabled, anonymous visitors receive a random localizepilot_visitor_id cookie. The plugin stores a one-way hash of that identifier, the normalized source page URL, language code, and visit time. Raw IP addresses and user-agent strings are not stored. The same visitor is counted once per language page in unique visitor reports, while every repeat visit remains available as a page-view event.

Using WordPress’s Delete action for the plugin runs uninstall.php and removes LocalizePilot settings, usage counters, translation records, analytics events, the analytics table, scheduled cleanup, and generated cache files. Deactivation alone does not delete data.