Checking multilingual indexing after a Cloudflare Workers migration
I work on GoSIM.ch , a travel eSIM shop. We recently moved from self-hosted Django to Cloudflare Workers and added Simplified and Traditional Chinese. Tonight I checked whether the translated pages were actually reaching search engines. The files existed, the pages rendered, and the sitemap included them. Google and Bing still showed different stages of discovery. Count the translations, then…
The article discusses the process of checking multilingual indexing after a migration from self-hosted Django to Cloudflare Workers for a travel eSIM shop, GoSIM.ch. The company added Simplified and Traditional Chinese translations to their site, and after verifying the translations and their presence in the live sitemap, they proceeded to check the indexing status with Google and Bing.
They found that both Chinese homepages were submitted and indexed by Google, but the student-discount guides were not indexed yet. However, Bing's sitemap report showed its last crawl was from November 1, while Google's latest fetch was on November 6, and Bing had no usable crawl record for the four Chinese URLs they sampled. The article emphasizes the importance of understanding the differences between published, submitted, and indexed in the context of multilingual content changes.
Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.
