LangRelayVSLinguise

The Linguise alternative that checks before it publishes

Linguise translates your whole site once it is connected, and lists 40+ CMS integrations, WordPress among them. LangRelay is built for WordPress 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, Joomla and the rest of its 40+ CMS integrations

Who decides what goes live

You choose: right away (the default), after a 24-hour hold, or once you approve. Free checks hold pages with untranslated text, the wrong language or a changed price

Translations go live once the site is connected; you edit them afterwards

Keeping translations current

The plugin reports each edit, and the new text goes live unless the free checks hold it

New and changed text is translated and served automatically

Price

Free, or from €19 a month

From $15 a month

Linguise translates and publishes your whole site at once. LangRelay translates WordPress and holds a page with untranslated text, the wrong language or a changed price.

Linguise translates your whole site in one step, and fits if your site is not on WordPress or you want unlimited languages and automatic URL translation today. On WordPress, LangRelay works differently: free checks hold a page with untranslated text, the wrong language or a changed price before it goes live, Relay drafts the changes you ask for, and your glossary and each language’s formality guide the translation.

When to choose LangRelay, and when to choose Linguise

Choose LangRelay if

  • Your site runs on WordPress and you want a page held back before it goes live when it has untranslated text, the wrong language or a changed price.
  • You want to describe a change in a sentence and have an agent draft it for you.
  • You want a glossary and a formality setting for each language.
  • You run several sites and want them on one plan.

Choose Linguise if

  • Your site runs on Joomla, Shopify, Wix, Webflow or another platform Linguise supports, not WordPress.
  • You want unlimited languages on every plan.
  • You want URL slugs translated automatically today.
  • You want the whole site translated and live as soon as you connect it, without a review step.

Where Linguise and LangRelay differ

Linguise translates and publishes your whole site in one step. Here is where the two part ways.

01

Who decides what goes live

Linguise’s WordPress install guide says your whole site is translated into every language once you connect it, and we found no approval step before translations go live; you review them afterwards in its dashboard or Live Editor. LangRelay also puts translations live by default, but its free checks hold a page with untranslated text, the wrong language or a changed price first. Legal pages, pricing pages and sweeping changes wait for you, and you can choose to approve every page yourself.

02

What happens after you edit

Both pick up changes to the original automatically. Linguise’s docs say changed text gets a new automatic translation, which replaces any manual edit of it, and we found no step to check it first. In LangRelay, the plugin reports an edit about a minute later, only the new text is translated, and that translation goes live like any other: right away by default, unless the free checks hold it.

03

AI that drafts and reviews, not only translates

Linguise translates with Google Cloud by default, and bills Linguise AI, an LLM-based option, separately as a prepaid quota. We found no assistant in Linguise. Relay, LangRelay’s built-in agent, reads your Site’s pages and translations and drafts the changes you ask for, and reviews any page you ask it to, quoted in AI credits first. Relay never approves or publishes.

04

Terms and tone

Linguise uses replace and exclude rules, which you can scope by URL, language, CSS selector or pattern. LangRelay has a glossary for each language and a formality setting per language, and its AI translation follows both.

05

Where it works

Linguise has native extensions for WordPress and Joomla, and lists 40+ CMS integrations in all, including Shopify, Wix and Webflow. On WordPress it adds hreflang, canonicals, translated metadata and multilingual sitemaps. LangRelay serves search-friendly translations on WordPress; on other sites its script embed translates in the browser, without SEO value. If your site runs on another platform Linguise supports, Linguise translates it with SEO output today.

06

How you pay

Each Linguise plan covers one domain, with unlimited languages; every domain and subdomain is billed separately, with a discount from the third domain. LangRelay’s paid plans include several Sites, with a set number of languages per Site and a word allowance each month. Text that has not changed costs nothing again.

LangRelay and Linguise, 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
CapabilityLangRelayLinguise
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:

Hosted service. WordPress and Joomla connect through an extension, Shopify through an app, other CMSs through a script; self-hosted sites get subfolders like /fr, cloud-hosted ones subdomains like fr.domain.com.

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.

Yes:

Translates the rendered page and doesn’t duplicate content in your database.

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, x-default, canonicals, SEO metadata you can edit, and multilingual sitemaps.

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.

Yes:

Translated automatically, and editable in the dashboard.

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.

Yes:

New and changed text is detected and translated automatically. A manual edit is replaced if the original later changes.

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.

No

The install guide says the whole site is translated once the API key is applied; no approval step found. Edits happen afterwards.

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.

Yes:

Live Editor: click and edit on the real translated page, metadata included.

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

Partly

Replace and exclude rules instead of a glossary, by URL, language, CSS selector or pattern.

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.

Yes:

Google Cloud translation by default. Linguise AI, an LLM-based option, is billed separately as a prepaid quota.

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 linguise.com.

APIProgrammatic access for developers.Planned

On the way, for the Growth plan and up.

Not found

No public developer API found.

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.

Same subdirectories, fresh translations

LangRelay doesn’t need an export from Linguise. 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
  • Subdirectory URLs like /fr/, the structure Linguise uses on WordPress
  • hreflang with x-default, a canonical per language, and translated titles and meta

Translations are made fresh, so the first crawl uses words from your allowance. Linguise translates slugs automatically; in LangRelay you set translated slugs by hand, or add redirects.

What you pay, and what it counts

Source words times target languages, per domain. Human edits and page views don’t count. Prices in dollars.

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.

Linguise

$15a month

START, $15 a month per domain: 200,000 translated words, unlimited languages.

Free plan: No free plan. A one-month trial of up to 600,000 words, with no credit card needed.

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

Frequently asked questions

What people ask when they weigh Linguise 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.

Is LangRelay a Linguise alternative?

Yes, for WordPress sites. Like Linguise, LangRelay translates the rendered page without duplicating posts, but it holds a page with untranslated text, the wrong language or a changed price before it goes live and adds an agent that drafts changes for you. On Joomla, Shopify, Wix or another platform Linguise supports, Linguise fits today.

Does Linguise publish translations automatically?

Linguise’s WordPress install guide says that once you connect, the whole site should already be translated in all your languages. We found no step to approve a translation before it goes live; you review afterwards in the dashboard or the Live Editor, and can invite translators by language. LangRelay also publishes by default, but its free checks hold a page with untranslated text, the wrong language or a changed price first, and you can choose to approve every page yourself.

Does Linguise duplicate WordPress posts?

No. Linguise says it uses a remote cache and doesn’t duplicate any content in your local database; translations are stored on its servers. LangRelay also keeps one post and translates the rendered page, and serves translations through LangRelay.

How does Linguise pricing compare with LangRelay?

Both count a source word once for each language it is translated into. Linguise START is $15 a month per domain for 200,000 translated words, with unlimited languages; LARGE, $45 a month, has no word limit (fair usage applies). LangRelay Starter is €19 a month for 3 Sites, 3 languages per Site and 50,000 words a month. After the first translation, only new or changed text uses words.

Can I switch from Linguise to LangRelay?

Yes. Install the LangRelay plugin and connect your Site; LangRelay crawls and translates your pages, so you don’t need an export from Linguise. On WordPress both use subdirectories such as /fr/. Linguise translates URL slugs automatically, while LangRelay’s are set by hand, so set the slugs you want to keep or add redirects so existing links keep working.

Does Linguise have an MCP server?

Not that we could find on linguise.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

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 Polylang

A free WordPress plugin with 900,000+ active installations on WordPress.org. Each language is its own post, translated by hand; Pro adds DeepL one post at a time, slug translation and more. Editing the original does not update its translated text.

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 Linguise claim on this page comes from Linguise’s own pages: its website, its documentation or its WordPress.org listing. Spotted something out of date? Tell us and we’ll correct it.

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