Skip to content

Guide · For business

Translating WordPress: export, translate, import

How to export WordPress content so that structure, links and SEO fields are preserved, how the import works and which content regularly gets forgotten when you translate a WordPress site.

  • 6 steps, a checklist and a PDF
  • Updated

In short

  1. With a multilingual plugin such as WPML or Polylang Pro, you export XLIFF files. The structure and the link to the original page are preserved.
  2. Without a plugin, Tools → Export only gives you a WXR file. It mixes text and markup and is a stopgap.
  3. Set up the target languages before you export, or the import will have nowhere to go.
  4. Meta titles, descriptions, alt texts, menus and theme texts are separate content and need to be exported too.
  5. Work on a staging site with a backup, not directly on the live website.

Which export route suits your website

The clean route is a multilingual plugin. WPML and Polylang Pro export XLIFF files that keep the source text, the target text and the link to each page together. The import then creates the translation automatically as a language version.

WordPress’s own export under Tools → Export, by contrast, produces a WXR file: XML with text and markup mixed together. It works as a stopgap if no plugin is installed, but it needs more rework and doesn’t create language versions. Copying and pasting from the editor is no alternative: hidden fields get lost, and that is often where half of your search engine optimisation lives.

Six steps from export to import

It takes six steps to get from your existing content to a published language version. Plan the export for when the source pages are finished: every change during translation creates rework.

  1. Take stockWhich pages, post types and languages
  2. PrepareBackup, staging site, target languages
  3. SelectMark content and fields in the plugin
  4. ExportDownload the XLIFF files
  5. TranslateSpecialist translation with a glossary
  6. ImportImport, check, publish
Six steps from selecting content to a published language version.

1. Take stock of your content

Decide which pages and post types need translating, including custom post types and, with WooCommerce, your product data. Exporting the entire website is rarely necessary and makes the review needlessly time-consuming.

2. Backup and staging site

Make a backup and work on a staging site. Check that the plugin and WordPress are on the version they will still be on at import time, and don’t run any updates in the middle of the project.

3. Set up the target languages

Set up the target languages in the plugin settings before you export. Without a configured language, the import later has no target and may file the content under the source language.

4. Select and export the content

In the translation management screen, select the content and add it to the translation basket. Choose the option to handle the files yourself and download the XLIFF files. Menu labels vary depending on the plugin and version.

5. Have it translated

The XLIFF files come to us. Specialist translators work in the format itself, with shortcodes, block markers and placeholders protected. A glossary and translation memory keep terminology and recurring text consistent.

6. Import and check

Import the files back into the plugin, starting with a single page as a test. Then check the language switcher, menus, forms and layout before you publish.

Tool · Download

The WordPress checklist as a PDF

The checklist and points to check on one page, to pass on to your agency or developers. Currently available in German only.

Download the checklist as a PDF (German)

Checklist before you export

Sort out these points in advance and you won’t need a second export round.

Tool · Checklist

Preparing a WordPress export

What often gets forgotten in a WordPress export

This content sits outside the body text and only gets noticed once the language version is live.

Content Why it slips through
Meta titles and descriptions They live in the SEO plugin, not in the editor
Image alt texts They sit in the media library and matter for accessibility
Menus and widgets Depending on the plugin, they are translated separately
Forms Field labels and error messages live in the form plugin
Cookie banners and legal texts They often come from third-party providers and need their own language versions
Slugs and permalinks Otherwise they stay in the source language, and they matter for search
Product attributes in the shop Variants, units and filters are separate records
Theme texts Labels such as “Read more” and “Search” come from the theme

Common mistakes

The most common problems come from rushing: no backup, no test run, changes in the middle of the process.

Avoid Better Why
Importing directly on the live website Import and check on a staging site Otherwise a failed import affects every visitor.
Copying text out of the editor Export through the plugin Copying loses SEO fields, alt texts and page links.
Leaving slugs untranslated Give slugs in the target language Source-language URLs on a translated version look unfinished.
Changing source pages during translation Collect changes and apply them afterwards Otherwise the export and the website no longer match.
Publishing machine translation without approval Plan for post-editing by a professional Otherwise mistakes go straight into the public language version.

Frequently asked questions

Do I need a plugin to have WordPress translated?

For a clean process, yes. WPML and Polylang Pro export XLIFF files and create the translation as a language version when you import it. Without a plugin, you are left with the export under Tools, which is only a stopgap.

What is XLIFF?

An XML format for translations. It holds the source text and the target text side by side, along with the link to each page. That way, the system knows where every text belongs when you import it.

Does this work with WooCommerce too?

Yes. Product data, variants and attributes are separate records and are selected along with everything else. Allow more review time for them than for plain text pages.

How long does it take to translate a website?

That depends on the volume. Three factors matter for planning: the word count, the number of languages and the time needed for import and review on your side. The review time is usually underestimated.

Can we automate the process?

Yes. With the API or tolingo connect, exports can be handed over and translations imported back automatically. That pays off when content changes regularly.

More guides

Written by the tolingo editorial team

Last updated 16 October 2026