LangRelayVSTranslatePress
The TranslatePress alternative with an approval step and an AI agent
TranslatePress and LangRelay both translate the rendered WordPress page without duplicating posts. The difference is what happens before a translation goes live. Here is how they compare.
- Free plan, no card
- WordPress plugin
- Nothing publishes without you
- Built for
WordPress sites that keep changing
WordPress sites translated from the front end
- Who decides what goes live
Nothing goes live until someone approves it
- Asking for a change
Ask Relay in a sentence; it drafts the change for approval
- Price
Free, or from €19 a month
Both translate the page WordPress renders. TranslatePress publishes straight away; LangRelay waits for your approval.
Both translate the rendered WordPress page and leave your posts alone. TranslatePress keeps everything in your database and publishes automatic translations straight away. LangRelay adds an approval step to every translation, and an agent that drafts the changes you ask for.
When to choose LangRelay, and when to choose TranslatePress
Choose LangRelay if
- You want nothing published that nobody checked.
- You want to describe a change in a sentence and have an agent draft it for you.
- You want to ask an agent what still needs doing, in plain language.
- You would rather pay monthly than commit to a yearly licence.
Choose TranslatePress if
- You want every translation stored in your own WordPress database.
- You want automatic slug translation today.
- You prefer one yearly payment over a monthly plan.
- You want automatic translations live straight away, without a review step.
TranslatePress is quick until a translation needs a second look
TranslatePress serves automatic translations straight away. Here is where the two part ways.
01
Review before it goes live
TranslatePress serves automatic translations as soon as they exist; its own site pitches this as not needing to review them. A paid add-on can hide a whole language until you publish it. LangRelay holds every translation until someone approves it.
02
AI that reviews, not only translates
TranslatePress AI routes each language pair to an LLM or DeepL or Google. LangRelay translates with AI too, and when Relay drafts a change, a separate reviewer agent checks it the way a language expert would.
03
Asking in plain language
Relay, LangRelay’s built-in agent, answers questions about your Site and drafts the changes you ask for. We found no assistant in TranslatePress; you work in its visual editor and string lists.
04
Where translations live
TranslatePress stores translations in your WordPress database, and the plugin keeps working if the licence expires. LangRelay’s translations are served through LangRelay. If keeping everything inside WordPress matters most, TranslatePress is built for that.
05
How you pay
TranslatePress is a yearly licence by number of sites, with AI words granted each licence year. LangRelay is a monthly plan with a word allowance each month; text that has not changed costs nothing again.
06
Translated URLs
TranslatePress’s SEO Pack can translate slugs automatically. In LangRelay you set translated slugs by hand today; automatic slug translation is on the way.
LangRelay and TranslatePress, side by side
- No · Not offered
- Partly · With a limit
- Planned · Announced, not shipped
- Not found · Not on the vendor’s own pages when we checked
- Yes · Included
| Capability | LangRelay | |
|---|---|---|
| Delivery and SEOHow translated pages reach visitors and search engines. | ||
| How translated pages are servedHow the translated page reaches visitors: from your own server, through a proxy, or swapped in by the browser. | Yes: WordPress plugin serves translated HTML from your server. A script tag works on any other site, without SEO. | Yes: WordPress plugin. Translations are stored in your database and served by your site on a subdirectory. Source, checked 5 October 2026 |
| WordPress: one post, no copies per languageWhether WordPress keeps one post per page, instead of a separate copy for every language. | Yes: Translates the rendered page. Your posts stay as they are. | Yes: One post. Translations are stored per string and linked to the original. Source, checked 5 October 2026 |
| hreflang and per-language URLsA URL per language with hreflang tags, so search engines find and index each language. | Yes: Subdirectories (/fr/), hreflang with x-default, a canonical per language, and translated titles and meta. | Yes: hreflang for every page. Translated metadata and multilingual sitemaps need the SEO Pack, on paid plans. Source, checked 5 October 2026 |
| Translated URL slugsURLs in the visitor’s language, like /fr/a-propos instead of /fr/about. | Partly Set by hand per page and language. Automatic slug translation is on the way. | Partly SEO Pack, on paid plans: by hand or automatically. Source, checked 5 October 2026 |
| Workflow and reviewWhat happens when content changes, and who decides what goes live. | ||
| Picks up edits to the originalWhen you edit the original page, whether the tool notices and translates what changed. | Yes: The WordPress plugin reports an edit about a minute later, and only the new text is translated. Other sites can call a change hook from their CMS or deploy. | Yes: An edited string is treated as new and translated when a visitor next opens the page in that language. Source, checked 5 October 2026 |
| Approve before it goes liveWhether a person can check a translation before visitors see it. | Yes: Nothing goes live until someone approves it. | Partly Automatic translations are served without a review step. A paid add-on can hide a whole language until you publish it. Source, checked 5 October 2026 |
| Visual editorEditing translations on the page itself, rather than in a list of strings. | Yes: Click text on the rendered page to edit, at desktop, tablet and mobile widths. | Yes: Front-end editor with a live preview, in the free plugin. Source, checked 5 October 2026 |
| GlossaryFixed translations for names and terms, applied every time they appear. | Yes: Per-language terms, “keep as source”, and match case. Paid plans. | Yes: Applies to new automatic translations when TranslatePress AI is the engine. Source, checked 5 October 2026 |
| AI and integrationsHow much of the work AI takes on, and how you reach it. | ||
| Machine translationThe machine or AI translation the tool uses. | Yes: AI translation that follows your glossary and each language’s formality. | Yes: TranslatePress AI picks between LLMs (Gemini, GPT) and DeepL or Google per language pair. Google or DeepL with your own key also work. Source, checked 5 October 2026 |
| AI quality reviewAI that checks translations for mistakes, not only writes them. | Yes: A separate reviewer agent checks every change Relay drafts, the way a language expert would. Paid plans. | Not found No AI quality score or review queue found. |
| AI assistant in the productAn assistant inside the product that you can ask in plain language. | Yes: Relay, a chat agent that reads your Site’s pages and translations and drafts changes for your approval. | Not found No AI assistant found. |
| MCP server for your own AILets your own AI assistant, such as Claude or ChatGPT, work with the tool directly. | Planned On the way: connect Claude or ChatGPT to your Sites. | Not found Not found on translatepress.com. |
| APIProgrammatic access for developers. | Planned On the way, for the Growth plan and up. | Partly PHP functions and hooks. No public REST API for managing translations found. Source, checked 5 October 2026 |
Translation that waits for your yes
The translating is the easy part. LangRelay is built around what happens next: checking it, changing it, and deciding when it goes live.
01
Nothing goes live unapproved
Every translation waits for someone to approve it. Then activate one page, or everything approved at once.
02
Ask Relay in a sentence
Relay reads your Site’s pages and translations and drafts the change you describe, for you to approve. It can never approve or publish on its own.
03
A second agent checks Relay’s work
Every change Relay drafts goes to a separate reviewer agent, which checks it the way a language expert would.
04
Edit on the rendered page
Click any text in the visual editor to change it, at desktop, tablet or mobile width, with titles and meta in the same panel.
Same URL structure, fresh translations
Both plugins translate the rendered page and use /fr/-style subdirectories, so your URL structure carries over. Install the LangRelay plugin, connect your Site, and LangRelay crawls and translates it.
What comes across
- Every page the crawl finds, translated into your languages
- The same /fr/-style subdirectory URLs
- hreflang, a canonical per language, and translated titles and meta
Translations are made fresh, so the first crawl uses words from your allowance. Slugs translated with the SEO Pack are set again by hand.
What you pay, and what it counts
A yearly licence by number of sites. AI words are counted per word, per language, granted each licence year, and carry over while the licence is active.
LangRelay Starter
€19a month
3 Sites, 3 languages per Site and 150K words a month. A word is a source word translated into one language; unchanged and reused text uses none.
Or start free: 1 Site, 1 language, 10K words a month.
TranslatePress
€99a year
Personal, €99 a year: 1 site, 50,000 AI words, SEO Pack and unlimited languages.
Free plan: Free plugin: one extra language, the visual editor and 2,000 AI words.
Frequently asked questions
What people ask when they weigh TranslatePress against LangRelay: how each one stores and publishes translations, what the prices count, and what moving involves.
Something we missed? Book a demo or write to us.
Does TranslatePress duplicate WordPress posts?
No. TranslatePress stores translations per string, linked to the original post, so there is one post per page. LangRelay works the same way: it translates the page WordPress renders.
Does TranslatePress publish automatic translations?
Yes. TranslatePress’s AI page says new content is translated automatically and you won’t need to review it unless you prefer to. There is no approval step per translation; a paid add-on can keep a whole language hidden until you publish it.
How does TranslatePress pricing compare with LangRelay?
TranslatePress Personal is €99 a year for 1 site with 50,000 AI words, counted per word, per language. LangRelay is a monthly plan with words included each month; see the pricing comparison above for both.
Can I switch from TranslatePress to LangRelay?
Yes. LangRelay crawls and translates your pages from the rendered site, so you don’t need an export to start. Both use language subdirectories such as /fr/; if you translated slugs with the SEO Pack, set the same ones in LangRelay so existing links keep working.
Does TranslatePress have an MCP server?
Not that we could find on translatepress.com. LangRelay’s MCP is on the way; today you can ask Relay, LangRelay’s built-in agent, from inside the dashboard.
Keep comparing
LangRelay vs Weglot
The best-known translating proxy. It works on almost any platform; its help center describes machine translation going live automatically unless you switch on manual approval. Pricing caps the total number of translated words and languages.
LangRelay vs WPML
The longest-standing WordPress translation plugin. Each language is its own post in your database, with deep review controls and integrations. AI translation is paid per word on top of a yearly licence.
LangRelay vs Polylang
A popular free plugin for translating WordPress by hand. Each language is its own post; Pro adds DeepL, slug translation and more. Nothing is translated or updated automatically.
LangRelay vs Linguise
A hosted service that translates everything automatically and serves it straight away. Strong SEO output and unlimited languages; there is no review step before translations go live.
LangRelay vs GTranslate
Best known for its free Google Translate switcher, which translates in the browser without SEO. Paid plans add a translating proxy with indexable pages and no word limits.
LangRelay vs ConveyThis
A plugin and proxy for many platforms, with a visual editor on every plan and a read-only MCP server. Translations go live by default; subdirectories need a higher plan.
The 2026 buyer’s guide
Eight website translation tools compared on delivery, SEO, review, AI and pricing.
Sources
Every TranslatePress claim on this page comes from TranslatePress’s own pages: its website, its documentation or its WordPress.org listing. Spotted something out of date? Tell us and we’ll correct it.
TranslatePress
- translatepress.com/docs/translation-function/ (checked 5 October 2026)
- translatepress.com/docs/frequently-asked-questions/ (checked 5 October 2026)
- translatepress.com/docs/settings/ (checked 5 October 2026)
- translatepress.com/docs/automatic-translation/translatepress-ai/ (checked 5 October 2026)
- translatepress.com/docs/translation-glossary/ (checked 5 October 2026)
- translatepress.com/ai/ (checked 5 October 2026)
- translatepress.com/multilingual-seo/ (checked 5 October 2026)
- translatepress.com/docs/translation-editor/url-slug-translation/ (checked 5 October 2026)
- translatepress.com/docs/translation-editor/ (checked 5 October 2026)
- translatepress.com/pricing/ (checked 5 October 2026)
Start with one client site.
Pick one site and one language. See how LangRelay handles changes, review, and SEO on a real client workflow.