Shopify International Domains: 3 URL Choices Before You Scale

Ecommerce leads comparing international URL options

Shopify supports international domains through Shopify Markets, letting you give each country or region its own unique URL using subfolders, subdomains, or country-specific top-level domains. For most merchants, subfolders offer the best mix of simplicity and shared SEO authority, while subdomains and country domains make more sense once a market justifies the extra setup and maintenance work.

TL;DR:

  • Use subfolders to test demand because they need no extra domain purchase and share existing authority; reserve ccTLDs for markets worth separate upkeep.
  • Every international market needs a custom domain, and secondary markets require combined language and country paths such as /fr-ca rather than /fr.
  • Shopify does not automatically redirect visitors between EU country domains, while search crawlers are never redirected, so verify campaign deep links and localized landing pages.
  • Subdomains and country domains need deliberate cross domain tracking, or customers who switch domains may appear as separate sessions and distort conversion attribution.
  • Check redirects, hreflang tags, translation publishing, and localized prices at least monthly, especially after market changes or bulk product updates.
Quicktoimpress
Build a Shopify Store Ready to Scale
Quick To Impress helps commerce teams build growth platforms and connected systems, including Shopify engineering, integrations, and workflow automation.
Explore growth engineering

Table of Contents

URL structure options: subfolders, subdomains, and country domains

Shopify Markets gives you three ways to structure a market-specific URL, and each one trades simplicity for local SEO strength in a different way.

A subfolder looks like example.com/fr and sits under your primary domain. A subdomain looks like fr.example.com and operates as a separate web address tied to the same root domain. A country-code top-level domain, or ccTLD, looks like yourstore.fr and functions as a fully independent domain registered for that country.

Subfolders share domain authority with your main site and carry the lowest setup complexity, subdomains sit at medium complexity, and top-level domains demand the most management but send the strongest local relevance signal to search engines in that country.

  • Subfolders consolidate backlinks and domain trust under one root domain, so a new market benefits from authority you have already built.
  • Subdomains behave as semi-independent properties, giving you more flexibility for region-specific branding without fully separating SEO equity.
  • Top-level domains build their own authority from scratch but tell local customers and search engines that you have a genuine presence in that country.
  • Operational cost rises in the same order: subfolders need no extra registration, subdomains need DNS records on your existing domain, and ccTLDs require registering and renewing a separate domain, sometimes with local residency requirements.

Registration costs for a new domain typically fall in the $10 to $30 per year range, which is a real but modest line item compared to the engineering and content work of maintaining a separate property.

Stage of expansion should drive the decision. Merchants testing demand in a new country before committing budget usually start with subfolders, since they require no new domain purchase and let existing rankings carry some weight. Brands that want distinct language or regional branding, perhaps a dedicated storefront experience for a market with different merchandising needs, often move to subdomains. Businesses planting a long-term flag in a specific country, especially where local trust signals matter for conversion, tend to justify the cost and upkeep of a ccTLD.

Three visual patterns for market-specific URLs

How to set up international domains in Shopify Markets

Setting up international domains follows a defined sequence in the Shopify admin, and skipping a step tends to surface as a broken redirect or a market that silently fails to localize.

  1. Add or buy a custom domain. Purchase a domain through Shopify or connect one from a third-party registrar. You cannot assign a myshopify.com domain to an international market; Shopify requires a custom domain for every localized URL.
  2. Create a market in Shopify Markets and add the countries or regions you want to target under that market.
  3. Choose the URL structure per market, selecting a domain, subdomain, or subfolder for that specific group of countries.
  4. Assign the domain or subdomain to the market and confirm DNS records point correctly to Shopify’s servers.
  5. Publish languages for that market and verify translated content appears on the correct URL pattern.
  6. Set localized pricing and catalogs so customers in that market see the right currency, products, and availability.
  7. Verify SSL status on the new domain or subdomain before sending any traffic to it.
  8. Test redirects, deep links, and sitemap updates to confirm the new market URL behaves as expected across devices and entry points.

Pro Tip: Test your new market URL in an incognito browser window from a VPN located in the target country before announcing the launch, since cached sessions and your own IP location can mask redirect problems.

Each step depends on the one before it. A domain with incomplete DNS propagation will show SSL warnings even if languages and currencies are configured correctly, and a market with no published language will serve English content on a French subfolder regardless of how the URL is structured. Running through the full testing checklist, redirects, deep links, language activation, currency display, and sitemap entries, catches the gaps that a quick visual check of the homepage misses.

Redirection behavior and the EU ccTLD exception

Shopify Markets can detect a visitor’s location and automatically send them to the correct localized URL, but the mechanics differ depending on whether a market uses a dedicated domain or shares one with your main store.

When a market uses a shared domain, like a subfolder on your primary .com, Shopify adjusts the storefront experience in place rather than redirecting to a new URL. When a market has its own dedicated domain or subdomain, a qualifying visitor is redirected to that separate address.

  • EU ccTLDs are exempt from automatic cross-country redirection. A shopper who lands on a .de storefront is not automatically bounced to a .fr storefront even if their browser or IP suggests France, which avoids surprising visitors who deliberately typed or clicked into a specific country domain.
  • Search engine crawlers are never redirected. Each market URL is crawled and indexed on its own terms, which is what makes independent indexing of subfolders, subdomains, or ccTLDs possible in the first place.
  • Deep links should bypass automatic redirection when you are running a country-specific campaign, since sending a paid visitor through an unwanted redirect loop can cost you the click.
  • Disable automatic redirection selectively for landing pages tied to email or ad campaigns where you need the visitor to land exactly where the link pointed, not wherever geolocation logic decides.

The practical takeaway is that redirection behavior is a feature you configure around your campaigns, not a background process you can ignore. A merchant running a France-specific promotion through a .de domain’s shared catalog needs to know whether a French visitor arriving via that email link will see the intended page or get rerouted somewhere unexpected.

SEO considerations for international URLs

Shopify automates a meaningful share of the technical SEO work once your markets and domains are configured, which removes a lot of manual effort that used to fall on developers.

Hreflang tags, XML sitemaps, and canonical URLs are generated automatically for each market-specific URL, telling search engines which language and country version of a page corresponds to which URL, and preventing duplicate content penalties across near-identical pages in different markets.

  • Subfolders inherit domain authority, which tends to produce faster indexing and ranking lift for new markets since search engines already trust the root domain.
  • ccTLDs build authority independently, offering the strongest signal of local relevance but requiring their own backlink and content investment before rankings catch up.
  • Validate hreflang and sitemap coverage in your search console tooling after any market change, since a misconfigured market can silently drop pages from an index.
  • Watch for duplicate content signals between near-identical market pages, particularly when two English-language markets share most of their catalog copy.

Pro Tip: Check your hreflang implementation whenever you add, merge, or deactivate a market, since a stale tag pointing to a removed market URL can confuse crawlers for weeks before anyone notices the ranking drop.

Most of this works without intervention for a straightforward setup: one language per market, one currency per market, one domain type across the store. The complexity climbs fast once you run mixed structures, a subfolder for one region and a ccTLD for another, or need cross-domain analytics tracking that Shopify’s native tools do not fully cover. Teams managing hreflang at scale across many localized pages sometimes automate tag generation directly in their deployment pipeline rather than relying solely on platform defaults. That is usually the point where an SEO or engineering partner earns their fee: large migrations, multi-market catalogs with overlapping languages, or any setup where a manual sitemap check is no longer realistic.

Managing international domains day to day

Launching a market is the easy part. Keeping redirects, translations, and pricing in sync as markets change is where most merchants run into friction.

  1. Review the effects of moving a country between markets. Changing a market’s country list can shift which domain or subfolder serves that country, so check redirects immediately after any reassignment.
  2. Confirm translation publishing status whenever you add a language, since an unpublished translation will quietly fall back to the store’s default language.
  3. Re-verify localized pricing and catalogs after bulk product updates, which can reset market-specific overrides without obvious warning.
  4. Check domain renewal dates and SSL status on a recurring schedule, particularly for ccTLDs that may carry separate billing and residency requirements from your primary domain.
  5. Segment analytics by market so a traffic or conversion drop in one country does not get buried inside aggregate store-wide numbers.

Organizations running genuinely separate storefront experiences, distinct catalogs, pricing logic, or checkout flows per region, sometimes outgrow what Markets-level customization inside one store can support. Expansion stores on Shopify Plus exist for exactly that case, offering fully separate store instances rather than market variations within a single store. Most merchants never need that step, but it is worth knowing the ceiling exists before you try to force a single store to behave like multiple stores.

Why systems-first implementation matters for multi-market domains

Shopify Markets gives you the controls, but a market configuration is only as reliable as the testing and observability around it. We treat domain and Markets rollouts as systems to own, not settings to toggle once and forget: version-controlled DNS records, documented redirect rules, and monitoring that flags a broken hreflang tag before it costs you a quarter of organic traffic.

The common failure pattern is not a wrong setting; it is drift. Redirects break after a market reassignment, a translation silently falls back to English, or analytics fragment across domains so nobody notices a market’s conversion rate quietly sliding. Embedding strategy and execution in one team closes that gap because the people who designed the market structure are the ones checking it after launch.

Merchants typically need implementation support once catalogs overlap across markets, checkout logic gets complicated by local payment methods, or traffic volume makes a manual QA pass impractical.

— Service

Language and currency handling per market

Each market in Shopify Markets carries its own language and currency settings, and subfolder naming has a specific rule worth knowing before you set one up. Your primary market can use a language-only subfolder, such as /fr for French, but secondary markets must use a combined language-country code like /fr-ca for French-Canadian content.

This matters because a language-only subfolder on a secondary market will not map correctly, Shopify expects the fuller code to distinguish, say, France-targeted French from Canada-targeted French. Currency display follows the market assignment independently of the URL structure: a subfolder, subdomain, or ccTLD can all show prices in the local currency once that market’s settings specify it.

Get this wrong and the symptoms show up as mismatched content: a Canadian visitor landing on generic French copy written for a French audience, with pricing that does not reflect local tax expectations. Checking the language code against the market’s actual country list, not just the display language, avoids the mismatch before it reaches customers.

Impact of international domains on Shopify apps and integrations

Adding international domains changes how some apps and integrations behave, since many third-party tools are built with a single-domain store in mind. Apps that inject scripts, track conversions, or manage reviews sometimes need separate configuration per domain or subdomain, particularly if they rely on cookies scoped to a specific origin.

Checkout and payment apps generally respect Markets-level settings without extra work, since Shopify’s checkout is centralized regardless of which storefront domain the customer arrived through. Marketing and personalization apps are more likely to need a second look: anything that builds customer segments based on domain or URL path should be checked against your new subfolder, subdomain, or ccTLD structure to confirm it is still capturing the right audience.

Review your installed app list after adding a market and spot-check anything that depends on URL patterns, cookie scope, or domain-level tracking before assuming it carried over cleanly.

Analytics and tracking setup for multi-domain stores

Running multiple domains or subdomains for different markets fragments analytics by default unless you configure tracking deliberately. A subfolder structure keeps everything under one property in most analytics tools with minimal extra setup, since the root domain stays constant.

Subdomains and ccTLDs require more deliberate cross-domain tracking configuration to avoid treating each market as a disconnected, unrelated site. Without that setup, a customer who starts on your .com and completes checkout on a .de domain may show up as two separate sessions instead of one continuous journey, which distorts conversion attribution.

Segmenting reports by market, rather than relying on default domain-based views, gives a clearer read on which countries are actually performing. This is also where a dip in one market can hide inside aggregate numbers if nobody has set up market-level segments ahead of time, a problem worth catching before a launch, not after muddled data accumulates.

Selling internationally brings country-specific obligations that exist independently of how you structure your domains, and Shopify’s domain tooling does not resolve them automatically. Tax collection rules, consumer protection disclosures, and data privacy requirements vary by country and sometimes by region within a country.

Markets configuration helps you localize pricing and currency, but tax registration, VAT or GST collection, and privacy notices like cookie consent banners typically require separate setup or dedicated apps, and the correct approach depends on where your business is registered and where your customers are located. A merchant selling into the EU, for instance, has different consent and disclosure obligations than one selling only domestically, regardless of whether that market uses a subfolder or a ccTLD.

Confirming the specific legal requirements for each country you target, ideally with a professional familiar with that jurisdiction, is a separate workstream from the domain and SEO decisions covered here, and it deserves its own checklist rather than an assumption that Markets handles it by default.

What actually matters in a multi-market domain strategy

Most advice on this topic treats domain structure as the headline decision, but the structure matters far less than whether redirects, translations, and analytics stay in sync after launch. A subfolder, subdomain, or ccTLD choice made correctly on day one still breaks if nobody checks hreflang tags after the next market change.

The conventional advice undersells operational maintenance. Plenty of guides cover how to pick a URL pattern and stop there, leaving the harder, ongoing work of monitoring redirects and translation publishing as an afterthought. That is backward: the setup decision is only one part of the work, while the drift that follows a market reassignment or a bulk catalog update can quietly cost rankings and revenue over time.

Prioritize building a recurring check, monthly at minimum, that verifies redirects, hreflang accuracy, and localized pricing across every active market. Get that habit in place before worrying about whether a ccTLD will outrank a subfolder.

— Service

How we help merchants scale across markets

Expanding internationally on Shopify tends to surface gaps that a single setup checklist cannot fully close: catalogs that drift out of sync, redirects that break after a reassignment, or analytics that fragment across domains. We build and maintain the systems behind Shopify and BigCommerce engineering for brands managing exactly this kind of complexity.

Quicktoimpress

  • We audit existing Markets and domain configurations to catch misconfigured redirects or hreflang gaps before they cost rankings.
  • We implement domain mapping, catalog localization, and automation so multi-market setups stay consistent as you add countries.
  • We stay embedded through ongoing support, not a one-time handoff, so configurations keep working as your catalog and markets change.

A scoped audit typically leads into a prioritized roadmap, then implementation sprints, then ongoing operational support. Review our capabilities or pricing starting at $3,500 per month for Core capacity, and reach out for a discovery conversation about your multi-market setup.

FAQ

Can Shopify be used internationally?

Yes, Shopify supports international selling through Shopify Markets, which lets you configure localized pricing, currencies, languages, and domains for different countries from a single admin. Managed and self-managed options exist depending on your region, with Shopify Managed Markets automating merchant-of-record tasks in eligible areas.

Which domain is international?

An international domain on Shopify is any custom domain, subdomain, or subfolder assigned to a specific market inside Shopify Markets, such as a ccTLD like .de or a subfolder like /fr. You cannot use your default myshopify.com domain for an international market; a custom domain is required.

Is it better to buy a domain through GoDaddy or Shopify?

Shopify lets you either purchase a domain directly through its platform or connect one bought from a third-party registrar, and both paths work for setting up international markets. The right choice depends on your existing domain portfolio and whether you prefer managing renewals and DNS in one place or keeping registrations with a separate provider.

Is Shopify still worth it in 2026?

Shopify remains a common platform choice for merchants expanding internationally because Markets handles localization, currency, and domain configuration natively rather than requiring custom-built infrastructure. Whether it is the right fit depends on your catalog complexity and growth stage, and merchants with highly complex multi-market needs sometimes bring in engineering support to configure it fully.