LocalizePilot – Multilingual Content & Media

LocalizePilot creates language-prefixed versions of WordPress posts and pages while retaining the original page path. Administrators can generate translations through a supported translation or AI provider, then review and correct each language version in the WordPress block editor.

The plugin is disabled by default. It does not contact an external translation provider until an administrator configures a provider, enables LocalizePilot, and generates, tests, refreshes, or visits content that requires translation.

Gutenberg translation workflow

• Open a WordPress post or page.
• Create a language version from the LocalizePilot panel.
• Review the generated title, excerpt, blocks, links, and media in Gutenberg.
• Set the translation status to Automatic, Edited, Reviewed, or Needs update.
• Save the translation to update its content snapshot and invalidate its rendered-page cache.

Main features

• Gutenberg-editable translations for posts and pages
• Automatic, Edited, Reviewed, and Needs update statuses
• Language-specific featured images and Gutenberg media
• Same-page language URLs, such as /de/blog/example-post/
• TranslateX and Google Cloud Translation support
• OpenAI, Gemini, Claude, Kimi, DeepSeek, Mistral, Groq, and OpenRouter support
• Editable AI model IDs and translation instructions
• Optional fallback provider
• Shortcode: [localizepilot_switcher]
• Dynamic Gutenberg language switcher block
• Optional automatic header language switcher
• RTL, canonical, and hreflang support
• Persistent Gutenberg content snapshots
• Rendered-page HTML file cache
• Optional WordPress object-cache layer
• Paginated cache history and cache-management actions
• First-party visitor analytics by language page
• Unique visitor and repeat page-view reporting
• Analytics filters for language, date range, and URL
• Configurable daily automatic-translation limit

Translation statuses

• Automatic: generated by the selected provider.
• Edited: changed by a WordPress editor.
• Reviewed: manually checked and approved.
• Needs update: the source post or page changed after translation.

Cache storage

For published source content, Gutenberg translation content can be exported to:

Complete public rendered pages are cached separately at:

The WordPress translation record remains the source of truth. Clearing cache files does not delete manual corrections.

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.