Translate in place, not on another site
Why the Translate button rewrites the post where it is, how it keeps headings and code, and what it does with your language.
Most blogs that offer translations do it one of two ways: a separate set of routes per language, or a link to an external translator. The first means maintaining copies. The second sends your readers away.
In place
Press Translate, pick a language, and the post rewrites itself paragraph by paragraph. Headings stay headings, lists stay lists, code blocks are left exactly as they were. The original comes back with one click.
Which language first
The menu lists the languages in site.ai.languages and puts the reader’s browser language first when it is one of them. Change the list to the languages your readers actually have.
Cost
A 1,200-word post is roughly 1,600 tokens in and 1,800 out, so a translation costs about 3,400 tokens from the site’s allowance. The free allowance covers a few hundred of them. Readers who translate the same post twice in a session get the cached result.
When not to use it
If you already maintain real translations, turn the button off for those posts with ai: { translate: false }. A human translation of your own writing is better than an on-the-fly one, and the starter should not get in its way.