Choosing a subfolder such as /tr/ or a subdomain such as tr.example.com connects technical architecture with publishing operations. Neither structure is automatically the best option for every organisation. Consider who manages the languages, how much infrastructure they share and whether existing URLs must move. The address format should support a workable operating model.
Decide how independently the versions must operate
A shared team, design and content model may suit a closely integrated setup. Separate teams, catalogues or publishing schedules can create a need for greater separation. Document these requirements before choosing the URL structure.
Clarify language and country scope too. The label in a URL does not explain every content decision. Version selection, visitor navigation and equivalent-page relationships still need their own design.
Compare management implications
Google's international guidance includes both subdomains and subdirectories among the available structures, with different management and separation considerations. Treating one choice as a ranking guarantee is not a sound basis for architecture.
| Decision area | Question | Work affected |
|---|---|---|
| Infrastructure | Will languages share one system? | Development and maintenance |
| Team | Who publishes and approves? | Permissions and editorial workflow |
| Measurement | How will markets and languages be reported? | Data organisation |
| Migration | Will existing addresses change? | URL mapping and redirects |
| Experience | Will language switching preserve context? | Navigation and content relationships |
Recognise the cost of changing an existing setup
A new project differs from a site already operating across languages. Existing addresses may have links, visibility, shared documents and campaign destinations. If a move is necessary, prepare the mapping and validation plan before changing a setting.
In a hypothetical move from a language subdomain to /tr/, page paths, forms, media and old internal links may be affected. A working homepage does not establish that migration is complete. Check representative service and content journeys as well.
Record why the structure is sustainable
Explain the selected option, its rationale and dependencies. Consider how another language would fit later. Managing content identities and language relationships independently of the address format can make future changes easier to understand.
After implementation, review access, language switching and reporting consistency. Evaluate the actual setup instead of drawing conclusions from the structure's name. A suitable choice supports a team that can maintain the content and visitors who can find the appropriate page.