The site has two language versions, the switcher works, hreflang is declared — and yet the search engine sees only one language. We break down five real configurations where the language markup is formally there but works against the site.
A bilingual site is not two versions of the text but an agreement with the search engine: this page is in Ukrainian, here is its counterpart in another language, show each person the one that suits them. The agreement is formalized with the hreflang attribute.
The problem is that a broken hreflang looks exactly like a working one: the site opens, the switcher works, the markup is there in the code. The error only becomes visible when you look for it deliberately.
Below are five real configurations we have come across while measuring Ukrainian sites.
The most complex case we have seen. On a lingerie store, language markup had been added by two different mechanisms at once — probably by the theme and a separate extension that did not know about each other.
The first set declared ru-ru, uk-ua and pl, pointing to root URLs. The second declared ru, x-default and uk, pointing to URLs with the /ua/ prefix. On top of that, the link declared as uk-ua served Russian content, and the same was true of the Polish one.
For a search engine this is not “two opinions” but a contradiction it resolves at its own discretion — which most often means ignoring both sets.
On a military gear store, the language versions really did exist — the root one and /ua/. In the markup they were declared as uk-UA and uk-RU.
The second code does not mean “Russian for Ukraine”: the first part is the language, the second is the region. uk-RU reads as “Ukrainian language, Russia region”. The correct code for a Russian-language version of a Ukrainian site is ru-UA.
An extra touch on the same site: <html lang="ru"> on the root version, meaning the page’s language attribute contradicted what hreflang declared.
A separate variant of this error turned up in a sample of construction companies: the same language code declared twice — one site out of eight checked on 8 August 2026.
The site is bilingual, hreflang is declared correctly — but the sitemap has URLs in only one language. The second version exists for a person using the switcher and does not exist for a crawler that starts from the sitemap.
From real measurements:
<html lang="uk"> and hreflang for Ukrainian is declared;There is no pattern in which language “disappears” — and that is the best proof that the cause is technical, not content-related: that is simply how the sitemap generator ended up configured, and nobody checked the result.
A subtler case. The language version exists, the interface is translated, <html lang="uk"> is set correctly — but the <title> and meta description stayed in the original language.
We saw this on the lingerie store: the Ukrainian-language /ua version had a translated interface and the correct language attribute, but its meta tags remained Russian. To a search engine such a page looks like a duplicate — meta tags are the primary way it tells pages apart.
This is the classic partial localization mistake: what is visible in the layout gets translated, and what is visible only in search results does not.
The reverse case: the markup declares language versions that physically do not exist — a leftover from plans or from a template. The search engine follows the link, gets a 404 or a redirect to the same page, and stops trusting the entire group.
A separate variant is hreflang with only one entry pointing to the page itself, plus x-default. Formally not an error, in practice markup that does nothing: a group of one page does not connect it to anything.
hreflang. There should be as many as you have language versions, plus x-default if needed.uk-UA for Ukrainian, ru-UA for the Russian-language version of a Ukrainian site. Each code should appear exactly once.<html lang> with what hreflang declares — they should match.<title> and meta description on the second language version — they should be translated, not inherited.The markup itself takes hours: it is a block of links in <head> generated from the list of a page’s language versions. What can be harder is untangling a situation where the theme and an extension both add markup at the same time: first you need to find both sources and disable one.
The most expensive item is usually the fourth — translating meta tags on every page of the second language version. This is no longer technical work but content work, and on a catalog of thousands of items it requires either a translator or automation followed by spot checks.
The figures are measurements taken on specific dates (August 2026); we deliberately do not name the sites. The market sample of construction companies that the duplicated language code example comes from consisted of eight sites — so the “1 of 8” share describes those particular sites, not the market.
Your opinion helps us create better content
Help others learn about it - share the article on social networks
Thank you for helping us grow
Writes about what he builds himself: online stores on OpenCart, applications on Next.js, integrations and site speed. The articles carry measurements and checks a reader can repeat on their own project, not general advice. Commercial development since 2015.
Answers to common questions on the topic
ru-UA: the first part is the language, the second the region. The code uk-RU, which we found on one measured site, reads as "Ukrainian language, Russia region" — not what was intended.
Technically yes, and it is a real defect: a theme and a separate extension add markup independently of each other. We saw a site where two sets contradicted each other, and the URL declared as the Ukrainian version served Russian content.
The most common reason is that the sitemap contains URLs for only one language. Crawling starts from the sitemap, and the second version remains reachable only through internal links.
No. If the title and meta description remain in the original language, the page looks like a duplicate to a search engine — meta tags are the primary way it tells pages apart. This is the classic partial-localisation mistake.
If page A declares page B as its language version, page B must declare A in return. One-sided declarations are ignored — the group is treated as incomplete.
Subscribe to our newsletter and receive useful tips, insights and news about web development, marketing and business.
Technical SEOOn 17 September 2026 we recounted in the web archive what losing our own store along with its domain looked like from the outside: 2,378 captures of the home page in March 2022, the first 301 on the first of April, the last capture of our content on 18 May. We show what the archive restores and what it does not.
Technical SEOFrom 2 August to 3 September 2026, our IndexNow script submitted six sitemap file URLs to Bing instead of pages, and every submission came back “successful”. We break down why the 200 code proved nothing and how to check in 15 minutes what exactly your module submits.
Site performanceOn 17.08.2026 an audit showed a CLS of 0.2283 on our website’s desktop homepage. The cause turned out to be the font: the ch unit in a paragraph and a skewed decorative band. We break down which tips measurably did not help, what got us to 0.0056 and how to check your own site.
