How a multi-language website is solved, case by case
Four recurring scenarios: a store, an agency, a blog and a corporate website. For each one, the starting situation, how it's set up with WP-Translate and what remains working at the end.
From a website in one language to a website that sells in four
It's not translating texts: it's publishing an indexable version per language, with its URL, its menu and its content maintained over time. That's what changes in the four scenarios on this page.
A WooCommerce store that sells outside of Spain
The starting point. Catalog of several hundred products, with product sheets, categories, cart texts, and order emails. Translating that manually is a weeks-long project, and each new product restarts the problem.
How it's set up
Four languages are activated and the batch translation of the entire catalog is launched.
WooCommerce texts —cart, checkout, emails— are included in the same batch.
The translation memory resolves repeated phrases in hundreds of product sheets for free.
The language selector is placed in the store header.
What remains working. The store is published in four languages, each with its indexable URL, and new products are translated from the product sheet itself without
An agency that delivers multilingual websites to its clients
The starting point. Each new project requires choosing a translation plugin, setting it up and explaining it to the client. Annual licenses accumulate and must be renewed one by one each year.
How it's set up
A single license with multiple sites covers the entire project portfolio.
Test and staging environments do not consume activations.
The visual editor allows the client to correct their text without touching the dashboard.
Translations are exported from one project and imported into the next.
What remains working. Multi-language setup stops being a budget item and becomes something that is resolved in an afternoon, with a cost that is not repeated every year.
A blog that wants to multiply its organic reach
The starting point. Hundreds of articles positioned in a single language. Each manual translation costs money and time, and the old archive never gets translated.
How it's set up
Batch translation of the complete archive, starting with the articles with the most traffic.
hreflang and sitemap by language so Google indexes each version separately.
Yoast metadata (title and description) is also translated.
New articles are translated upon publication, in one click.
What remains working. The same content archive now competes in several search markets, without rewriting anything and without changing the publication flow.
A B2B company with a corporate website in Elementor
The starting point. Twenty-page website built with Elementor, with legal texts and forms. The marketing team doesn't want to depend on anyone to change a phrase.
How it's set up
Translation of all pages, including sections built with Elementor Pro.
Glossary with brand terms and product names, which are never translated.
Human review: AI proposes, the marketing manager approves.
Role-based permissions to separate who translates and who publishes.
What remains working. The website speaks the language of each market and the internal team maintains it without calling the agency for every text change.
Here you won't find invented testimonials
WP-Translate has just gone on sale. Instead of filling this page with stock photo faces and percentages that no one can verify, we publish what the plugin does in each scenario. Cases with names and surnames will arrive when clients give permission to tell them.
Your website can be in four languages this week
One-time payment, lifetime license and all updates included.