Expanding a Shopify store into new countries is not only a translation task.
As soon as a business begins serving different markets, the URL structure becomes part of the commerce architecture. The store may need different languages, currencies, content, legal information, products, pricing and regional experiences.
Shopify Markets supports different ways to structure these experiences. A market can use a subfolder, subdomain, or separate top-level domain, and each approach has different implications for SEO, operations and future growth.
The important question is not simply: “Which URL looks better?”
It is: “Which domain structure best matches the commercial, SEO and operational model of each market?”
Market and language are not the same thing
One of the most common mistakes in international Shopify setups is treating language and market as if they were the same concept.
They are not.
A market represents a commercial region or group of countries. A language determines the content experience shown to customers.
Two different markets can use the same language but still require different prices, products, shipping rules or domain structures.
For example:
United States
Language: English
Currency: USD
Domain: brand.com
United Kingdom
Language: English
Currency: GBP
Domain: brand.com/en-gb/
Both markets use English, but they are still separate commercial markets.
Option 1: Subfolders
A subfolder structure uses the primary domain and adds a localized path.
For example:
brand.com/tr/brand.com/de/brand.com/en-gb/
Subfolders are usually the simplest structure for stores that want to centralize SEO authority under one main domain.
A simplified architecture might look like:
brand.com → United States / English
brand.com/tr/ → Türkiye / Turkish
brand.com/de/ → Germany / German
When do subfolders make sense?
- One Shopify store manages several markets.
- The brand wants to consolidate SEO authority.
- The same domain identity is used globally.
- Market operations are mostly centralized.
- There is no strong reason to separate countries into independent domains.
They are also easier to maintain than managing several completely separate domain properties.
However, the URL structure should be planned early. If the primary domain changes later, subfolder URLs change with it. Market deactivation can also require redirect planning for old localized URLs.
Option 2: Subdomains
A subdomain separates a market under the same root domain.
For example:
tr.brand.comde.brand.comuk.brand.com
This creates clearer structural separation between markets while still keeping them under the same brand domain.
When can subdomains be useful?
- Markets need clearer technical separation.
- Different teams manage different regional storefront experiences.
- The business already operates with a subdomain strategy.
- Regional systems or integrations are structured separately.
- The company wants market-specific URLs without registering multiple country domains.
For example, tr.brand.com might serve Türkiye while global.brand.com serves international customers.
This model can also be useful when different markets have very different operational or payment architectures.
However, a subdomain should not be chosen simply because it “looks international.” It adds another layer of domain management and requires deliberate SEO planning.
Option 3: Separate country domains
The third option is using a completely separate top-level domain.
For example:
brand.combrand.com.trbrand.debrand.fr
This approach can create a very localized brand presence.
When do separate domains make sense?
- The brand already has an established local domain.
- Local SEO is strategically important.
- Regional teams operate relatively independently.
- A country-specific legal or commercial structure exists.
- Local marketing has already built authority around that domain.
- The business wants a clearly separate market identity.
But separate domains also create more work. Each domain may need its own SEO authority, domain management, tracking validation and ongoing maintenance.
Subfolder, subdomain and separate domain: a simple comparison
| Structure | Example | Main advantage | Typical use |
|---|---|---|---|
| Subfolder | brand.com/tr/ | Shares domain authority | Most multi-market stores |
| Subdomain | tr.brand.com | Clear structural separation | More independent market architecture |
| Separate domain | brand.com.tr | Strong local identity | Strategic country-specific presence |
There is no universal winner. The right choice depends on how independently each market needs to operate.
One market can also have multiple languages
A market does not need to equal one language.
For example, a Canadian market could support:
brand.com/en-ca/brand.com/fr-ca/
This is particularly important in multilingual countries or regions.
The architecture should therefore be designed around both country / market and language, rather than assuming that each country has one language.
Hreflang should be part of the architecture, not an afterthought
International stores need to help search engines understand which page version belongs to which language or region.
This is what hreflang tags are used for.
When markets, languages and domains are configured properly, Shopify can generate hreflang relationships between localized versions and manage related international SEO signals.
For example:
brand.com → English / US
brand.com/tr/ → Turkish / Türkiye
brand.com/de/ → German / Germany
The key point is that the market and language configuration must be correct first. A poor market setup cannot be fixed simply by adding SEO tags later.
Duplicate content risks still need attention
Using multiple domains or market URLs does not automatically create an SEO problem.
The problem appears when the same content exists across multiple URLs without clear localization signals.
This is another reason to keep the architecture simple. If two URLs do not need to exist separately, creating both usually adds unnecessary complexity.
Localization should go beyond translation
A market-specific experience is not only about translating text.
Different markets may need different:
- product descriptions,
- campaign messaging,
- legal content,
- delivery information,
- return information,
- banners,
- product availability.
For example, two markets may both use English but still require different content:
US English
“Free shipping over $100”
UK English
“Free delivery over £80”
The language is the same. The commercial content is different.
This is where the distinction between translation and localization becomes important.
Automatic redirection should not replace clear navigation
Automatic redirection based on customer location can help visitors reach the appropriate market experience.
But stores should still offer visible country and language selectors.
Customers might be travelling, using a VPN, shopping for another country or simply prefer another language.
Automatic detection is useful. Manual control is still necessary.
Think about domain architecture before migration
If an existing ecommerce site is moving to Shopify, the international domain structure should be defined before redirect planning begins.
For example, an old website may currently use brand.com/tr/products/... while the new Shopify structure becomes brand.com/tr/collections/... or perhaps tr.brand.com/....
That decision directly affects the 301 redirect map.
The recommended sequence is:
Define markets → Define languages → Choose domain strategy → Build Shopify URLs → Prepare redirects → Launch
Not the other way around.
A practical decision framework
- How many markets will the business operate?
- Which languages will each market support?
- Are pricing and product availability different between markets?
- Does the brand already own strong local domains?
- Should SEO authority remain under one main domain?
- Do markets need technical or operational separation?
- Are payment and logistics systems different by country?
- Will local teams manage content independently?
- Is market-specific content required beyond translation?
- How will the architecture affect existing URLs and redirects?
Once these questions are clear, the domain strategy usually becomes much easier to choose.
Digimaps perspective
For most Shopify projects, we prefer to define markets, languages and URL architecture before translation or migration work starts.
Subfolders are often the simplest structure, but the correct choice depends on SEO history, local domains, payment architecture and operational separation.
The goal is not to create the most complex international setup. It is to create a structure that remains understandable as the number of markets grows.
If you are planning international expansion with Shopify Markets, we can review your current domain, language and market structure before implementation.