TranslatePress vs the rest: why it is the best choice in 2026
Making a WordPress site bilingual without breaking its layout: how visual translation works, what it costs, and what to know before translating a Quebec site.
In Quebec, the bilingual-site question always comes up eventually. On WordPress, several plugins do the job, with very different approaches — and very different bills.
The problem with the classic approaches
Most multilingual plugins duplicate every page: a French version and an English version, managed separately in the admin. That works, but it means two page trees to maintain, and translation done blind, in a text field, without seeing the result.
The usual consequence: a button whose English text is 30% longer overflows its frame, and nobody notices before a client does.
TranslatePress's approach
The plugin shows your site as it is and lets you click any text to translate it, in place. You see the result immediately: the length of the button, the height of the block, the title that now wraps onto two lines.
What follows from that approach:
- everything is translatable: the content, but also the menus, the forms, the text baked into the theme and the plugins — exactly where other solutions leave gaps
- the layout is preserved, since you work inside it
- no technical knowledge is needed by whoever does the translating
What to watch on the search side
A badly configured bilingual site gets penalized for duplicate content. Three things to check, whichever plugin you use:
Distinct addresses. `/en/services` for English, `/services` for French. Not one link that switches language based on a cookie — Google will never see the English version.
Hreflang tags. They tell Google that two pages are two versions of the same content, not copies. TranslatePress adds them automatically.
Translated metadata. Title and description for every page, in both languages. That is what appears in search results.
Machine translation: yes, but
The plugin can connect a machine translation service and process the whole site at once. It is tempting, and it is a good starting point — provided you proofread.
Machine translation shipped as-is produces nonsense on the terms of your trade, and a tone that rings false. For a Quebec site, it also ignores local usage.
The sensible method: machine translation to rough it out, human proofreading of the pages that matter — home, services, contact, pricing. Blog articles can wait.
The real cost
The free version translates into one language. For a French site adding English, that is enough in many cases.
The paid version unlocks additional languages, translator accounts, advanced multilingual SEO and built-in machine translation. Budget an annual subscription.
Weigh that against the alternative: two separate sites to maintain, or an agency billing every change twice.
Before translating anything
Ask the real question: how many of your customers search in English? If the answer is "almost none", a bilingual site adds maintenance for nothing. If you are targeting Montreal, Ontario or export markets, it is the opposite — and better to do it properly from the start.