{"id":2889,"date":"2022-07-27T02:11:26","date_gmt":"2022-07-26T23:11:26","guid":{"rendered":"https:\/\/new.seotools-blog.com\/?p=2889"},"modified":"2023-08-27T21:50:13","modified_gmt":"2023-08-27T18:50:13","slug":"movni-versiyi-sajtu-pokrokova-instrukcziya-yak-pravylno-pereklasty-sajt-ukrayinskoyu-movoyu","status":"publish","type":"post","link":"https:\/\/seotools-blog.com\/en\/language-versions-of-the-site-step-by-step-instructions-on-how-to-correctly-translate-the-site-into-ukrainian\/","title":{"rendered":"Language versions of the site: step-by-step instructions on how to correctly translate the site into Ukrainian"},"content":{"rendered":"

<\/span>Language versions of the site: step-by-step instructions on how to correctly translate the site into Ukrainian<\/span><\/span><\/h1>\n

Many of our clients ask similar questions when they apply for a website translation. In order not to repeat ourselves, we have collected for you in this article the information that most often occurs, and which will help you understand how to translate the site correctly and work with language versions. Recently, there are more and more clients who want their site to be translated directly into Ukrainian as well (although not all languages \u200b\u200brequire such an intensive process as Ukrainian). The intensity also lies in the fact that a law on language has come into force in Ukraine.<\/p>\n

<\/span>\"\"Law on the Ukrainian language<\/span><\/h2>\n

On July 16, 2019, the Law of Ukraine On ensuring the functioning of the Ukrainian language as the state language No. 2704-VIII<\/a> entered into force. The purpose of the law is to ensure the priority of the Ukrainian language in more than 30 areas of public life in Ukraine: public administration, media, education, science, culture, advertising, services. According to the law, the introduction of the priority of the Ukrainian language in these areas is proceeding smoothly, some norms have been delayed for 6 months, and even 2-10 years.<\/p>\n

<\/span>Regulations of the law on services and information<\/span><\/h2>\n

The law came into force on January 16, 2021 (18 months after its adoption) and obliges all enterprises to provide information in Ukrainian. Those who don’t<\/p>\n

\"\"<\/h2>\n

will be prosecuted or fined if they ignore warnings about this violation.<\/p>\n

<\/span>What does the law say about commercial and non-commercial sites<\/span><\/h2>\n

The law requires that all sites that operate in Ukraine and provide goods or services to users be available, although in the full version in Ukrainian. The Ukrainian version of the site should be on the main version, without prefixes and slashes (https:site.com\/ua,uk,ua). And it should be loaded by default (Article 27 paragraph 6). That is, when searching, an exclusively Ukrainian site was opened.<\/p>\n

<\/span>Creation of new language versions of sites<\/span><\/h2>\n

If it so happened that the Ukrainian site exists only in a foreign language, then by January 16, 2021, it was necessary to create a Ukrainian version and fulfill all the requirements of the law. Creating additional pages (Google crawler considers similar content from other languages) can be both a plus and a minus. This issue must be approached as responsibly and organized as possible, otherwise the loss of traffic is inevitable. However, the new version of the site is also new traffic. How to turn the weaknesses of this process into strengths and get an additional boost?<\/p>\n

<\/span>Multilingual website is a problem for marketers and SEO specialists<\/span><\/h2>\n

Yes. A truly multilingual site can create certain problems with indexing, problems with canonical pages and duplicates. How is it that, as it were, an increase in pages and the entry of new keys should give more traffic. Because search engines understand that your pages in different language versions are almost the same content, but in different languages. Especially this problem can occur when the site uses one language group.<\/p>\n

\"\"<\/p>\n

<\/span>Everyone thinks that translating the site and putting it on the main version of Ukrainian is easy<\/span><\/h2>\n

 <\/p>\n

one has only to do not complicated manipulations with the plugin and determine in it which version to issue the main one. The main common points are:<\/p>\n

    \n
  • Go to WPML plugin settings (if you have WordPress)<\/li>\n
  • In the settings, set “Default language”. And if you had the default before, then another language is added. Next, change the checkbox to Ukrainian. Thus, Ukrainian becomes the default and any other is not.<\/li>\n
  • We choose how the language for the user is determined. Add hreflang tags.<\/li>\n
  • Choose the order of languages<\/li>\n
  • Adding a language switcher to the site<\/li>\n
  • Updating the sitemap<\/li>\n
  • Submitting the site for re-indexing<\/li>\n<\/ul>\n

    <\/span>Even if you did everything technically correct<\/span><\/h2>\n

    \"\"<\/p>\n

    From a technical point of view, everything is done correctly, but when it comes to the policy of the Google search engine, problems arise. That is, we have two versions: one static page associated with our domain, and another dynamic, where there is a language selector (selected here via ?lang=X).<\/p>\n

    But when Google starts indexing the Russian version of our site, at some point it starts to forcefully re-index all pages.<\/p>\n

    You didn’t redirect or pass the weight of the page, you just put it in the selector. Google understood what was done, and the attitude towards the site will be different now. Now our Russian-language version will be ranked in a new way. It is clear that there are no axioms in SEO. And there is not a big chance that the traffic will not suffer. But practice shows that in most cases this is exactly the case.<\/p>\n

    <\/span>The best way to comply with the law “about MOV” and not lose traffic<\/span><\/h2>\n

    Many are wondering how to comply with the law on the Ukrainian language and\"\" not completely kill the traffic andimage potential of the site. A lot has been said about this on the Internet, but as always, nothing really. Recommend different. From just double redirects between versions to just deleting the “ru” version. Neither one nor the other can be considered a reasonable way because in the first option you transfer the “ru” version to the “RU” subdomain, and the “UK” or “UA” version. But on the main version there was a “ru” version. What will the search engine do? Correctly! The search engine will definitely lower your site and you will lose traffic.<\/p>\n

    In the case of the second option, and this is the removal of the “ru” version, or the closure from indexing, you will lose Russian-language traffic. Which even today is more than 60%.<\/p>\n

    Another separate nonsense on the network is the recommendation to leave it as it is and make a redirect. But you need to understand that a redirect is a redirect. We tell the search engine that this page is exactly the same as it was here, but moved over there.<\/p>\n

    <\/span>The best way to translate a website into Ukrainian<\/span><\/h2>\n

    We do not recommend anything that we have not tested ourselves on our own sites or on client sites. Therefore, regarding language versions, our version can be safely used.<\/p>\n

    In order to transfer site versions and not lose traffic, you need to:<\/p>\n

    -buy a new domain (com,org.ua,in.ua ) but under your brand<\/p>\n

    – make a backup of the site to a new domain<\/p>\n

    -close a new site from indexing<\/p>\n

    -move the versions of the site, where the main version will have the Ukrainian version of the site<\/p>\n

    -open the site for indexing<\/p>\n

    – make redirects from the old site to the new one<\/p>\n

    -set the hreflang attributes and the alternate attribute<\/p>\n

    Thus, you do a one-time redirect. Your website is legal. And search engines understand that you have a multilingual site, and depending on what query the user enters and what position you have on this query, they will show the desired language version to the user.<\/p>\n

    As for the norm of the law, which says that the Ukrainian version should be loaded by default, this is nonsense of the people who wrote this law. If we substitute the Ukrainian version for a non-Ukrainian query, we can get sanctions for cloaking.<\/p>\n

    There is nothing difficult in translating the site into the Ukrainian version and complying with the law on the Ukrainian language. Below will be listed sites that have recently moved exactly as we described. The old URLs will be redirected, and you will see for yourself that everything works.<\/p>\n

    List of sites:<\/strong><\/p>\n

    https:\/\/ubi-pack.com.ua\/<\/p>\n

    https:\/\/ubi-logistic.com.ua\/<\/p>\n

    https:\/\/aph-tehnik.com.ua\/<\/p>\n","protected":false},"excerpt":{"rendered":"

    Language versions of the site: step-by-step instructions on how to correctly translate the site into Ukrainian Many of our clients ask similar questions when they apply for a website translation. In order not to repeat ourselves, we have collected for you in this article the information that most often occurs, and which will help you […]<\/p>\n","protected":false},"author":2,"featured_media":6537,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[45],"tags":[],"class_list":["post-2889","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cases-en"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/seotools-blog.com\/en\/wp-json\/wp\/v2\/posts\/2889","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/seotools-blog.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/seotools-blog.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/seotools-blog.com\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/seotools-blog.com\/en\/wp-json\/wp\/v2\/comments?post=2889"}],"version-history":[{"count":1,"href":"https:\/\/seotools-blog.com\/en\/wp-json\/wp\/v2\/posts\/2889\/revisions"}],"predecessor-version":[{"id":6541,"href":"https:\/\/seotools-blog.com\/en\/wp-json\/wp\/v2\/posts\/2889\/revisions\/6541"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/seotools-blog.com\/en\/wp-json\/wp\/v2\/media\/6537"}],"wp:attachment":[{"href":"https:\/\/seotools-blog.com\/en\/wp-json\/wp\/v2\/media?parent=2889"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/seotools-blog.com\/en\/wp-json\/wp\/v2\/categories?post=2889"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/seotools-blog.com\/en\/wp-json\/wp\/v2\/tags?post=2889"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}