My account Get a quote
Web

Multilingual Website Guide: URL Structure, Hreflang and Translation

Multilingual website guide: URL structure options, hreflang rules, translation quality, localization, the language selector and a step-by-step setup plan.

· 6 min read
Multilingual Website Guide: URL Structure, Hreflang and Translation

Three decisions matter most when building a multilingual website: the address structure in which the language versions will be published, how the relationship between versions is communicated to search engines with hreflang, and the quality of the translation. When these three are solved correctly, visitors find the page in their own language, search engines do not confuse the versions, and your brand appears trustworthy in every language. Below, we cover each heading with decision tables and step-by-step guidance.

When is a multilingual site needed?

If you sell abroad, have tourist or foreign customers, or want to be a brand that offers its service in several languages, a language version is a worthwhile investment. However, you do not have to translate every page. First determine the target countries and languages, and verify with search and customer data whether there is really demand in those languages; the maintenance of every translated page will also be work for you. Before starting, you can review your site's technical foundation with the concepts in our article what is a website and what is website software.

URL structure options

You can present language versions with three main methods. The choice affects your budget, management convenience and search visibility.

MethodExampleProsCons
Subfolderexample.com/en/Single domain and single hosting; consolidates authority in one place; easiest to manageAll versions sit on the same server and location; country-specific hosting is difficult
Subdomainen.example.comVersions can be moved to separate servers; the structure is clearSearch engines sometimes treat them as separate sites; management is more complex
Country domainexample.deStrong local signal for the country; high user trustEach domain has a separate cost and management; authority is split

For most corporate sites and e-commerce, the subfolder structure is the most balanced option. Country domains can be considered where there is local brand identity and separate operations in several countries. To recall domain concepts, see our article what is a domain name.

There are approaches to avoid: changing the language only with a cookie or session while showing a different language at the same address, changing the language only with a parameter (?lang=en), and forcibly redirecting visitors according to their browser language. Each language version should have its own fixed, shareable address.

Hreflang: tell search engines about the language relationship

Hreflang is a tag that tells search engines about the language or regional versions of the same content. This way, a Turkish searcher is shown the Turkish page and an English searcher is shown the English page, and the versions are not treated as duplicates of each other.

  • Each version marks all of its counterparts, including itself; the relationship must be reciprocal, otherwise the tags may be ignored.
  • Use a two-letter language code (tr, en), and where needed combine it with a region (en-GB).
  • Every address marked must be crawlable, return a 200 status code and have its own canonical address.
  • Define a default version with x-default for users whose language cannot be determined.
  • The tags can be provided in the page head, in the HTTP header or in the XML sitemap; do not give conflicting information through several methods at the same time.

Note how it works together with canonical: each language version should give a canonical to its own address, not to the page in another language. For a general technical audit, the technical SEO checklist is useful.

Translation quality and localization

The most visible weak point of a multilingual site is poor translation. Word-for-word or unreviewed machine translation lowers brand credibility; customers hesitate to pay on a page with faulty text.

Choosing a method

MethodWhen?Watch out for
Professional translatorHome page, product and service pages, legal texts, advertising copyCostly but the most reliable; share a terminology glossary
Machine translation plus human reviewLarge numbers of pages, product descriptions, blog archiveMust be checked by a native-level speaker
Machine translation onlyLow-risk, internal or temporary contentNot recommended for home and sales pages

Localization is more than translation

  • Show currency, date, time and measurement units according to the target country.
  • Arrange address, phone and tax or delivery information according to the country.
  • Adapt text in images, examples and cultural references.
  • Titles, meta descriptions, image alt texts and form error messages must also be translated; these are often forgotten.
  • Determine keywords not by translating them, but by looking at what people in that language actually search for.
  • Have legal pages and payment conditions checked for compliance with the country's legislation by an expert; this section is general information and does not replace legal advice.

Content management and sustainability

The real challenge of a multilingual site is not the launch but the maintenance after it. When a price, campaign or legal text changes in the main language, the other languages must also be updated the same day; otherwise visitors see different information in different languages. So assign a responsible person for each piece of content, flag pages awaiting translation in the panel, and do not associate pages with incomplete translations through hreflang. Rather than publishing a page whose translation is incomplete, it is usually better not to publish it at all.

You do not have to write all translated content from scratch; however, it is important to know for each language which pages are "direct translations" and which are "adapted content". For example, about us and service pages can be translated directly, while campaigns, blog posts and case studies should be adapted to the target market. If you prepare a terminology glossary and style guide, the brand voice stays consistent even when different people do the translation.

Performance and measurement should be run separately as well. Split analytics reports by language version, and monitor each language's Search Console performance and conversion rates separately. This shows which language your investment is paying off in, and lets you diagnose more quickly what is missing in weak versions.

Language selector and user experience

Visitors should be able to change the language easily. Keep the selector visible and in the same place on all pages, and write languages with their own names (e.g. Türkçe, English, Deutsch) rather than flags, since a flag represents a country rather than a language. When the language is changed, ideally the user should land on the counterpart of the same page; if there is no counterpart, redirect them to the home page of that language.

Rather than detecting the browser language and redirecting automatically, showing a suggestion notification is safer. Bots usually come from a single location and language, and automatic redirection can prevent the other versions from being crawled. The selected language can be remembered for the user, but the address must still carry the language version.

Technical details

  • Page encoding should be UTF-8 so that special characters in Turkish, German and Arabic display correctly.
  • Specify the page language in the HTML tag (lang attribute); for right-to-left languages, also set the text direction.
  • Write a separate page title, meta description and heading structure for each language version.
  • List all language versions in the XML sitemap.
  • Use translated, readable phrases in addresses (slugs); simplify special characters if needed.
  • Make sure your database and admin panel can keep multilingual content in separate fields.
  • Define a process that links the corresponding language versions each time a new page is added; unrelated pages are the main source of hreflang errors.

Multilingual site setup: step by step

  1. Determine the target countries and languages, and verify the demand with search data.
  2. Choose the address structure (usually a subfolder) and record the decision in writing.
  3. Determine the translation method and terminology glossary, and rank the pages to be translated by priority.
  4. Set up the language and content association in the admin panel.
  5. Translate titles, descriptions, image alt texts and form texts for each version.
  6. Create the hreflang tags and the multilingual XML sitemap.
  7. Add the language selector and test that it leads to the counterpart on each page.
  8. Monitor errors and warnings in Search Console, and crawl the site after publication to catch translation and layout errors.

Common mistakes

  • Translating only the menu and leaving the content half-finished; mixed-language pages mislead both users and search engines.
  • Not giving reciprocal hreflang tags, or marking an incorrect address.
  • Changing the language at a single address through a cookie.
  • Treating translation as a one-time job and not carrying updates over to the other languages.
  • Opening the site without preparing payment, delivery and support methods for the target country.

Conclusion

A multilingual site, with a sound address structure, correct hreflang and careful translation, is one of the most effective ways to open up to new markets. Starting small with language versions and growing them in a healthy way is the safest approach. If you want to plan your project together, you can get in touch with Erdem Software.

Frequently asked questions

For a multilingual site, should I choose a subfolder or a subdomain?

For most corporate sites and e-commerce, subfolder management is the easiest and consolidates authority in one place. If separate operations and local branding are needed, a subdomain or country domain can be considered.

Is hreflang mandatory?

It is not mandatory but it is recommended. If the same content has several language versions, it helps search engines show the right version to the right user. The tags must be reciprocal, and all marked addresses must be crawlable.

Is machine translation enough?

Not on its own for home and sales pages. If you use machine translation, have it corrected by a native-level speaker.

Should I redirect visitors automatically based on their browser language?

Showing a language suggestion is safer than a forced redirect. Automatic redirection can prevent bots from crawling the other versions.

Do I have to translate every page?

No. Translate the most important pages first and monitor demand. A small, fully translated version is better than pages that are half-translated and mixed-language.

Need help with this?

Fast, search-friendly, multilingual sites you can update easily from a panel.

See the serviceGet a quote

Related posts

All →