WordPress
Translate WordPress posts and pages through Polylang or WPML, and keep them translated as they are published.
WordPress keeps each language of a post as a post of its own, which Polylang or WPML links to the original. The Lingo.dev connection reads published posts in the source language, translates their title, excerpt, and block content through a localization engine, and writes the result into the linked translation of each post. Block markup, block settings, shortcodes, and embed addresses stay as they are; the text inside them, and the labels of blocks such as Search and Navigation, is translated.
Start with one post type. Once a site is set up, publishing a post of a selected type in the source language starts its translation, with no separate switch to turn on, so run a manual Sync and inspect the result before selecting more.
WordPress integration comes with the Enterprise plan. See pricing for current availability. Settings → Integrations shows Not on your plan beside WordPress when the organization needs plan access.
Prepare the site #
The site must answer over HTTPS at a public address, and run Polylang or WPML with its languages set up. Lingo.dev translates into a WordPress language through the locale WordPress gives it, such as de_DE for de-DE, so no language mapping is configured. A language whose locale another language already uses falls back to a shorter one, such as de for de_DE_formal beside de_DE.
Install and activate the Lingo.dev plugin from the WordPress plugin directory. Then open Settings → Lingo.dev in WordPress and generate a key. The plugin keeps only a hash of the key, so copy it before leaving the page. Generating a new key replaces the old one, and syncing stops until you enter the new key in Lingo.dev.
Connect the site #
Open Settings → Integrations in Lingo.dev and select Connect for WordPress, or start in Studio with Add an integration → WordPress, which opens the same form. Enter a connection name, the site's address, and the key. Select Connect: Lingo.dev checks that the plugin answers with the key, that the site reports the same address, and that Polylang or WPML is active, then hands the plugin the address it notifies when posts change. A site can be connected to one organization at a time.
Connecting from Studio goes straight on to the setup. A site connected in Settings shows Set up in Studio on its connection page; in Studio, you can also select it under Connected, then select Set up. Choose the localization engine and the post types to translate. Lingo.dev translates from the site's default language into every other language of the site that has a WordPress locale; a language you add in Polylang or WPML later is translated too.
Translate one post type #
Run Sync, open its workflow run, and inspect a translated post in WordPress. Check its wording, links, blocks, and publication state, then read it on the site.
A first Sync keeps the translations the site already has. When a post's translation holds only some of its fields, such as a translated title without an excerpt, the first Sync keeps the translated fields and translates the rest.
Translations are published while their source post is published. A private or scheduled translation keeps its status, and unpublishing a source leaves its translations as they are.
Keep translations aligned with source changes #
When a post of a translated type is published or updated in the source language, the plugin notifies Lingo.dev, which reads the post again and translates what changed. Saving a draft or a translation does not start translation. Lingo.dev also checks for posts modified since its last check every hour, so a missed notification is caught up.
Use Sync for changed posts and missing translations. Use Retranslate when you intend to replace translations, including hand-edited ones.
Edits during a sync #
Every write carries the site's hash of the source post as it was read, and of its translation when one already existed. If an editor changes either one while the sync translates, the plugin refuses a write that would overwrite the edit, and the run reports the post as skipped. Use Sync to pick up a changed source post, and Retranslate to replace an edited translation.
Change settings or disconnect #
Change the engine and post types in Studio, on the integration's Settings tab, and the languages in Polylang or WPML. Rename the connection, replace its key, or disconnect it in Settings → Integrations. After generating a new key in WordPress, select Replace key and enter it.
Changing the site's address requires a new connection. Disconnecting asks the plugin to stop notifying Lingo.dev, removes the connection's history and sync state, and leaves translated posts in WordPress. The plugin accepts that request only with its current key, so after generating a new key in WordPress, select Replace key before disconnecting. If the site was disconnected with an old key, the plugin keeps sending notifications, which Lingo.dev ignores; deleting the plugin in WordPress stops them.