International SEO for Shopify Stores Selling to the EU and UK

If you're running a US-based Shopify store, there's a good chance you're already getting traffic from the UK and Europe. You're just not converting it well.

Most of the time, the setup is the problem. Visitors from the UK and EU reach your store, but small inconsistencies push them away before they place an order. They see prices showing in dollars instead of pounds. The checkout is missing the payment method they normally use, and Google sends them to the US version of the page instead of the local one.

This guide walks through that setup in the order the decisions actually need to happen: URL structure, Markets, hreflang, crawling, compliance, localization, local authority, trust signals, and schema. At each step, what to configure, and where stores quietly lose money.

The EU and the UK are more different than you think

Brexit changed this permanently. Before January 2021, one compliance and tax setup could cover both the UK and the EU. That stopped being true the moment the UK left, and the two have drifted apart ever since.

They now run on separate regulatory frameworks, VAT regimes, product safety rules, and consumer protection laws, with different customs thresholds, checkout requirements, and return expectations. So if your whole European strategy is a single "rest of world" market in Shopify, you are already behind before you have optimized a thing.

In practice, one Shopify Markets configuration cannot serve both markets correctly without a deliberate, separate setup for each. The upside is that Shopify handles this cleanly once it is set up correctly, so the rest of this article walks through how to do so, one step at a time.

1. Choose Your URL Architecture First

The first decision is your URL architecture, and it has to come before you configure a single market in Shopify. Get it wrong, and you are redoing everything downstream, so it is worth a few minutes up front.

Your three options are subdirectories, subdomains, and country-code top-level domains (ccTLDs).

• Subdirectories add a path prefix to your existing domain: yourstore.com/en-gb, yourstore.com/de, yourstore.com/fr. All traffic is consolidated under a single domain, so your existing US domain authority carries over directly. Shopify handles this natively when you add markets and enable international domains.

• Subdomains split your domain at the prefix: uk.yourstore.com, de.yourstore.com. Google treats subdomains as partially separate from the root domain, so authority transfer is weaker than subdirectories.
  
  There are edge cases where this makes sense, primarily when international markets require significantly different site structures, design choices, or app configurations.

• ccTLDs give you a fully local domain: yourstore.co.uk, yourstore.de. Google treats these as the strongest geographic signal.
  
  The problem for US merchants is that you're starting from zero on domain authority in each market, you need to manage separate DNS configurations, and you're committing to long-term investment in link building per market.

The table below provides an overview of which URL architecture is best for you.

How to get started?

For most stores, the answer is subdirectories. You carry your existing domain authority into each new market. Shopify's hreflang implementation works cleanly with this structure, and if a market later grows enough to justify a ccTLD, you can migrate then. It is painful, but possible.

Example of using subdirectories

There is one case where a ccTLD makes sense from day one: when you already own yourstore.co.uk, and it has real organic history behind it. When that is true, keep it and build on it separately rather than redirecting it into a subdirectory, which would throw away years of link equity for no reason.

2. Should You Choose Shopify Markets or Managed Markets?

Shopify gives you two ways to sell internationally, and which one you pick will drive how you handle everything downstream, even though the choice itself has no direct effect on your rankings.

Standard Shopify Markets is included on every Shopify plan. It handles currency display, language switching, market-specific pricing, and basic tax calculation.

You can set up separate domains or subdirectories for each market, control which products are available in each market, and configure shipping rates by region.

The view from the Markets Dashboard. The key is understanding how to use Markets to its limits on all Shopify plans.

What it does not do is collect and remit VAT on your behalf or take on any legal liability for your cross-border transactions. That part stays with you.

Managed Markets (formerly Markets Pro) is primarily available to US-based merchants, with limited availability in Canada and the UK. When you use Managed Markets, Global-e becomes the merchant of record for your international orders. It requires a US-based business with US fulfillment locations and Shopify Payments.

In exchange, they handle customs documentation, guaranteed landed costs, duty and tax collection at checkout, fraud protection on international orders, and local payment methods across 150+ markets. You ship domestically to a consolidation point, and they take it from there.

Is Managed Markets worth it?

Weigh that fee against what it would cost to handle compliance yourself: EU VAT registration and filing, duty calculation software, fraud exposure on international orders, and the day-to-day overhead of cross-border returns.

At lower volumes, doing it yourself might cost less. The crossover tends to sit somewhere around 200 to 500 international orders a month, though it moves a lot depending on your VAT obligations and average order value (AOV).

The table below gives a good summary of both options.

3. Implement Hreflang Correctly on Shopify for UK/EU

Hreflang tags are small labels in the <head> of a page that tell Google that a localized version exists elsewhere and which language and region it is intended for. Leave them out, and Google treats your US, UK, and German pages as duplicates fighting over the same queries, so it ranks one and largely ignores the rest.

Set them up correctly, and each version ranks in its own market instead. It is not a step you can skip, and it is worth an audit once it is live.

On Shopify, Hreflang tags are generated for you once you configure Markets and enable international domains, which makes it feel like a solved problem. But is usually is not. The automatic output is often wrong enough that you have to check it by hand after the initial setup and again after any structural change to the store. Three things go wrong more than the rest, so those are the ones to look for first.

We went through this ourselves when deciding how to handle sherocommerce.com in the UK and Finnish markets.

The first is reciprocity. Every page that lists hreflang alternatives must be referenced by all others in the same set. If your US page points to the UK page, the UK page has to point back to the US page. Miss that return reference on even one page and Google discards the whole cluster for that URL, so a single gap takes down the group with no obvious error to warn you. Screaming Frog's hreflang report catches these quickly.

An example of an audit from Screaming Frog

The second is canonical tags, and they cause trouble precisely because nothing looks broken on the page. Each localized version needs a canonical that points to itself, not back to your main domain. When one hardcoded global canonical points every market version to yourstore.com, you are telling Google to index only the US version, regardless of what your hreflang tags say. Open the page source on your UK and EU pages after launch and confirm that the canonical points to that page, not the home page.

Use Google-aligned validators to catch structural issues

The third is x-default, the fallback for visitors whose language or location does not match any market you have configured. Point it at your main English page or a language selector. Leave it off, and Google decides on its own which version those visitors see, which is rarely the one you would have picked.

Two more cases to keep in mind for US stores. The first is English itself. Expanding from the US into the UK leaves you with two almost identical English pages, yourstore.com and yourstore.com/en-gb, the same language and nearly the same copy. That is the hardest kind of duplication for Google to untangle, and it is usually the first one a US store runs into. The region codes are what separate them: en-us and en-gb tell Google these are two pages for two countries, not one page copied twice. Use a bare "en" and it simply picks one, normally the US version.

The second is treating a language as a market. German is not one market. Visitors from Germany, Austria, and Switzerland all can read German, and their pricing, shipping, and VAT differ, which makes de-DE, de-AT, and de-CH three separate targets. French works the same way across France and Belgium. If you serve a single German page to every German speaker, plain "de" is enough. The moment you split pricing or policies by country, switch to region codes so the right page appears in the right country.

How to implement Hreflang?

The three implementation methods:

1- Via HTML head (recommended for most Shopify stores):

html
<link rel="alternate" hreflang="en-us" href="https://yourstore.com/" />
<link rel="alternate" hreflang="en-gb" href="https://yourstore.com/en-gb/" />
<link rel="alternate" hreflang="de" href="https://yourstore.com/de/" />
<link rel="alternate" hreflang="x-default" href="https://yourstore.com/" />

2. Via XML sitemap (better for large catalogs with hundreds of product pages):

xml
<url>
  <loc>https://yourstore.com/</loc>
  <xhtml:link rel="alternate" hreflang="en-us" href="https://yourstore.com/"/>
  <xhtml:link rel="alternate" hreflang="en-gb" href="https://yourstore.com/en-gb/"/>
  <xhtml:link rel="alternate" hreflang="x-default" href="https://yourstore.com/"/>

3. Via HTTP headers: used for non-HTML resources like PDFs. Not relevant for most Shopify stores.

Go deeper in our Hreflang Audit and Best Practices article

4. Stop Shopify From Redirecting Googlebot

This step can quietly undo everything above it. You can have perfect hreflang, clean canonicals, and market-specific schema, and still watch your international pages get ignored, simply because Google never sees them.

Shopify's geolocation recommendation and most popular geo-redirect apps send visitors to a version of the site based on their IP address. Googlebot crawls almost entirely from US IP addresses. So when Google tries to crawl yourstore.com/en-gb or yourstore.com/de, the redirect bounces it straight back to the US page. Your localized pages get crawled thinly or not at all, and the market you set up never really enters gets indexed.

The fix is to suggest the local version rather than force it. A banner or a small popup that recommends the right market and lets the visitor choose does the job, and Shopify's own geolocation app works this way when you set it to recommend instead of auto-redirect. What you are avoiding is the hard, IP-based redirect that fires before anyone, human or crawler, ever sees the page.

To find out whether it is happening to you, open Google Search Console and run the URL Inspection tool on a UK or EU URL, then look at the page Google actually fetched. If it shows your US content or a redirect back to the US URL, the issue is live. You can confirm it a second way by crawling your international URLs in Screaming Frog with a Googlebot user agent from a US connection and watching whether they resolve or redirect.

5. Check Compliance Non-Negotiables for US Merchants Entering EU and UK

Selling into the EU and UK comes with a compliance baseline that applies to every merchant, regardless of where you're based. These are the laws/regulations that directly affect your Shopify setup.

EU

• GPSR - Every non-food product needs an EU-based Responsible Person named on your listings. In force December 2024.

• IOSS - Collect EU VAT at checkout for orders under €150. No minimum threshold for non-EU merchants.

• Customs duty exemption - From July 1, 2026, the previous €150 customs duty exemption is replaced by a temporary flat €3 duty per item, applying until July 1, 2028. A separate handling fee, widely reported at around €2 per declaration line, is expected later in 2026, bringing the combined charge to roughly €5 per declaration line. C2C shipments between private individuals remain exempt. If you priced EU shipments before this change, recalculate your landed costs

UK

• £135 VAT rule - Collect and remit UK VAT yourself for orders under £135. Shopify does not handle this automatically, HMRC registration required.

• DMCCA - All fees must be visible at the product page level, not introduced at checkout. In force April 2025.

Both markets

• EU AI Act, Article 50: Any AI-powered chat or recommendation tool visible to EU consumers (not UK ones) needs a disclosure. In force August 2, 2026.

• GDPR - Cookie consent, DSARs, and app data governance apply the moment you have EU or UK visitors. Full Shopify setup: GDPR for Shopify Stores.

We covered the Shopify-specific setup in detail in "GDPR for Shopify Stores."

6. What is the Difference Between Translation and Localization?

Shopify's Translate and Adapt app handles most of the mechanical translation work. It integrates with third-party translation providers and can push content across your markets without manual export and import. That part is fine.

Where it goes wrong is when teams treat that machine translation as finished localization. It is only the first half of the job.

Translation converts text from one language to another. Localization adapts content for how people in that market actually search, buy, and communicate.

A German product description translated from English reads like a translation. German shoppers notice. German search behavior also differs; search queries are longer, more specific, and often use compound nouns that a translation engine splits incorrectly or misses entirely. Even if the meaning is still there, an AI crawler will have a hard time indexing your product on AI overviews or LLMs if your PDP language doesn't match the user questions.

At a minimum, these content areas need human review before you publish:

• Product titles and descriptions for your top 20% of SKUs by revenue

• Collection page copy

• Meta titles and meta descriptions (these directly affect click-through rate in local SERPs)

• Checkout and post-purchase emails

• Returns and shipping policy pages

Research keywords in the market, don't translate them

The most common version of this mistake is taking your US keywords and translating them straight across. The translated phrase is often not what people in that market actually type. Sneakers become trainers in the UK, a cell phone becomes a mobile, and in German the term people search is frequently a single compound noun rather than the two-word phrase a translation engine hands back.

Build the keyword list inside each market instead. Run your seed terms through a tool that reports volume by country, Ahrefs or Google Keyword Planner set to the target location, and pull the phrases local shoppers actually use. Then map those terms onto your product titles, collection pages, and meta. That is the difference between a page that is technically in German and a page that ranks in Germany.

7. Build Local Authority in Each Market

Architecture and hreflang are good starting points to get your UK and EU pages into the running, but they don't solve everything. In a new market, you are up against local stores that have spent years earning links in that country, and Google leans on those local signals when it decides who to show.

On subdirectories, your existing US domain authority carries into each market, which is a real head start. But the ranking gap in competitive EU and UK SERPs usually comes down to local relevance signals you have not built yet.

What should you do to move the needle per market:

• Links and mentions from publications and blogs in the target country, on the local ccTLD where you can get them (.co.uk, .de)

• Listings in local directories and marketplaces that shoppers in that market already trust

• Content that answers questions specific to that market: EU sizing, local shipping and returns, country-specific buying guides

• Reviews on the platform that the market uses, Trustpilot in the UK, and Trusted Shops in Germany

This is the slowest part of international SEO and the hardest to shortcut. Start it the day the market goes live, not six months later when you notice the pages are not moving.

8. Apply The Local Trust Signals That Convert EU and UK Traffic

Ranking in the EU and UK SERPs is one job. Turning that traffic into orders/sales is a different one, and it usually comes down to a handful of trust signals that US stores routinely miss.

Payment methods by market.

Payment is where a lot of international carts are abandoned, whether it is a missing local method, a cross-border transaction that fails, or fees that quietly turn a sale unprofitable.

A US checkout, Visa, Mastercard, PayPal, converts poorly in most European markets. Local payment methods vary significantly by country, and missing them costs you orders.

Find the best payment method that makes the most sense for your store

Landed cost transparency

UK and EU consumers expect to see the full price they will pay before they commit to a purchase. Enable duty and import tax estimates at checkout. This is available on all Shopify plans (a 0.5% per-order fee applies), or, as discussed above, Managed Markets handles it automatically. This single change typically has a meaningful impact on international conversion rates, which add to your overall monthly Shopify Costs.

UK-specific trust signals

UK shoppers have strong preference signals that US stores often miss:

• A .co.uk domain or /en-gb subdirectory clearly signaling they're on the UK version of the site

• GBP pricing displayed without requiring a currency toggle

• A UK returns address or explicit UK returns policy

• Terms of service governed by UK law

• A UK phone number or UK-timezone customer support hours

Rankings aside, each of these affects whether a UK visitor trusts the store enough to buy.

9. Apply Schema markup per market

Your product schema, its price, currency, and availability need to match the market the visitor is in. If a UK shopper lands on a page whose structured data still outputs USD, Google can show that dollar price in the UK SERP rich snippet. Now the shopper sees a £ price on the page and a $ price in search, and both your click-through and your credibility take the hit.

Fixing it comes down to making sure your schema pulls market-specific pricing once you have international URLs configured.

If your theme generates Product schema via Liquid, check that the price output reflects the active market currency rather than your store's default. If you're using a schema app, verify that it supports market-aware pricing before assuming it handles this automatically.

The two schemas from the standard and the en-GB localized page

How to Know If It's Working After Launch

Most international SEO work happens before launch, which is exactly why the period after launch is where it tends to go wrong. Merchants think it's set-it-and-forget-it, and problems go unnoticed for months.

To prevent this,  set up Google Search Console per market. Register each international version as its own property or URL prefix. For subdirectories, add yourstore.com/en-gb/ and yourstore.com/de/ as separate URL prefix properties, and monitor each one on its own. Submit the right XML sitemap to each. Without this setup, you have no read on indexing status, hreflang errors, or click performance in any single market.

View from the Google Search Console Performance Tab

When You Might Need a Separate Store

For most US merchants expanding into the EU and UK, a single Shopify store with Markets configured correctly is the right architecture. It only breaks down past a certain point, and it helps to know where that point is before you hit it.

Consider a separate store (expansion store) when:

• Your business operates under different legal entities in different markets, separate tax registrations, separate bank accounts, and separate compliance obligations that can't share a single Shopify Payments account

• You run genuinely different product catalogs per region, different SKUs, different suppliers, and different launch calendars, well beyond pricing or availability

• Your EU or UK operation has its own team that needs independent admin access without touching the US store configuration

• You need fulfillment from EU or UK warehouse locations that require a separate Shopify Payments setup

• You're selling into markets with regulatory requirements that conflict with your US store configuration in ways that Markets can't resolve.

Keep in mind that running multiple stores multiplies your operational overhead: separate theme maintenance, app stacks, SEO programs, and analytics. Treat each expansion store as its own P&L and build your team and processes accordingly before you commit.

How Shero Approaches EU and UK Expansion

We work inside the EU and UK markets ourselves. With clients and offices across the Nordics, EU, and UK, we deal with Shopify's international architecture as practitioners, not from the outside.

Although this post is written from a US merchant perspective, the same can apply to an EU or UK merchant trying to expand in the US. In addition to technical SEO, we suggest addressing compliance first. 

All of it is cheaper to fix before launch than after. If you are planning EU or UK expansion and want a clear read on what your store actually needs, talk to our team. Book a Free Consultation.

FAQs on International eCommerce SEO