JournalInternational websites
International websites

Bilingual Websites: URL Structure, Hreflang and Real Localization

A language switcher is only the visible tip of an international website. Routing, page equivalents, content ownership and editorial maintenance determine whether it works.

IN BRIEF

  • Give each published language edition a crawlable URL.
  • Connect equivalent pages with accurate reciprocal hreflang references.
  • Translate the user journey and maintain editorial parity—not just menu labels.
/ 01

Translation and localization are different jobs

Translation conveys a message in another language. Localization adapts the entire experience to that audience: terminology, examples, navigation, regional conventions, contact expectations and even the assumptions behind a service description. The goal is not to write two pieces of unrelated copy. It is to provide equivalent decisions and information in each language.

For an independent studio serving clients locally and abroad, English and Turkish can share a visual system while requiring different editorial phrasing. A literal translation of “Let’s make it happen” may sound unnatural in a professional Turkish context. Choose wording appropriate to the audience while preserving the offer, scope and tone.

  • Establish a glossary for service names and recurring terms.
  • Write titles and descriptions based on language-specific intent.
  • Check forms, error messages, buttons and legal text independently.
  • Identify region-sensitive facts that must be verified for each edition.
/ 02

Choose URL architecture early

Common patterns include subdirectories such as /en/ and /tr/, separate subdomains, or separate domains. Subdirectories are often easier to maintain in one shared application because content, routing, hosting and deployment can remain centralized. There is no universally superior pattern; organizational and market requirements matter more than fashion.

Do not switch language by replacing visible text only on one URL. Search engines and people need shareable addresses for each edition. Keep paths stable and human-readable. If an article exists at /en/blog/web-performance/, its Turkish counterpart can use a natural Turkish slug rather than forcing English terminology.

  • Publish the homepage and every indexable page on its own locale URL.
  • Use the same content ID internally for translated equivalents.
  • Preserve canonical trailing slashes and redirect alternate forms consistently.
  • Plan how the application behaves when no translation exists.
/ 03

Use canonical and hreflang for different purposes

A canonical indicates the preferred URL for a page or near-duplicate set. Hreflang indicates language or regional alternatives. The English and Turkish pages should generally each reference themselves as canonical, while their alternate links reference both editions. A canonical from Turkish to English can undermine the intent to index both language versions.

Every equivalent should link back to the others, use valid language codes, and point to pages that actually exist and return successful responses. x-default can designate a default version, but it is not a substitute for correct language targeting. Do not claim content is a translation if the linked pages solve different problems.

  • English canonical: the English page URL.
  • Turkish canonical: the Turkish page URL.
  • Both pages: reciprocal en and tr hreflang links.
  • Optional x-default: a sensible neutral or default landing page.
/ 04

Keep the language switcher contextual

A visitor reading an article should land on that article's translation when changing language—not on the other language's homepage. The same applies to service and project pages. A central route registry that knows content IDs and their language slugs makes this possible without duplicating header code.

If a translation is not ready, avoid inventing an equivalent URL. Either make the available editions explicit or provide a clearly explained fallback, depending on the product's policy. On mobile, the language control must remain reachable, keyboard operable and visually distinguishable without relying on color alone.

  • Link translated equivalents by content ID.
  • Mark the current language accessibly.
  • Keep contact forms and confirmation messages in the chosen language.
  • Test a direct shared link, refresh, back navigation and language switching.
/ 05

Localize metadata and structured content

Page titles, descriptions, article headings, summaries and image alternatives need language-aware editing. The metadata should describe the actual page, not blindly prepend translated keywords. Language tags on the HTML element and structured data can help systems understand the edition, while visible content remains the main source of meaning.

For articles, use separate summaries and topic labels for each language. Keep authorship, publication dates and factual claims consistent. If one edition is revised materially, record whether the counterpart also needs review. A translation backlog is an operational issue, not merely a copywriting task.

  • Store editorial metadata alongside each localized article.
  • Reuse shared facts without forcing identical sentence structures.
  • Inspect social previews, browser titles and snippets for each locale.
  • Version meaningful content updates and verify parity after publishing.
/ 06

Test the details people actually notice

Automated checks can verify URL status, redirects, language attributes, canonical links, hreflang and sitemap entries. They cannot reliably judge whether a sentence feels professional or whether an unfamiliar idiom changes the promise. Both technical validation and human review are required.

Test in the real hosting environment. Confirm that Apache rewrites and HTTPS work for every path, that templates do not break when translated text grows longer, and that no unnecessary JavaScript blocks the initial content. A multilingual site is only complete when both experiences are coherent.

  • Check language routing and 404 behavior for all published paths.
  • Validate navigation, footer, forms, privacy pages and mobile layouts.
  • Proofread terminology and typography with native-language context.
  • Verify sitemap alternates and actual page availability together.
YOUR QUESTIONS

Frequently asked questions

Should English and Turkish share one URL?

For independent indexable language editions, separate URLs are the clearest approach. A client-side switch on one URL makes discovery, sharing and canonical management more difficult.

Does hreflang translate a page?

No. Hreflang only declares a relationship between existing pages. Content and metadata still need to be authored and maintained.

Must URL slugs be translated?

No search engine requirement forces translated slugs, but natural language-specific paths can improve clarity for users. Consistency and correct linking matter more.

PUT IT INTO PRACTICE

Treat localization as product architecture. Our website systems use shared templates with separately managed content, metadata and URLs for each language.

Services