Skip to main content

Works with AI · Verified on v3.3.8

TranslatePress logo

Manage TranslatePress Languages with AI

Connect TranslatePress to Claude, ChatGPT, or any AI assistant with WPVibe. Add a language, publish it when it is ready, change its URL and fix the default language, by asking in plain English.

400,000+ active installs 7 verified abilities Last verified Oct 24, 2026

What your AI can do with TranslatePress

One connection gives your assistant structured, permission-checked access to the whole site.

Add a language

Set up a second language with a URL slug that clashes with nothing, hidden until it is translated.

Show or hide

Publish a finished translation, or hide one while you rework it, keeping every translation.

URL slugs

Move a language to a new slug, checked against your pages, with a warning about old links.

Swap languages

Replace the one extra language the free plugin allows; old translations stay saved.

Default language

Make the default match the language your content is written in.

Things to ask

Paste any of these into Claude or ChatGPT once TranslatePress is connected.

“Add Spanish to my site with TranslatePress, hidden until I have translated it.”
“Show the French version of my site to visitors now.”
“Change the URL of my Spanish version from /es/ to /mx/.”
“Replace German with French Canadian on my site.”
“My site is written in Spanish. Make that the default language in TranslatePress.”

Up and running in three steps

1

Install WPVibe

Add the free WPVibe plugin from WordPress.org to the site running TranslatePress.

2

Connect your AI

Claude, ChatGPT, Cursor, and more. One click to authorize, and no passwords ever go in the chat.

3

Ask in plain English

“Add Spanish to my site with TranslatePress, hidden until I have translated it.”

Verified TranslatePress recipes

Copy-paste playbooks, each one tested on a live TranslatePress install before it ships.

Every TranslatePress ability

TranslatePress registers these with the WordPress Abilities API under the translatepress namespace. Your AI finds them with discover_abilities and calls them with run_ability. WPVibe asks for your approval only when an ability is marked destructive and deletes something or runs code; everything else runs as soon as your AI calls it. Verified means we ran it on a live install of v3.3.8. Registered means a fresh install of v3.3.8 ships it and we have not run it yet.

Requires TranslatePress with its abilities on WordPress 6.9 or newer, and an administrator account. The abilities are on as soon as the plugin is active. Tested on TranslatePress 3.3.8 (free) with WordPress 7.1.3.

Ability What it does Access Status

List languages

translatepress/list-languages
The default language and every other language set up, with its URL slug and whether visitors can see it. Read Verified

List language codes

translatepress/list-available-languages
Every language TranslatePress supports, with its code and English name. Read Verified

Add a language

translatepress/add-language
Adds a language with an optional URL slug. Write Verified

Change a language

translatepress/update-language
Sets a language's URL slug and whether visitors can see it. Write Verified

Set the default language

translatepress/set-default-language
Makes a language that is already set up the default. Write Verified

Remove a language

translatepress/remove-language
Removes a language other than the default. Write Verified

Turn on automatic translation

translatepress/enable-automatic-translation
Turns on automatic translation with the engine you name. Write Verified

Set the license key

translatepress/set-license-key
Saves a TranslatePress license key, then checks it. Write Registered

What we learned testing it

Behavior the ability descriptions do not mention.

  • Language changes are site-wide and live at once. A language you add is shown to visitors straight away, so the recipes hide it in the next step until you have translated it.
  • TranslatePress refuses another language's URL slug when you change one, but not when you add a language: then it quietly resets every language's slug to its language code (such as en_US), your default's included. Neither check looks at your pages: in our test the slug shop turned the WooCommerce shop page into the Spanish home page. The recipes check your pages, your other languages and common addresses first.
  • After a URL slug change, TranslatePress does not redirect the old slug: in our test WordPress forwarded an old page link to the same page in your default language, and other old links can show page-not-found. Change slugs before you share a language's links.
  • Translations are kept per default language. Changing the default hides the existing translations until it is changed back, so set the default before you translate. The old default stays as a translation language and, on the free plugin, takes the one extra slot until it is removed.
  • The free TranslatePress allows one language besides the default. Removing a language keeps its translations in the database; adding it again brings them back.
  • Automatic translation: with no engine named it keeps the engine already set, or uses TranslatePress AI if none is, which needs a TranslatePress license. Google Translate needs its own API key, entered in TranslatePress's settings; none of these tools set it. Any engine name is accepted, so check the spelling.
  • The license key is saved before it is checked, so a mistyped key replaces a working one. Paste the key yourself in TranslatePress's settings, or check it twice.
  • Removing a language asks for your approval on WPVibe's page in your browser. The other changes run without one, so the recipes show you each change and wait for your yes.

Verified, and kept that way

Works with AI is WPVibe’s verification program. Every ability marked verified was run on a live TranslatePress install, and we rescan WordPress.org weekly so a release that adds or removes abilities shows up here before it surprises you.

Learn more about TranslatePress at translatepress.com.