Title: interPROter
Author: bastinet
Published: <strong>November 16, 2026</strong>
Last modified: November 16, 2026

---

Search plugins

![](https://ps.w.org/interproter/assets/icon-256x256.png?rev=3804597)

# interPROter

 By [bastinet](https://profiles.wordpress.org/bastinet/)

[Download](https://downloads.wordpress.org/plugin/interproter.0.2.2.zip)

 * [Details](https://wordpress.org/plugins/interproter/#description)
 * [Reviews](https://wordpress.org/plugins/interproter/#reviews)
 *  [Installation](https://wordpress.org/plugins/interproter/#installation)
 * [Development](https://wordpress.org/plugins/interproter/#developers)

 [Support](https://wordpress.org/support/plugin/interproter/)

## Description

interPROter translates your whole site automatically and keeps the translations 
in your own WordPress database.

**Any text on the page gets translated.** interPROter works on the final HTML your
site sends to the visitor, so it does not matter which theme or page builder produced
the text. Titles, menus, widgets, footer, meta descriptions and Open Graph tags 
are all covered without registering anything.

**Nobody has to press a button.** A new or changed page is translated within minutes
of publishing, and the whole site is checked once an hour. A language is published
on its own once every text on the site has a translation.

**The translations are yours.** They live in your own database. Serving a translated
page never contacts an outside service. If the translation service is unreachable,
nothing breaks: new texts just stay untranslated until the next run.

**Fix a translation by clicking it on the page.** Open any translated page as an
editor and click “Fix translations” in the toolbar. Every translated text becomes
clickable: you see the source and the translation side by side, and the change takes
effect immediately. No separate editor, no searching a list for the right row.

**Human corrections stick.** However you edit a translation — on the page or in 
the admin list — the automatic runs will never overwrite it. You can also mark texts
that should never be translated, such as names.

**Publish when you are ready, or let it publish itself.** By default a language 
goes live on its own once everything is translated. If nothing may reach visitors
before a person has read it, switch that one language to “Require approval”: the
machine keeps translating, but the language stays hidden until you publish it.

**Search engines are told about every language.**

 * Language prefix in the URL (`/de/`, `/en/`) and translated slugs (`/de/zimmer/`).
   The original slugs keep working.
 * `hreflang` tags, translated `canonical`, `html lang`, Open Graph URL and locale.
 * A multilingual sitemap at `/wpt-sitemap.xml`.
 * Canonical and Open Graph filters for Yoast SEO (verified) and Rank Math (implemented,
   not yet verified).

**Light.** No JavaScript is added to the front end for translation. A small language
switcher with SVG flags is included.

#### Where the translations come from

Translations are produced by machine translation. You can use either:

 * **The interPROter translation service** (recommended). The plugin requests a 
   key for your site itself; no account or card is needed. The key starts with a
   one-time preview allowance of 5,000 characters, and a paid plan (from EUR 149
   a year per site, see https://interproter.com/#hinnat) gives a monthly allowance
   of 1,000,000 characters that renews every month. The service holds the translation
   engine credentials.
 * **Your own DeepL API key**, entered in the settings. The plugin then talks to
   DeepL directly.

Both are only used when new texts need translating. Visitors never trigger a request
to either.

#### Requirements

 * A real server cron is strongly recommended. WP-Cron only fires on page loads,
   so on a quiet site translations would wait for the next visitor. Run `wp cron
   event run --due-now` every 10 minutes, or point a system cron at `wp-cron.php`.

#### What interPROter does not do yet

We would rather say this here than have you find out.

 * Order emails and admin-side texts are not translated.
 * Text that is written into the page by JavaScript after loading is not seen by
   the plugin and stays in the original language.

### External services

This plugin connects to outside services only to produce new translations and, when
you add a language, to download WordPress’s own language packs. Serving a page to
a visitor never contacts any outside service.

**interPROter translation service** (`kaannos.bastinet.fi`), used only if you choose
it in the settings.

 * _Getting a key:_ only when an administrator presses “Get a translation key” in
   the settings or runs `wp interproter ota-kayttoon`. The plugin sends your site
   address and the e-mail address in the form (pre-filled with the site admin address,
   can be changed or left empty; used only to warn before the monthly allowance 
   runs out). To confirm that the request comes from your site, the service then
   loads one address on your site with a one-time code (`?wpt-haaste=…`), and the
   plugin answers it.
 * _Translating:_ when the automatic run finds texts without a translation (within
   minutes of publishing, and once an hour). The plugin sends those texts, the source
   and target language codes, your key and your site address (so the service can
   count your allowance).

The service is operated by Bastinet, Finland. Terms of use: https://interproter.
com/terms.html — Privacy policy: https://interproter.com/privacy.html

**DeepL API** (`api.deepl.com` or `api-free.deepl.com`), used only if you enter 
your own DeepL key. When the automatic run finds texts without a translation, the
plugin sends those texts, the language codes and your key directly to DeepL. DeepL
terms: https://www.deepl.com/en/pro-license — Privacy policy: https://www.deepl.
com/en/privacy

**WordPress.org language packs** (`api.wordpress.org`, `downloads.wordpress.org`).
When you add a language, the plugin asks WordPress to install the official translations
for WordPress, your theme and your plugins in that language, using WordPress’s own
language pack functions. No data about your site is sent other than what WordPress
itself sends for any language pack update.

**Your own site.** To find the texts on your pages, the automatic run loads your
site’s own public pages from your own server (`home_url()`), the same way a visitor
would. Nothing is sent anywhere else.

No visitor data is sent to any of these services, and nothing is tracked.

## Installation

 1. Upload the plugin folder to `/wp-content/plugins/` or install it from the Plugins
    screen, then activate it.
 2. Go to **Translations  Settings**. Add the languages you want and choose where translations
    come from: the interPROter service key or your own DeepL key.
 3. Make sure automatic translation is on (it is by default). The first full run starts
    within minutes.
 4. Check **Translations  Before translation** to see what would be translated and 
    what the plugin suggests leaving out.
 5. Once a language is fully translated it is published automatically. You can also
    publish or unpublish a language by hand.

WP-CLI is supported: `wp interproter` lists the commands.

## FAQ

### Does it work with my page builder?

Yes. interPROter translates the finished HTML, so it does not need to know anything
about Elementor, Divi, Gutenberg or a hand-made theme. It has been run on an Elementor
site and on a custom theme.

### What happens if I stop paying for the service?

Your site keeps working in every language, because the translations are already 
in your database. Only new texts stop getting translated.

### Does deleting the plugin delete my translations?

No. By default the translation tables stay in your database so a reinstall picks
them up. If you want everything removed, turn on _When the plugin is deleted  Also
delete all translations and settings_ before deleting.

### Does it slow my site down?

Measured on a test site running the standard WordPress theme unit test content (
WordPress 7.1, PHP 8.3, median of eight requests per URL):

 * A normal post with 74 translatable texts: **7 extra database queries, 6.6 ms,
   and 2.5 KB** added to the page.
 * The front page with 378 translatable texts: 7 extra queries, 25 ms, 2.4 KB.
 * With the plugin installed but no languages added: 4 extra queries and nothing
   added to the page.

The 2.4 KB is the hreflang tags and the language switcher. No JavaScript is loaded
on the front end for translation, and pages in the original language are not touched.

### Can I edit a translation?

Two ways. On the page: open a translated page, click “Fix translations” in the toolbar,
then click the text you want to change. Or in the admin under **Translations**: 
search for the text, edit it, save. Either way the translation is locked and never
overwritten by the automatic run.

### Does it work with WooCommerce?

Yes, including the cart and the checkout. Measured on WooCommerce 11.1 in a real
browser.

Shop, category and product pages translate in full, and every add-to-cart link, 
product ID and product URL stays exactly as it is in the original language.

The cart and the checkout are React blocks: their text is generated in the visitor’s
browser, so it never appears in the page the server sends. Two things reach it. 
The interface itself — “Proceed to Checkout”, “Subtotal”, “Quantity” — comes from
the translations WooCommerce already ships for every language, installed for you
when you add a language. Your own product names and descriptions are translated 
from your own store.

That split is deliberate, and it is also cheaper: standard interface text has been
translated well by thousands of people already, and there is no reason to pay a 
machine to do it again. Your translation budget goes to your own writing.

### Where does a visitor-only page get translated?

A page that exists only for one visitor — a cart with something in it, a search 
result, a form’s error message — can never be reached by a crawl. Two things cover
it. Anything a plugin or theme wrote is already translated, because the page runs
in the visitor’s language and WordPress’s own translations apply. Anything else 
the plugin writes down as it renders, and the next automatic run translates it.

### Can I stop a language from going live before I have read it?

Yes. In **Translations  Settings**, switch that language to “Require approval”. 
The machine keeps translating it, but it stays hidden from visitors until you press“
Approve and publish”. Every other language keeps publishing itself.

### Does it translate URLs?

Yes. Translated pages get translated slugs based on the translated title, for example`/
de/zimmer/`. The original slug under the language prefix keeps working too, so shared
and indexed links do not break.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“interPROter” is open source software. The following people have contributed to 
this plugin.

Contributors

 *   [ bastinet ](https://profiles.wordpress.org/bastinet/)

[Translate “interPROter” into your language.](https://translate.wordpress.org/projects/wp-plugins/interproter)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/interproter/), check
out the [SVN repository](https://plugins.svn.wordpress.org/interproter/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/interproter/) by
[RSS](https://plugins.trac.wordpress.org/log/interproter/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 0.2.2

 * Fix: on a translated page whose language uses WordPress’s own language pack (
   for example English), the original page was announced with the translated language
   in `hreflang`, and the language switcher showed the original language under the
   translated language’s name (“English | English”). The site language is now read
   before the page language is switched.

#### 0.2.1

 * Fix: on sites where the WordPress template output buffer is turned off (Elementor
   does this on WordPress 6.9 and later), translated pages were shown in the original
   language. The plugin now checks whether WordPress starts the buffer and opens
   and closes its own if it does not.

#### 0.2.0

 * All internal names now use the prefix `interproter` (options, database tables,
   scheduled events, hooks, filters, the `[interproter_kielet]` shortcode). Existing
   installations are renamed automatically on the first page load after updating;
   translations and settings are kept.
 * On WordPress 6.9 and later, pages are translated through WordPress’s own template
   output buffer instead of a buffer opened by the plugin.
 * Admin, on-page editor and language switcher styles and scripts are loaded with`
   wp_enqueue_style`, `wp_enqueue_script` and `wp_add_inline_style`.

#### 0.1.1

 * Version information for the WordPress updates screen (zip downloads from interproter.
   com). No changes to translation, routing or rendering.
 * Plugin Check: input sanitisation and output escaping tightened; 0 errors, 0 warnings.

#### 0.1.0

 * First public version. Automatic translation, translated URLs, hreflang and canonical
   handling, multilingual sitemap, language switcher, on-page and admin editing,
   per-language approval gate, WooCommerce support including cart and checkout, 
   WordPress’s own language packs for plugin interface text, WP-CLI commands, interPROter
   service or direct DeepL as translation source.

## Meta

 *  Version **0.2.2**
 *  Last updated **1 day ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.0 or higher **
 *  Tested up to **7.1.4**
 *  PHP version ** 7.4 or higher **
 * Tags
 * [deepl](https://wordpress.org/plugins/tags/deepl/)[hreflang](https://wordpress.org/plugins/tags/hreflang/)
   [language switcher](https://wordpress.org/plugins/tags/language-switcher/)[multilingual](https://wordpress.org/plugins/tags/multilingual/)
   [translation](https://wordpress.org/plugins/tags/translation/)
 *  [Advanced View](https://wordpress.org/plugins/interproter/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/interproter/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/interproter/reviews/)

## Contributors

 *   [ bastinet ](https://profiles.wordpress.org/bastinet/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/interproter/)