To build a multilingual website you only need to get three things right: separate, crawlable URLs for each language (for example `/tr` and `/en`), `hreflang` tags that tell search engines which page belongs to which language, and a setup that lets you manage all content from one place. A browser auto-translate widget (like a Google Translate button) is almost useless for SEO; each language needs its own real page that Google can index.
When do you need a multilingual site?
Any company that exports, serves clients abroad, works in tourism, or wants to reach different language communities at home needs a multilingual site. Users stay far longer and convert far better on a site in their own language. But the real win is in search: once you have English content, you open up to thousands of potential customers searching in English — your Turkish page would never appear in those results.
URL structure: subdirectory, subdomain, or separate domain?
On a multilingual site the first and most permanent decision is URL structure; changing it later is costly for SEO. You have three options:
- Subdirectory (example.com/tr, example.com/en): domain authority stays in one place, and it’s the easiest to set up and manage. This is the recommended choice for most corporate sites.
- Subdomain (tr.example.com, en.example.com): Google may treat these as partly separate sites, splitting authority. It makes sense when you need infrastructure separation.
- Separate domains (example.com.tr, example.com): gives a strong local signal, but you must build each domain’s authority from scratch; the highest-effort, highest-budget option.
Practical recommendation: for most companies the subdirectory structure (/tr, /en) is the right call — all SEO value accumulates on one domain, it’s simple to manage, and it works cleanly with hreflang.
hreflang: the most critical technical step
`hreflang` is the tag that tells Google “the Turkish version of this page is here, the English version is there.” Set up wrong, Google shows the wrong language to the wrong country, may treat your pages as duplicate content, and your rankings drop. Every page must point to all language versions, including itself (reciprocity is required):
<link rel="alternate" hreflang="tr" href="https://example.com/tr/hizmetler" />
<link rel="alternate" hreflang="en" href="https://example.com/en/services" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/services" />On a modern foundation like Next.js these tags can be generated automatically for every page; instead of writing them by hand, you define `alternates.languages` inside `generateMetadata` and the whole site stays consistent. We cover this approach in detail in our building a corporate website with Next.js article.
Localization, not translation
The value of a multilingual site is not in moving text into another language, but in adapting it to that culture. Literal translation usually reads as artificial and untrustworthy. Localization goes beyond language:
- Currency, date, and number formats (₺ / $, DD.MM.YYYY / MM/DD/YYYY)
- Titles and descriptions chosen separately for each market’s actual search terms
- Cultural tone: casual in one market, more formal in another
- Local contact details, legal pages (KVKK / GDPR), and payment methods
Why does auto-translate hurt SEO?
A “Translate” button or browser translation only converts content temporarily, on the user’s screen. Google never sees that translated text — it only indexes the page in its original language. So a user searching in English can’t find you. Worse, low-quality machine-translated pages that no one reviewed can be penalized by Google. The right method is always the same: a real, indexable, separate URL for each language.
Managing content from one panel
For a multilingual site to be sustainable, when you update one page you must be able to edit it for all languages from the same place. When text is separated from code and kept in language files (or a content panel), adding a new language is no longer a whole project — it’s just adding one more translation file. This structure lets your site grow without breaking its search engine compatibility.
Conclusion
Done right, a multilingual website is not just a site read in different languages — it’s a growth channel that gets found in every market and converts. The three keys are clear: the right URL structure, flawless hreflang, and real localization. If you’re planning a fast, hreflang-compliant multilingual site for your company, talk to our web development team about what you need, and check our SEO-friendly website guide for international visibility.