Title: Langferry
Author: Langferry
Published: <strong>November 18, 2026</strong>
Last modified: November 18, 2026

---

Search plugins

![](https://ps.w.org/langferry/assets/banner-772x250.png?rev=3810600)

![](https://ps.w.org/langferry/assets/icon-256x256.png?rev=3810600)

# Langferry

 By [Langferry](https://profiles.wordpress.org/langferry/)

[Download](https://downloads.wordpress.org/plugin/langferry.2.8.1.zip)

 * [Details](https://wordpress.org/plugins/langferry/#description)
 * [Reviews](https://wordpress.org/plugins/langferry/#reviews)
 *  [Installation](https://wordpress.org/plugins/langferry/#installation)
 * [Development](https://wordpress.org/plugins/langferry/#developers)

 [Support](https://wordpress.org/support/plugin/langferry/)

## Description

Langferry translates your WordPress site into 100+ languages and makes every translation
discoverable in search engines. The translation runs inside WordPress and the translations
are stored in your own database; the Langferry Cloud service provides the machine
translation and one dashboard for all your sites.

 * **Real translated pages** — `/es/about/`, `es.example.com` or your own domain
   per language. Every page is translated on the server, so search engines index
   it.
 * **Sentence-level machine translation** — whole sentences are translated together(
   links and formatting included), giving natural grammar instead of word-salad.
 * **Translation memory** — every sentence is translated once and reused across 
   your site. Editing one paragraph only re-translates that paragraph.
 * **Multilingual SEO built in** — hreflang + x-default on every page, translated`
   <html lang>`/`dir`, `og:locale`, self-referencing canonicals, translated meta
   descriptions, alt text and titles, an XML sitemap with language alternates, optional
   translated URLs.
 * **Works with your SEO plugin** — Yoast SEO, Rank Math, All in One SEO or SEOPress
   keeps doing its job: its titles, descriptions and canonical tags carry over to
   every language, and each language’s sitemap leaves out what it leaves out. With
   no SEO plugin, the sitemaps follow WordPress’s own rules.
 * **Edit any translation** — a searchable translation editor; your edits are never
   overwritten.
 * **WooCommerce** — orders remember the customer’s language and customer e-mails
   are sent in it.
 * **Language switcher** — nine styles, floating or inline, block, widget, menu 
   or shortcode. Choose the flag for English (UK, USA or Canada), French (France
   or Quebec), Portuguese (Portugal or Brazil) and Spanish (Spain, Mexico, Argentina
   or Colombia). Links are real, crawlable `<a href>`s. Switcher shortcodes from
   other translation plugins keep working, so switching doesn’t break your theme.
 * **One account for all your sites** — connect any number of sites to one Langferry
   login; manage languages, settings, plans and billing for all of them in one dashboard
   with one invoice.
 * **Developer friendly** — WP-CLI commands (`wp langferry status|connect|sync|translate
   |purge`), `notranslate` class / `translate="no"` support, filters for everything.

#### Plans

Every feature of this plugin works on every plan, Free included: indexable translated
pages, hreflang, sitemaps, the translation editor, and subdomains or your own domain
per language. Plans differ in what Langferry Cloud does for the site: how many languages
and new characters a year it translates, whether it translates WooCommerce email
text (Startup and above) and page addresses (Business and above). Prices and details:
[langferry.com/pricing](https://langferry.com/pricing/). Every new site gets a 14-
day trial.

### External services

This plugin connects to **Langferry Cloud** (app.langferry.com), the service that
translates your text and runs your Langferry account. It needs a Langferry account(
the Free plan is enough to try it). Nothing is sent until you click Connect.

 * **When you connect:** the site’s address, so the account can link to it.
 * **Every hour, and when you save settings:** the site’s address, its language 
   settings, the plugin, WordPress and PHP versions, and counts of translated strings
   and manual edits. This keeps the dashboard and plan limits in step. The hourly
   report also includes the titles of the site’s main pages, of pages waiting to
   be translated and of pages that couldn’t be finished, so the dashboard can show
   progress, and counts of pages translated, waiting and set aside. Nothing is sent
   to any new place: Langferry’s signature for its own requests goes only to your
   site itself.
 * **When a page, a page address or a WooCommerce email contains text that hasn’t
   been translated yet:** that text, the source and target language, and what it
   is for (page, address or email), and, when Langferry translates ahead of visitors,
   whether the text is for one of the site’s main pages. Text on pages shown to 
   signed-in visitors and in order emails can include personal details unless you
   exclude those pages or emails; that text is marked private, so Langferry Cloud
   doesn’t keep it in its shared translation cache, and this site deletes it 30 
   days after its last use. Visitors’ IP addresses, cookies and requests are never
   sent.
 * Langferry Cloud has the text translated by **Google Cloud Translation**.
 * Langferry Cloud can also send signed requests to this site (for example, to confirm
   the plugin answers at the site’s address, or to say the settings changed).

Langferry: [Terms of Service](https://langferry.com/terms/), [Privacy Policy](https://langferry.com/privacy/),
[Subprocessors](https://langferry.com/subprocessors/). Google Cloud: [Terms](https://cloud.google.com/terms),
[Privacy Policy](https://policies.google.com/privacy).

## Screenshots

[⌊Settings: choose languages and style the language switcher.⌉⌊Settings: choose 
languages and style the language switcher.⌉[

Settings: choose languages and style the language switcher.

[⌊The translation editor: search any sentence and change its translation.⌉⌊The translation
editor: search any sentence and change its translation.⌉[

The translation editor: search any sentence and change its translation.

[⌊URLs & SEO: subdirectories, subdomains or your own domain per language, hreflang
and sitemaps.⌉⌊URLs & SEO: subdirectories, subdomains or your own domain per language,
hreflang and sitemaps.⌉[

URLs & SEO: subdirectories, subdomains or your own domain per language, hreflang
and sitemaps.

[⌊A translated page with the language switcher.⌉⌊A translated page with the language
switcher.⌉[

A translated page with the language switcher.

[⌊The Langferry dashboard: every site, plan and invoice in one place.⌉⌊The Langferry
dashboard: every site, plan and invoice in one place.⌉[

The Langferry dashboard: every site, plan and invoice in one place.

## Blocks

This plugin provides 1 block.

 *   Language Switcher

## Installation

 1. Install and activate the plugin.
 2. Go to **Langferry  Settings** and click **Connect to Langferry** (free account).
 3. Pick the languages to translate into and save. Your pages are now available at `/
    es/`, `/fr/`…

## FAQ

### Do translated pages work with page caching?

Yes. Each language has its own URL, so server caches and CDNs cache every language
separately. Caching plugins that save pages from inside WordPress, such as SiteGround
Optimizer’s file-based cache, are told not to save translated pages (the standard
DONOTCACHEPAGE flag), so a translated page can never be saved as the original-language
one. Pages in your original language are cached as before.

### Does it work with my SEO plugin?

Yes, with Yoast SEO, Rank Math, All in One SEO and SEOPress. Set up your SEO plugin
for your main language as usual. Langferry translates the titles and descriptions
it writes, points its canonical tags at the translated page, and gives each language
a sitemap that lists the same pages, posts, categories and tags as your SEO plugin’s
sitemap. Pages set to noindex, or whose canonical points elsewhere, stay out. Details:
[langferry.com/seo](https://langferry.com/seo/).

### What counts toward my translation allowance?

Only text that has never been translated before. Re-serving existing translations
is unlimited. Paid plans include a yearly allowance; the free plan includes 100,000
characters per domain.

### How do I know which plan fits my site?

Tick languages in Settings and Langferry shows how much text your site has, how 
much is left to translate in those languages, and what your plan does with it: all
at once, or at its daily pace and how long that takes. Each language’s Translations
tab shows how much of your site it has so far.

### Do bots and crawlers use up my allowance?

No. Everyone is served the translations you already have, but only people cause 
new text to be translated, and the Langferry worker, which translates your pages
in the background. While the worker is running, the search engines that index translated
pages (Google, Bing, Yandex, Baidu, Apple, Seznam, Naver) get the translations you
already have too; they find the finished pages through hreflang and your sitemap.
If the worker can’t run on your site (for example, your host blocks the site’s requests
to itself, or WP-Cron never runs), they cause new text to be translated, as before,
until it runs again. A search engine has to prove who it is: its network address
must belong to it. Anything that only calls itself Googlebot gets the cached version,
as do SEO tools, AI crawlers, scrapers, scripts, search results and 404 pages, whose
text a visitor can make up. Langferry Cloud also paces your allowance, so a crawl
can’t use up a year in a day, and keeps part of it for people. Developers can change
this with the `langferry_translate_new_text` filter.

### Which pages are translated first?

Your main pages: the home page and the pages in your menus, language by language
in the order of your language switcher, so your first language is finished before
the next one starts. Then the pages people asked for, by opening them in a language
where they weren’t finished, and then the rest of your sitemap, newest first. Langferry
translates one page completely before it starts the next, a few at a time in the
background, within your plan’s daily pace. A page a person opens is still translated
at once. The usage card shows how far it has got.

### Can I exclude parts of a page?

Add `class="notranslate"` (or `translate="no"`) to any element, or list CSS selectors/
page paths in Settings  Exclusions.

### Can I switch from another translation plugin?

Yes. Deactivate your current plugin, activate Langferry and connect. Common language
switcher shortcodes from other translation plugins are rendered by Langferry automatically.

### Which features need a paid plan?

None of the plugin’s features: indexing, hreflang, sitemaps, the editor and custom
domains work on every plan. Paid plans give Langferry Cloud more to do: more languages
and characters a year, translated WooCommerce email text (Startup and above) and
translated page addresses (Business and above).

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“Langferry” is open source software. The following people have contributed to this
plugin.

Contributors

 *   [ Langferry ](https://profiles.wordpress.org/langferry/)

[Translate “Langferry” into your language.](https://translate.wordpress.org/projects/wp-plugins/langferry)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/langferry/), check 
out the [SVN repository](https://plugins.svn.wordpress.org/langferry/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/langferry/) by [RSS](https://plugins.trac.wordpress.org/log/langferry/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 2.8.1

 * Clearing a finished page from your page cache now clears only that page in every
   supported caching tool. Before, SiteGround Optimizer and WP Rocket also cleared
   every page under it. Where a tool can’t clear one page alone, Langferry leaves
   it alone, and its own request still reaches WordPress.
 * When a translation starts or stops being listed for search engines, the original-
   language page is cleared too, so its language links follow.
 * Pre-translation requests are signed with a secret only your site knows. A request
   that merely claims to be Langferry’s gets the translations you already have and
   is never recorded.
 * The background worker may now use the part of your budget kept for visitors, 
   but only for your main pages. Search engines and the rest of your pages still
   leave it for visitors.
 * A page that redirects to the same address on https or www counts as a failed 
   try. A page that asks visitors to sign in is set aside for 7 days without pausing
   pre-translation.
 * The usage card counts every page that couldn’t be finished. It names up to 10
   and counts the rest.
 * The usage card’s note about clearing your page cache now also appears when your
   cache tool can’t clear single pages in your address setup.
 * When Langferry Cloud pauses one language for a few minutes, the other languages
   carry on.
 * `wp langferry translate` now stops with exit code 1 and says so when Langferry
   Cloud has paused every language that is left.
 * If your server can’t generate random numbers, Langferry now stops pre-translating
   with a clear message instead of setting pages aside.
 * Fixed: updating on a busy site could schedule the background worker twice.

#### 2.8.0

 * Main pages first: your home page and the pages in your menus are translated before
   anything else, language by language in the order of your language switcher, one
   page completely before the next. Then come the pages people asked for, and then
   the rest of your sitemap.
 * Langferry translates in the background, a few pages at a time, so you don’t have
   to wait for visitors. It stays within your plan’s daily pace and keeps part of
   it for people.
 * Before it translates a page, and when the page is finished, Langferry asks your
   caching plugin or host cache to clear that page (SiteGround Optimizer, WP Rocket,
   W3 Total Cache, LiteSpeed Cache, WP Super Cache and Cache Enabler), so visitors
   and search engines get the finished page. Its own request for the page carries
   a one-time query argument, so page caches pass it through to WordPress; nothing
   links to it. On a site with a language on its own domain or sub-domain, SiteGround’s
   cache is cleared only for the site’s own domain. When Langferry can’t clear your
   site’s page cache, the usage card says so: finished pages reach visitors when
   that cache expires.
 * A page that can’t be finished is set aside for 7 days after 3 tries. A page people
   asked for that is gone (it answers 404, 410 or a redirect) is taken off the list
   instead. A page that takes longer than 20 seconds to render is left to finish
   before the next one starts, and never pauses the worker. If the site’s requests
   to itself keep failing (3 runs in a row, or 10 different pages in a row), the
   worker pauses for a day and people’s visits translate pages as before. Only a
   page your site answers normally counts as translated: a maintenance-mode page
   never does.
 * Search engines are pointed only at finished translations: with the setting “Hide
   pages from search engines while they are mostly untranslated” on (the default),
   hreflang and the multilingual sitemap list a translation once it isn’t hidden
   as incomplete. While the worker runs, search engines get the translations you
   already have instead of spending your allowance on pages they happen to pick.
 * Your sitemaps are always readable: every file the sitemap index lists answers
   with valid XML and at least one page, from the day you switch a language on.
 * Text over 10,000 characters in one piece is left in the original language, so
   it no longer stops the rest of its page from being translated.
 * The usage card shows progress: how many main pages are done in each language,
   what is next, and any page that couldn’t be finished and why.
 * `wp langferry translate` follows the same order. `--limit` counts pages. It exits
   with code 1 when it stopped early (your plan’s pace, Langferry Cloud unavailable,
   or the site not answering its own requests), and with 0 when it finished or reached`--
   limit`.

#### 2.7.2

 * Security hardening: every address, form field and cookie the plugin reads is 
   sanitized as it is read and checked against what it may be, and every piece of
   HTML it prints is escaped where it is printed. The language switcher is printed
   through an allowlist of its own markup. Each settings action checks its nonce
   before it reads the form, and the return from connecting to Langferry Cloud now
   carries a nonce of its own.
 * Database queries name their tables with placeholders.

#### 2.7.1

 * Fixed: with a caching plugin that saves pages from inside WordPress (SiteGround
   Optimizer’s file-based cache, among others), a visit to a translated page could
   be saved as the original-language page, so everyone opening that address saw 
   it in another language. Langferry now tells these caches not to save translated
   pages. After updating, purge your site’s cache once.

#### 2.7.0

 * While you choose languages, Settings shows how much text your site has, how much
   is left to translate in the languages you’ve ticked, and what your plan does 
   with it: all of it right away, or at its daily pace and about how long that takes.
 * The Translations screen shows how much of your site each language has translated.
 * The usage card shows your plan’s pace: what’s available now and what it adds 
   each day. When new text is waiting for the pace, it says so, instead of looking
   like a problem.
 * The hourly report to your Langferry dashboard includes the same numbers (characters
   only, never your text), so the dashboard can show them too.

#### 2.6.0

 * Search engines prove who they are before their visits translate new text: the
   visit’s address must belong to Google, Bing, Yandex, Baidu, Apple, Seznam or 
   Naver. Anything that only claims to be one gets the translations you already 
   have.
 * Works with Langferry Cloud’s pacing: the plugin says whether a person or a search
   engine is asking, so part of your allowance is kept for people, and when your
   budget says “not yet” it waits instead of asking on every page.
 * Text inside `<template>` elements, which themes and plugins copy into the page
   with a script (a footer, a pop-up), is translated, and its links point to the
   same language.

#### 2.5.2

 * Ready for the WordPress.org plugin directory: the plugin is named Langferry, 
   and the author link, which was the same address as the plugin’s, is removed.
 * Code tidy-up flagged by WordPress’s Plugin Check; nothing changes on your site.

#### 2.5.1

 * With Yoast SEO or SEOPress, the multilingual sitemap also lists an empty category
   that has posts in a category below it, as those plugins’ own sitemaps do. Checked
   against Yoast SEO 28.8’s real sitemap.

#### 2.5.0

 * The multilingual sitemap now lists your category and tag pages in every language,
   in files of their own (/langferry-sitemap-es-taxonomies-1.xml), so search engines
   find their translations. It lists the ones your SEO plugin’s sitemap lists (Yoast
   SEO, Rank Math, All in One SEO or SEOPress), or, without one, the ones WordPress’s
   own sitemap would. Empty categories aren’t listed.
 * Fixed: with All in One SEO set to noindex the whole site, posts of a type with
   no search-appearance setting of its own were still listed.
 * New filters: langferry_sitemap_taxonomies and langferry_sitemap_excluded_term_ids.

#### 2.4.2

 * The multilingual sitemap now leaves out what your SEO plugin leaves out of its
   own sitemap: post types it doesn’t list (such as Elementor’s templates), pages
   set to noindex, pages whose canonical points elsewhere, and its list of excluded
   posts. Works with Yoast SEO, Rank Math, All in One SEO and SEOPress; without 
   one, it follows WordPress’s own sitemap rules.
 * Fixed: with every post type left out, the sitemap listed blog posts.
 * New filters: langferry_sitemap_excluded_post_ids and langferry_sitemap_page_size.

#### 2.4.1

 * The flag choices under Language switcher  Flags show each country’s flag beside
   its name, so you can see which flag you’re choosing before you save.

#### 2.4.0

 * Choose which country’s flag a language shows in the switcher: the USA’s or Canada’s
   for English, Quebec’s for French, Brazil’s for Portuguese, and Mexico’s, Argentina’s
   or Colombia’s for Spanish. Set it under Language switcher  Flags, here or in 
   your Langferry dashboard; the two stay in sync. Only the picture changes.

#### 2.3.0

 * Reorder languages on the settings page: drag the numbered chips above the language
   grid, or focus one and use the arrow keys. This is the order in the language 
   switcher, and it syncs with your Langferry dashboard.
 * Fix: a floating switcher set to “Flags with codes” (or another flags, names or
   codes style) showed flags with names. It still opens as a menu, but now shows
   the flags and labels of the style you chose.
 * Fix: some themes, such as Hello Elementor, put the switcher’s flag on its own
   line above the language name and gave the switcher their own button and link 
   colours. The switcher now keeps its layout and the light, dark or auto look you
   chose.

#### 2.2.2

 * Fix: saving the Langferry settings page in WordPress put your languages back 
   in alphabetical order, undoing the order you dragged them into in your Langferry
   dashboard. Languages you’d already chosen now keep their place, and newly ticked
   ones go last.
 * Fix: on PHP 8.5, sites with WP_DEBUG on showed “SplObjectStorage::contains() 
   is deprecated” notices on every translated page. Langferry now uses the methods
   PHP recommends instead, which work the same on every supported PHP version (7.4
   and later).
 * The settings page now says where to change the language order, with a link to
   your dashboard.

#### 2.2.1

 * Fix: with “Custom domain per language”, a language whose domain was left empty
   took over the site’s own address, so every visitor saw that language and the 
   switcher couldn’t go back. It’s now served at its code in front of your address(
   es.example.com), as the settings page says, and the site’s own address always
   shows the original language.
 * A language given the site’s own address as its domain is treated as having none.

#### 2.2.0

 * Personal data stays out of shared storage: text from order emails, pages shown
   to signed-in customers, and the cart, checkout and account pages is translated
   without being kept in Langferry Cloud’s shared cache, and this site keeps it 
   for 30 days after last use (filter: langferry_private_text_days). It never appears
   in the translation editor.
 * New filter langferry_private_text marks more pages as private.

#### 2.1.0

 * Bots, crawlers, search results and 404 pages no longer use up the translation
   allowance: they get cached translations only.
 * Every plugin feature now works on every plan, Free included: indexing, hreflang,
   sitemaps, the translation editor and custom domains. Plans differ in what Langferry
   Cloud translates.
 * The Connect reminder shows only on the Dashboard and Plugins screens and can 
   be dismissed.
 * Suggested privacy-policy text under Settings  Privacy.

#### 2.0.0

 * Complete rewrite: server-side translation engine with translation memory, multilingual
   SEO, translation editor, cloud dashboard connection, WooCommerce e-mails, WP-
   CLI.

## Meta

 *  Version **2.8.1**
 *  Last updated **2 days ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.2 or higher **
 *  Tested up to **7.1.5**
 *  PHP version ** 7.4 or higher **
 * Tags
 * [hreflang](https://wordpress.org/plugins/tags/hreflang/)[multilingual](https://wordpress.org/plugins/tags/multilingual/)
   [translate](https://wordpress.org/plugins/tags/translate/)[translation](https://wordpress.org/plugins/tags/translation/)
   [woocommerce](https://wordpress.org/plugins/tags/woocommerce/)
 *  [Advanced View](https://wordpress.org/plugins/langferry/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/langferry/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/langferry/reviews/)

## Contributors

 *   [ Langferry ](https://profiles.wordpress.org/langferry/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/langferry/)