Translate Content

The Content page is the starting point for most day-to-day work.

Filter the queue

Use the content type filter and search controls to narrow the list before you translate anything. That makes it easier to focus on one release, one content type, or one campaign at a time.

You can also filter by Contentful tags. Tag filtering is useful when your team already uses tags to group campaigns, releases, page owners, or localization readiness.

Tag filters use the tags available on the project's configured top-level content types. If a tag is not available in Inverb, first confirm that the tagged entry belongs to a selected top-level content type in Settings > Contentful.

Use page links

When page links are configured, entry detail pages show a link near the current translation so reviewers can open the matching page in another tab.

If more than one environment is configured, use the environment selector to switch between links, for example Preview and Production.

Translate a single entry

Open an entry, then:

1. choose a target locale
2. choose the AI model
3. start the translation

Single-entry work is the best way to validate a new model or a sensitive page before scaling up.

Create a translation batch

From the content index, select multiple entries and create a batch when you want to process a larger slice of work together.

Batch setup currently lets you choose:

• target locales
• AI model
• whether auto push should run after translation
• whether auto publish should run after push

When to use single entry vs batch

Use a single entry when:

• you are validating a workflow
• a page is high risk
• the copy needs close review

Use a batch when:

• the content shape is consistent
• the glossary is already in decent shape
• the team is ready to monitor work centrally from Translations