Multiregional websites: subdomains, subfolders or geo pages
The moment a company opens a second city, the architecture question arrives. Getting it wrong is expensive: migrating later costs rankings.
Three architectures
Subdomains such as samarkand.example.uz give each city its own space and suit genuinely autonomous branches with separate pricing, stock and management. The cost is that Google largely evaluates each subdomain separately, so the main site's authority does not transfer in full.
Subfolders such as example.uz/samarkand are the default for most companies: authority concentrates on one domain and each city section inherits it. The third option is geo pages inside the normal structure, appropriate when cities differ only in contacts and delivery area.
Choosing, and combining with languages
Rule of thumb: differing address and phone only means geo pages suffice; differing range or pricing means subfolders; genuinely independent businesses mean subdomains. For most Uzbek companies opening a second or third city, subfolders are the right answer — subdomains usually just split an already modest domain authority three ways.
The local complication is that geography stacks on top of languages. Keep /ru/samarkand, /uz/samarqand, /en/samarkand manageable rather than nesting languages inside per-city subdomains. Language first, geography second, and hreflang links the language versions of one city to each other — Samarkand and Bukhara are different pages, not alternates.
Duplication is the real risk
A multiregional structure produces duplicates almost automatically: the same service copy across ten city pages. Google sees ten near-identical documents, picks one, and the other nine simply do not compete.
Every city page needs a genuinely unique block — address, team, cases, pricing, call-out terms, local reviews. Shared service copy may repeat, but it must not constitute the whole page: strip the repeated text and the page should still make sense on its own.