<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Seo on Rustam Garifulin</title>
    <link>https://n69.in/blog/seo/</link>
    <description>Recent content in Seo on Rustam Garifulin</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <copyright>Copyright © 2025, Rustam Garifulin.</copyright>
    <lastBuildDate>Thu, 01 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://n69.in/blog/seo/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Language Switchers: The Rules I Follow</title>
      <link>https://n69.in/blog/language-switcher-en/</link>
      <pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://n69.in/blog/language-switcher-en/</guid>
      <description>&lt;p&gt;A language switcher looks like a five-minute task. Put a dropdown in the header, add two items, ship it. Then the bug reports start. Someone lands on a page they can&amp;rsquo;t read and has no idea how to get out. Google indexes the same text under five URLs. A screen reader announces &amp;ldquo;Русский&amp;rdquo; with an English voice and it comes out as gibberish.&lt;/p&gt;&#xA;&lt;p&gt;I recently made &lt;a href=&#34;https://makersew.com&#34;&gt;makersew.com&lt;/a&gt;, a directory of garment manufacturers in Central Asia, bilingual. Below are the rules I followed while building its switcher, and the screenshots come from that site.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
