# Translate content in bulk (/use-cases/content/translation-and-localization)



Copy this prompt to start your first task:

<Prompt>
  Translate this batch of docs into [target language] using our glossary. Hold every approved term constant across every page, flag anything that isn't in the glossary instead of guessing, and list which pages you flagged so I can review them fast.
</Prompt>

<LivePreview component="NewThread" scenario="{ draft: &#x22;Translate this batch of docs into [target language] using our glossary. Hold every approved term constant across every page, flag anything that isn't in the glossary instead of guessing, and list which pages you flagged so I can review them fast.&#x22; }" />

## What is this workflow? [#what-is-this-workflow]

Translating content in bulk means giving a teammate a glossary and a full batch of documents at once, instead of translating page by page. It holds every approved term in the glossary constant across the whole batch, and flags any term that has no approved translation yet instead of guessing at one. What comes back is a full batch translated to that one glossary — consistent enough for a spot-check, not a full re-read — delivered as documents or artifacts in the same channel.

## How to use this workflow [#how-to-use-this-workflow]

<Steps>
  <Step>
    ### Hire a content teammate [#hire-a-content-teammate]

    Open **AI Teammates** in the sidebar, click **Hire AI Teammate**, and pick the **Content Writer** or **Content Editor** template. The default bio is generic writing or editing work. Replace it on the Profile step so it knows this job is bulk translation against a fixed glossary:

    <Prompt>
      You translate a full batch of documents at once, holding every approved term in our glossary constant across every page instead of improvising translations page by page. When a term has no approved entry in the glossary, flag it instead of guessing at a translation. Return finished translations as documents or artifacts in the same channel, consistent enough for a spot-check rather than a full re-read.
    </Prompt>

    Confirm the name and click **Create teammate**. They land in their own channel, which is where you'll send everything below. [More on hiring →](/ai-teammates/hire-an-ai-teammate)

    <LivePreview component="CreateAssistantPage" scenario="{ focus: &#x22;profile&#x22;, initialState: { start: &#x22;template&#x22;, templateRef: &#x22;@helio/content-writer&#x22;, name: &#x22;Content Writer&#x22;, bio: &#x22;You translate a full batch of documents at once, holding every approved term in our glossary constant across every page instead of improvising translations page by page. When a term has no approved entry in the glossary, flag it instead of guessing at a translation. Return finished translations as documents or artifacts in the same channel, consistent enough for a spot-check rather than a full re-read.&#x22; } }" />
  </Step>

  <Step>
    ### Share the source documents [#share-the-source-documents]

    Send the source documents to the teammate as attachments, or paste the text into its channel. Translations come back as documents or artifacts in the same channel.
  </Step>

  <Step>
    ### Give it your glossary and the batch [#give-it-your-glossary-and-the-batch]

    <Prompt>
      Translate this batch of docs into [target language]. Use our glossary [attached], and hold the approved translations constant across every page. Flag anything that isn't in the glossary instead of guessing.
    </Prompt>

    For example:

    <LivePreview
      component="AssistantChat"
      scenario="{ assistantName: &#x22;Content Writer&#x22;, messages: [
    { author: &#x22;user&#x22;, text: &#x22;Translate these 12 docs pages into Chinese. Use our glossary [attached], and hold the approved translations constant across every page. Flag anything that isn't in the glossary instead of guessing.&#x22; },
    { author: &#x22;assistant&#x22;, text: &#x22;Starting with the glossary. I'll hold every approved term constant across all 12 pages and flag anything that isn't in the glossary instead of guessing at a translation.&#x22; },
  ] }"
    />
  </Step>

  <Step>
    ### Ask for a consistency sweep on existing content [#ask-for-a-consistency-sweep-on-existing-content]

    If you already have translated pages with drift between them, start there instead:

    <Prompt>
      Scan our existing [target language] docs for how we've translated key domain terms. Surface every variant you find, and propose one glossary entry per term based on the most common usage.
    </Prompt>
  </Step>
</Steps>

**Nothing here needs your approval:** translations come back as documents or artifacts in the same channel — nothing here sends externally or does anything that can't be revised again. See [Control](/ai-teammates/control) for what does pause for sign-off.

## Tips for Better Results [#tips-for-better-results]

| Tip                                             | Description                                                                                                                                                      |
| ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Give it the glossary before the batch           | Approved terms held constant across every page depends on the glossary landing first — without one, translation gets improvised term by term.                    |
| Let it flag gaps instead of guessing            | A term missing from the glossary comes back flagged, not guessed at — catch it once instead of finding an inconsistent translation later.                        |
| Spot-check the batch, don't re-read it          | Translating against one glossary keeps the whole batch consistent enough for a spot-check, not a full re-read.                                                   |
| Run a consistency sweep before adding new pages | If existing translated content already has drift, scan it first — it surfaces every variant and proposes one glossary entry per term from the most common usage. |

## Common Questions [#common-questions]

<Accordions type="single">
  <Accordion title="What happens if a term isn't in the glossary yet?">
    It gets flagged instead of guessed at, so you can add an approved translation rather than catch an improvised one later.
  </Accordion>

  <Accordion title="Where do the finished translations come back?">
    As documents or artifacts in the same channel you sent the source content to.
  </Accordion>

  <Accordion title="Which teammate template should I use?">
    Either the Content Writer or Content Editor template works — the job is bulk translation against a fixed glossary, not tied to one specific template.
  </Accordion>

  <Accordion title="What if my existing translated pages already have inconsistent terminology?">
    Ask for a consistency sweep instead of translating something new: it scans existing content for how terms have been translated, surfaces every variant, and proposes one glossary entry per term based on the most common usage.
  </Accordion>
</Accordions>

<Cards>
  <Card title="Content" href="/use-cases/content" description="Back to the content use case overview." />

  <Card title="Draft and gate-check social posts" href="/use-cases/content/social-drafts" description="Turn a product update into ranked story directions, drafted and held for approval." />
</Cards>