Title: Wrong language code Last modified: August 31, 2016 --- # Wrong language code * Resolved [esemlabel](https://wordpress.org/support/users/esemlabel/) * (@esemlabel) * [10 years ago](https://wordpress.org/support/topic/wrong-language-code/) * Ukrainian language code should be ‘uk’ and not ‘ua’. WordPress uses ‘uk’ code, google uses ‘uk’, iso 639-1 table inform to use ‘uk’ [https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes) * For seo-freandly I had to disable predefined Ukrainian language (ua) and manualy add correct one Ukrainian with ‘uk’ code. * Please, fix it. Thank you. * [https://wordpress.org/plugins/qtranslate-x/](https://wordpress.org/plugins/qtranslate-x/) Viewing 6 replies - 1 through 6 (of 6 total) * Plugin Author [John Clause](https://wordpress.org/support/users/johnclause/) * (@johnclause) * [10 years ago](https://wordpress.org/support/topic/wrong-language-code/#post-7446771) * Two-letter language code can be arbitrary and not important for SEO. Locale is what is important for SEO, the one which is shown in and tags of the source. Locale is ‘uk’ on the preset, same as on WP. * You may alter locale shown at front end with option “Locale at front-end” on language configuration page. You do not need to disable the default preset, you may simply edit it as you wish. * Two-letter code ‘ua’ was suggested by other ukrainian people, to make it different from ‘uk’, which rings as “United Kingdom” for most people at first place. Basically, using country code for two-letter language code seems to make better sense in this particular case and it does not hurt SEO. * We should run a survey among ukrainian people to find out what they prefer 😉 * Thank you very much for your suggestion. With the explanation above we will keep preset for now as is and see if more ukrainian people want to change it. * Thank you for using qtx and good luck to you in the further development! * Thread Starter [esemlabel](https://wordpress.org/support/users/esemlabel/) * (@esemlabel) * [10 years ago](https://wordpress.org/support/topic/wrong-language-code/#post-7446772) * Strange thing.. But “United Kingdom” is not a language ). * Since last past years most people are not using countries or flags (your another issue with flags, that seems to be reffered to languages) for targeting languages. I think its’ a big misunderstanding, since the language defines language code, and not a country, whereas people using different languages, even in law. There are lot of discussions about this, for example [http://wplang.org/never-use-flags-language-selection/](http://wplang.org/never-use-flags-language-selection/) * I hope you wiil change view on issue. * Ps. Two-letter language code appears not only in backend as shortname of language( country in your case), but in frontend in URL aslo. In my opinion, using /ua/ instead of /uk/ in URL path can confuse visitors as there are survey Ukrainian language page and not Ukrainian country page. There is big difference. Those ukrainians, who told you using ‘ua’ didn’t consider about linguistic difference. In Ukraine ‘ua’ means abbreviation of country name, not language. We are using‘ ua’ in car signs, domain names and others as it targets country, not language. * Plugin Author [John Clause](https://wordpress.org/support/users/johnclause/) * (@johnclause) * [10 years ago](https://wordpress.org/support/topic/wrong-language-code/#post-7446778) * Well, it is easy to configure it in the way you wish. I personally do not really have a strong opinion either way. It is configured as the first ukrainian person who cared told us to configure it and it stays like this ever since. Whatever ukrainian people want to do, it is up to them, our business is to provide opportunity for them to do whatever they want and such opportunity is provided. I believe there might be some other languages ambiguity too, and the same reasoning would apply to them. * Thread Starter [esemlabel](https://wordpress.org/support/users/esemlabel/) * (@esemlabel) * [10 years ago](https://wordpress.org/support/topic/wrong-language-code/#post-7446779) * > You do not need to disable the default preset, you may simply edit it as you > wish. * The reason why I disabled predefined language and added new one was in loose overrided settings on plugin updates. I don’t know is this ‘feature’ still present in the latest version. * Thread Starter [esemlabel](https://wordpress.org/support/users/esemlabel/) * (@esemlabel) * [10 years ago](https://wordpress.org/support/topic/wrong-language-code/#post-7446781) * Plugin Author [John Clause](https://wordpress.org/support/users/johnclause/) * (@johnclause) * [10 years ago](https://wordpress.org/support/topic/wrong-language-code/#post-7446789) * Editing of preset should survive the plugin updates, the customization is stored in the database. Either way is good, it is not very much important 😉 Viewing 6 replies - 1 through 6 (of 6 total) The topic ‘Wrong language code’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/qtranslate-x_f9f9f9.svg) * [qTranslate X](https://wordpress.org/plugins/qtranslate-x/) * [Frequently Asked Questions](https://wordpress.org/plugins/qtranslate-x/#faq) * [Support Threads](https://wordpress.org/support/plugin/qtranslate-x/) * [Active Topics](https://wordpress.org/support/plugin/qtranslate-x/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/qtranslate-x/unresolved/) * [Reviews](https://wordpress.org/support/plugin/qtranslate-x/reviews/) * 6 replies * 2 participants * Last reply from: [John Clause](https://wordpress.org/support/users/johnclause/) * Last activity: [10 years ago](https://wordpress.org/support/topic/wrong-language-code/#post-7446789) * Status: resolved