A language switcher does not prove that the browser understands the text's language. Check each version's declaration. LANGUAGE, NOT COUNTRY W3C recommends declaring the main HTML document language with lang on the html element. Do not choose a language code from a flag. Ukrainian uses uk; a website section's name and its language declaration are separate things. FOLLOW A REAL JOURNEY Open the home page, a domain listing, an article and an inquiry form in each language. Compare the visible text with lang in the source HTML. Then use the switcher and repeat. Record pages that retain the previous language's declaration. PASSAGES IN ANOTHER LANGUAGE Individual passages may need their own lang. Changing the attribute does not translate content. Do not automatically label every domain name as a different language: consider context and pronunciation with an editor. CHECK THE EXPERIENCE Listen to the page with a screen reader, ideally with someone who uses one. Include instructions, errors and inquiry confirmations. An accurate declaration helps tools process text, but it does not guarantee Google rankings. When comparing domains in the catalogue, plan the future website's languages early. Store the findings alongside the translation inventory: this is a concrete acceptance check that a polished language switcher can easily conceal. Image: a new AI photoillustration for this article; a conceptual scene, not a documentary photograph. Domain catalogue: https://domainevery.com/en/domains Primary sources: https://www.w3.org/International/questions/qa-html-language-declarations https://www.w3.org/International/articles/language-tags/index.en
