How to translate a new WordPress site before it goes live
Add a language, keep it offline while you translate it, publish it when it is finished. Nobody sees a half-translated page, Google never indexes one, and you work at the pace real life allows. Five steps, plus the trap that catches everyone six months later.
1.1.0 — publish a language when it is ready, and one SEO panel with everything in it
A language can now be added and kept offline while you translate it: it stays out of the language switcher, out of your sitemap and out of the hreflang tags, and its URLs send visitors to your default language — while you keep working on the real pages. Nothing half-translated ever reaches your visitors or Google.
The SEO panel in the visual editor now holds everything search engines read, in one order: the address, the title and description, the social preview, the keywords, then every image on the page and every translatable attribute — titles, placeholders, ARIA labels. Each line takes you to that element on the page and opens the right editor.
This release also fixes a real gap: when a SEO plugin set its own og:title or Twitter card, that text was never collected, so every share of a translated page went out in the source language. It is collected and translated now.
Translate WordPress with Chrome’s built-in translator — no API key
Chrome and Edge carry a translator that runs on your own computer, for free. Here is the whole process step by step, with the numbers from a run we timed: 464 strings in 42 seconds, nothing sent anywhere.
Human vs AI vs Google Translate: Which Way Should You Translate Your Website?
Professional human, AI (DeepL/GPT/Gemini), or free Google Translate? An evidence-led guide to choosing the right way to translate your website — and why a hybrid usually wins.
Hreflang Explained Simply: Multilingual SEO Without the Headache
What hreflang is, why it matters for multilingual SEO, a simple tag example, the common mistakes to avoid, and how to generate it automatically in WordPress.
How to Make a WordPress Site Multilingual — Free, Step by Step (2026)
Make your WordPress site multilingual for free, step by step: install the plugin, pick languages, translate by hand, Google, or AI, preview, and go live with SEO-ready URLs.
Why a multilingual website matters — the data, for hotels & B&Bs
76% of shoppers prefer buying in their own language and 40% won’t buy otherwise (CSA Research). We pulled together the real numbers — EU language preferences, Italy’s inbound tourism, the SEO opening — and what they mean for accommodation businesses.
TranslateRocket 0.7.9 — Preview mode: check everything before the world sees it
Migrating from another translation plugin — or reviewing a big batch of machine translations — used to involve a leap of faith: the moment your new translations were active, visitors saw them, polished or not. Version 0.7.9 removes that leap.
Turn on Preview mode (“Who sees the translations” in Settings) and the translated site becomes visible to administrators only. You browse every language on the real rendered pages and fix anything with the visual editor; meanwhile visitors keep seeing the default language — language URLs quietly redirect, the switcher is hidden and no hreflang or sitemap signals go out to search engines. Happy with the result? Flip visibility back to “Everyone” and you are live, instantly.
It pairs perfectly with the one-click importers: bring your translations over from TranslatePress, Polylang or WPML, check them at your own pace, then publish.
TranslateRocket 0.6 — built for the biggest sites
Most translation plugins load every translation you have on every page view — fine at 2,000 strings, a white screen at 200,000, where big WooCommerce shops live. We rebuilt the engine to look up only the strings on the page being viewed, through an indexed cache.
In a July 2026 load test on a single WordPress install with 500,000 stored strings, the old whole-map approach exhausted the 256 MB PHP memory limit and never rendered. TranslateRocket served the same page, byte-for-byte, in 1.5 seconds. Memory stays flat whether your site has 500 strings or 500,000 — no setup, the engine switches modes by itself.
This site translated itself into 21 languages — in one afternoon
We put our money where our mouth is: every word of this website was translated into 21 languages with TranslateRocket itself, mostly with DeepL through the new provider fallback chain. Give two or more AI providers a priority and a big job simply keeps going when one runs out of credit — the next one takes over automatically.
Along the way the built-in translation memory copied 792 repeated strings for free, so we never paid to translate the same phrase twice. Switch language at the top of any page and read this site in yours.
Free — and we mean it
No paid tier inside the plugin. No cap on strings, languages or traffic. Bring your own AI key and you pay the provider directly — we take nothing per word. The core is GPL and open source; professional setup and priority support are how we keep the lights on.
