Translate any page in one click
Clone content, ACF fields, featured image, template and page attributes into the other language — or link two pages that already exist. Unlink any time; nothing gets deleted.
For WordPress developers & agencies
Two languages.
Nothing else.
Duolangue runs a bilingual WordPress site — no custom database tables, no settings maze, no translation marketplace bolted onto your checkout. Pick two languages. That's the whole plugin.
No custom SQL tables Works with any language pair Automatic hreflang
Everything a two-language site needs. Nothing it doesn't.
A hard cap at two languages is the feature, not a limitation — it's why setup takes minutes instead of an afternoon.
URLs and slugs, per language
Translate the URL base per post type and taxonomy — /blog/ becomes /blogue/. The same slug is allowed in both languages — that's no longer treated as a conflict.
Menus that speak both languages
Drop a language-switcher item anywhere in a menu, or link two whole translated menus together. Without a linked menu, items swap to their translated equivalents automatically at render time.
Categories and tags, translated
A dedicated screen links each term to its translation, name and slug included — and every native admin list is filtered by language, with EN/FR tabs and per-language counts.
Real screens, not mockups
Duolangue lives inside the native WordPress admin — familiar list tables, familiar metaboxes, one focused settings screen.
Not another multilingual suite
WPML and Polylang are built to support any number of languages. Duolangue is built for the far more common case: exactly two.
| Capability | Duolangue | WPML | Polylang |
|---|---|---|---|
| Languages supported | Exactly 2 | Unlimited | Unlimited |
| Custom database tables | None | Yes | Some |
| Typical setup time | Minutes | Hours | ~1 hour |
| Machine translation | Not included — by design | Paid add-on | Via add-ons |
| Same slug in both languages | Allowed | Conflict | Conflict |
Priced like a plugin, not a platform
One-time-feeling, billed annually. Includes updates and support.
Single Site
CA$49.99/year
For one client site.
- 1 site license
- Two languages, any pair
- Updates & support, 1 year
MOST COMMON
Agency — 5 Sites
CA$89.99/year
For agencies with a handful of client sites.
- Up to 5 site licenses
- Two languages, any pair
- Updates & support, 1 year
Agency — Unlimited
CA$149.99/year
For agencies running Duolangue everywhere.
- Unlimited site licenses
- Two languages, any pair
- Updates & support, 1 year
Frequently asked questions
Straight answers — the same ones the plugin's design is built on.
Can I add a third language later?
No. Duolangue is deliberately capped at two languages — that hard limit is why setup takes minutes, why there are no custom database tables, and why nothing ever conflicts with your theme or builder. If you expect to need three or more languages, a full multilingual suite is the right tool.
Does it work with any pair of languages?
Yes. English–French, Spanish–German, any pair. Language codes, names and WordPress locales are fully configurable, and the plugin's routing, hreflang, menus and admin screens all follow whatever pair you choose.
What exactly gets copied when I translate a page?
One click clones the blocks and content, custom fields (including ACF), the featured image, the template and page attributes, then links the two pages. You can also link two pages that already exist without copying anything, and unlink any pair at any time — nothing is ever deleted.
Where is the data stored? What happens if I uninstall?
Everything lives in standard WordPress post meta, term meta and one option — no custom SQL tables. Uninstalling preserves language assignments and translation links by default, so reinstalling restores every page to its language instantly. A wp-config constant is available if you want a full wipe instead.
Does Duolangue do machine translation?
No, by design. Duolangue manages the structure of a bilingual site — languages, links, URLs, menus, terms — and leaves the words to you or your translator. There is no translation marketplace bolted onto your checkout.
Is it compatible with Oxygen, ACF and custom post types?
Yes. Duolangue was built inside a WordPress agency that runs Oxygen Builder and ACF Pro across client sites. Every public post type and taxonomy gets language columns, tabs and translated URL bases, and page builders that register no menu locations are covered by an all-menus option.
Ship the bilingual site your client actually has.
No third language to plan for, no import wizard, no table migrations to worry about at 2am. Install it, pick two languages, start linking pages.
View pricing