A Russian link opens in English for an overseas visitor, while a search bot receives only one language version. Automatic language detection can prevent other pages from being accessed reliably. Start by checking the direct URLs for each version and whether visitors can choose a language manually.
An explicit language URL should open directly
It is more reliable to check how versions are discovered through regular links with accessible href attributes. Official documentation.
The service at /ru/service/ and its English version at /en/service/ should have their own clear URLs. A visitor should be able to open the Russian URL intentionally, even if their browser is set to English. An automatic decision based on IP or Accept-Language—the preferred language sent by the browser—cannot know this intent. Set the behavior for /ru/, /en/, and the root / separately. At the root, you can offer a choice or a prompt; an explicit language version must remain reliably accessible. This prevents every address from effectively leading to just one language, making the other content impossible to open directly.
Check both versions and the site root
| Site entry point | What is known about the language | Expected response | What to check without cookies |
|---|---|---|---|
| /ru/service/ | Explicitly a Russian URL | Preserve access | Different Accept-Language values |
| /en/service/ | Explicitly an English URL | Preserve access | Correct content |
| / | Neutral entry point | Separate policy | Check the choice |
| Language switcher | User preference | Corresponding page | Not always the homepage |
Repeat the request with a different browser language
Request each language URL with Accept-Language: ru, with Accept-Language: en, and without this header. Use a clean session, then repeat with a saved choice. Record the status, Location, and final text. If the language choice saved in a cookie differs from the browser header, decide in advance which choice to preserve. Do not treat one tester's successful redirect as universal behavior. Server-side geolocation is an additional variable if it is actually used; check it through authorized infrastructure and logs rather than inferring it from a single public request made from another IP.
For the Russian URL with an English request language, run this in a terminal or send it to a developer:
curl -sS -H 'Accept-Language: en' -D headers.txt -o response.html 'https://example.com/ru/service/'headers.txt will contain the first response, without following the Location redirect. For the specified /ru/service/, expect the Russian page even with Accept-Language: en. Check the language of response.html separately from the header text. Replace example.com with your domain; this GET request does not change site settings. curl documentation.
The Russian URL should keep serving the Russian page. Then request /en/service/ with Accept-Language: ru. For /, check the language choice separately. curl does not run JavaScript, so also check client-side switching in a browser.
Preserve manual language choice
Use regular language-switching links with correct href attributes. A client-side prompt can suggest another language while allowing visitors to stay on their chosen version. If the server continues to detect language at the root, do not apply that rule unconditionally to /ru/ and /en/. Check direct entry from a bookmark and an external link. A person's IP and browser settings may differ from their preference, so the interface should let them control their choice. Ask the site owner to confirm that an explicit language URL should be preserved and that an automatic prompt can be shown at the root.
Check canonical and hreflang
Canonical specifies a page's preferred URL, while hreflang identifies its language versions. For the Russian page, check that canonical points to its own URL and hreflang points to the English translation. For the English page, check the reciprocal link and that canonical points to the English URL. Do not automatically canonicalize all translations to one language: they have different texts for different visitors. Make sure hreflang points to the corresponding content, not the homepage. Do not add a fake pair for a translation that does not exist. Check the final URLs and statuses of every destination. These tags describe the relationships between available pages, but they do not fix incorrect routing or guarantee that a search engine will always show the version you selected.
Switch languages on a nested page
The language link should lead to the corresponding service, not automatically to the homepage. After refreshing and opening a saved link, the version should remain accessible. Compare all the main text: a translated title with unchanged content does not mean the language version is working.
Read also: International SEO: how to promote a website in different languages and Hreflang: how to set up multilingual SEO. Website checks are available on the reChecker technical audit page.