International Ecommerce SEO: Country vs Language URL Structure
A country versus language URL structure decision is about what each version of your store is for. Language versions serve speakers of a language anywhere; country versions serve a market with its own currency, prices and shipping. Most stores need a mix, and the URL pattern follows from that choice.
- Language vs country
- Folders, subdomains, ccTLDs
- Platform checks
- Decision guide
A country versus language URL structure decision is about what each version of your store is for. Language versions serve people who speak a language wherever they are. Country versions serve a market with its own currency, prices, shipping and rules. Most international stores need a mix, and the URL pattern, whether folders, subdomains or country domains, follows from that.
The choice looks technical, but it is mostly a business question. How many markets will you open? Do they differ in more than language? Who will run them? Can your platform support the structure you prefer? The answers narrow the options quickly, and the SEO side is mostly about avoiding structures that are hard to maintain or hard for search engines to follow.
This guide sets out the options, what each means in practice, and how I would decide. It is a judgment guide, not a rulebook, and where Google documents something I link to it. Once the structure is chosen, the next step is hreflang for ecommerce stores. For help with a specific store, see international SEO for ecommerce stores.
Language or Country: What Is Each Version For?
Start with purpose, not URLs. A version of your store can target a language, a country, or a language in a country. Those are different promises, and they lead to different pages.
| Targets | Fits when | Example pattern |
|---|---|---|
| A language | The offer is the same for speakers anywhere, and only the language differs | /de/ for German |
| A country | Currency, pricing, shipping, tax or catalogue differ by country | /at/ for Austria |
| A language in a country | You need both: the language and local commercial details | /de-at/ for German in Austria |
| A region of several countries | A shared offer across a group of countries, such as one euro shop | A single region page, with its limits understood |
The common mistake is to build country versions for markets that only need a language, or the other way round. A store that ships worldwide at the same price but wants to serve German speakers may need only a German language version. A store with different prices, stock and delivery times in the UK, Ireland and Australia needs country versions even though the language is the same.
The Three URL Patterns
Google’s guidance on multi-regional and multilingual sites lists the main options: country-specific domains, subdomains and subfolders. It also notes that URL parameters and cookie or location based switching are not recommended for language versions. Each of the three recommended options has trade-offs.
| Pattern | Example | Strengths | Costs |
|---|---|---|---|
| Subfolders | example.com/de/ | One domain and usually one platform. Simple to set up and maintain | One server location. Separating markets technically or legally is harder |
| Subdomains | de.example.com | Easy to set up. Can sit on different servers or platforms. Easy to separate | Users may not recognise the country from the URL. Often treated as separate sites to manage |
| Country domains (ccTLDs) | example.de | A clear country signal. Easy to separate. Suits local entities and local teams | More expensive. More infrastructure. Each domain builds its own visibility. Some country domains have registration rules |
Two judgment calls sit on top of the documented facts. First, many consultants prefer subfolders for stores that run one platform, because there is less to maintain and a new market launches inside an existing site. Second, a country domain can make sense when a market needs its own entity, team, payment setup or hosting. Neither is a rule, and the right answer depends on your stores and your team.
What Your Platform Allows
The structure you want has to be one your platform can produce cleanly. Check this before you commit, because a structure that needs workarounds tends to produce duplicate and broken URLs later.
| Platform | What to check | Common catch |
|---|---|---|
| Shopify | Which structure your Markets setup uses for each market and language, and what happens to URLs and currency | Market and language settings can change the URLs. Test before moving traffic |
| WooCommerce | Whether your multilingual plugin supports folders, subdomains or separate domains, and how it handles WooCommerce URLs | WooCommerce has no built-in multilingual feature, so the plugin decides the pattern |
| Magento | How store views, store codes and base URLs are configured per market, and how language and currency are separated | Many store views multiply catalogue and URL checks |
| BigCommerce | Whether a multi-storefront setup gives each market a separate domain or path, and how product data is shared | Separate storefronts can mean separate sitemaps and annotations to maintain |
I describe these as things to check because platform features change, and the options available can depend on the plan or version you use. Confirm current behaviour in the platform’s documentation and on a test market before you rely on it.
How I Would Decide
These are starting points, not rules. Use them to frame the conversation with your team, then test the choice against your platform.
| Situation | Where I would lean | Why |
|---|---|---|
| One team, one platform, a few markets, limited budget | Subfolders | Least to maintain, and each new market is a new folder |
| Separate local teams, entities or payment setups per country | Country domains or subdomains | Operations are already separate, so the structure can match |
| Different platforms or servers per market | Subdomains or country domains | Subfolders are awkward when markets run on separate systems |
| Language-only need, same offer everywhere | A language folder | No need for country versions you cannot differentiate |
| Uncertain which markets will last | Subfolders, opened one at a time | Easier to open, and easier to remove with redirects |
Duplicate Content Across Markets
When two country versions share a language, the pages can end up near-identical. Google may group near-duplicates and choose one as the main page, even when hreflang is present. That does not usually mean a penalty. It means the version you wanted in a market may not be the one Google shows.
- Give each country version something real: its own price and currency, shipping and returns details, availability and local spelling.
- Use hreflang to connect the versions and give each a canonical tag pointing to itself.
- Avoid copying every product description across markets without checking that it suits each market.
- If two versions would stay near-identical, ask whether one version with a country selector would do.
The same product also tends to have several URLs inside one market, which is a separate problem covered in the duplicate product URLs guide. Fix that first, so each market starts from one clean canonical URL per product.
Currency, Pricing and Market Switchers
A market switcher lets shoppers choose a country or language. How it works affects what search engines can see.
| Approach | What search engines can see | My view |
|---|---|---|
| Separate URL per market with a visible selector | Each market is a crawlable URL | The safest option |
| Banner that suggests a market without forcing it | The page they requested | A good addition to the selector |
| Automatic redirect by IP or browser language | Often only the market of the crawler’s location | Risky, because other versions may not be reached |
| Same URL, different prices by cookie or location | Usually one version only | Avoid for pages you want indexed per market |
Show the price and currency a buyer in that market will actually pay, in the page content and in the Product structured data. If a page shows one price and the structured data or the product feed says another, that mismatch can cause problems with Google Merchant Center as well as with search.
Changing the Structure Later
Changing structure later is a site migration. Every moved URL needs a one-step redirect, canonicals and hreflang must be updated, sitemaps replaced and internal links changed. The replatforming SEO checklist applies to this kind of move as well. The cheaper path is to choose carefully before the markets build up visibility.
Frequently Asked Questions
Are subfolders better than subdomains or country domains?
Often the easiest to run, but not automatically better. Subfolders keep everything on one domain and one platform, which usually means less to maintain. Country domains give a clearer country signal but mean running and building up separate sites. Whether a subfolder benefits from the strength of the main domain is a common view, and Google does not publish how it treats each option, so I treat it as a judgment call.
Can I use URL parameters for languages?
Google advises against it. Its guidance recommends separate URLs for each language version, such as folders, subdomains or country domains, and does not recommend parameters like ?lang=de for language versions.
Do I need a separate version for each country that speaks the same language?
Only when something real differs: currency, prices, shipping, availability, spelling or legal text. If US and UK pages would be near-identical, think about whether two versions are worth the upkeep, since Google may group near-duplicates anyway.
Should I redirect visitors to the right country automatically?
I would not force it. Search engines usually crawl from a limited set of locations and may never reach the other versions, and shoppers sometimes want a different market from the one their location suggests. A visible selector, with an optional banner that suggests the other market, is safer.
Can I change the structure later?
Yes, but it is a migration. Every URL that moves needs a redirect, and hreflang, canonicals and sitemaps have to be updated. It is cheaper to choose carefully at the start than to change the structure after the markets have built up visibility.
URL Structure Checklist for International Stores
- Each market has a stated purpose: a language, a country, or both.
- Country versions exist only where price, currency, shipping or catalogue really differ.
- The chosen pattern is one your platform and your team can keep clean.
- Each version has its own crawlable URLs, not parameters, cookies or location switching.
- Each version has a self-referencing canonical and is connected with hreflang.
- A visible market selector exists, and any automatic suggestion does not force a redirect.
- Prices and currency on the page match the structured data and the product feed.
- There is a plan for how markets are opened one at a time and checked before the next.
To set up the annotations once the structure is chosen, read hreflang for ecommerce stores. For a view of how this fits into your store, see international SEO for ecommerce stores and the ecommerce SEO consultant page.
Book a call and we will go through your markets, platform and team, then agree on the structure that fits and the order to open the markets in.
Book a Call
I work on online stores that sell into more than one country or language. This guide sets out the URL options and how I would choose between them, and it does not promise how rankings will change.
More SEO guides
Hreflang for Ecommerce Stores
How to set up hreflang for an ecommerce store: language and region codes, self-references, return links, x-default, canonicals and the mistakes that break it.
Abdullah Mahmud
Duplicate Product URLs in Ecommerce
Why one product can have several URLs on Shopify, WooCommerce and Magento, how to find them, and how to fix them with canonicals, redirects and cleaner links.
Abdullah Mahmud
Ecommerce Replatforming SEO Checklist
An ecommerce replatforming SEO checklist: the 301 map, page parity, internal links, sitemap, launch-day checks and what to monitor after the move.
Abdullah Mahmud
Opening a new market and want the structure checked first?
Get the URL structure, hreflang plan and platform setup reviewed before the new market goes live.
I’m an awarded SEO expert and seo consultant with 11+ years of experience. I have generated over $100M in tracked organic revenue by SEO for my clients like you 👉 See Case Study