To localise a Shopify store for European markets, set up a separate Shopify market per country, give each one its own subfolder or ccTLD, then replace machine output with human-adapted copy on product pages, navigation, metadata and checkout. Shopify handles the currency, hreflang and URL scaffolding automatically — it does not handle tone, in-market keywords, or EU compliance text. Those three are where UK stores lose rankings and conversions.
Most UK stores we work with are not starting from zero. Markets are live, Translate & Adapt has been run once, the German storefront exists — yet sales from it stay flat. At Marketing Translations UK, our specialists work only on marketing and ecommerce content, so we see this root cause repeatedly: the platform layer was finished and the language layer was skipped. Here is what needs fixing, in the order that matters.
What Shopify Markets Covers For European Markets, And What It Does Not
Shopify Markets localises your infrastructure, not your message. Thinking of it as two layers makes the gap obvious.
The platform layer covers pricing, rounding rules, shipping zones, duties, tax handling, domains and URL structure. This is included on all paid plans and it is solid. You should use all of it.
The content layer covers whether your headline lands with a French buyer, whether your German product title matches what German shoppers actually type into Google, and whether your returns wording reads as trustworthy in Dutch. Shopify’s auto-translation fills this layer with output that is grammatically fine and commercially dead.
The visible symptom is a hero banner converting at UK levels in the UK and a fraction of that in Spain, because the promise was converted word by word rather than rebuilt. The same failure mechanism at campaign scale is explained in why machine translation fails for marketing campaigns in Europe.
Decide Your Url Structure Before You Translate Anything
Choose this first, because changing it later means redirecting every translated page you have already paid for. For most UK stores expanding into the EU, subfolders are the right default.
| Structure | Example | Best for | Trade-off |
|---|---|---|---|
| Subfolder | yourbrand.com/de/ | Most UK stores; the first one to four EU markets | Shares your existing domain authority — the fastest route to ranking |
| ccTLD | yourbrand.de | Brands with real local presence, a warehouse or a local entity | Strongest local trust signal, but each domain starts from zero authority |
| Subdomain | de.yourbrand.com | Rarely the best pick | Splits signals without the trust benefit of a country domain |
Start with subfolders, prove one market, then graduate a winning market to a country domain once it justifies the SEO cost of starting again.
One related mistake worth avoiding: do not switch on every available language for every market. A France market carrying an indexed Spanish version wastes crawl budget on pages nobody will click.
The Multilingual Seo Errors That Cost You European Rankings
Shopify generates hreflang tags automatically for configured markets, but automatic does not mean correct. Untranslated pages, headless builds and half-published languages all produce broken signals. Google’s own hreflang documentation is worth bookmarking, since the rules are stricter than most Shopify guides let on.
Run this check before you scale spend on any market.
Validate hreflang after every structural change. Look for the alternate link tags in your page source and confirm every language version points back at all the others, including itself. A one-directional set is worse than none.
Translate your URL slugs. /products/chair should become /produkte/stuhl. An English slug on a German page is a weak relevance signal and an obvious tell to the buyer.
Localise meta titles and descriptions separately from body copy. A German page with English metadata will lose the click in the results page before anyone sees how good the translation is.
Do keyword research inside each language. Converting your English keyword list rarely matches how Germans or Poles search. The literal translation of your best UK term is frequently a term nobody uses.
Generate and check a sitemap per market. Submit each one in Search Console and monitor indexation per language rather than as a total. A market that is not indexing will look fine in an aggregate report.
Never rely on hreflang to excuse thin content. Search engines will index half-translated pages happily. They simply will not rank them.
The Rollout Order For Your First Eu Market
Do one market properly before doing four badly. A single fully localised German store will outperform four half-translated ones every time.
- Pick the market on evidence. Use your existing analytics — where are the EU sessions, add-to-carts and abandoned checkouts already coming from? That country is your first market, not the one that sounds most exciting in a planning meeting.
- Build the platform layer. Create the market, set currency and price lists, map the subfolder, enable duties, configure shipping zones and tax handling.
- Research keywords natively. Before a single word is written, find out what that market types when it wants your product. This determines your titles, slugs and metadata, so it has to come before translation, not after.
- Adapt the money pages by hand. Homepage, top collections, top products, navigation, checkout, returns and delivery. Getting product descriptions right matters more here than most stores expect, since a page that reads as machine-translated costs the sale before checkout is even reached.
- Publish, then validate. Check hreflang, slugs, metadata and the market sitemap in Search Console. Do this after publishing, because half of these break at the moment of going live.
- Measure for 60–90 days, then repeat the same playbook for market two.
Configuration Details That Trip Up A Shopify Store For European Markets
A few Shopify-specific settings cause more problems than they should.
Price rounding. Shopify will convert £50 into whatever the exchange rate produces unless you set rounding rules or a local price list. A threshold displayed as €57.43 tells a buyer instantly that this store was built for someone else’s country.
Duties at checkout. Post-Brexit, an unexpected customs bill on the doorstep is the single biggest driver of refused EU deliveries and chargebacks. Enable delivered-duty-paid so the total is visible before payment.
VAT and IOSS registration. Handle this before volume builds rather than after. It is an administrative job with a lead time, and it is easier to sort out at ten orders a week than at two hundred.
Local payment methods. These matter more in Europe than in the UK, and a card-only checkout underperforms across most of the continent. Which methods matter depends heavily on the country — the country-by-country picture for France and Germany is in selling online in France and Germany.
Product safety information. Products sold into the EU need safety details and a responsible-person contact, readable in the language of the country of sale. Automated safety wording is a genuine risk rather than a quality issue. Confirm your specific obligations with a compliance adviser.
Frequently Asked Questions
Is Shopify Translate & Adapt Good Enough On Its Own?
It is a reasonable starting layer for bulk content and lower-value pages such as long-tail products and blog archives. It is not enough for headlines, product descriptions, checkout copy or compliance text. Those need human adaptation, because the machine converts words while your buyer responds to tone and intent.
How Many Languages Should A Uk Store Launch With?
One, done completely. Depth outperforms breadth here. Launching four half-finished languages splits your attention, dilutes crawl budget and produces four underperforming storefronts instead of one profitable one.
Do I Need A .De Or .Fr Domain To Rank In Europe?
No. Subfolders inherit the authority your main domain has already earned, which is usually the faster route to visibility. A country domain becomes worthwhile once a market is proven and you have genuine local presence — a warehouse, an entity or a local support line — to justify starting from zero.
Will Translated Pages Create Duplicate Content Problems?
Not if hreflang is correct and each version is genuinely distinct. Problems appear when the same English copy sits on several market URLs, or when hreflang is broken by unpublished languages. Validate the tags after every structural change to your store.
Should I Use A Translation App Or Export The Content?
Apps are convenient for keeping content in sync and are fine for bulk pages. For your money pages, export the copy so a translator can work on it properly and return it with the structure rebuilt rather than the sentences swapped. Most stores end up using both.
Can I Localise Ads And Emails Separately From The Store?
You can, but consistency is what builds trust. When a German ad promises one thing and the German landing page says another in a different tone, conversion drops. Adapt campaign copy and storefront copy together so the whole journey reads as one brand.
Ready To Localise Your Store The Right Way?
Localisation is not a plugin decision — it is a revenue decision, and it rewards stores that treat European buyers as a primary audience rather than an afterthought. The UK stores that win in Germany, France, Spain and the Netherlands are the ones that got the platform layer right and then refused to ship machine output on the pages that carry the sale.
Send us your store URL and the market you are planning first. We will look at what is already live, check the technical setup, and tell you which pages to rebuild before you spend anything on traffic. Request a free localisation review here.
