Title: LocalizePilot – Multilingual & AI Translation Author: Golam Mostafa Published: Тамыз 10, 2026 Last modified: Тамыз 15, 2026 --- Search plugins ![](https://ps.w.org/localizepilot/assets/banner-772x250.png?rev=3648548) ![](https://ps.w.org/localizepilot/assets/icon-128x128.png?rev=3648548) # LocalizePilot – Multilingual & AI Translation By [Golam Mostafa](https://profiles.wordpress.org/golammostafa95/) [Download](https://downloads.wordpress.org/plugin/localizepilot.1.0.1.zip) * [Details](https://kk.wordpress.org/plugins/localizepilot/#description) * [Reviews](https://kk.wordpress.org/plugins/localizepilot/#reviews) * [Installation](https://kk.wordpress.org/plugins/localizepilot/#installation) * [Development](https://kk.wordpress.org/plugins/localizepilot/#developers) [Support](https://wordpress.org/support/plugin/localizepilot/) ## Description 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. ## Screenshots [⌊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 Dashboard & API with translation status, provider selection, API usage, fallback settings, and AI translation controls. [⌊Choose from translation and AI providers including TranslateX, Google Cloud Translation, OpenAI, Gemini, Claude, Kimi, DeepSeek, Mistral, Groq, and OpenRouter.⌉⌊Choose from translation and AI providers including TranslateX, Google Cloud Translation, OpenAI, Gemini, Claude, Kimi, DeepSeek, Mistral, Groq, and OpenRouter.⌉[ Choose from translation and AI providers including TranslateX, Google Cloud Translation, OpenAI, Gemini, Claude, Kimi, DeepSeek, Mistral, Groq, and OpenRouter. [⌊Configure available languages and preview same-page language-prefixed URLs.⌉⌊Configure available languages and preview same-page language-prefixed URLs.⌉[ Configure available languages and preview same-page language-prefixed URLs. [⌊Manage translation rules and Gutenberg workflow statuses including Automatic, Edited, Reviewed, and Needs Update.⌉⌊Manage translation rules and Gutenberg workflow statuses including Automatic, Edited, Reviewed, and Needs Update.⌉[ Manage translation rules and Gutenberg workflow statuses including Automatic, Edited, Reviewed, and Needs Update. [⌊Edit translated WordPress content and language-specific images or media in Gutenberg.⌉⌊ Edit translated WordPress content and language-specific images or media in Gutenberg .⌉[ Edit translated WordPress content and language-specific images or media in Gutenberg. [⌊Configure the LocalizePilot language switcher with shortcode, Gutenberg block, and frontend display options.⌉⌊Configure the LocalizePilot language switcher with shortcode, Gutenberg block, and frontend display options.⌉[ Configure the LocalizePilot language switcher with shortcode, Gutenberg block, and frontend display options. ## Blocks This plugin provides 1 block. * Language Switcher Display the LocalizePilot language switcher anywhere in your content or templates. ## Installation 1. Upload the plugin ZIP through Plugins > Add New > Upload Plugin. 2. Activate LocalizePilot. 3. Open LocalizePilot from the WordPress admin menu. 4. Select the languages visitors should be able to access. 5. Choose a translation or AI provider and enter the required API key. 6. Test the selected provider. 7. Review translation, fallback, cache, analytics, and language-switcher settings. 8. Enable LocalizePilot and save the settings. 9. Edit a WordPress post or page and create its language versions. 10. Review or customize each translation in Gutenberg. Pretty permalinks should be enabled for language-prefixed URLs. If a translated language URL returns a 404, open Settings > Permalinks and click Save Changes. ## FAQ ### Can LocalizePilot translate WordPress automatically? Yes. LocalizePilot can generate automatic translations using the translation or AI provider selected and configured by the site administrator. ### Which translation and AI providers are supported? LocalizePilot supports TranslateX, Google Cloud Translation, OpenAI, Google Gemini, Anthropic Claude, Kimi, DeepSeek, Mistral AI, Groq, and OpenRouter. Each provider requires its own configuration and may have separate pricing, quotas, terms, availability, and privacy practices. ### Can I edit automatic or AI translations in Gutenberg? Yes. Each translated post or page can be opened directly in Gutenberg. You can change text, blocks, links, images, featured media, and other supported content independently for each language. ### Can each language have different images and media? Yes. Each translated language version can use its own featured image and Gutenberg media. This means English, German, French, Arabic, or other language versions can use different banners, hero images, screenshots, product graphics, CTA images, and other supported visual content. ### Does LocalizePilot include a language switcher? Yes. Use the `[localizepilot_switcher]` shortcode, the LocalizePilot Language Switcher Gutenberg block, or the optional automatic header language switcher. ### Does switching languages keep visitors on the same page? Yes. LocalizePilot is designed to switch between equivalent language versions while preserving the current post or page path. For example: ``` /de/blog/example-post/ ``` can switch to: ``` /fr/blog/example-post/ ``` instead of sending the visitor back to the homepage. ### Does LocalizePilot localize internal links? Yes. Supported internal links can inherit the selected language so visitors remain inside the active language path as they continue browsing. External links are not changed. ### What happens when the original content changes? Connected translations can be marked **Needs Update**, helping editors identify language versions that should be reviewed again. ### What happens if my translation provider is temporarily unavailable? When stale-cache fallback is enabled, LocalizePilot can serve an existing translated cache entry instead of requiring a new provider response. ### Does LocalizePilot include multilingual analytics? Yes. Optional first-party analytics can report unique visitors, page views, repeat visits, language activity, and page-level performance. Reports can be filtered by language, date range, and specific URL. ### Will clearing the cache delete my translation edits? No. Manual corrections are stored in WordPress. Gutenberg snapshots and rendered-page HTML caches are generated files and can be recreated. ### Does LocalizePilot support RTL languages? Yes. LocalizePilot supports right-to-left language configurations for languages such as Arabic. ### Does the plugin translate pages for logged-in visitors? Yes. Normal frontend posts, pages, archives, menus, headers, and footers can be translated for both logged-in and logged-out visitors. Logged-in responses are translated in memory and are not saved to the shared full- page HTML cache. The WordPress admin bar is excluded from translation. For privacy and security, password-protected content, non-GET requests, and common WooCommerce cart, checkout, and account pages remain excluded from automatic full- page API translation. ### How are analytics visitors counted? When analytics is enabled, LocalizePilot stores each eligible page visit as an event. Unique visitor reports count the same one-way visitor identifier once for each page and language combination, while Page Views includes repeat visits. Raw IP addresses are not stored. ### Are automatic or AI translations guaranteed to be accurate? No. Machine and AI translations can contain errors or wording that does not fit the intended context. Review important legal, medical, financial, product, technical, and marketing content before publishing. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “LocalizePilot – Multilingual & AI Translation” is open source software. The following people have contributed to this plugin. Contributors * [ Golam Mostafa ](https://profiles.wordpress.org/golammostafa95/) [Translate “LocalizePilot – Multilingual & AI Translation” into your language.](https://translate.wordpress.org/projects/wp-plugins/localizepilot) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/localizepilot/), check out the [SVN repository](https://plugins.svn.wordpress.org/localizepilot/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/localizepilot/) by [RSS](https://plugins.trac.wordpress.org/log/localizepilot/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.0.1 * Added a new Analytics tab with visitor and page-view reports for each language page. * Added language, date-range, and specific URL filters. * Added a built-in visitor and page-view graph without external chart libraries. * Added unique visitor counts to the cache history table. * Stored repeat visits as separate events while counting each visitor once per language page. * Added configurable analytics retention and complete analytics-data removal. * Excluded WordPress `/embed/` endpoints from translation, cache, and analytics processing. * Removed trailing `/embed/` from URLs displayed in cache and analytics reports. * Kept translated links on the selected language and translated normal frontend pages for logged-in and logged-out visitors. * Kept shared rendered-page caching disabled for logged-in and personalized responses. #### 1.0.0 * Initial WordPress.org release. * Added Gutenberg-editable translation records and review statuses. * Added language-specific media support. * Added translation and AI provider integrations with optional fallback. * Added the shortcode and dynamic Gutenberg language switcher block. * Added same-page language URLs, RTL, canonical, and hreflang support. * Added persistent content snapshots, rendered-page caching, cache history, and pagination. ## Meta * Version **1.0.1** * Last updated **20 часа ago** * Active installations **Fewer than 10** * WordPress version ** 6.2 or higher ** * Tested up to **7.0.4** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/localizepilot/) * Tags * [ai translation](https://kk.wordpress.org/plugins/tags/ai-translation/)[automatic translation](https://kk.wordpress.org/plugins/tags/automatic-translation/) [multilingual](https://kk.wordpress.org/plugins/tags/multilingual/)[translate](https://kk.wordpress.org/plugins/tags/translate/) [translation](https://kk.wordpress.org/plugins/tags/translation/) * [Advanced View](https://kk.wordpress.org/plugins/localizepilot/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/localizepilot/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/localizepilot/reviews/) ## Contributors * [ Golam Mostafa ](https://profiles.wordpress.org/golammostafa95/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/localizepilot/)