Adding a second (or fifth) language to a WordPress site used to mean a paid plugin, a per-word translation bill, or a plan that caps your word count. It doesn’t anymore. With a free plugin from the official WordPress.org directory, you can add unlimited languages, translate however suits you — by hand, with free Google Translate, or with your own AI key — and publish each language on its own clean, search-friendly URL.
This guide is written to be done, not just read. Follow the numbered steps below and you’ll have a working multilingual site by the end of the afternoon. We’ll use TranslateRocket as the walkthrough plugin because it’s free and covers every step here, but the workflow — install, pick languages, choose a method, preview, go live — is the same idea whichever tool you land on.
Step 1 — Install the plugin from your dashboard (2 minutes)
You don’t need to download anything by hand. Everything in the WordPress.org directory installs straight from your admin area:
- Log in to your WordPress dashboard and go to Plugins → Add New.
- Type your translation plugin’s name into the search box (for this guide, TranslateRocket).
- Click Install Now, then Activate.
That’s the whole install. These are the same steps WordPress documents for any plugin in the official Manage Plugins guide, and everything in the directory is free to install. Once activated, a new menu appears in your sidebar where the rest of the setup happens.
Step 2 — Pick your languages
Open the plugin’s settings and set two things: your source language (the language your site is written in today) and one or more target languages you want to add. Add as many as you like — there’s no per-language fee or word cap to worry about.
A practical tip: start with just one target language for your first pass. It’s the fastest way to see the whole flow end to end — translate, preview, publish — before you scale up to the rest. You can always add more languages later; nothing you translate is lost when you do.
Step 3 — Choose how to translate: by hand, free Google, or your own AI key
This is the step that decides your cost and your quality. You have three routes, and you can mix them freely:
- By hand — you (or a bilingual colleague) type the translations in a side-by-side editor. Zero cost, and the best quality for a handful of high-value pages like your homepage, pricing, and contact page.
- Free Google Translate — machine-translate the whole site in one pass at no cost. Ideal for getting a full site live quickly, or for long-tail pages where perfect wording matters less.
- Your own AI key — plug in an API key from a provider you already use to get higher-quality automatic translations. You pay that provider directly at their rates, with no markup added by the plugin.
The smart pattern most site owners use: machine-translate everything first so the site is fully live, then hand-polish the few pages that carry the most weight. A machine draft you refine is faster than a blank page, but always review anything customer-facing — automatic translation is a strong starting point, not a finished one.
Step 4 — Review privately with Preview mode before anyone sees it
Don’t publish a half-translated site to the public. A good multilingual plugin lets you keep the new languages visible to you as an admin while guests still see only your original language. In TranslateRocket this is called Preview mode: while it’s on, logged-in admins can browse and check every translated page, but visitors are quietly kept on the original site — the language switcher and the alternate-language tags stay hidden until you’re ready.
Use this window to click through your key pages in each new language, fix any awkward machine wording, and confirm nothing broke in your layout. When it reads well, you flip the switch — and only then does the multilingual version become public.
Step 5 — Go live
Turn Preview mode off. Your language switcher appears on the site, each translated page becomes publicly reachable at its own URL, and visitors can move between languages themselves. That’s the whole launch — no rebuild, no separate install per language, no re-doing your theme.
Note that Google specifically advises against automatically redirecting visitors to a language based on their browser or location, because it can trap both users and search crawlers on one version. Letting people choose with a visible switcher — which is exactly how this works — is the recommended approach.
What about SEO? (hreflang and translated slugs, handled for you)
This is where a proper multilingual plugin earns its keep, and it’s mostly automatic. Two things matter for search:
- Separate URLs per language. Google recommends a different URL for each language version of a page — typically a subdirectory like
yoursite.com/fr/— rather than swapping content on the same URL. That’s exactly what you get: each translation lives at its own address, and the slug itself gets translated too (your/about/page becomes/fr/a-propos/), which reads better and helps ranking. - hreflang tags. These are hidden tags that tell Google a page is the French (or German, or Spanish) version of another page, so it serves the right language to the right searcher. Google explains their role in its localized-versions documentation. The plugin generates them for you on every page — you don’t touch any code.
Between translated slugs, correct hreflang, and a multilingual sitemap, each language version can be found and ranked on its own. You get the SEO benefit of a properly internationalized site without hand-editing a single tag.
Frequently asked questions
- Is it really free? Yes. The plugin installs free from WordPress.org, and translating by hand or via free Google Translate costs nothing. The only optional cost is if you choose to bring your own AI key — and you pay that provider directly, at their rate.
- How many languages can I add? As many as you want. There’s no per-language fee and no word-count cap to plan around.
- Will this slow my site down? Translations are stored and served as normal pages, so visitors load a static translated page rather than translating on the fly. Keep your usual caching in place and speed stays comparable to your original site.
- Do I have to translate everything at once? No. Machine-translate the whole site to get live fast, then hand-polish your most important pages over time. You can also add a new language months later without redoing existing work.
- I already use WPML, TranslatePress, Polylang or Weglot — do I start over? No. TranslateRocket can import existing translations from WPML, TranslatePress, Polylang and Weglot, so you keep the work you’ve already paid for or done by hand.
- Can I check it before the public does? Yes — that’s what Preview mode in Step 4 is for. Review every language privately as an admin, then go live when it’s ready.
Ready to do it? Install the free plugin from WordPress.org and work through the five steps above.
Sources
- WordPress.org — Manage Plugins documentation — wordpress.org
- Google Search Central — Managing Multi-Regional and Multilingual Sites — developers.google.com
- Google Search Central — Localized Versions of your Pages — developers.google.com
- WordPress.org — TranslateRocket plugin page — wordpress.org
Make your site multilingual — free
