RJVV Tools Translate for WPML is built for site owners running WPML on a site that stores much of its content in Advanced Custom Fields rather than the standard editor.
Instead of copying repeater rows, flexible content and nested group values across languages untouched, it reads that structure and translates the text inside it, producing translations that WPML treats as genuine linked entries in the same translation group, correctly assigned to their language and marked complete.
Translation requests are sent to OpenAI using an API key the site owner supplies and pays for directly, so there is no per-word fee or translation credit system built into the plugin.
Results come back through structured outputs, meaning the model can only return the same fields it was given, and they are applied directly to the WPML translation from inside the WordPress admin. Each field is hashed so that editing a page later sends only the fields that actually changed back to OpenAI, rather than the whole page again.
Powered by Fabio ChatBot
Is RJVV Tools Translate for WPML yours?
Tell readers what is limited and unlimited in the free version, and what the AI does in your plugin. Help them decide faster and reach the people already looking at it. In return, you answer their questions.
Key Features of RJVV Tools Translate for WPML
Translates ACF fields in depth. Reads text, textarea and wysiwyg fields anywhere in a post, including those nested inside repeaters, flexible content and groups, and sends their values for translation rather than copying them as is.
Covers core post content. Translates the title, slug, content and excerpt for posts and any custom post type WPML has marked as translatable, including the WooCommerce short description where that applies.
Creates proper WPML translations. Output is saved into the same translation group as the original post, assigned to the correct language and marked complete, rather than sitting outside WPML as a separate duplicate.
Sends only changed fields. Each field value is hashed, so editing the original later triggers a fresh translation request only for the fields that actually changed, leaving the rest untouched.
Per language status overview. A content table shows, for each original and each language, whether a translation is missing, outdated, up to date, or was created outside the plugin and therefore left alone.
Custom instructions and exclusions. Standing instructions can be given to the model, such as tone or names that should never be translated, and specific fields can be excluded by name or pattern to keep codes or references identical across languages.
How to Install RJVV Tools Translate for WPML
Step 1: Install and activate. Go to Plugins > Add New Plugin in the dashboard, search for RJVV Tools Translate for WPML, then click Install Now and Activate. WPML must already be active; Advanced Custom Fields is optional but needed for field-level translation.
Step 2: Add the API key. Open AI Translate > Settings and paste in an OpenAI API key.
Step 3: Configure translation settings. Choose the model to use, the status new translations should get (draft or published), which content types are included, and the source language if content is not written in the WPML default language.
Step 4: Review and translate content. Open the Content tab to see every original item with its translation status per language, then trigger translations from there.
Step 5: Check post type visibility. If a content type does not appear in the list, confirm it is set as translatable under WPML > Settings > Post Types Translation, since WPML needs that setting to link a translation to its original.
Good to Know About RJVV Tools Translate for WPML
According to the plugin’s documentation, WPML is a hard requirement, since translations are created and linked through WPML’s own translation API; it does not work alongside other multilingual plugins. ACF is optional rather than required: without it the plugin still handles titles, slugs, content and excerpts, while plain ACF free fields are supported and repeaters or flexible content need ACF PRO.
The developer notes that translations made outside the plugin are marked as external and skipped automatically, so manual work is not overwritten unless forced individually. Content is sent to OpenAI’s API only when a translation is manually triggered, with no background or scheduled sending.
Download RJVV Tools Translate for WPML on WordPress.org