Shopify international SEO: subfolders vs subdomains

The decision every international Shopify store has to make

The day a Shopify store decides to sell beyond its home country, it has to answer a question that sounds technical and is really strategic: where will the other versions of the store live? There are three common answers. The store can add a folder for each market on the existing domain, such as example.com/fr or example.com/en-ca. It can add a subdomain, such as fr.example.com. Or it can register a separate domain for each country, such as example.fr. Each option affects how search engines understand the site, how authority is shared, how much work the store needs, and how hard it is to change course later.

This article compares subfolders and subdomains in plain terms, explains what Shopify's fixed URL conventions add to the picture, and gives a decision framework you can apply to your own store. It belongs to our coverage of Shopify SEO and links naturally to our guide on international SEO for ecommerce. Shopify's international features change over time, so confirm current options in Shopify's own documentation before you commit to a structure.

What "fixed" means on Shopify

Shopify decides the first part of many URLs for you. Products live under /products/, collections under /collections/, standalone pages under /pages/, and blog articles under /blogs/. You can change the handle that follows, but you cannot remove or rename the prefix on a standard store. That is what people mean when they call the URL structure fixed.

For international SEO the fixed structure has two consequences. First, you cannot translate the prefixes. A French store will still have /collections/ and /products/ in its addresses unless you use workarounds such as redirects or a proxy, which carry their own risks. Search engines handle this without trouble, because the page content and the hreflang annotations signal the language. It is a cosmetic point more than a ranking problem, but some brands care about it for trust and consistency. Second, the handle after the prefix belongs to the item, and translated stores may or may not translate it, depending on the tools you use. Decide whether translated handles matter for your market and test how your tools handle them.

Shopify's international tools, known as Markets, let a store define regions, set languages and currencies for each, and choose how each market is addressed. The options include publishing each language or country as a folder on the primary domain, using a country domain, or using a subdomain. Not every combination is available on every plan, and the details evolve, so treat the following discussion as a framework and not as a feature list.

The three structures compared

Google's published guidance says that all three are workable, and that it can handle each of them. What differs is the effort and the trade-offs, not whether the approach is allowed. Google has also said that it does not treat subfolders and subdomains in a way that makes one automatically better, though in practice simpler structures that keep content together are easier to manage and tend to concentrate signals. There are no guarantees, and the right choice depends on the business.

When subfolders are the right answer

For most Shopify merchants expanding internationally, subfolders are the sensible default. The reasons are practical.

• One site to build authority for. Links and brand recognition earned by the main domain help every market. A new market does not start from zero.
• One property to monitor. A Domain property in Search Console covers everything, and URL-prefix properties let you review each folder separately.
• Less operational overhead. There are no extra certificates, DNS records or hosting arrangements for each market.
• Faster to launch. A new market can be added in the admin without new infrastructure.
• Consistent technical setup. One theme, one set of apps, one sitemap structure, one place to fix a mistake.

The trade-offs are real. A single site means a single point of failure: a faulty template or a manual action affects all markets. Subfolders give a weaker geographic signal than a country domain, so for markets where shoppers strongly prefer local domains, such as some European markets, you may want to supplement with other local signals. And if one market is very large and needs a very different catalog, a different team or different legal entities, the single-site model can become constraining.

When subdomains make sense

Subdomains are a middle path that is chosen more often for operational reasons than for SEO reasons. They fit when a market is run by a separate team, needs a different platform or hosting arrangement or has a materially different business, for example a wholesale store at wholesale.example.com or a regional operation with its own catalog.

From a search perspective, a subdomain is usually treated as closely related to the main domain but not identical to it. Signals are not shared automatically in the way they are across folders. Each subdomain typically needs its own links, its own sitemap and its own monitoring in Search Console. That is manageable for a few large markets, and burdensome for many small ones.

A common pattern is to choose subdomains for flexibility and then discover that the savings are smaller than expected, because the extra setup and the weaker consolidation cost more than they save. If you have no operational reason for separation, subfolders usually serve better.

Country domains: the strongest signal at the highest cost

A country-code domain tells searchers and search engines exactly which country a store serves, and shoppers in some markets trust them more. They also give legal and operational separation. The costs are significant: each domain needs its own SEO program, its own links, its own reviews and often its own content team, and a new domain starts with no history. They are most justified for large, established operations in markets where local presence matters most, or where regulation demands a local entity.

If you are unsure, start with subfolders, build evidence of demand in each market and move a market to its own domain later if the data justifies it. Moving later is possible but requires careful redirects and monitoring, so treat it as a migration. Our guide to platform and domain migration SEO explains what is involved.

Hreflang: telling search engines which version is for whom

Whatever structure you choose, you need hreflang annotations when you publish several versions of the same page for different languages or regions. Hreflang tells Google that the versions are alternates of each other and which one suits which audience, so that a searcher in Canada is shown the Canadian version rather than the American one. Google has said that hreflang is not a ranking factor. It is a signal used to swap the right version into results for the right user.

The rules are strict, and mistakes are common.

• Annotations must be reciprocal. If the English page points to the French page, the French page must point back to the English page.
• Each page should reference itself as well as its alternates.
• Use valid codes. Language codes follow ISO 639-1 (for example en, fr, de) and optional region codes follow ISO 3166-1 alpha-2 (for example US, CA, GB). Region alone is not a valid value.
• Point to canonical, indexable URLs that return a 200 status. Alternates that redirect, error or carry noindex break the cluster.
• Include an x-default for visitors whose language or region is not covered, where appropriate.
• Keep the cluster complete and consistent. If a product exists in only some markets, the annotations should reflect that.

Shopify can output hreflang tags automatically for markets and languages in many themes, which removes much of the manual work. You still have to verify it. View the source of a sample page in each market, confirm that the tags are present, correct and reciprocal, and check that nothing in the theme or an app duplicates or overrides them. Our guide to how Shopify Liquid renders meta tags shows where in the head these tags are printed.

Language versus country: a distinction that shapes the structure

Many stores confuse the two. A language is how people read. A country is where they buy, with its own currency, shipping, taxes and laws. A store may want to serve one language in several countries, such as English in the United States, Canada, the United Kingdom and Australia, or several languages in one country, such as English and Spanish in the United States or French and English in Canada.

This matters because the structure you choose should reflect the real differences. If the only difference between the United States and Canada is currency and shipping, a single English version with market-specific pricing might be enough, and duplicating the entire catalog in separate folders creates near-identical pages that compete with each other. If product ranges, legal copy, units and terminology really differ, separate versions are justified. Hreflang can distinguish near-duplicate versions for different regions, but the more different each version is, the less duplication risk there is and the more value each page offers.

A good rule: create a separate market version when you can offer shoppers something genuinely different or more relevant, such as local pricing, local availability, local delivery information, local language and local examples. Do not create one only to have a page for each country name.

Do not force visitors with automatic redirects

It is tempting to redirect shoppers automatically to the version that matches their IP address. Google's guidance advises against this approach for two reasons. Googlebot crawls mostly from the United States, so it may never see your other versions if every request is redirected to the American one. And visitors sometimes want a different version from the one their location suggests, for instance a traveler or an expatriate.

The better pattern is to let people choose. Show a banner or a country and language selector that suggests the local version, and remember the choice, but let every version be reached by a plain link. Shopify's market features include geolocation tools that offer this suggestion pattern. Configure them to suggest, not to force. The rule to remember is simple: suggest, never force.

Content, currency and localization

Technical structure is only half of international SEO. The pages themselves must be right for the market.

• Translate with care. Machine translation without review often produces awkward text, and awkward text converts and ranks poorly. Native review is worth the cost on your most important pages.
• Research keywords per market. People in different countries use different words for the same product, so translate the intent, not just the phrase.
• Show local currency and prices. Shopify's markets features can handle currency conversion and local pricing. Make sure the price in structured data matches the price visitors see.
• Adapt shipping, returns and legal pages. Shoppers look for local delivery times and rights, and search engines read those signals of relevance.
• Use local payment methods where they matter, as they influence conversion rather than rankings.
• Localize images and examples where practical, including units, sizes and cultural references.

Duplicated English text across several English-speaking markets deserves particular care. Google generally understands that regional versions are alternates, but pages that are word-for-word identical offer no reason to rank them separately. Differences in spelling, currency, availability and local details help justify the separation.

Sitemaps, Search Console and monitoring

Shopify generates a sitemap index automatically, with separate sitemaps for products, collections, pages and articles. When you add markets, check how URLs for each market appear. Shopify may list alternate language versions within the sitemap entries, and the structure can differ between setups, so look at yours directly.

In Search Console, add a Domain property for the whole site, which covers all subdomains and folders, and add URL-prefix properties for each major subfolder or subdomain so you can see performance by market. Note that Google retired the old International Targeting report in 2022, so geographic targeting now rests on your structure, hreflang, language and local signals. Monitor the following:

• Indexing coverage for each market, looking for unexpected exclusions.
• Performance by country and by property, to see whether each version is reaching its intended audience.
• Search appearance and structured data warnings for each version.
• Core Web Vitals field data per market, since visitors in different regions have different connections. Our Core Web Vitals guide explains the metrics.

Performance and hosting for international stores

Shopify serves stores through its own content delivery network, so shoppers in different regions generally receive pages from nearby servers regardless of which URL structure you choose. That removes one of the traditional arguments for country domains, which was hosting location. Performance for international visitors depends far more on what your theme and apps load than on where the server is. Extra apps for translation, currency conversion, popups and reviews can add weight, and visitors on slower mobile networks feel it most. We cover that in the impact of Shopify apps on Total Blocking Time.

Navigation and internal linking across markets

A multi-market store has to help both shoppers and crawlers move between versions without getting lost. A few habits keep the structure clean.

• Link within the market. Menus, breadcrumbs, related products and in-content links on the German version should point to German pages, not to the English originals. A site where every version links back to the primary language creates confusing paths and weakens each market's own structure.
• Offer a visible selector. A country and language selector in the header or footer, implemented as ordinary links, gives crawlers a path to every version and gives people a way to correct a wrong guess.
• Keep sitemaps in step. If a product is unavailable in a market, it should not appear in that market's sitemap or be promoted in its navigation.
• Handle missing translations deliberately. Untranslated pages inside a translated folder look unfinished. Either translate them, hide them in that market or leave them in the primary language and make that choice explicit in the hreflang cluster.
• Be careful with shared content. Blog articles, policies and help pages do not always need a copy in every market. Publish them once in the language they were written in and link to them from the relevant versions, unless you can translate and localize them well.

The principle behind each of these is consistency. A shopper in Germany should be able to complete a journey from the home page to checkout without meeting an English page by accident, and a crawler following links should be able to discover the German version without help from the English one.

Legal, tax and trust points that affect conversion

International selling involves obligations that are outside the scope of SEO but change what a market page must contain. Rules about consumer rights, returns, data protection, product safety labeling, taxes and price display differ between countries and can change. Where the rules require particular information, such as a seller's identity, a returns period or whether prices include tax, the page needs to show it, and shoppers also look for it as a sign of legitimacy.

From an SEO angle, the useful principle is that pages that answer real local questions tend to perform better. If shoppers in a market always ask whether duties are included, or how long delivery takes, answer it on the product and shipping pages for that market. Take legal advice for your own situation, because this article cannot tell you what applies to your business.

Pricing, currency and structured data

Each market version should show the price and currency that shoppers in that market will pay, and the structured data for each product page must match it. If the visible price is in euros and the markup says dollars, search engines may ignore the markup or show a mismatch. Review how your theme and any app outputs the price and currency in each market, using the Rich Results Test on a product page in each version.

Availability works the same way. A product that cannot ship to a market should not show as in stock there. If a shopper clicks through from a result expecting to buy and finds that the store does not deliver, the visit is wasted and the experience is poor. It is better to hide the product from that market or show a clear message.

Changing structure later

Sometimes a store outgrows its first choice. A market that began as a subfolder may justify its own domain, or a collection of subdomains may be consolidated into folders to simplify operations. These moves are possible, and they are migrations, with the risks that implies.

1. Map every old URL to its new equivalent one to one, at page level, not by redirecting everything to a home page.
2. Update hreflang, canonicals, sitemaps and internal links to the new addresses before or at the moment of the switch.
3. Use permanent redirects and keep them in place for at least a year.
4. Set up the new properties in Search Console and, where the tool allows it, use the change of address feature for domain moves.
5. Launch at a quiet time, monitor daily for the first weeks and compare crawl, indexing and traffic with a baseline.
6. Expect a dip. A temporary fluctuation is normal, and a sustained drop is a sign that something is wrong, usually in redirects or indexing.

Because the stakes are high, treat any structural change as a project with a plan, an owner and a rollback. Our SEO migration page describes how we run them.

A pre-launch checklist for a new market

• The market's URL structure is decided, documented and approved by the SEO and development teams.
• Pages are translated or localized by a competent reviewer, and key pages have been proofread by a native speaker.
• Keyword research has been done in the target language and mapped to categories and products.
• Hreflang annotations are present, reciprocal and valid for a sample of every template.
• Canonical tags on each version point to that version's own URL.
• Prices, currency, shipping, taxes and returns information are correct for the market.
• Structured data matches what is visible on each page.
• The country and language selector works with ordinary links, and no forced redirects are in place.
• Sitemaps list the right URLs, and the new market is verified in Search Console.
• Core Web Vitals have been measured for the new market's templates.
• A monitoring plan exists for indexing, performance and errors for the first ninety days.

A decision framework

1. Start with the business model. How many markets, how different are they and who will run them?
2. Ask whether the markets differ enough to need separate versions. If they differ only in currency and shipping, avoid duplicating the catalog.
3. Default to subfolders unless you have a specific reason not to, such as separate teams, separate legal entities or a market where a local domain is essential.
4. Consider subdomains when a market needs operational separation but you still want to keep the brand under one domain.
5. Consider country domains when local trust and legal separation are decisive and you can fund independent SEO programs.
6. Plan the hreflang cluster and the way you will verify it before launch.
7. Plan the content for each market: translation quality, local keyword research and local trust information.
8. Launch one market first, measure and then extend. A pilot exposes problems cheaply.
9. Document the structure so that future developers and agencies do not undo it by accident.

Measuring whether a market is working

A new market needs a scorecard from the first day, so that you can tell the difference between normal slow growth and a problem. Track a small set of measures for each market and review them monthly.

• Indexing. The share of submitted URLs that are indexed, and the reasons for any exclusions. A market where most URLs are "discovered, currently not indexed" after several weeks needs attention to quality or internal links.
• Impressions and clicks by country. Compare the share of traffic from the target country with the share from elsewhere. If the German folder is receiving most of its visits from the United States, hreflang or language signals may be wrong.
• Queries. Check that the queries are in the market's language and match the products you expected, which confirms that the translations and keyword choices are working.
• Conversion rate and revenue. Compare organic sessions, add-to-cart rate and revenue per market. A market with traffic but few orders points to price, shipping, trust or payment problems.
• Speed. Field data per market from Search Console and your analytics, because visitors in different regions can have very different experiences.
• Errors. Redirect chains, 404 pages and structured data warnings per market.

Give each market a realistic period before judging it. Search visibility in a new language usually takes months to build, as described in our guide to how long SEO takes, and early numbers are small. What matters in the first weeks is that the foundations are correct and the trend is in the right direction.

Common mistakes

1. Choosing a structure by default. Decide deliberately, and write down why.
2. Launching many markets at once. Problems multiply, and you cannot learn from the first launch.
3. Duplicating English pages across markets without any real difference.
4. Broken or one-way hreflang. Annotations that are not reciprocal are ignored.
5. Forcing redirects by IP address. It can stop search engines and visitors seeing the right version.
6. Translating without keyword research. Literal translations rarely match how people search.
7. Ignoring local trust factors. Currency, delivery and returns matter for conversion.
8. Forgetting to monitor each market separately. Problems in a small market can hide in the sitewide totals.
9. Relying on apps that rewrite URLs without checking the output. Verify what actually prints and what actually loads.
10. Treating the structure as permanent. You can change it, but only with a proper migration plan.

A worked example

A fictional Shopify store sells specialty coffee equipment from the United States and wants to expand to Canada, the United Kingdom and Germany.

Canada shares a language with the United States and has similar products, so the team creates a Canadian version at /en-ca with local pricing in Canadian dollars, local shipping and returns, and a few localized pages. The United Kingdom differs in spelling, plug standards, voltage and delivery, so it gets a /en-gb version with adjusted product details. Germany requires translation, different regulations and different product names, so it gets a /de version with professionally translated pages and keyword research done in German.

All markets stay on the main domain as subfolders because the business has a single team and wants new markets to inherit the brand's authority. Hreflang is generated by Shopify, then verified by crawling a sample of each template in each market. The store launches Canada first, watches indexing and performance for six weeks, then adds the United Kingdom and finally Germany. Along the way, the team discovers that an app is printing its own alternate links, fixes the duplication and updates its checklist for the next launch.

It is not glamorous, and it works because each decision was made for a reason and each step was verified before the next.

How we help

At AH SEO Agency we help stores choose and implement an international structure that fits their business, then verify it in the rendered output and in Search Console. We map markets, plan hreflang, review translations and keywords, check theme and app behavior and monitor each market after launch. Read about international SEO for ecommerce, see our Shopify Plus SEO page for larger brands or request a free SEO audit. The next article in this series, on Shopify apps and Total Blocking Time, covers one of the most common performance problems for stores of every size.

Summary

• Shopify's URL prefixes are fixed, but you can choose subfolders, subdomains or country domains for each market, and all three are allowed by Google.
• Subfolders are the best default for most stores because they share authority and are simplest to run.
• Subdomains suit separate operations, and country domains suit large, established markets that can fund independent SEO.
• Hreflang must be valid, reciprocal and point to indexable pages, and you should always verify Shopify's output.
• Do not force visitors by IP address, and localize content, pricing and trust information, not only language.
• Launch one market at a time and monitor each in Search Console.