Multilingual SEO

How to Translate Shopify Store Pagination, Breadcrumbs and Site Architecture for International Crawling and Indexing

Most Shopify merchants translate their product names and meta titles, then stop. What they miss — and what quietly kills international rankings — is the navigational scaffolding that wraps every page: breadcrumbs, pagination controls, and the URL patterns that connect them. When those elements stay in English on a French or Japanese storefront, crawlers receive contradictory signals and shoppers bounce. This guide explains how to get shopify multilingual site architecture right at the structural level, with concrete steps you can act on today.


Why Structural Elements Matter More Than Most Merchants Realise

Product copy is visible. Navigation is infrastructural. When a crawler lands on yourstore.com/fr/collections/robes/page/2, it needs three things to do its job:

  1. Readable breadcrumbs in the target language, so it understands page hierarchy.
  2. Consistent URL patterns per locale that it can predict and re-crawl.
  3. Correctly attributed canonical and hreflang tags so it doesn't treat page 2 of your French collection as a duplicate of page 2 in English.

Fail on any of these and you're not just losing a ranking signal — you're making it harder for Googlebot to even find the pages you've translated. See Shopify Multilingual SEO: How to Rank in Every Language for the broader ranking context, but the structural layer is what this article focuses on.


Translating Breadcrumbs on Shopify: What Actually Needs to Change

Breadcrumbs on Shopify are almost always rendered in Liquid. A typical snippet looks like this:

<li>{{ 'breadcrumbs.home' | t }}</li>
<li>{{ collection.title }}</li>
<li>{{ product.title }}</li>

The | t filter pulls from your theme's locale files (locales/en.json, locales/fr.json, etc.), so static labels like "Home," "Back to," and category separators will update automatically if those keys exist in every locale file.

Checking Your Locale Files

Open your theme code and navigate to locales/. You should see one file per language you've activated. A minimal French breadcrumb block in locales/fr.json looks like this:

"breadcrumbs": {
  "home": "Accueil",
  "you_are_here": "Vous êtes ici",
  "aria_label": "Fil d'Ariane"
}

If those keys are missing, the Liquid filter silently falls back to the English default. You'll see "Home" in a French breadcrumb trail — not because translation failed, but because nobody told the theme what the French equivalent is.

What you need to audit:

  • Every static string in your breadcrumb Liquid snippet
  • The aria-label on the breadcrumb <nav> element (screen readers and structured data parsers both read it)
  • The BreadcrumbList schema markup, which needs name values in the page's target language

Dynamic values — collection.title, product.title — come from Shopify's translation layer, so if you've translated those fields correctly they'll appear in the right language automatically. The gap is almost always the static strings.

For collection-level translation best practices, How to Translate Shopify Store Category Pages and Collection SEO for Every Language covers the field-by-field approach.


Pagination: The Part Most Translation Guides Skip Entirely

Shopify generates paginated collection URLs in a predictable pattern: /collections/handle/page/2. When you activate a second language, that becomes /fr/collections/handle/page/2. The pages exist and are crawlable — but several things can still go wrong.

Canonical Tags on Paginated Pages

Shopify's native multilingual storefront assigns each locale its own canonical. Page 2 of your French collection should canonicalise to itself (/fr/collections/robes/page/2), not to page 1 and not to the English equivalent. Verify this by pulling the page source and checking the <link rel="canonical"> value. If it points to /collections/robes (the English root), crawlers may ignore the paginated content entirely.

rel=prev/next: What's Still Useful

Google officially deprecated support for rel=prev and rel=next in 2019, so these tags no longer influence Google's understanding of pagination sequences. However, Bing's published crawler documentation still lists them as a supported hint for content discovery — though Bing has not publicly confirmed the degree to which these tags affect ranking for Shopify-style paginated storefronts specifically. The practical guidance: implement them if your theme already supports it and the cost is low, but don't treat them as a ranking lever. The more reliable signal for both engines is a well-structured XML sitemap that includes paginated URLs per locale.

For sitemap specifics, How to Translate Shopify Store XML Sitemap and Submit It to Google for Each Language walks through the submission process end to end.

Pagination UI Labels

"Next," "Previous," and "Page 2 of 5" are almost always hardcoded strings or theme translation keys. The same locale file audit that applies to breadcrumbs applies here. Check locales/fr.json for keys like pagination.next, pagination.previous, and pagination.current_page. If they're absent, add them. Visible untranslated UI labels are a minor but real user-trust signal — and How to Translate Shopify Store Pagination, Sorting and Category Navigation for International Markets goes deeper on the full navigation layer.


URL Structure and Crawl Depth Across Locales

Shopify's native multilingual approach uses language subfolders (/fr/, /de/) rather than subdomains. This is generally the right call for most merchants — it concentrates domain authority and simplifies crawl management. If you want the full case for subfolders, Subfolders vs Subdomains for Multilingual Stores: Which Wins? lays it out with specifics.

What matters architecturally is crawl depth consistency across locales. If your English collection pages sit two clicks from the homepage, your French collection pages should also sit two clicks from /fr/. Inconsistent depth means shallower crawl budgets for translated pages, which means slower indexing.

A quick way to check: use Screaming Frog with your /fr/ subfolder set as the start URL. Compare the average click depth of French collection and product pages against the English baseline. A difference of more than one level is worth fixing.

Internal Linking Within Each Locale

Every internal link on a French page should point to other French pages — not back to English URLs. This is easy to miss when you're copying navigation menus or related-product blocks from your default theme. Shopify's routes object in Liquid will generate locale-aware URLs automatically when used correctly ({{ routes.root_url }} respects the active locale), but custom hardcoded links will not. Audit these carefully.


Hreflang: The Glue That Holds Multi-Locale Architecture Together

Breadcrumbs tell crawlers where a page sits in your hierarchy. Hreflang tells them which pages are language equivalents of each other. Both signals need to be present and consistent.

The most common hreflang mistake on paginated pages is pointing all page-2-and-beyond URLs to the root collection URL in the alternate language. If /fr/collections/robes/page/2 has an hreflang pointing to /collections/dresses (not /collections/dresses/page/2), Google sees a mismatch and may discount the signal. Each paginated URL needs its own correctly matched hreflang set. Hreflang on Shopify: The Complete Guide to International SEO Tags covers the full implementation, including the x-default value and self-referencing requirements.


Running This as an Audit, Not a One-Time Fix

Site architecture changes when you add collections, rename products, or restructure navigation. That means breadcrumb locale files, pagination labels, and hreflang sets need to stay current as your store evolves.

Build a lightweight recurring check into your workflow:

  • Monthly: Pull a Screaming Frog crawl of each locale subfolder. Flag any page where the breadcrumb <nav> aria-label is in a different language than the page content.
  • On every new collection: Verify the collection title is translated before publishing, so breadcrumbs and paginated pages inherit the correct string from day one.
  • After theme updates: Re-check locale files. Theme updates frequently overwrite locales/*.json additions you've made manually.

Using Google Search Console to Monitor Your Multilingual Store explains how to set up per-locale performance tracking so you can spot indexing gaps early rather than after rankings drop.


A Note on Tooling

The following section describes what StoreLingo handles automatically — mentioned here because the manual alternatives above are time-consuming at scale.

StoreLingo translates Shopify's native content fields (product titles, collection descriptions, page content, meta fields) using AI, and keeps a glossary to ensure brand terms stay consistent across every locale. It detects content changes and re-translates only what's updated, which matters for the architecture concern here: when a collection title changes in English, the French breadcrumb and pagination label that inherit from it need to update too, not stay stale.

What StoreLingo does not replace is the Liquid locale file work described above — static theme strings like "Home" and "Next page" live in your theme code, not in Shopify's content API, so they require the manual locale file edits covered in this article.

Add StoreLingo on the Shopify App Store →


FAQ

Do I need to translate the URL slugs in my breadcrumb path, or just the visible labels? Shopify generates URL handles from your collection and product titles. If you translate the title field, Shopify creates a translated handle in the locale subfolder automatically — so /fr/collections/robes rather than /fr/collections/dresses. The visible breadcrumb label and the URL slug will align as long as the content fields are translated before the collection goes live.

Google deprecated rel=prev/next in 2019 — do I need to do anything about pagination for SEO? The most reliable approach post-deprecation is to ensure every paginated locale URL is included in your XML sitemap and has a correct self-referencing canonical tag. This tells crawlers the pages exist and are intentional, which covers both Google and Bing without relying on a hint that Google no longer processes and whose current weight in Bing's algorithm for Shopify storefronts is not publicly confirmed.

My breadcrumbs show "Home" on the French version of my store even though everything else is translated. What's wrong? Almost certainly, the breadcrumbs.home key is missing from your locales/fr.json file. Open your theme code, find the locale file for French, and add the key with the value "Accueil". Then find every breadcrumb-related Liquid string in your theme snippets, check which translation keys they reference, and add any missing keys to all active locale files. The | t filter will not throw an error when a key is missing — it silently returns the English fallback, which is why this bug is easy to miss.

Choose from 47 languages

StoreLingo translates products, collections, pages and articles with AI — review and approve by default. On paid plans from Starter, auto-translate is off by default and publishes new or updated products automatically. Keep your brand terms consistent.

Add to Shopify →