TranslateSense – AI Translation for Polylang
TranslateSense – AI Translation for Polylang

TranslateSense – AI Translation for Polylang

0/5 (0 ratings) — active installs Updated Nov 14, 2026

TranslateSense is an AI Translation for Polylang plugin built to make translating multilingual WordPress websites faster and easier. Its powerful Bulk Translation feature lets you translate multiple WordPress posts, pages, custom post types, WooCommerce products, and taxonomy terms into one or more languages in a single workflow using AI.

Select the content you want to translate, choose your target languages, select an AI provider, and start bulk translation. With Background Translation, OpenAI and Google Gemini translation jobs can run through WP-Cron, so you can continue working while your content is being translated. Monitor progress, review completed or failed translations, and manage pending jobs from the translation progress modal.

Need to translate individual posts? Use Page Editor Translation to translate and review individual strings directly inside Gutenberg, Elementor, or Classic Editor. You can search, edit, reset, and retry translated strings before applying them to your content.

Choose from OpenAI, Google Gemini, or Built-in Browser AI to translate your website. On WordPress 7.0 and newer, TranslateSense also supports supported providers through WordPress AI Connectors.

Beyond content translation, TranslateSense supports automatic taxonomy translation, Advanced Custom Fields (ACF), WooCommerce, SEO metadata, custom fields, internal links, and media references. Its built-in Translation Memory reuses previously saved translations to reduce repeated AI requests.

Resources

📖 Documentation | ✨ TranslateSense Pro

Key Features

  • Bulk Translation: Translate multiple WordPress posts, pages, custom post types, and taxonomy terms into one or more languages in a single workflow.
  • Background Translation: Process OpenAI and Google Gemini post translation batches in the background using WP-Cron, with progress monitoring, batch management, and pending job controls.
  • Multiple AI Providers: Choose OpenAI, Google Gemini, or Built-in Browser AI. WordPress 7.0+ users can also connect supported providers through WordPress AI Connectors.
  • Automatic Taxonomy Translation: Translate categories, tags, and supported custom taxonomy terms. Translate and assign related terms automatically during supported post translation workflows.
  • Page Editor Translation: Translate individual posts directly inside Gutenberg, Elementor, and Classic Editor. Search, edit, reset, and retry individual translated strings before applying them.
  • Gutenberg and Elementor Support: Translate supported blocks and widgets while preserving their content structure and layout.
  • ACF and Custom Fields: Translate supported Advanced Custom Fields (ACF), including Repeater, Flexible Content, Group, and supported relationship fields.
  • WooCommerce Translation: Translate supported product content, product taxonomies, and configured custom fields.
  • SEO Metadata and Slugs: Translate supported SEO titles, meta descriptions, and post slugs for Yoast SEO, Rank Math, and SEOPress.
  • Internal Links and Media: Update supported internal links and media references to use existing Polylang translations.
  • Translation Memory: Reuse saved translations to reduce repeated AI requests.
  • XML Configuration: Customize translation rules for additional Gutenberg blocks, Elementor widgets, and custom fields.

AI Providers

TranslateSense supports the following AI translation providers:

  • OpenAI: Connect using an OpenAI API key or a supported WordPress AI Connector. Supports background WP-Cron bulk translation and retrying individual failed strings in Page Editor Translation.
  • Google Gemini: Connect using a Google Gemini API key or a supported WordPress AI Connector. Supports background WP-Cron bulk translation and retrying individual failed strings in Page Editor Translation.
  • Built-in Browser AI: Uses the browser’s on-device Translator API in supported Google Chrome and Microsoft Edge browsers (v131+). No external AI provider API key is required. Translation runs locally inside the active browser tab.

Built-in Browser AI supports 39 language codes through Chromium’s Translator API, depending on browser availability and the selected language pair.

Supported Editors and Integrations

  • Gutenberg (Block Editor): Includes 225 preconfigured block rules covering WordPress Core blocks, Core Embeds, TinyMCE Advanced, Spectra, Essential Blocks, Kadence Blocks, Otter Blocks, Stackable, Gutenverse, Ultimate Blocks, Qi Blocks, and Rank Math Table of Contents. Also includes fallback text extraction for supported unmapped blocks and automatic block recovery after bulk translation.
  • Elementor: Supports 8 core Elementor widgets, nested repeater lists, Elementor v4 atomic controls, page settings, and automatic schema discovery for unmapped widgets.
  • Classic Editor: Translates post titles, slugs, excerpts, content, and supported accessibility and UI attributes while preserving HTML markup.
  • Cross-Editor Protection: Detects when a post was built with Elementor and prompts you to open the translation in Elementor if you try to use Gutenberg or Classic Editor.
  • Advanced Custom Fields (ACF): Supports text, textarea, WYSIWYG, select, checkbox, radio, button group, link titles, Repeater, Flexible Content, and Group fields. Also supports translated ID mapping for supported image, file, gallery, relationship, post object, page link, and taxonomy fields.
  • SEO Plugins: Supports SEO metadata from Yoast SEO, Rank Math, and SEOPress. Additional field extraction can be configured through XML rules.
  • WooCommerce: Supports WooCommerce products and product taxonomies when enabled for translation in Polylang, including internal product and category link resolution.
  • Polylang: Uses Polylang for language management, linked translations, taxonomy assignments, sticky post status, media synchronization, and custom field synchronization detection.

Additional Gutenberg block, Elementor widget, and custom field rules can be configured using XML Configuration.

Translation Tools

Bulk Translation

Translate multiple WordPress posts, pages, custom post types, or taxonomy terms into different languages directly from your WordPress admin list screens.

Select the content you want to translate, choose your target languages, select an AI provider, and start the translation process.

  • Select multiple posts, pages, custom post types, or taxonomy terms.
  • Choose one or more target languages.
  • Select your preferred AI provider.
  • Start translation and monitor progress through the progress modal.
  • Review completed, failed, skipped, and existing translation results.
  • Manage pending translations and skip items that are waiting in the queue.

Background Processing (OpenAI and Google Gemini):

Post translation batches run through WP-Cron. Background processing includes:

  • Memory-limit protection to help prevent server memory issues.
  • Time budgeting for translation batches.
  • Active batch switching and queue management.
  • Live translation progress monitoring.
  • Status filters for completed, failed, and skipped or existing translations.
  • Options to skip pending translations.

Browser Processing (Built-in Browser AI and Taxonomy Terms):

Browser AI and taxonomy term translation run sequentially in the active browser tab. Keep the tab open until the process is complete.

Page Editor Translation

Translate individual posts directly inside Gutenberg, Elementor, or Classic Editor using the TranslateSense metabox or toolbar button.

  • Choose an enabled AI provider and monitor translation progress.
  • Search and filter strings to find the content you want to review.
  • View translation statistics, including character, string, and processing time information.
  • Edit translated strings directly in the translation list.
  • Reset edited strings to their original AI-generated translations.
  • Retry empty or failed strings using OpenAI or Google Gemini.
  • Click Apply to Page to add translations to your editor. Your content is not saved until you review and save the post yourself.

Translation Memory & Automatic Cache Cleanup

TranslateSense stores source strings, translation packages, and translated strings in custom WordPress database tables.

When the same source text is encountered again, TranslateSense can reuse a previously saved translation instead of sending another request to the AI provider.

A scheduled WP-Cron task runs every three days to remove unused cached translations older than 30 days and unused package mappings older than 10 days. You can also clear cached data manually from the Cache tab.

Plugin Settings

Manage TranslateSense from Languages > TranslateSense in your WordPress dashboard.

  • Home Tab: View quick-start guides for supported editors and Bulk Translation, along with translation statistics and provider usage.
  • General Settings Tab:
    • Default AI Engine: Choose the AI provider selected by default.
    • Enable or Disable Providers: Enable or disable OpenAI, Google Gemini, and Chrome Built-in AI.
    • API Keys and AI Connectors: Configure provider API credentials or connect supported providers through WordPress AI Connectors on WordPress 7.0+.
    • Model Selection: Choose from the available models provided by your connected AI provider.
    • Batch Size: Configure how many strings are sent in each AI request.
    • Response Timeout: Set the maximum time allowed for an AI request.
    • Max Tokens: Configure the maximum output tokens for AI responses.
    • Temperature: Adjust how consistent or creative AI-generated translations should be.
    • Bulk Post Status: Choose whether newly created bulk translations are saved as Draft or Publish.
    • Slug Translation: Translate slugs, generate slugs from translated titles, or keep original slugs.
    • Custom AI Prompt: Customize the translation prompt using the available language and content placeholders.
  • Gutenberg Blocks and Elementor Widgets Tabs: Search, filter, and customize supported, custom, and unsupported block or widget XML rules.
  • Cache Tab: View database cache counts and clear translated strings, source strings, package logs, or all cached data.

External Services

TranslateSense connects to external services when you choose an AI provider or voluntarily submit feedback and diagnostic information.

When you request an AI translation, the selected source text and relevant language or prompt information are sent to the provider you choose.

  • OpenAI (https://api.openai.com): Receives text submitted for translation and related language and prompt information when you use OpenAI. TranslateSense also retrieves available model information when validating credentials or loading models. Privacy Policy | Terms of Use
  • Google Gemini (https://generativelanguage.googleapis.com): Receives text submitted for translation and related language and prompt information when you use Google Gemini. TranslateSense also retrieves available model information when validating credentials or loading models. Privacy Policy | Terms of Service
  • Dragwyb Deactivation Feedback (https://feedback.dragwyb.com): If you voluntarily submit the optional deactivation feedback form, your selected reason, optional comment, and plugin information are sent to Dragwyb. If you enable the diagnostics option, additional site and environment information may also be included. Privacy Policy | Terms
  • Built-in Browser AI (Chrome / Microsoft Edge): Uses the browser’s Translator API to process translation text locally. TranslateSense does not send that text to OpenAI or Google Gemini when you use this option.

Special Thanks

Special thanks to the team behind Polylang for creating and maintaining a great multilingual foundation for WordPress.

Source Code and Contributions

TranslateSense is open source under the GPLv2 or later license. Explore the source code, report issues, or contribute on GitHub:

GitHub Repository