How to Make a Website Multilingual Without a Translator

No translators, no plugins. Use AI to localize your website into many languages and get every language version correctly indexed by Google. This is the exact method morganvault.com uses to run 23 languages — one translation dictionary, one static HTML page per language, and hreflang.

Six steps

1. 1. Choose languages and URL structurePick your target languages and give each its own URL path, e.g. /en/, /ja/, /es/. Subdirectories are the simplest structure for Google to crawl and index per language.
2. 2. Put all text in one translation dictionaryMove every piece of UI text into one place keyed by a short id (a JSON or JS object), one set per language. This becomes the single source of truth for every translation.
3. 3. Translate with AI, not an agencyAsk Claude to translate the dictionary into each target language. Re-check tone on your highest-traffic pages (home, pricing, FAQ); have a native speaker proof them before launch if budget allows. Far cheaper and faster than hiring translators for every language up front.
4. 4. Generate one static HTML page per languageFor SEO, render a real static HTML page for each language so crawlers see fully localized content, not a blank page waiting on JavaScript. A small script can stamp the dictionary into a template, one page per language.
5. 5. Add hreflang and canonicalOn every page add hreflang link tags pointing to each language version plus a self-referencing canonical. This tells Google which language to serve to which user and avoids duplicate-content confusion.
6. 6. Add a language switcherGive visitors a visible menu to switch languages and remember their choice. Don't auto-redirect by browser language: Google advises against redirecting users based on a guessed language, because it can stop people and Googlebot from reaching other versions. Suggest the matching version with a dismissible banner instead.

Google's five official rules for multilingual sites

Google publishes its own rules for multilingual sites in Search Central. These five decide whether your language versions get indexed correctly — each one comes from Google's documentation, not SEO folklore.

• One URL per language: Google recommends a dedicated URL for each language version rather than switching language on one URL with cookies or browser settings.
• No auto-redirect by guessed language: Google advises against redirecting visitors based on what you think their language is. Link to the other versions instead.
• hreflang must point both ways: if page A lists page B as an alternate, page B must list page A back, or the annotations can be ignored. Use ISO 639-1 language codes, optionally with an ISO 3166-1 region (e.g. en-GB).
• Google reads the visible text to decide a page's language: it doesn't use code-level signals such as the lang attribute, so the body must really be translated, not just re-tagged.
• AI translation isn't banned: Google's March 2024 spam-policy update targets pages mass-produced mainly to manipulate rankings, no matter how they're created. Reviewed, useful translations are fine; thousands of unreviewed auto-pages are the risk.

Sources: Google Search Central — Managing multi-regional and multilingual sites · Google Search Central — Tell Google about localized versions of your page · Google Search Central Blog — March 2024 core update and new spam policies

Why trust this method? This site is the proof

The site you are reading runs 23 languages, all generated from a single translation dictionary, one static HTML page per language, with full hreflang — no translators hired, no multilingual plugin. The engine itself is not much code; the real cost is translation review and keeping content in sync, not engineering. This is exactly what Chapter 4 of the Morgan Vault e-book walks you through.

Frequently asked questions