Short answer
To build a multilingual website, first choose the URL structure (subfolder, subdomain or country domain), give each language its own address and keep one language per page. Do not redirect visitors by guessing their language; add a visible language switcher. Translate forms, emails, error pages and metadata too.
Picture this: you have published the English version of a Turkish site. The home page, the services and the about page are ready. A week later one visitor writes, “I filled in the form in English and the confirmation email came in Turkish”; another keeps being thrown back to the Turkish page even though they chose English in the menu. The hard part of how to build a multilingual website is not the translation itself; it is making these small decisions at the start. This article lists them in order.
We covered the tag side, meaning how the hreflang lines are written, in a separate piece: what is hreflang and how to use it on a multilingual site. Here we look at the build decisions. The examples use Turkish and English and example.com.
Step 1: choose the URL structure
Google’s documentation on multi-regional and multilingual sites compares the URL structures that make it easy to target a site at different regions, with pros and cons. The table below summarises that comparison; for the parameter URL the document says “not recommended”.
| Structure | Example | Pros the document lists | Cons the document lists |
|---|---|---|---|
| Country domain | example.de |
Clear geotargeting, server location irrelevant, easy separation of sites | Expensive (availability can be limited), needs more infrastructure, sometimes strict requirements, targets a single country |
| Subdomain | de.example.com |
Easy to set up, different server locations possible, easy separation of sites | Users may not recognise the targeting from the URL alone (is “de” the language or the country?) |
| Subfolder | example.com/de/ |
Easy to set up, low maintenance (same host) | Users may not recognise the targeting from the URL alone, single server location, separation of sites is harder |
| URL parameter | example.com?loc=de |
None | Not recommended, segmentation by URL is difficult, users may not recognise the targeting from the URL alone |
The decision depends first on one question: do you offer the same content in different languages, or do you run a separate team and server for each country? In the first case we suggest a subfolder: one domain, one round of maintenance. In the second, a country domain or a subdomain makes more sense. That is our reading; the document does not declare any structure “right”.
One more thing: “en” or “de” in the address does not decide the target audience on its own. According to the Google document, the signals for the target audience include the country domain, hreflang, server location and things such as local addresses and phone numbers, language and currency. Using Turkish words or an internationalised domain name in the address is allowed, as long as you use UTF-8.
When choosing the platform, also check whether it can manage multilingual content from one panel; the article on choosing a content management system helps with that.
Step 2: give each language version its own address, and keep one language per page
Google recommends giving each language version its own URL rather than changing the page language with cookies or browser settings. It also writes that if you change content dynamically or redirect users, Google might not find and crawl all the variations. The reason it gives is that Googlebot usually comes from the USA and sends its requests without an Accept-Language header.
The same document says Google determines a page’s language from its visible content. So keep content and navigation in one language and do not use side-by-side translations. Translating only boilerplate text such as the menu and footer and leaving the bulk of the content in one language can also create a bad experience. The same content can then appear several times in search results with different boilerplate languages.
We suggest putting the language folder at the start of the address: example.com/tr/hizmetler/ and example.com/en/services/. If the end of the address will differ by language, keep the page pairs in a table; we come back to that table in Step 6.
Step 3: do not redirect, add a language switcher
Google recommends that you avoid automatically redirecting users from one language version to another; for example, do not redirect based on what you think the user’s language is. Such redirects can stop users and search engines from seeing all the versions. Its advice is to link to the other language versions. It also says not to adapt content by IP analysis: location analysis is difficult and generally not reliable.
The W3C page takes a different view here. It finds it usually helpful for the server to read the browser’s language preference and guide the visitor to the page in that language, and recommends doing so. It is wary of guessing the language from the IP address. Alongside that, it says it is “always best” to add links to the other language versions on every page. Its reasons include the visitor using someone else’s computer or preferring to read the original. So Google and W3C part ways on automatic guidance by browser language and agree on language links. We suggest not setting up a redirect at all and leaving the choice to the visitor.
These points from the W3C page help when you build the switcher:
- Put it on every page. A visitor can arrive in the middle of the site. W3C wants the links to be easy to find; the top bar is a good place for them.
- Write each language’s name in that language. “Türkçe” and “English”; a visitor on a page they cannot read should still find their own language.
- Do not use flags. W3C says flags are not appropriate for pages that are simply translations, because a country can have more than one language and a language can be spoken in more than one country.
- Offer to remember the choice. W3C says to give visitors the opportunity to remember their choice when they switch.
- Keep the links in one place. On its own pages W3C generates the language links automatically and stores the data in one external file, which makes adding or removing a language easier.
Our addition: let the switcher go to the equivalent of the current page, not to the home page. If there is no equivalent, grey that language out or hide it.
Step 4: decide how the translation is done
Google’s spam policies have no separate heading for machine translation; the closest section is “scaled content abuse”. According to the policy, using generative AI tools to produce many pages without adding value for users is among its examples. So is producing many pages from scraped content through automated transformations such as translating, where little value is provided to users.
We found no separate line on translating your own content. Our suggestion is the practical conclusion we draw from this policy. Treat machine translation as a draft, have someone who knows the language read every page, and do not translate the whole site in bulk and publish it in one go. Start with the pages where visitors decide, the home, service and contact pages; the blog archive can come later.
A small glossary speeds the work up and keeps terms consistent; that is our suggestion. Fix the brand name, product names and frequent terms there.
Step 5: translate the parts people forget
Once the page text is translated, the job looks finished. The things that leave visitors stranded are usually outside the page. The table below lists these parts; the “What to do” column is our suggestion except where the text cites a source.
| Part | Why it is forgotten | What to do |
|---|---|---|
| Form labels and error messages | They live in code, not visible in the panel | Move labels, placeholders, validation and thank-you messages into a language file; serve pages in UTF-8 |
| Automatic emails | They sit in another tool | Send confirmation, order and password emails in the language of the form |
| Error pages (404, 500) | Nobody tests them | Write a separate 404 page for each language and link it to that language’s home page |
| Metadata | It is not in the page view | Translate the title, description, image alt text and share title |
lang attribute |
One value stays in the template | Each language version should carry the right value, such as <html lang="en"> |
| Button and menu text | It comes from the design | Leave room for the translation to be longer |
A few details. W3C’s multilingual form encoding page recommends serving all pages in UTF-8 for forms; browsers send form data back in the page’s encoding, so the user can type in any language and script. For button and label space, W3C’s text size in translation page passes on the average expected expansion rates published by IBM. For translation from English into European languages, the rate for texts of up to 10 characters is 200 to 300%; the shorter the source text, the greater the expansion. Avoid small fixed-width containers, buttons and tabs.
W3C also says to always declare the lang attribute on the html tag. Google writes that it determines a page’s language from the visible content. Our reading: write the attribute correctly, but what really sets the language is the translation on the page. For the forms themselves, use the checklist in how to design a contact form; for error pages, see 301 redirects and 404 errors.
Step 6: set up a workflow that keeps versions in step
The real cost of a multilingual site is not the build but the months after: the Turkish page is updated and the English one stays old. This section is our suggestion, not a rule from Google or W3C documentation.
- Pick one source language. Changes are made there first.
- Keep every page pair in a table. Columns: Turkish address, English address, date of last translation, status (current, waiting, no translation).
- Open a translation note when the source page changes. Note the changed sentence; the whole page does not need retranslating.
- Have someone who knows the language read the translation. This is the last check before publishing.
- Publish the versions on the same day. If you cannot, put an “update pending” note on the older version.
- Check the links. Do the language switcher and the hreflang set point to the new address?
Every three months, count the “waiting” rows in the table. If the number is growing, review your capacity or the number of translated pages. If translation cannot keep up, not publishing some pages in that language at all is better than showing half-finished, outdated ones. When pages have to move, the redirect logic in SEO when changing your domain name applies to language addresses too.
Common mistakes
- Forcing visitors to another version by IP or browser language. Google does not recommend it; visitors and search engines may not see the other versions.
- Translating only the menu and leaving the body in one language. Google writes that the same content can appear several times in search results with different boilerplate languages.
- Publishing machine translation unread. The spam policy targets scaled content that adds little value; our suggestion is to have one person read every page.
- Choosing a language by flag. According to W3C, a country can have more than one language and a language can be spoken in more than one country.
- Translating the form and forgetting the email. The visitor notices the language change in the second message.
Common questions
Should I use a subfolder or a subdomain?
Google’s document calls both easy to set up. A subfolder has low maintenance because it is the same host; a subdomain allows different server locations. If you are only adding languages, we suggest a subfolder; if you need a separate structure for each country, a country domain or subdomain is worth considering.
Do I have to translate every page?
No. But on a page you do translate, translate the main content as well; Google writes that translating only the boilerplate text and leaving the bulk of the content in one language can create a bad experience. For a page that is not translated, we suggest not showing an equivalent in the language switcher.
Will Google penalise me for using machine translation?
In the documents we read there is no line that bans translating your own content. The spam policy targets producing content at scale without adding value, and translating scraped content. Our suggestion is to treat the translation as a draft and have someone who knows the language read it.
One thing you can do today
Open your site on your phone, switch to the second language and fill in and send a form. In which language do the form messages, the confirmation email and the 404 page that a wrong address opens appear? Write every Turkish part you see into the table in Step 5; your translation list is ready.
If you are building a multilingual site from scratch or adding a language to an existing one, in our web and software service we build multilingual sites, managed from your own panel, together with design and measurement.
Sources
- Google Search Central: Managing multi-regional and multilingual sites
- Google Search Central: Spam policies for Google web search
- W3C Internationalization: Guiding users to translated pages
- W3C Internationalization: Declaring language in HTML
- W3C Internationalization: Text size in translation
- W3C Internationalization: Multilingual form encoding
This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 15 November 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.