Translating articles into your site's languages

Your site's languages are part of the content settings: the language articles are written in, and the other languages each article is translated into once it is approved. AutoPSEO translates on research credits, checks every translation against the original, and publishes the article with every language that passed. A site whose own AI writes its articles writes its translations too, and AutoPSEO never translates for it.

Set your languages

Under Settings on the Content page:

• Language articles are written in is the primary language.
• "Other languages each article is translated into when it is approved, on research credits:" lists the rest as checkboxes.

The engine writes 27 languages: English, Simplified and Traditional Chinese, Japanese, Korean, French, Spanish, German, Portuguese, Hindi, Vietnamese, Russian, Filipino, Thai, Indonesian, Turkish, Dutch, Italian, Polish, Ukrainian, Romanian, Swedish, Greek, Czech, Hungarian, Arabic and Urdu. The site scan proposes the languages your site already publishes in. Changing the primary language checks every topic in the backlog again.

When translations are made

When a revision is approved, or published on its own with approval off, and it lacks some of your languages, the task shows Publishing while a translation run works through them, one language at a time. Each language gets at most two model calls: the translation, and one fix when the translation fails the checks below. A translation that fails is not retried on its own.

The article then goes live with every language that passed. Languages that failed are kept on the revision:

• In Waiting for review, a red badge names them.
• In Published, a badge shows how many languages the article has (for example 3/4), and Translate the missing languages tries them again on research credits.

Translations cost research credits, at model cost plus the platform markup (1,000 credits are US$1). When the month's credits are used up, the missing languages fail with "This month's research credits are used up." and the article publishes without them.

With Publish a new article only when every language passed on, a new article whose translations fail goes back to review instead; approving it again translates only the languages that failed. Translate the missing languages on a live article publishes whatever passes either way.

What every translation must pass

• A title within your title width, suffix kept; a meta description, H1 and direct answer; the question field when the original has one.
• The same number of key takeaways, sections and FAQ entries as the original.
• In every section, exactly the original's links, and the same number of paragraphs, lists, list items and code spans.
• On typed pages, the same lists with the same number of items.
• Every number in the original, with separators ignored, so 1,200 and 1.200 match.
• The brand name, when the original has it.
• Every entry of Names translations keep exactly as written, at least as often as in the original.
• Nothing longer than 24 characters left word for word as in the original, which fails as "Still in the original language".

Sources and the category are copied from the original and never sent for translation.

Where translations appear

On a site that receives articles through the webhook, each delivery carries the primary language as copy and every other language under translations, and your site decides each language's address. On AutoPSEO hosting, the primary language lives at the article's path and each translation at the same path behind its language code, for example /de/answers/plan-a-content-calendar, with hreflang alternates linking them. Google explains those annotations in Tell Google about localized versions of your page.

Sites whose own AI writes

When Who writes the topics in the queue is Your own AI, through MCP, AutoPSEO does not translate for the site. Publishing a draft that lacks languages is refused with "Still missing ... This site's own AI writes its translations, and AutoPSEO does not translate for it: send them with content_submit_translation (its next run does), then publish." and Translate the missing languages is not offered.

The AI reads content_get_translation, which returns the translator's rules, the original without sources and category, and the current translation when there is one, then sends content_submit_translation. The same checks apply, and it costs nothing. Languages of one draft can be sent in parallel, because each is added on its own. On a live article, a new language is published straight away, while a changed translation of an existing language becomes a new revision that can be rolled back. See writing with your own AI.