How-To · Multilingual SEO
How to Translate a Webflow Store: Products, URLs, hreflang and Metadata, Step by Step
Translating a Webflow store is not one task; it's eight, and the translation itself is only one of them. Stores usually fail at the structural steps — URLs, hreflang, sitemap, metadata — which is why so many "translated" stores never appear in foreign search results. This is the full sequence, in order, with the failure points marked. It applies whatever tooling you use; where Webflow's own tooling stops (it doesn't support ecommerce — see the gap, explained), the steps still stand.
Step 1 — Pick languages from evidence, not vibes
Start where demand already exists: check your analytics and order history for countries that visit or buy despite the language barrier, and your Search Console data for foreign-language queries you already surface for. Two or three languages with proven demand beat ten languages of hope. Every language you add multiplies catalog work, review work and support questions.
Step 2 — Inventory everything that needs translating
List it all before translating any of it: product titles, descriptions and variants; collection names and descriptions; static pages; navigation and footer; transactional text (cart, checkout-adjacent copy, emails where your tooling allows); and the invisible layer — page titles, meta descriptions, image alt text, URL slugs. Stores routinely translate the visible 80% and leave the SEO-critical 20% in the original language.
Step 3 — Choose the URL structure: subdirectories
For most stores the right answer is language subdirectories on the main domain — yourstore.com/fr/, yourstore.com/de/. They consolidate all languages under one domain's authority, they're the structure Google's multilingual documentation illustrates most, and they're dramatically cheaper to run than separate sites per country. Subdomains are a workable second choice; separate domains are a maintenance trap for a small team.
Step 4 — Translate the catalog in bulk, as data
Export the catalog and translate it as structured data — fields in, fields out — not by clicking through product pages. Machine translation (DeepL, Google, or a current LLM) is the sensible first pass for a whole catalog; it's what every major tool uses under the hood. Keep product IDs attached to every string so translations land back on the right product, and keep a glossary of terms that must never be translated literally: brand names, product line names, technical terms.
Step 5 — Rewrite metadata per language; don't just translate it
Titles and meta descriptions decide whether your translated pages rank and get clicked. A literal translation of your English title often misses the words buyers in that language actually search with. Adapt titles and descriptions per language — same intent, local phrasing — and translate URL slugs where the platform allows it. This step is the difference between a translated store and a store that gets found.
Step 6 — Implement hreflang like you mean it
hreflang tells Google which language version to show which visitor. It is also the most-misimplemented tag in multilingual SEO: an Ahrefs study of 374,756 domains found 67% had at least one error. The recurring failures, from that same study:
- Missing x-default — 56.3% of the domains with errors.
- Missing self-referencing tag — 18%. Every page must list itself.
- Tags pointing at redirects or dead URLs — 16.9%. Every target must be a live 200 page.
- Missing return tags — 15.3%. If page A points to page B, B must point back to A, or both are ignored.
Run the checklist on every publish, not once at setup: catalogs change, and hreflang rots quietly.
Step 7 — Publish a multilingual sitemap
Your sitemap should list every language version of every URL (with hreflang alternates declared in it or in the page head). Without it, translated product pages can sit undiscovered for months — Google is under no obligation to find your /fr/ tree by crawling alone, especially on a store where the language switcher is the only link path.
Step 8 — Review, then measure per language
Before launch, have the translations for your top-selling products reviewed by a native speaker if you can; machine translation is a draft. After launch, measure per language in Search Console: are the localized URLs indexed, and for which queries? Indexing problems show up here first — wrong versions indexed, or none — and they're fixable precisely because you can see which layer broke.
The honest footnote for Webflow stores
Steps 3–7 are exactly the layers Webflow's own Localization would handle for a regular site — and exactly what it doesn't do for ecommerce. Doing them by hand for a full catalog is why most Webflow stores stall at Step 2. It's also the gap LocalePress is being built to close, validated by presale before a line of it ships: bulk catalog translation plus steps 3–7 as a hosted service, priced by catalog size. The founder presale — $15, fully refundable, built only if 5 founders pre-order by December 7, 2026 — is how we're testing whether store owners actually want it.
FAQ
Subdirectories, subdomains or separate sites — which structure is best?
For most stores, language subdirectories (yourstore.com/fr/) on the main domain. They keep all languages under one domain's authority, are the structure Google's own documentation walks through most often, and are far cheaper to maintain than separate sites.
Can I just machine-translate everything and publish?
You can, and it's how most stores should start — but review matters. Google's scaled-content policy targets bulk auto-generated pages with no added value, and unreviewed machine translation is the textbook example. Translate in bulk, then review at least your top sellers, and lock brand and product terms in a glossary.
Why is my translated store not showing up in Google?
The usual causes, in order: the translations aren't separate crawlable URLs (a switcher widget); hreflang errors (missing x-default, missing self-references, tags pointing at redirects); no multilingual sitemap, so pages were never discovered; or titles and meta descriptions were never translated, so the pages rank for nothing.