Have AI Read Your Articles Aloud · Auto-Translate into 3 Languages
Expand your reach after writing — at no extra cost
機械翻訳 / Machine-translated
There are ways to deliver an article beyond simply having people read it. MiraiPage has AI text-to-speech and automatic translation built right in, and both require almost zero extra effort from the writer. Here's how to use them, and when they actually work.
There is a "Listen" button on every article page. Press it, and audio of the article body begins playing.
The audio is synthesized using Google's Gemini, and the generated audio is saved — so from the second listener onward, playback is instant. Only the very first listener waits for it to be generated.
Before being read aloud, the body text is formatted as plain text. Heading markers like ##, bold markers like **, list markers like -, link syntax, code blocks, and images — all of these are stripped out before the audio is produced.
In other words, symbols are never read aloud as-is. Just write normally in Markdown and you're fine.
The third condition matters. Paid articles and salon-member-only articles cannot be read aloud. This is an intentional restriction to prevent the body text from leaking through the audio.
Text-to-speech shines when readers can't use their hands — commuting, cooking, exercising.
It works especially well for long articles. Articles over 3,000 characters tend to get saved for later and forgotten, but audio gets consumed during a commute. If you've written a long piece, just add a single line somewhere in the article saying "You can also listen to this" — that alone changes how often it gets finished.
MiraiPage can translate articles into English, Chinese (Simplified), and Korean.
Translated articles are accessed via a parameter like ?lang=en. Rather than having a separate URL, translations are treated as language variants of the same article.
This is a quietly powerful part of how it works.
If you edit the title, subtitle, or body of an article after it has been translated, the system detects the change and retranslates it. You'll never end up in a state where the Japanese version is updated but the English version is stale.
The mechanism works by storing a hash of the source text at the time of translation, then flagging the article for retranslation whenever the current source no longer matches that hash.
The free/paid boundary in paid articles (<!-- paywall -->) is preserved as-is after translation. Translation will never cause paid content to leak into the free portion.
Honestly, not every article needs to be translated. Some are better suited for it than others.
Good fits
Poor fits
Text-to-speech and translation are both functions that expand your reach after writing, at no additional cost.
If you spent five hours writing an article, the few minutes it takes to set up these two features will absolutely pay off. Long explanatory articles in particular benefit from both audio and multilingual delivery.
Next time, I'll write about posting directly to MiraiPage from Claude — covering the API and MCP.