Organising WordPress contact pages by enquiry type
28/10/2026Keeping page context when switching WordPress languages
28/10/2026Managing WordPress translation approvals
Practical WordPress guides · Forms and collaboration
At a glance
Multilingual content remains reliable when changes to the source and translated versions are coordinated. A translation plugin cannot replace editorial ownership.
Approach and context
Define a source version and responsible reviewers for each published language. When content changes, make clear which translations need another review. Separate language approval from functional testing: correctly translated text can still lead to the wrong form or offer. Include text embedded in images, downloads and automated messages in the review inventory.
Implementation checklist
- Record source language, owner and approval status for each content item.
- Identify changed passages and related media for translation.
- Before publishing, test links, forms and confirmations in the target language.
Illustrative example
A German service page receives a new scope. Its English version must not continue presenting the old scope as current. Track the change until the translated version has been approved.
A common pitfall
Unreviewed automatic translation can misrepresent specialist terms or service conditions.
How to check the outcome
Each language presents the same approved version of the relevant offer.
Further official documentation: Google Search Central: Multilingual sites. The exact controls depend on your theme, extensions and installed versions.