How to Translate Pages and Content in TYPO3 CMS

TYPO3 makes it possible to manage multiple language versions within the same page hierarchy. Translated pages usually follow the structure of the original-language page, helping editors maintain consistency across multilingual websites without creating separate page trees for every language.

Editors can create and manage translations directly from the TYPO3 page or content module. However, translating the page itself and translating its content elements are two separate tasks. Page translation covers properties such as the title, URL slug and metadata, while content translation includes text, images, links, buttons and other content elements.

This guide explains how to translate pages and content elements in TYPO3, choose between connected, free and mixed translation modes, review translated content and publish it correctly. It also covers multilingual SEO and key workflow differences across TYPO3 12, TYPO3 13 and TYPO3 14.

TYPO3 Translation vs Localisation: What Is the Difference? 

Page translation and content translation are closely connected in TYPO3, but they handle different parts of a multilingual page. Understanding this distinction helps editors avoid missing important fields during the translation process.

Translating a TYPO3 Page

Page translation covers the settings and information attached to the page itself. This usually includes the page title, navigation title, URL slug, SEO title, meta description, social metadata and other page-level settings.

These fields control how the translated page appears in menus, search results, social media previews and the browser address bar. Translating only the visible content while leaving these fields unchanged can result in mixed-language URLs, metadata and navigation labels.

Translating TYPO3 Content Elements

Content-element translation covers the actual information displayed within the page. This may include headings, body text, images, alternative text, buttons, links, downloads, tables and embedded media.

Each content element must be reviewed separately to ensure that both visible and supporting information are translated. For example, translating an image caption without updating its alt text can leave part of the page inaccessible or inconsistent.

Translation Versus Localisation

Translation focuses on converting content from one language into another. Localisation goes further by adapting the page for a specific country, region or audience.

This may involve adjusting terminology, currencies, date formats, regional offers, images, legal information and calls to action. A technically accurate translation may still feel unnatural if these local details are not adapted for the target audience.

Key Checks Before Translating TYPO3 Pages

Before creating a translated page, confirm that the language setup, source page and editor permissions are ready.

Check the Target Language

Make sure the target language:

• Is configured by a TYPO3 administrator
• Is enabled for the correct site
• Is available to the editor

Confirm the Source Page Exists

Before creating a translation:

• The page must exist in the default language
• It must be saved in the correct page hierarchy

Check Editor Permissions

The editor should be able to:

• Access the page
• Use the target language
• Edit page properties
• Translate content elements
• Enable or publish translated records

Identify Your TYPO3 Version

• TYPO3 14: Modern Translate and Copy workflow
• TYPO3 13: Traditional page-language workflow
• TYPO3 12: Legacy instructions may apply

How to Switch Between Columns and Languages in TYPO3

TYPO3 lets editors view content either by page columns or by language. Choosing the correct view makes it easier to manage page structure and compare translated content.

Columns View

The Columns view displays content elements according to the page layout, such as:

• Normal
• Left
• Right
• Border
• Custom backend columns

Use this view when editing the layout or managing content in a single language.

Languages View

The Languages view displays content by language rather than page column. It helps editors:

• View the default and translated languages
• Compare source and translated content
• Translate content elements
• Review missing or outdated translations
• Manage multilingual pages side by side

Switching from Columns to Languages

Open the page in the TYPO3 page or content module and switch the view from Columns to Languages.

Depending on the TYPO3 version and backend configuration, the module name, menu position or switch button may appear differently. In some installations, editors can display:

• One selected language
• The default and target languages
• All configured languages side by side

Use Columns view for layout editing and Languages view for translation work.

Step 1: Create a New Page Translation in TYPO3

Start by opening the source page in the default language. TYPO3 creates the translated version within the same page hierarchy.

Open the Default-Language Page

Open the required page in the TYPO3 Page or Content module and switch to the Languages view.

Select “Create a New Translation of This Page”

Click Create a new translation of this page below the page title.

This option appears only when:

• The page does not already have a translation in that language
• The target language is configured for the site
• The editor has permission to use the language

If the option is missing, check the existing translations, editor permissions and site-language configuration.

Select the Target Language.

Choose the required language from the available options. Only languages configured by an administrator and assigned to the editor will appear.

Step 2: Translate TYPO3 Page Properties

After selecting the language, TYPO3 opens the translated page properties. Source-language values may be copied or displayed for reference while you enter the translated information.

Translate the General Page Information

Review and translate:

• Page title
• Alternative navigation title
• Subtitle
• Page description
• URL segment

Translate the TYPO3 Page URL Slug

Create a clear, language-specific URL slug for the translated page.

Check for:

• Slugs left in the source language
• Duplicate URL segments
• Incorrect regional terminology
• Slugs that were not updated after changing the page title

Translate the SEO Metadata

Update the translated page’s search and social metadata:

• SEO title
• Meta description
• Robots settings
• Canonical URL override
• Open Graph title
• Open Graph description
• Social sharing image

TYPO3 can generate canonical and hreflang elements through its SEO configuration, but each translated page should still be reviewed individually.

Review Page Access and Visibility

Check:

• Publication date
• Expiration date
• Hidden status
• User-group restrictions

Save the Translated Page Properties

Save and close the page properties. The Languages view should now display:

• The source-language column
• The target-language column
• No translated content elements yet, unless they were created during the page translation process

Step 3: Choose Between Translate and Copy in TYPO3

Before translating content elements, choose whether the target-language content should remain connected to the source or work independently.

What Does Translate Mean in TYPO3?

The Translate option creates connected translation records.

Connected translations:

• Remain linked to the source content
• Support structured translation workflows
• Can be marked as outdated when the source changes
• Show source changes during translation review
• Usually follow the same content structure and order

Changes made to the source do not automatically rewrite the translated text. Editors must review and update the translation manually.

What Does Copy Mean in TYPO3?

The Copy option creates independent content records in free mode.

Use Copy when:

• Each language needs a different layout
• Regional websites require unique content
• Content order varies by market
• Some source elements do not need translated versions
• Editors need full control over the target-language page

TYPO3 Translate vs Copy

Requirement	Translate	Copy
Keep source and target connected	Yes	No
Track source changes	Yes	No
Use an independent element order	Limited	Yes
Add different regional content	Limited	Yes
Maintain a strict translation workflow	Recommended	Not ideal
Build flexible market-specific pages	Not ideal	Recommended

Which TYPO3 Translation Option Should You Choose?

• Corporate websites: Translate
• Government and public-sector websites: Translate
• International ecommerce websites: Translate for shared pages; Copy for market-specific offers
• Regional landing pages: Copy
• News websites: Translate for equivalent stories; Copy for local editorial content
• Campaign pages: Copy when messaging, layout or offers vary by region

Connected, Free and Mixed Translation Modes in TYPO3

TYPO3 supports different ways of managing relationships between source-language and translated content. The selected mode affects structure, content order and source-change tracking.

TYPO3 Connected Translation Mode

In connected mode, each translated content element remains linked to its source element.

This means:

• The source and target records stay connected
• TYPO3 can mark translations as outdated
• Editors can compare source changes
• Content structure usually remains aligned
• Source changes do not automatically replace translated text

When to Use Connected Mode

Connected mode is suitable for:

• Corporate websites
• Public institutions
• Regulated content
• Websites requiring consistent page structures
• Translation-team workflows

TYPO3 Free Translation Mode

In free mode, target-language content records work independently from the source-language records.

This means:

• Content can have a different order
• Each language can contain unique elements
• Layouts can vary between language versions
• Source changes are not tracked in the same connected workflow

When to Use Free Mode

Free mode is suitable for:

• Regional campaigns
• Country-specific offers
• Market-specific landing pages
• Different editorial calendars
• Language versions with different layouts

TYPO3 Mixed Translation Mode

Mixed mode combines connected translated elements with independent content records on the same page.

It is mainly relevant to older or existing TYPO3 installations that already contain both record types. TYPO3 14 guides editors towards either connected Translate mode or independent Copy mode to reduce inconsistent translation setups.

How to Identify Mixed-Mode Content

Mixed-mode pages may contain:

• Connected elements linked to source records
• Independent copied elements
• Unlinked translated elements
• Different content ordering between languages

Risks of Mixed Translation Mode

Mixed mode can lead to:

• Inconsistent element ordering
• Confusing editorial workflows
• Missing source-change notifications
• More difficult maintenance
• Accidental content duplication

Advanced: Link or Unlink TYPO3 Translated Content Elements

Editors can manually connect or disconnect translated content elements.

Link an Element

1. Open the translated element.
2. Go to the Language tab.
3. Select the related default-language element.
4. Save the record.

Use unique headings to identify the correct source element.

Unlink an Element

Set the source-record value to [0] in the Language tab and save.

Important: Test changes in staging or create a backup first. Field names may vary by TYPO3 version and backend configuration.

Translate Content Using TYPO3 Connected Mode

Connected mode keeps translated elements linked to their source records.

Step 1: Open the Translated Page Properties

Source-language values appear beneath or beside the translation fields for reference.

Step 2: Translate Page Details

Translate:

• Page title
• Navigation title
• URL slug
• SEO title
• Meta description
• Social metadata

Step 3: Save and Return to the Content Area

The Languages view should show the source-language and target-language columns.

Step 4: Click Translate

Click Translate in the target-language column.

Step 5: Continue Through the Wizard

Select Translate, click Next, review the options and click Next again. TYPO3 14 uses a modernised translation wizard.

Step 6: Select Content Elements

Exclude elements that are:

• Regionally irrelevant
• Outdated
• Language-specific
• Temporary
• Legally different

Step 7: Complete the Translation

Finish the wizard. The translated elements will appear in the target-language column and remain connected to their source records.

Step 4: Translate TYPO3 Content Elements

Replace all copied source content before publishing.

Translate Text and Links

Review:

• Headings and body text
• Buttons and calls to action
• Internal and external links
• Downloads and tables

Make sure links lead to the correct language version.

Translate Images and Media

Check:

• Alt text
• Captions and titles
• Images containing text
• Videos and documents

Check the Language Tab

Confirm that each translated element is linked to the correct source element.

Enable and Preview the Content

Translated records may initially be hidden. Review them before enabling.

Preview:

• Desktop and mobile layouts
• Navigation and language switcher
• Links and forms
• Images and content order

Add New Content to an Existing TYPO3 Translation

If new content elements are added to the source-language page, they must be translated separately.

Translate Newly Added Content

1. Open the page in Languages view.
2. Find the target-language column.
3. Start the translation workflow again.
4. Select only the new content elements.
5. Translate and review them.
6. Enable and publish the updated content.

To exclude an element from a language, deselect it in the translation wizard.

What Happens When TYPO3 Source Content Changes?

Connected translations may be marked as outdated when the original content changes. TYPO3 shows the previous and updated source values, but editors must still update the translation manually.

Understand the Change Comparison

• Red values: Removed or replaced source content
• Green values: New or updated source content

Update an Outdated Translation

1. Open the translated content element.
2. Review the source-language changes.
3. Update the translated fields.
4. Check links and media.
5. Save and preview the page.

Final Review of Translated TYPO3 Pages

The completed translation should include:

• A translated page record
• Translated page title and URL slug
• Complete target-language content
• Correct page and element visibility
• Proper source-element relationships
• Working navigation
• Correct frontend language
• No untranslated placeholders

Preview and Publish a TYPO3 Translation

Preview the target-language page before publishing to confirm that the correct version is displayed.

Check the Language Switcher

Make sure it:

• Opens the equivalent translated page
• Does not redirect users unnecessarily
• Highlights the active language

Enable the Translation

Check both:

• Page visibility
• Individual content-element visibility

Clear the TYPO3 cache where required by the website’s publishing workflow.

TYPO3 Translation Publishing Checklist

• Page title translated
• URL slug translated
• Metadata translated
• Content elements enabled
• Links tested
• Images localised
• Alt text translated
• Navigation checked
• Mobile layout reviewed
• Language switcher tested
• No source-language text remains

How TYPO3 Handles Missing Translations

TYPO3 uses language fallback settings to decide what appears when target-language content is unavailable.

Why Source-Language Content May Appear

Common causes include:

• Language fallback settings

• Missing element translations

• Content assigned to all languages

• Extension-specific localisation rules

Approach	Behaviour
Strict translation	Missing translated content is not displayed
Fallback	Content from another configured language is shown
Mixed configuration	Behaviour varies by record or extension

Editors may need administrator support for site languages, fallback chains, locale settings, routing or extension configuration.

Multilingual SEO for TYPO3 Pages

Every language version should be optimised as a separate search page.

Key SEO Checks

• Use a natural target-language URL slug.
• Translate SEO titles and meta descriptions.
• Check that canonicals point to the correct language page.
• Verify hreflang links between language versions.
• Confirm the correct HTML language attribute.
• Include translated URLs in XML sitemaps.
• Review noindex, nofollow and access settings.
• Research keywords separately for each market.
• Translate image alt text appropriately.

Avoid translating keywords word for word. Search behaviour, terminology and user intent often differ by country and language.

Translating TYPO3 News, Forms and Extension Records

Translating a page does not automatically translate every record displayed on it.

News, Categories and Tags

News articles, categories and tags may require separate translations within their own records.

TYPO3 Forms

Review and translate:

• Field labels
• Placeholders
• Validation messages
• Confirmation pages
• Email notifications
• Consent text

Custom Extension Records

Translation support depends on how the extension and its database fields are configured.

XLIFF Language Files

XLIFF files translate interface labels and extension text, not normal page content. For new TYPO3 14 projects, use the supported XLIFF 2.x format where applicable.

Manual, Automated and AI-Assisted TYPO3 Translation

The right translation method depends on content volume, risk and available review resources.

Manual Translation

Best for:

• Small websites
• Sensitive content
• Low translation volumes
• Editor-controlled workflows

Professional Translation

Useful when projects require:

• Translation agencies
• Terminology glossaries
• Review and approval stages
• XLIFF exchange
• High linguistic accuracy

Automated and AI-Assisted Translation

Translation extensions may connect TYPO3 with services such as DeepL or AI providers.

They can support:

• Draft translation
• Terminology consistency
• Tone adaptation
• Metadata translation
• Faster high-volume workflows

All automated translations should be reviewed before publication.

Which TYPO3 Translation Method Should You Choose?

Requirement	Recommended approach
Low content volume	Manual translation
Many languages	Automated or professional workflow
Limited budget	Manual or AI-assisted
High accuracy required	Professional translation
Legal or regulated content	Professional review
Frequent publishing	Automated or AI-assisted
Limited review resources	Professional translation service

Common TYPO3 Translation Problems and Solutions

Why is “Create a new translation of this page” missing?

Check:

• Existing page translation
• Language configuration
• Editor permissions
• Site root
• Backend module view

Why is the target language not available?

Check whether the language has been configured for the site and assigned to the editor.

Why is the Translate button missing?

Check:

• Page translation status
• Current module
• Content permissions
• Existing translation mode
• Backend configuration

Why is translated content hidden?

Check the visibility setting of both the page and individual elements.

Why is the original language displayed?

Check:

• Missing translation
• Fallback configuration
• “All languages” records
• Extension localisation settings

Why is the translation marked as outdated?

Explain that the connected source record has changed.

Why can’t I add independent content?

Explain connected-mode restrictions and when free mode is required.

Why are elements displayed in the wrong order?

Check:

• Translation mode
• Source order
• Independent copies
• Mixed-mode records

Why does the translated page return a 404 error?

Check:

• URL slug
• Page visibility
• Site-language base path
• Routing
• Cache
• Page access

Why are hreflang tags missing?

Check:

• SEO extension
• Site-language configuration
• Translated-page availability
• Locale values
• Canonical setup

Conclusion

Translating pages and content in TYPO3 helps businesses manage structured, multilingual websites from one backend. TYPO3 supports page translations, content-element localisation, connected workflows, independent language versions and source-change tracking.

For a complete translation, update both the page properties and its content elements. Before publishing, review the URL slug, SEO metadata, links, images, language switcher and visibility settings to ensure the correct language version is complete and accessible.

For related guidance, explore TYPO3 site-language configuration, multilingual SEO, language fallback and automated translation workflows.

Thank you for your time. See you in the next series. Until then, happy TYPO3 reading!