Search How to add a three-language website to Google Search Console and Yandex Webmaster
One domain property or three URL prefixes, where to place hreflang for Google and Yandex, and what to check after adding a three-language website.
Cookies on this site
The site stores what it needs itself: your theme, your animation setting and this choice. Analytics, marketing and external services switch on only with your consent. You can change your mind at any time. More about cookies
Search
First, find out whether Google knows about your site at all. Open Search Console and check the Page Indexing report, where each page is listed with its status and reason. If the site is under two weeks old, time might be the only issue. If it’s older, the reason could be a block left in the code or in the robots.txt file, or language versions that Google treated as duplicates. Below are the checks in the order you should do them, along with timelines from Google Help.
According to Search Console Help, Google needs about a week to start crawling and indexing a new page or website, while new content on an existing site takes a few days. Indexing is never instant, even if you submitted a crawl request directly.
| Item | Timeline from Google Help |
|---|---|
| New site or page starts getting crawled | About a week |
| New content on a known site | A few days |
| Crawling discovered URLs | Up to several weeks |
| Validating a fix in the report | Usually up to two weeks, sometimes longer |
| Issue remains in the report after it disappears | 90 days |
| Requesting a recrawl | If the change isn’t noticed for a week or more |
Google drops a page from search results if its code contains a noindex directive. It comes in two forms: a <meta name="robots" content="noindex"> tag in the <head> section or an X-Robots-Tag: noindex header in the server response. If the site was built on a staging site, check whether that directive was carried over with the code.
It’s easy to get confused by the robots.txt file. Google doesn’t support a noindex directive inside robots.txt. And if robots.txt blocks a page from crawling, the bot won’t see the noindex on it, which means the URL can still appear in search results. Google Help advises removing the block in robots.txt and using noindex if you need to hide a page. You can check what the crawler received with the URL Inspection tool in Search Console. After removing the block, Google has to visit the page again. According to Google Help, that sometimes takes months, so request a recrawl.
| Status | What it means according to Google Help | What to do |
|---|---|---|
| Crawled, currently not indexed | The page was crawled and not indexed; it may be indexed later, and there’s no need to resubmit it | Improve page content, wait |
| Discovered, currently not indexed | Google knows the URL but hasn’t visited it yet, probably postponing it to avoid overloading the site | Wait, check site speed |
| URL marked noindex | A noindex directive was found, and the page is not indexed | Remove the block if the page should appear in search |
| URL blocked by robots.txt | The page was blocked by the robots.txt file | Remove the block |
| Duplicate without user-selected canonical | The page is a duplicate of another, and Google picked the primary version on its own | Specify the canonical page |
| Page with redirect | The URL redirects to another address and isn’t indexed itself | Check that the redirect leads to the intended page |
| Soft 404 | The page shows “not found” but returns a success code | Return a 404 for deleted pages, add content for empty ones |
If you have versions in Armenian, Russian, and English, there are two common traps. The first is duplicate content: according to Google Help, language versions are treated as duplicates only if the page’s main content remains untranslated. A page where only the menu is translated while the body text stays in Russian is one such case. The second trap is hreflang tags: each language version must specify itself and all the others. If two pages don’t link to each other, the tags are ignored. Google determines a page’s language on its own from the text, not from the tag. You can read about how URL structure works in the article on a three-language website.
The check is simple: open the source code of the Armenian page and see if the <head> section lists the URLs of all three versions. Then open the Russian page and confirm that it references the Armenian one too.
Even an indexed site can be impossible to find if the words on its pages don’t match what your customers type. In Armenia, people search for the same service in Armenian, Russian, and English, and some may type Armenian words using the Latin alphabet. I don’t have search volume data for those queries, so take that with a grain of salt. Open the queries report in Search Console to see what terms people are already using to find you. The title and description of each language version should be in that version’s language.
Yandex requires a separate setup: you submit the site to Yandex Webmaster. Yandex holds a small market share in Armenia; details are in the article on Google and Yandex.
If the issue is a block in the code or in robots.txt, that’s a quick fix rather than months of SEO, and you don’t need to pay for ongoing SEO just for that. If there are no blocks and the site is still missing from search, the real work on content and structure begins: SEO promotion from 130 000 ֏ a month, with results evaluated no earlier than 3 months in, and no ranking guarantees. Send me your website’s URL, and I’ll check its status and let you know what I see.
SEO so people can find you in search, in Armenian, Russian and English. Reports in plain language.
Talk to us
Phone us, write to us or send a short brief. You get a clear next step and, after the first conversation, a written estimate.
Animation is off because your system asks for reduced motion.