Our NabWP translation tool creates a new draft from a supported WordPress page or post in your chosen language. The original content remains in place, giving you a separate version to review before you publish it. This is useful when you want to introduce your services to another language audience while retaining your existing website content.
IN THIS ARTICLE
01 Choose the original content and destination language
Select the original page or post and the destination language in the available translation controls.
You can choose from these supported languages:
- English, French, German, Spanish, Portuguese, Italian, Dutch.
- Arabic, Chinese, Japanese, Korean, Russian, Turkish, Polish.
- Swahili, Yoruba, Hausa, Igbo, Hindi, Indonesian.
02 Review meaning and check the complete draft
After the draft is created, review the title and each section. Give particular attention to names, local expressions, prices, contact information, technical terminology and the meaning of your calls to action. For customer-facing material, a fluent reviewer should check whether the translation sounds natural for the intended audience and preserves your intended meaning.
Translation applies to supported text blocks the tool can read from the selected page or post. The current workflow uses limits on the number and length of text items, so a long paragraph or a large page may not be fully represented in the translated draft. Compare the complete original with the draft and check for missing, shortened or untranslated material before publication. Plugin interfaces, images containing text, menus, checkout messages and content stored in an unrelated page builder may require separate editing or a suitable multilingual plugin.
03 Connect the translated page to your website
Publishing the draft also does not automatically create a complete multilingual navigation system. Decide how visitors will choose a language, how translated pages will link to each other and how you will keep versions updated when facts change. Check mobile presentation and writing direction where relevant. We can help you identify the additional configuration needed for a consistent multilingual website after the translated draft has been reviewed.
04 Example: review a translated service-page draft
For a fictional English service page with a French draft, a simple call to action such as Request a quote
might become Demandez un devis
. That short phrase is only one part of the review. Keep the generated page as a draft while comparing the complete source.
| Source detail | What to check in the draft |
|---|---|
| Service name and brand | Preserve the correct identity and intended meaning. |
| Price, address or telephone number | Verify every value against the approved business facts. |
| Long service explanation | Confirm that every section survived the supported-text limits. |
| Enquiry link | Open it and check the language and behaviour of the destination form. |
Expected result: a fluent reviewer approves an accurate, complete page. Menus, form messages and the language-switching journey are reviewed separately before publication.
Why should I compare a translated draft with the complete original?
- Choose the source page or post, destination language and Translate a page action.
- Open the resulting draft and compare every section, including long paragraphs and text stored in unusual blocks.
- Ask a fluent reviewer to check meaning, terminology and calls to action before publishing and linking the translated page.
The translation input is limited to a number of text items and a maximum excerpt length per item. A large page or long paragraph can therefore be shortened or omitted in the generated draft. The original stays in place, but a successful result is not evidence that every word, menu, form message or plugin interface has been translated.