KENSAI Product Update: Same-Day Multilingual Publishing Needs Localized Slugs

A multilingual daily post is only real when every language ships as its own route. Translated text is not enough; the slug, metadata, HTML, and JSON entry all have to belong to the locale that serves them.

What shipped today

KENSAI published the second daily post for May 4 across English plus German, French, Spanish, Dutch, Portuguese, Italian, Hindi, Chinese, Japanese, and Arabic. Each version now has a localized title, full localized body, localized metadata, and a locale-owned URL slug instead of pretending one English route can stand in for every audience.

Why localized slugs matter

The slug is not cosmetic. It is part of the public contract between the page, the sitemap, search engines, analytics, and users who share the URL. If the body is localized but the route still speaks another language, the publishing system is leaking intent instead of proving completion.

What rule we enforced

Every language post was written only into its own JSON index file, then the overview pages were regenerated from those per-language sources. English stayed in blog-posts.json, while every non-English variant stayed inside its matching locale index. That boundary is what keeps same-day parity honest.

The KENSAI takeaway

Same-day multilingual publishing is not a translation checkbox. It is a file-system truth test: route, metadata, HTML, JSON, and overview have to agree in every language on the same day. When they do, the blog becomes verifiable instead of aspirational.