LangRelayVSPolylang

The Polylang alternative that keeps up when your pages change

Polylang gives every language its own WordPress post, translated by hand or, in Pro, with DeepL. LangRelay keeps one post, translates the rendered page with AI, and holds a page with untranslated text, the wrong language or a changed price before it goes live. Here is how they compare.

  • Free plan, no card
  • WordPress plugin
  • Free checks before going live
Built for

WordPress sites that keep changing

WordPress sites translated by hand, one post per language

Who does the translating

AI translates every page, and free checks hold a page with untranslated text, the wrong language or a changed price

You, or DeepL in Pro, one post at a time

Keeping translations current

The plugin reports each edit, and only the new text is translated

Editing the original does not update its translated text

Price

Free, or from €19 a month

Free, or from €99 a year

Polylang lets you translate WordPress by hand, or with DeepL in Pro, one post per language. LangRelay translates the rendered page for you and asks before it publishes.

Polylang is the right pick if you want a free plugin, every translation as a WordPress post, and you are happy to translate and update each one yourself. LangRelay suits sites that change often: it translates every page, picks up edits about a minute later, holds a page with untranslated text, the wrong language or a changed price before it goes live, and Relay drafts the changes you ask for.

When to choose LangRelay, and when to choose Polylang

Choose LangRelay if

  • You want every page translated for you, not one post at a time.
  • You edit your pages often and want translations to follow.
  • You would rather not manage a copy of every post in every language.
  • You want to describe a change in a sentence and have an agent draft it for you.

Choose Polylang if

  • You want a free plugin with unlimited languages, and you are happy to translate each page yourself.
  • You want every translation stored as a WordPress post in your own database.
  • You need a subdomain or a separate domain per language.
  • You would rather pay a yearly licence priced by site, with machine translation on your own DeepL account.

Where Polylang and LangRelay differ

Both run inside WordPress. Here is where they differ day to day, from Polylang’s own pages and ours.

01

Who does the translating

In Polylang you translate each post yourself. Pro adds DeepL with your own API key, one post at a time, and its guide says content from some page builders, including Elementor and Divi, is not supported. LangRelay translates every page its crawl finds, with AI that follows your glossary and each language’s formality.

02

When the original changes

Polylang’s DeepL guide says a translation does not update when you edit the original: you edit it by hand, or regenerate it and use DeepL credits again. LangRelay’s plugin reports an edit about a minute later, and only the new text is translated.

03

One post, or one per language

Polylang creates a separate post for each language and links it to the original, so every language is its own content to manage. LangRelay keeps one post and translates the page WordPress renders, theme and page-builder text included.

04

Checks before it goes live

Both let a person decide what goes live. Polylang saves DeepL output as a draft that someone publishes, and Pro can restrict a role to one language. LangRelay puts translations live by default and its free checks hold a page with untranslated text, the wrong language or a changed price; you can choose to approve every page yourself, and you edit translations on the rendered page in the visual editor.

05

Asking in plain language

We found no AI assistant on polylang.pro. Relay, LangRelay’s built-in agent, reads your Site’s pages and translations and drafts the changes you ask for. It reviews any page you ask it to, quoted in AI credits first, and it can never approve or publish on its own.

06

Where translations live, and what you pay

Polylang’s translations are WordPress posts in your database, and a Pro licence that is not renewed keeps working, without updates or support. Pro is a yearly licence priced by number of sites, and machine translation runs on your own DeepL API key. LangRelay is a monthly plan with a word allowance, and its translations are served through LangRelay.

LangRelay and Polylang, 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
CapabilityLangRelayPolylang
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. A subdirectory, subdomain or separate domain per language.

Source, checked 7 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.

No

Each translation is a separate post, linked to the original.

Source, checked 7 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 tags and language-dependent meta tags.

Source, checked 7 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

Pro only: translates URL slugs for post types, taxonomies, categories, tags and author pages.

Source, checked 7 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.

No

Editing the original does not update its DeepL translation; you edit it by hand or regenerate it.

Source, checked 7 October 2026
Approve before it goes liveWhether a person can check a translation before visitors see it.Yes:

When you choose Ask me first. By default pages go live as they are ready, and free checks hold a page with untranslated text, the wrong language or a changed price. Legal pages, pricing pages and sweeping changes always wait for you.

Partly

DeepL output is saved as a draft that a person publishes. No approval workflow found.

Source, checked 7 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.

Not found

No front-end editor found.

GlossaryFixed translations for names and terms, applied every time they appear.Yes:

Per-language terms, “keep as source”, and match case. Paid plans.

Partly

Pro: choose a DeepL glossary, managed in your DeepL account.

Source, checked 7 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.

Partly

Pro only: DeepL with your own API key, one post, page or product at a time. Not for Elementor or Divi content.

Source, checked 7 October 2026
AI quality reviewAI that checks translations for mistakes, not only writes them.Yes:

Relay reviews any page you ask it to, the way a language expert would, quoted in AI credits first. It reviews legal pages, pricing pages and sweeping changes on its own while you have AI credits.

Not found

No AI review 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 polylang.pro.

APIProgrammatic access for developers.Planned

On the way, for the Growth plan and up.

Partly

Pro only: REST API support for languages and translations.

Source, checked 7 October 2026

Translation that goes live, safely

The translating is the easy part. LangRelay is built around what happens next: checking it, changing it, and deciding when it goes live.

01

Live by default, checked first

Free checks hold any page that looks wrong before it goes live: text left untranslated, the wrong language, a translation far longer than its source, or a changed number or price. Legal pages, pricing pages and sweeping changes always wait for you.

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

Relay is the expert you call

Ask Relay to review any page and it reads it the way a language expert would. It tells you the cost in AI credits before it starts.

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.

Start from your original pages

LangRelay translates from your original pages, so Polylang’s per-language posts aren’t imported. Once Polylang is off, its other-language copies of your pages and products become ordinary pages, still published, and the language-switcher menu item stays as a dead link. Before you connect, move those copies to Draft (or delete them), keep your original-language pages, and remove the old switcher from your menu. Then install the plugin, connect your Site, and LangRelay crawls your pages and translates them into the languages you choose.

What comes across

  • Every page the crawl finds, translated into your languages
  • Theme, menu and page-builder text, from the rendered page
  • hreflang, a canonical per language, and translated titles and meta

Translations are made fresh, so the first crawl uses words from your allowance. LangRelay serves languages under subdirectories such as /fr/. If Polylang used a subdomain, a separate domain or translated slugs, set matching slugs or add redirects so links keep working.

What you pay, and what it counts

A yearly licence priced by number of sites. Machine translation runs on your own DeepL API key and its quota.

LangRelay Starter

€19a month

3 Sites, 3 languages per Site and 50K 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, 2K words a month.

Annual billing and every plan on the pricing page.

Polylang

€99a year

Polylang Pro, €99 a year for 1 site, excluding VAT.

Free plan: Polylang on WordPress.org, with no limit on the number of languages.

From Polylang’s pricing page, checked 7 October 2026.

Frequently asked questions

What people ask when they weigh Polylang 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 Polylang translate my site automatically?

Not all at once. In the free plugin you translate each post yourself. Polylang Pro adds DeepL with your own API key, one post, page or product at a time; its features page says Pro has no one-click “translate everything” feature. LangRelay translates every page its crawl finds and puts it live, unless its free checks hold it.

Does Polylang update translations when I edit a page?

Not the translated text. Polylang’s DeepL guide says there is no automatic synchronisation between the original and its translation. You edit the translation by hand, or regenerate it, which uses DeepL credits again. Pro’s synchronized posts copy an edit to other languages, so they suit posts that read the same in each. LangRelay’s plugin reports an edit about a minute later, and only the new text is translated.

Does Polylang create a separate post for each language?

Yes. Polylang’s documentation describes each translation as its own WordPress post, linked to the original. That keeps translations in your database, and means each language is a separate post to manage. LangRelay keeps one post and translates the rendered page.

How does Polylang pricing compare with LangRelay?

The Polylang plugin on WordPress.org is free, with no limit on the number of languages. Polylang Pro is €99 a year for 1 site, up to €495 a year for 25 sites, excluding VAT. Pro is priced by site, and machine translation runs on your own DeepL API key and its quota. LangRelay is a monthly plan with words included each month; see the pricing comparison above.

Can I switch from Polylang to LangRelay?

Yes, but plan the URLs. LangRelay translates from your original pages, so Polylang’s per-language posts aren’t imported. Once Polylang is off, its other-language copies of your pages and products become ordinary pages, still published, and the language-switcher menu item stays as a dead link. Before you connect, move those copies to Draft (or delete them), keep your original-language pages, and remove the old switcher from your menu. LangRelay serves each language under a subdirectory such as /fr/, and translated slugs are set by hand. If Polylang used a subdomain, a separate domain or translated slugs, set matching slugs or add redirects so existing links keep working.

Does Polylang have an MCP server?

Not that we could find on polylang.pro. LangRelay’s MCP is on the way; today you can ask Relay, LangRelay’s built-in agent, from inside the dashboard.

LangRelay vs Weglot

A translating proxy that works on almost any platform. Its help center says languages are public by default and new text is translated automatically, unless you turn off automatic content translation or hide automatic translations. Pricing caps the total number of translated words and languages.

LangRelay vs WPML

A WordPress translation plugin that stores each language as its own post in your database, with review controls and integrations for page builders, WooCommerce and translation services. AI translation is paid per word beyond the words a yearly licence includes.

LangRelay vs TranslatePress

A WordPress plugin that translates the rendered page, with a front-end visual editor even in the free version. Translations live in your database; automatic translations are served without an approval step.

LangRelay vs Linguise

A hosted service that translates the whole site automatically and serves the translations from its own servers, with SEO output and unlimited languages. We found no review step before translations go live.

LangRelay vs GTranslate

A free language switcher that translates in the browser with Google Translate, without SEO; its WordPress plugin has more than 900,000 active installs. Paid plans add a translating proxy with indexable pages and no word limits.

LangRelay vs ConveyThis

A plugin and proxy with 35+ platform integrations, with a visual editor on every plan and a read-only MCP server. New translations show on the site as soon as they are made.

The 2026 buyer’s guide

Eight website translation tools compared on delivery, SEO, review, AI and pricing.

Sources

Every Polylang claim on this page comes from Polylang’s own pages: its website, its documentation or its WordPress.org listing. Spotted something out of date? Tell us and we’ll correct it.

Polylang

Product names and logos belong to their owners; shown to identify them for comparison, no affiliation or endorsement.

Start with one page.

Pick a language and a page. See how LangRelay handles changes, review, and SEO on your own site.

For WordPress, install the plugin first.

Part of a guide