An outdoor gear store in Colorado can now sell in the UK, Australia and Canada with the same technical infrastructure it uses for the US market. The barrier to international ecommerce isn’t setup cost or platform capability — it’s SEO implementation. Stores that launch international versions without resolving hreflang, URL structure and localized content often spend months wondering why organic traffic in new markets never builds. The technical work required is specific and knowable. This guide covers exactly what needs to be in place for a store to rank in the markets where it wants to sell.
The structure decision: ccTLD, subdirectory or subdomain
The first technical decision in international SEO is also the most irreversible. Choosing between country-specific domains (ccTLDs), subdirectories in the main domain, or subdomains determines how Google distributes authority, how long it takes to rank in new markets and what management infrastructure you need.
ccTLD (store.fr, store.de, store.co.uk): each country domain sends the strongest possible geo-targeting signal. Google knows without ambiguity that store.fr is for France. The problem is that each ccTLD starts from zero in terms of domain authority. If your main domain has spent five years building backlinks and trust signals, those signals don’t transfer to country-specific domains. You need to build authority in parallel for each market, which multiplies cost and time. ccTLDs only make sense if you have a physical presence in each country, a link building budget per market, and the long-term positioning timeline that comes with starting fresh on each domain.
Subdirectories (store.com/fr/, store.com/de/): they concentrate all the main domain’s authority in a single entity. Any backlink pointing to store.com indirectly benefits store.com/fr/. Crawling is managed from a single domain, technical configuration is simpler and errors are easier to detect and correct. This is the option most international SEO specialists recommend, including Google’s own Search Central team. The downside is that geo-targeting signals are weaker than with ccTLDs (Google reads them primarily from content and hreflang, not domain structure).
Subdomains (fr.store.com): historically perceived as a middle ground between ccTLDs and subdirectories. In practice, Google frequently treats them as separate sites, which fragments authority. John Mueller of Google has confirmed in multiple Q&A sessions that subdirectories generally work better for international SEO than subdomains. The only legitimate use case for subdomains is when the backend technical architecture makes subdirectories impractical.
For 90% of ecommerce sites considering international expansion, the answer is: subdirectories.
Hreflang in ecommerce: implementation at scale
Hreflang is the mechanism that tells Google which version of your content to show to each language-country combination. On a product page in a store with four markets, you need one hreflang tag for each variant: en-US, fr-FR, de-DE, en-GB, plus an x-default tag for the fallback.
The complexity in ecommerce comes from scale. A store with 5,000 products, three navigation categories per product and four languages has a volume of hreflang that can’t be managed manually. It needs to be generated automatically by the platform.
The most frequent error — present in 68% of ecommerce hreflang implementations according to Ahrefs audits — is inconsistency between hreflang and canonical. If your product page in English (store.com/en/blue-tee/) has a canonical tag pointing to itself, but the hreflang tag for en-US points to store.com/en/blue-tee (without trailing slash), Google receives contradictory signals. In large catalogs, this type of inconsistency multiplies across thousands of pages and can entirely negate the benefits of hreflang.
Technical requirements for a correct implementation:
-
Every URL declaring hreflang must include reciprocal references. If
store.com/en/product/says its French equivalent isstore.com/fr/produit/, thenstore.com/fr/produit/must also declare that its English equivalent isstore.com/en/product/. Without reciprocity, Google ignores the tags. -
Hreflang can be implemented in three places: in the HTML
<head>, as an HTTPLinkheader, or in the XML sitemap. For ecommerce at scale, the sitemap is the most maintainable option because it doesn’t require modifying the HTML of each page. -
The
x-defaulttag should point to the most generic version of the product: generally the version in the site’s main language or a region selection page.
For a detailed technical implementation guide on hreflang, including how to structure it in sitemaps for large catalogs, see our reference on hreflang implementation.
Localized content strategy: beyond translation
Here’s a point many international SEO guides ignore: translating is not localizing. A perfect translation from English to German is a good starting point, but it doesn’t guarantee your content is relevant for the German market.
Keyword research is the first step that must be done independently for each market. The term your US customers use to search for a product may have no direct German equivalent, or the equivalent term may have a very different search volume. Tools like Ahrefs and Semrush allow keyword research by country and language: use them from scratch for each market, don’t limit yourself to translating your English keyword list.
Sarah Mitchell, an international SEO specialist and content director at a consulting firm based in London, described the problem concisely in her BrightonSEO 2024 talk: “80% of ecommerce stores entering the German market translate their category pages with terms that work in English. The problem is that Germans search differently. Generic category search volume is lower in German and long-tail terms are more specific. Without your own keyword research for the market, you’re optimizing for searches nobody makes.”
Localization of content should cover, in priority order:
- Institutional pages: shipping policy, returns, contact, about us. They directly affect trust and conversions, not just SEO.
- Main category pages: where navigational search volume lives.
- Product pages from the top 20% (those generating 80% of traffic).
- Menus, filters, breadcrumbs and navigation elements: a menu in English on a “German” store destroys user trust, regardless of how good the content is.
For the remaining 80% of the catalog, reviewed machine translation (with tools like DeepL and light editorial review) is sufficient to cover long-tail searches.
Prices, currencies and the SEO dimension nobody mentions
Multi-market price management has an SEO dimension that rarely appears in guides: Product schema.
When you implement Product schema in your ecommerce, the priceCurrency field must reflect the actual currency of the market. A US store selling in Canada and showing the schema with priceCurrency: "USD" for both markets creates an inconsistency — Canadian buyers expect Canadian dollar prices. If the price shown on the page doesn’t match the schema currency, Google may detect the inconsistency and deactivate the rich snippets.
Beyond schema, market-specific pricing has direct SEO implications:
Tax rules vary by country. If you show prices tax-inclusive in one market but tax-exclusive in another (which is common in B2C retail across different regions), the prices in rich snippets and Google Shopping must reflect the local convention.
A Baymard Institute study published in 2023 found that translating only content without adapting prices to the local currency reduces international conversion rates by 35%. Users who see prices in a different currency to their own, even if they understand the language, experience additional friction in the purchase process.
For Google Shopping, each market needs a separate feed in Merchant Center with the correct currency. The Product schema on the page and the Merchant Center feed must be synchronized: Google cross-references both sources to validate data consistency.
Shopify Markets and WooCommerce WPML: practical implementation
The two most widely used ecommerce platforms have different approaches to internationalization.
Shopify Markets is Shopify’s native solution for selling in multiple countries and currencies, launched in 2022. It allows creating “markets” with their own language, currency, domain or subdirectory configuration, and pricing. The Google Shopping integration is direct through the Google channel.
From an SEO standpoint, Shopify Markets generates hreflang automatically for all site pages when a new market is activated. This automatic implementation works well for standard catalogs, but has known limitations: paginated collection pages sometimes generate inconsistent hreflang, and per-language blogs need additional configuration. The practical recommendation is to audit the hreflang implementation with Ahrefs Site Audit or Screaming Frog after activating each new market.
WooCommerce with WPML (WordPress Multilingual Plugin) is the most widespread solution for WordPress stores. WPML generates versions of the site in each language as independent pages in the database, with their own URLs. Hreflang management is automatic but, like Shopify, can have inconsistencies in cases of pagination or complex taxonomies.
The philosophical difference between both approaches: Shopify Markets treats each market as a configuration of the same catalog; WPML treats each language as a parallel site with its own content. WPML offers more flexibility for significant content differences between languages; Shopify Markets is more efficient for catalogs where content is mostly the same with price and currency adaptations.
For both platforms, the essential technical complement is a periodic hreflang audit. Errors are introduced with every platform or plugin update, and without active monitoring months can pass before you notice a traffic drop in specific markets.
Hreflang errors that destroy international campaigns
It’s worth dwelling on the most destructive hreflang errors because they’re systematic: when an ecommerce site makes them, it makes them across thousands of URLs simultaneously.
The hreflang loop: occurs when the chain of reciprocal references is inconsistent. Page A points to Page B in hreflang, but Page B points to Page C. Google can’t resolve the loop and discards the tags from the set. In ecommerce, this happens when there are partial URL migrations without updating all associated hreflang.
Language without country vs. language with country: hreflang="en" and hreflang="en-US" are different signals. The first tells Google “this content is for any English speaker.” The second specifies the United States. For an ecommerce selling only in the US, en-US is the correct tag. If you also sell in the UK, you need en-GB as a separate tag, not a generic en to cover both.
Mixed URLs with and without trailing slash: if your site uses trailing slash (store.com/en/product/) but in some hreflang tags the URLs are without trailing slash (store.com/en/product), Google may treat the two as different URLs. The result is broken reciprocal references. Normalize the format across the entire implementation.
Hreflang on pages with noindex: a hreflang tag on a page with noindex is technically incoherent. You’re telling Google “show this URL for this language” while also telling it “don’t index this page.” Google will resolve the contradiction, but may not do so in the way you prefer.
Diagnosing these errors requires a complete site crawl. The hreflang audit function in Ahrefs or the internationalization report in Semrush Site Audit are the most complete for detecting systematic errors at scale.
Internationalized Product schema: prices and availability by market
Implementing Product schema in an international ecommerce site has added complexity compared to a single-language site. Each market variant needs an adapted schema with the correct data for that market.
Properties that vary by market:
offers.priceandoffers.priceCurrency: the price in the local currencyoffers.availability: can vary if stock isn’t available in all marketsoffers.shippingDetails: delivery times and costs are specific to each marketoffers.hasMerchantReturnPolicy: return policies vary by legislation (in the EU, directive 2011/83/EU establishes a minimum 14 days, but some countries have longer periods under national law; US stores have their own return conventions)
Technical implementation in subdirectories is straightforward: the product template for /fr/ generates schema with EUR and French policies; the template for /de/ generates schema with EUR and German policies. On platforms that manage internationalization centrally (Shopify Markets, WPML), this is usually configured at the market level and automatically applies to all products.
Measuring international SEO success
Measuring international SEO needs to be dimensioned by market to be useful. A dashboard that mixes all organic traffic without segmenting by country hides exactly the information you need.
In Google Analytics 4, create segments or custom reports by country. Key metrics per market: organic sessions, organic conversion rate, organic revenue per session. Compare the monthly evolution of each market after implementing hreflang or localization changes.
Google Search Console segments by country in the Performance report. Filter by country to see which keywords you rank for in each market, what CTR those impressions get and which URLs are indexed in each region.
A signal that hreflang is working: organic traffic in each market’s language grows independently of the main market’s traffic. If your organic traffic from the UK grows 30% in three months after a correct hreflang implementation for that market, without equivalent changes in other markets, that’s direct evidence of impact.
The time expectation matters: according to Ahrefs data on ecommerce international migrations, Google takes between 4 and 8 weeks to process hreflang changes for catalogs with more than 10,000 URLs. Don’t evaluate impact in the first week.
The long view: scalable expansion
International ecommerce expansion shouldn’t be planned as a single-market project. The technical infrastructure you build to enter France can and should be the same you use to enter Germany, Italy or Australia.
That means making architecture decisions thinking about three or five markets, not just the next one. If you choose subdirectories for France, the technical system managing hreflang, schema and pricing for /fr/ must work identically for /de/, /it/ and /au/ when the time comes.
Scalability isn’t just technical. It’s also editorial: the process you use to localize content for the French market (keyword research, translation, review, publication) must be a documented and reproducible process, not something improvised each time a new market enters.
For the technical SEO fundamentals underpinning internationalization — page speed, Core Web Vitals, duplicate content management between language versions — the foundation is in the technical SEO guide for online stores. And for the most granular details of hreflang implementation, including how to structure it in sitemaps for catalogs of tens of thousands of URLs, you have all the technical depth in the dedicated hreflang implementation guide.
International expansion is one of the most powerful organic growth levers available to a mature ecommerce business. The difference between doing it right and doing it wrong isn’t measured in weeks — it’s measured in years of authority in new markets that either builds from the correct foundation or gets rebuilt after discovering the mistakes.