Shopify Multilingual SEO: URLs, Hreflang, Sitemaps
Shopify generates most multilingual SEO signals for you: each published language gets its own URLs, canonical URLs are set on all pages, hreflang tags are on by default for markets with a distinct domain, subdomain or subfolder, and sitemaps include the market-specific URLs. What you still own is the quality of the translation, the translated URL handles, the metadata, and checking that the output is correct. This article explains each signal, using Shopify's help center and developer documentation, which change often, so re-verify before acting.
How does Shopify generate language URLs?
Shopify's help center says each published language gets its own URLs. The domain structure comes from your market setup: its SEO page says you can use subfolders, subdomains or top-level domains for each market. Subfolders (yourstore.com/fr/) share domain authority with the primary domain, are the lowest effort and are what Shopify recommends for most stores; subdomains (fr.yourstore.com) need DNS setup and are described as treated as separate sites by some search engines; country domains (yourstore.fr) give the strongest local signal but need separate registration and management.
Google's guidance supports using a separate URL per language and lists the same structures, noting that URL parameters are not recommended. That is why a language switcher that only changes a cookie or parameter is not enough for SEO. The structural trade-offs are in subdirectories vs subdomains vs ccTLDs.
How does Shopify handle hreflang?
According to Shopify's help center:
- "Hreflang tags are generated automatically based on your market and language configuration."
- They are on by default for all stores, update when you change market domains or languages, and apply only to markets with a distinct domain, subdomain or subfolder.
- An
x-defaulttag points to your primary domain. - You can turn automatic hreflang off (the help center places the setting under Online Store → Preferences in the summary we saw; confirm in your admin), but you must then add your own to the theme, and Shopify advises against it for most stores.
Google's requirements still apply to whatever is output: every version must link to all others and to itself, URLs must be absolute, and language-region codes must be valid (a region alone is invalid). A correct set for a store with a French subfolder looks like this:
<link rel="alternate" hreflang="en" href="https://yourstore.com/products/linen-shirt" />
<link rel="alternate" hreflang="fr" href="https://yourstore.com/fr/products/chemise-en-lin" />
<link rel="alternate" hreflang="x-default" href="https://yourstore.com/products/linen-shirt" />
Do not assume this is what you have. View the source of a product page in each language and check that the URLs match the live, indexable pages. Third-party sources discuss cases where automatic tags go wrong after customizations or app changes; we could not verify those claims against Shopify documentation, so treat them as reasons to test, not as established facts. Background is in the hreflang guide.
Can I translate Shopify URL handles?
Yes, for the resources Shopify supports. The help center describes the steps: open Translate & Adapt, choose the language and content, and enter the translated handle in the URL handle field. Three points matter:
- It is manual. "Automatic translation doesn't include URL handles, so you need to add a translated URL handle manually for each language."
- Redirects are created. "When you create a translated URL handle, a redirect is created from the default language URL to the translated URL."
- Sitemaps follow. "Sitemaps are updated to include translated URL handles."
Shopify's developer example shows a locale-prefixed product path, /es/products/great-shirt, so the language prefix is added while the structural segment stays as is. Sources outside Shopify's own pages say that handles can differ by language but not by market, and that segments like /products/ stay fixed; we did not find that stated on Shopify's help pages, so test it on your store.
Are translated handles worth it? Google does not require translated words in URLs. They can help users and local search terms, but each one is manual work and a redirect to maintain. A reasonable rule is to translate the handles of high-value products, collections and content, and leave the rest. Weigh it with translating URLs and slugs for SEO. Note the documented limit: if a merchant changes a product's handle afterwards, redirects are not supported for language-specific URLs, so settle handles before launch.
What about meta titles and descriptions?
Search results show the title and description of each language version, so an English description on a French page wastes the translation. In Shopify, search engine listing fields (page title and meta description) belong to each resource, and Translate & Adapt is the documented place to translate resource content. The pages we could retrieve do not explicitly list those fields as translatable, and the developer page we read does not mention them, so verify in your own Translate & Adapt screen that the SEO title and description fields appear for products, collections, pages and articles in each language. Then spot-check the rendered <title> and <meta name="description"> in the page source. Keyword research should be per market too: see international keyword research.
How do canonicals and sitemaps work?
Shopify's help center says canonical URLs are set automatically on all pages to point to the primary version of each page, and that each version has a self-referencing canonical plus hreflang tags connecting all versions. That matches Google's recommendation to include a canonical on the page itself and keep it in the same language when using hreflang.
For sitemaps, Shopify says they are generated automatically and include all market-specific URLs, and each URL includes hreflang annotations. Adding a market updates the sitemap. To confirm, open /sitemap.xml on your store, follow the child sitemaps and look for your translated URLs and xhtml:link entries. Since hreflang can come from tags or sitemap, check that both agree. See multilingual XML sitemaps.
What are the known limits and pitfalls?
From the documentation we could verify:
- Untranslated fallback. Missing translations show default-language content at the new URL, which can create near-duplicate pages. Publish a language only when key templates are translated.
- Redirects. Shopify's help center says automatic redirection applies to customers but search engine crawlers are excluded. Google separately warns that redirecting by guessed language can keep users and crawlers from reaching all versions; make sure visitors can always switch language by link. See auto-redirect by language or location.
- Markets without distinct URLs. Automatic hreflang applies only to markets with their own domain, subdomain or subfolder. A market sharing the primary URL gets no alternate-language tags.
- Handle changes. Language-specific URLs lose redirect support if a product handle changes later.
- Apps and proxies. The developer documentation states app proxies do not support translations. Check any app that renders storefront text.
- Manual hreflang. If you switch off the automatic tags, you own them.
Also review the 301 behavior when you switch URL structure: moving from subfolders to subdomains changes every URL.
How do I audit a Shopify multilingual store?
- Pick five templates (home, collection, product, blog article, page) and view source in every language.
- Confirm the
<html lang>, canonical, hreflang set and translated title and description. - Open the sitemap and match the URLs.
- Test the language selector with JavaScript disabled to confirm it is real links.
- Use URL Inspection in Search Console on one URL per language and market.
Key takeaways
- Shopify's help center says hreflang, canonicals and sitemaps are generated automatically for markets with distinct URLs; verify rather than assume.
- Translated URL handles are manual per language, create redirects from default-language URLs, and update the sitemap.
- Settle handles before launch; later changes lack redirect support for language-specific URLs.
- Confirm in your own admin that SEO titles and descriptions are translated, because the documentation we reviewed does not state it.
- Avoid publishing languages with large untranslated areas.
Sources
- International SEO for markets – Shopify Help Center – automatic hreflang, canonicals, sitemaps, URL structures, redirection
- Translating URL handles in Translate & Adapt – Shopify Help Center – manual handles, redirects, sitemap updates
- Localization and translation – Shopify Help Center – language URLs and default-language fallback
- Manage translated content – Shopify.dev – handle redirect limitation, app proxies, locale URL example
- Localized versions of your pages – Google Search Central – hreflang requirements
- Managing multi-regional and multilingual sites – Google Search Central – URL structures and automatic redirect guidance
Frequently asked questions
Does Shopify add hreflang tags automatically?
Shopify's help center says automatic hreflang tags are on by default, generated from your market and language configuration, and apply only to markets with a distinct domain, subdomain or subfolder. An x-default tag points to your primary domain. You can turn them off, but then you must add your own.
Can I translate Shopify product URLs?
You can translate the URL handle for each language in Translate & Adapt, added manually since automatic translation skips handles. Shopify's help center says a redirect is created from the default-language URL. The fixed path segments, such as /products/, are not described as translatable in the pages we checked.
Are translated pages in the Shopify sitemap?
Shopify's help center says sitemaps are generated automatically, include all market-specific URLs, and carry hreflang annotations for each URL. It also says sitemaps are updated to include translated URL handles. Open your own sitemap and check a few translated URLs to confirm.
Why are my translated Shopify pages not indexed?
Typical causes are untranslated content that duplicates the default language, blocked or redirected URLs, or markets without distinct URLs. Inspect one affected URL in Google Search Console, then check its canonical, hreflang set and whether the page is in the sitemap.