How to Launch in Another Language: Translating the Page, URLs and Where to Post
Launch in another language by translating the whole page, not only the menus, giving each language its own URL, and linking the versions to each other with hreflang so search engines can match readers to the right one. Add a language only when you can support it with answers, emails and wording for prices. Google’s multilingual guidance recommends separate URLs over cookies or browser settings and warns against redirecting visitors by guessed language.
Should you translate the launch yet?
Answer three questions first. Can you reply to support messages in that language? Is there evidence that people who speak it have the problem, such as someone who asked, visitors from that country in your analytics, or a community in that language where the problem is discussed? Does the product itself work there, with the right currency, date format, names and rules? Two yeses and a no usually mean wait.
Google separates two ideas that people blur. A multilingual site offers content in more than one language, such as English and French. A multi-regional site targets users in different countries, such as one version for Canada and another for the United States. Your launch is probably multilingual first; the country question, with its prices and laws, comes second.
| Situation | Do now | Wait |
|---|---|---|
| You speak the language and know its users, for example a German-speaking freelancer building InvoiceNest for other freelancers | Launch in that language first, and add English later if you want | Nothing |
| You only have a machine translation and no reader to check it | Keep the product in your own language and find a native reader | Public translated pages |
| People from one country already use the product and ask for their language | Translate that one language, fully | Five other languages at once |
| You want the language only for search traffic | Check whether the language’s users have the problem and whether you can support them | The whole project until you know |
What does Google say about structuring language versions?
We read Google Search Central’s pages on managing multi-regional and multilingual sites and on localized versions on 13 November 2026; the first was last updated on 10 December 2025. Check them again before you build, since search guidance changes.
- Separate URLs per language. Google recommends a different URL for each language version rather than using cookies or browser settings to switch the content on one URL.
- hreflang annotations. Each language version must list itself and all the other versions, with fully qualified URLs. If two pages do not point to each other, the tags are ignored.
- A fallback. Consider an
x-defaultpage for visitors whose language you do not cover. - Visible content decides the language. Google says it uses the visible content, not the
langattribute or the URL, so keep one language per page and avoid side-by-side translations. - Translate the substance, not the template. Translating only the navigation while the main content stays in one language can create a poor experience, and localized versions count as duplicates only when the main content remains untranslated.
- No automatic redirects by guessed language. Do not redirect people from one language version to another based on what you think their language is. Let them switch with ordinary links, and do not adapt content by IP address.
You can declare the versions in the page’s HTML, in an HTTP header or in your sitemap. Google says the three methods are equivalent, so pick the one that is easiest for you to keep right and use only that one.
Which URL structure suits a small product?
| Option | Example | What Google lists in its favour | What it lists against |
|---|---|---|---|
| Country-code domain | example.de | Clear geotargeting, easy separation | Can be expensive or restricted; targets one country only |
| Subdomain | de.example.com | Easy to set up, easy separation | Users may not read “de” as a language or a country |
| Subdirectory | example.com/de/ | Easy to set up, low maintenance | Separation of the sites is harder |
| URL parameter | example.com?loc=de | None listed | Not recommended |
For a first extra language on a small product, a subdirectory is the least work, going by those listed trade-offs. That is our reading of Google’s table, not a ranking claim. A snippet of what the German page in the example would carry in its head:
<link rel="alternate" hreflang="en" href="https://example.com/" /> <link rel="alternate" hreflang="de" href="https://example.com/de/" /> <link rel="alternate" hreflang="x-default" href="https://example.com/" />
What does “translated” have to include?
Everything a visitor sees on the path to the core task. Text in screenshots is the one people forget: an English interface in a German page is a half-translation. Add prices and currency, date and number formats, error messages, the sign-up and onboarding emails, and the pages for pricing, contact and terms. Rules can differ by country even when the language is the same, so a translated invoice template may still not suit the reader’s country; check local requirements before you promise it.
Have a native reader check the result. Machine output is a fine first draft, and a quick review catches the odd phrase that makes a product look careless. Google’s spam policy lists translating scraped content to produce many low-value pages as scaled content abuse. Translating your own page for people who read that language is a different thing; our reading is that the reviewed, useful version is the safe one.
Where do you announce a product in another language?
Go to the communities where people in that language already discuss the problem, and find them by searching for the problem in their words, not yours. Read each community’s rules, and have someone fluent read your post before it goes out. How to reuse your launch content explains which parts of a launch stay fixed and which change for each audience, and the same split applies to a translation: facts stay, the opening and the ask adapt. This board is in English. We have not tested listings in other languages, so write the listing in English and link to your translated page from your own site. Launch your product for free in English, then point readers of the other language to the version made for them.
Most big launch sites are English-first, but we have not read each one’s language rules, so check before you submit. The free launch directories tool is a starting list, and where to launch a side project puts the main places in an order.
How do you measure a second-language launch?
Keep the numbers apart from the start. Put each language under its own path, such as /de/, so your analytics can split visits and completions by path, and give each community post its own tagged link. How to measure a launch explains the tags. Compare how many visitors finished the core task in each language with the same count for your first language, and watch the questions that arrive in the new language. Search traffic from a new language page is slow to build and nobody can predict it, so judge the first weeks by people who tried the product, not by rankings. The ideas board shows what people are building and, by implication, who might need it in their own language.
Frequently asked questions
Do I need hreflang to launch in a second language?
Not to launch, but Google recommends it when you have several language versions of a page. Each version lists itself and all the others, and the tags are ignored unless the pages point to each other. Without it, Google may still find the versions, but it is usually best to say so explicitly.
Is it better to use a subdirectory or a separate domain for another language?
For a small product, a subdirectory such as example.com/de/ is easy to set up and low maintenance, according to Google’s table of options. A country-code domain gives clear geotargeting but can be costly and targets one country. Whichever you choose, give each language its own URL and link the versions.
Can I translate my launch with machine translation?
Use it for a first draft, then have a native reader fix the result before you publish. Google says to translate the substance of the page and keep one language per page. Unreviewed output can make a product look careless, and Google’s spam policy names scraping content and translating it into many low-value pages as an example of scaled content abuse.
Should I redirect visitors to their language automatically?
No. Google advises against automatically redirecting people between language versions based on a guess, because it can stop both visitors and search engines from seeing all versions. Offer a visible language switch with ordinary links instead, and use hreflang to tell search engines which version suits which reader.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.