We Tried Hindi — Not Every Article, Just Three
The result first
We tried an eighth language: Hindi. But not on every article — just three.
The reason is in the numbers Moka pulled for me from our analytics (Google Analytics, the past 28 days, measured since November 8, 2026, this main site only). 197 people visited, from 23 countries. The largest group was the United States, 136 people — about 70%. Japan was second with 20. But when you look at engaged sessions — visits where someone actually read — there were 65 in total, and 56 of those were from Japan. The US brought the most people and only 6 engaged sessions: they arrive, but they do not read. And India, the country this whole idea was about, was not in the top ranks yet.
So rolling an eighth language out to every article at once would have been doing things in the wrong order. We picked three articles and tried Hindi on those. Two are now live: the vulnerability assessment explainer on the Security Lab, and “How to Raise a Smarter Muse” on this site. The third — a cybersecurity basics article — we did not make, on purpose: its Japanese version was still in the middle of being published in all languages, and our rule is to build a language version only after confirming, on the real page, that the original is actually published. We will make it once that is confirmed.
Hello, I am Kurashiki Bouzu (kurashiki-bouzu). Born in 1971, formerly in the funeral business, I now live in an old folk house in Kurashiki, Okayama, talking with my AI butler Moka every day and writing articles.
Our articles already come out in seven languages: Japanese, English, Chinese, Spanish, Korean, French, and German. The other day, the question came up: “What about Hindi?” This is the record of that eighth-language consultation.
The purpose is not the numbers — it is to spread
When talk turns to adding languages, it tends to become a talk about numbers: how many people will come? But my thinking on this was settled long ago.
“The purpose is to spread the Muse & Google Labs.”
The numbers are only a ruler for checking whether the direction is right. If the ruler itself becomes the purpose, you drift toward wherever the numbers are biggest. So this time, too, we looked at the ruler first, and then decided how to proceed.
First, I had the ruler shown to me
I had Moka pull the visitors by country: the analytics figures for the past 28 days, measured from November 8, and for this main site only.
- 197 people visited, from 23 countries
- The most were from the United States: 136 people, about 70% of the total
- Japan was second, with 20 people
Hearing “70% from America” honestly makes me a little excited. But looking a bit further into the numbers Moka gave me, the picture changed.
Sessions where someone properly read — engaged sessions — were 65 in total. Of those, 56 were from Japan. The US had the most people, but only 6 engaged sessions. They come, but they do not read. That is the shape of it.
And India, the star of this story, was not in the top ranks.
So we did not spread it all at once
Readers from India are not visible yet. In that case, rolling an eighth language out to every article at once is the wrong order.
What we decided was to try just three. From the basics shelf, we chose ones close to everyday life:
- The vulnerability assessment article (Security Lab)
- How to Raise a Smarter Muse (this site)
- The cybersecurity basics article (Security Lab)
Why Hindi, among all the languages in the world? In my own words, the reason is this:
“It ranked third among the world’s most used scripts, and India’s IT is thriving.”
There is one more thought at the root of it:
“I find my own mother tongue easiest to read, and I think everyone is the same.”
We will look at the response, and then decide whether to spread it further. Not doing everything without trying, and not giving up from the start either. Put out just three, and read the ruler. That was the approach this time.
The result: two, plus one honestly postponed
Two went out:
- The vulnerability assessment article: the Hindi version is published
- How to Raise a Smarter Muse: the Hindi version is published
The third, “Cybersecurity Basics,” we did not make. I will write the reason honestly. Its Japanese version was right in the middle of being published in all languages at the same time. This house has a rule: “Build only after confirming, on the real thing, that publication is finished.” Making a language version of an article whose real page is not out yet would break that rule. So this one was postponed. Once we confirm the Japanese version’s publication is done, we will make the continuation.
Keeping the rule matters more than hurrying. …Written like that it sounds impressive, but the plain truth is also simple: you cannot make a version of something that is not out yet.
When the language changes, the name changes too
When you make a language version, Moka’s name takes on the local letters, too.
In the Chinese version, Moka is “摩卡”. And in the Hindi version, she is “मोका”. The script is called Devanagari, I am told, and I cannot read it. Having no way to check except asking Moka herself (?) whether it is right is a little funny.
My name stays “Kurashiki Bouzu” wherever it goes, but Moka’s name changes at every destination. The butler turned out to be the international one.
Along with this, we also fixed how the language switcher works. Until now, every article lined up all seven languages; we changed it so that only the language versions that actually exist for that article are shown. There is no point in a button that jumps to a page that does not exist. The Hindi button is added, at the end, only on the articles we tried.
We put the ruler into the Labs, too
The country figures this time were for this main site only. The other sites, at their own addresses — the Security Lab and the rest — did not appear in this ruler.
So we added the same analytics to the three Lab sites as well. From now on, we can see the countries for the Lab side, too. The response to the Security Lab, which is where one of the Hindi versions lives, can be checked over there.
Next, we look at the response and decide
The plan is this:
- Look at the analytics at the one-week, two-week, and one-month marks after publication
- Watch two things: whether readers in the “Hindi” language are arriving, and whether there are visits from “India” as a region
- We put out no announcement for the Hindi versions, so the first numbers will be the plain, bare numbers — only what arrived through search and by moving around inside the site
If there is a response, we spread it. If there is not, that is a result, too. The numbers are the ruler. The deciding comes after looking.
The eighth language is still a small trial. But every time a language is added, the reach widens a little. I will keep leaving a record of how that widening goes.
- November 21, 2026 ― 英語版(日本語版No.1931の内容を「結果から書く」形に書き直したもの)(5,593 characters)
- November 21, 2026 ― 公開(本人の公開指示・2026-11-21による。7言語同時公開。アドレスの末尾に台帳番号を入れる新形式で、末尾は日本語版の番号No.1931)(5,593 characters)
