> For the complete documentation index, see [llms.txt](https://developer.esw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.esw.com/shopify/shopify-native/configuration/setup-automatic-country-and-language-redirection.md).

# Setup Automatic Country and Language Redirection

Automatically route shoppers to the right market and language using location and browser settings.

{% hint style="danger" %}

#### Managed Process

* Configuration is implemented by ESW.
* Contact your ESW onboarding manager.
  {% endhint %}

Automatic redirection routes shoppers to the best storefront experience. It uses **location** and **browser language**.

<div data-with-frame="true"><img src="https://content.gitbook.com/content/OZrcZKoZhyUFlsuSu228/blobs/SlrblpTyVuuGMMHw3yxI/image" alt=""></div>

{% hint style="warning" %}

### Prerequisites

* Your markets are configured in **Settings → Markets**.
* Your languages are added, translated, and published.
* Languages are assigned to the right markets. Refer to  [Languages & Domains](/shopify/shopify-native/configuration/languages-and-domains.md) for more info.
  {% endhint %}

### Enable country/region redirection

This redirects shoppers to the correct market. It can change domain, subdomain, or subfolder.

{% stepper %}
{% step %}

### Open Preferences

From your **Shopify Admin**, go to **Online Store → Preferences**.
{% endstep %}

{% step %}

### Turn on Country/Region

In **Automatic redirection**, enable **Country/region**.
{% endstep %}

{% step %}

### Save

Click **Save**.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Automatic redirection does not replace a manual selector. Add country/language selectors to your theme, or use a selector app.
{% endhint %}

### How country/region redirection behaves

#### Markets using dedicated domains

Dedicated domains include:

* Dedicated domain (example: `example.ca`)
* Subdomain (example: `ca.example.com`)
* Subfolder (example: `example.com/en-ca`)

Shoppers are redirected to the matching market URL. Search engines can index each market URL separately.

#### Markets using a shared domain

Shared domain means multiple markets use the same domain. Shopify adjusts content without changing the domain.

Example:

* US market: `example.com` in `USD`
* Canada market: `example.com` in `CAD`

Search engines won’t index separate market domains.

### EU behavior (ccTLD)

EU legislation restricts some automatic redirects. If a shopper visits a **country-code top-level domain (ccTLD)**, Shopify does not auto-redirect them to a different ccTLD.

Example:

* French shopper visits `example.de`
* They are not redirected to `example.fr`

If you use a non-country domain (like `.com`), automatic redirection can apply.

{% hint style="info" %}
For EU stores, consider a geolocation or recommendation app. Use it to suggest the “right” store and let the shopper choose.
{% endhint %}

<details>

<summary>EU ccTLD list</summary>

Common EU ccTLDs:

`.at`, `.be`, `.bg`, `.hr`, `.cy`, `.cz`, `.dk`, `.ee`, `.fi`, `.fr`, `.de`, `.gr`, `.hu`, `.ie`, `.it`, `.lv`, `.lt`, `.lu`, `.mt`, `.nl`, `.pl`, `.pt`, `.ro`, `.sk`, `.si`, `.es`, `.se`, `.eu`

</details>

### Enable language redirection

Language redirection switches to the best-matching language. It uses the shopper’s browser language.

#### Requirements

* The language is added to your store.
* The language is published.
* The language is assigned to the relevant market.
* Translations exist for the storefront content.

Example:

* Domain: `example.ca`
* Default language: English
* Browser language: French
* Result: shopper lands on `example.ca/fr`

{% stepper %}
{% step %}

### Open Preferences

From your **Shopify Admin**, go to **Online Store → Preferences**.
{% endstep %}

{% step %}

### Turn on Language

In **Automatic redirection**, enable **Language**.
{% endstep %}

{% step %}

### Save

Click **Save**.
{% endstep %}
{% endstepper %}

### Related topics

<table data-view="cards"><thead><tr><th>Topic</th><th data-card-target data-type="content-ref">Link</th></tr></thead><tbody><tr><td>Languages &#x26; Domains</td><td><a href="broken://spaces/69bGsllGv04t8wHIHruV/pages/0418d191c245bb5f8df7b834e0d8ae79a29a34b1">Broken link</a></td></tr><tr><td>Create a New Market</td><td><a href="broken://spaces/69bGsllGv04t8wHIHruV/pages/a0a2eadad4c5ff61afd8a05174598e97ac510f88">Broken link</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.esw.com/shopify/shopify-native/configuration/setup-automatic-country-and-language-redirection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
