Cookie settings

Choose what to allow. The site always stores what it needs; everything else stays off until you turn it on.

Choice

A website in Armenian, Russian, and English: how to keep Google from getting confused

  • 30 October 2026
  • 5 min read
  • Harutyun Elibekyan

Give each language its own URL and distinct pages, link the versions with hreflang tags, and add a language switcher rather than redirecting visitors automatically. This helps Google show people the right page for their language and keeps it from mistaking the versions for duplicate content. On our site, Armenian sits at the root address, Russian is in the /ru/ folder, English is in /en/, and page URLs are identical across all three languages.

Which URL structure to choose

Google’s documentation on multilingual and multiregional sites compares several options. Here is a summary:

OptionExampleWhat Google says
Foldersexample.am/ru/Simple to maintain on a single host. But the server stays in one place, and separating versions from each other is harder
Subdomainsru.example.amServers can be kept in different locations. Visitors might not understand from the URL which audience the version targets
Separate country domainsexample.ru, example.amClear country targeting, but expensive, and each domain targets a single country
URL parametersexample.am?lang=ruNot recommended

For languages spoken within a single country, folders are the simplest approach: you use one domain, keep versions side by side, and link them together. That’s how our site works.

Google’s documentation lays down clear rules for hreflang tags. Every language version must reference itself and all the others. If two pages don’t link back to each other, Google ignores the tags. URLs must be fully qualified, starting with https://. You set the language with a two-letter code (hy, ru, en); you can append a country code after it, but you can’t specify a country on its own. The x-default version acts as a fallback for visitors whose language doesn’t match any option, and it’s intended for a language selector page. There are three ways to implement these tags: <head> elements, HTTP response headers, or a sitemap. Using more than one method at the same time brings no benefit.

PageURLTag
Armenian version/prices/hy, also x-default
Russian version/ru/prices/ru
English version/en/prices/en

Each of the three pages lists all three URLs, meaning three tags plus x-default.

What Google advises against

According to Google’s guidance, you shouldn’t automatically redirect visitors to a different version based on their browser language or IP address: IP geolocation is unreliable. Instead, provide links to the alternative versions and let people choose for themselves. Don’t translate just the template while leaving the main content in a single language; Google notes that this creates a frustrating experience. Stick to one language per page and avoid side-by-side translations. If the main content stays untranslated, Google treats the pages as duplicates.

What to translate

Translate everything the visitor sees: menus, buttons, forms, error messages, search titles and descriptions, and image captions. If you accept card payments, the bank permits a payment interface in Armenian and, where possible, in other languages (clause 3.6 of Ameriabank’s terms), while the document confirming a transaction for sales with delivery must at least be in English (clause 3.7).

Make sure the Armenian version is complete, not stripped down. When most of your clients speak Armenian, that version should be your primary one, with the others added on top.

How to check your versions

  1. View the source code of each version and check the hreflang tags: all three pages must reference the same three URLs.
  2. Click the language switcher: it should take you to the equivalent page in the other language, not back to the homepage.
  3. Read each version from start to finish to ensure no text was left in the wrong language.
  4. Check the pages on a phone to verify that longer words still fit neatly on buttons.

How this affects the price

Each language requires its own copy and search titles, as well as separate layout testing: long Armenian words and button labels have to fit. That’s why a second and third language add to both the cost and the turnaround time. The workload scales through simple multiplication:

Pages in one languageOne languageThree languages
55 pages15 pages
1515 pages45 pages

You can start with a single language and add the others later. If the site structure is built for multiple versions from day one, new languages will slot right into ready-made URLs. We quote the price of adding languages upfront.

When you don’t need three languages

If all your clients speak Armenian and you don’t deal with international customers, start with Armenian. Add a Russian version when Russian-speaking clients ask for it, and an English version when you work with foreign partners and guests. You can find search engine market shares for each of these languages in our article on Google and Yandex. If you already have localized versions that aren’t showing up in Google, check them against the list in our article on why a site isn’t in Google.

We build websites in Armenian, Russian, and English: first setting up the structure for all languages, then filling in as many as you need right now. Tell us which languages your customers use to contact you, and we will suggest a rollout plan.

Sources

Related services

  • Web development

    Websites, online stores and landing pages in three languages, so visitors understand your offer and get in touch.

Talk to us

Ready to talk about your project?

Phone us, write to us or send a short brief. You get a clear next step and, after the first conversation, a written estimate.

Or reach us directly

  • Quick reply to your request or call
  • Languages Armenian, Russian, English
  • Written estimate after the first conversation

Animation is off because your system asks for reduced motion.