Quick answer: Maintaining a multilingual website means checking more than whether both WordPress URLs load. After a change, review the VI and EN copy, language switcher, menus, forms, email notifications, canonical and hreflang signals, and the public cached output. The goal is a complete journey in each language: the visitor gets the right information and the enquiry reaches the right team.
This guide is for businesses already running Vietnamese and English pages with WPML or a comparable translation system. It addresses ongoing operation, not the initial translation of an entire site. Translation strategy and market-specific keyword research require their own editorial scope.
Does the EN page still show Vietnamese or lose enquiries?
IT Systems can review paired URLs, language navigation and public form delivery before defining the repair scope.
A translated page is not necessarily a translated journey
A service page may have an EN version while its header button, FAQ, image text, enquiry form or confirmation email remains in Vietnamese. Sometimes the EN URL exists but contains the VI body, an old slug, or a language switcher that returns visitors to the homepage instead of the equivalent page. A flag in the header does not tell you whether a prospective customer can complete the task.
Measure a paired journey, not just the count of translated pages: search result or menu, service answer, call to action, form, confirmation and receiving team. Each version should make sense to its intended reader. Translation of button labels alone is not localization.
Map the URL pairs before changing settings
Inventory the pages that matter most to revenue and trust: home, services, pricing, contact and important support articles. Record the VI and EN URLs, content owner, translation state, latest approved change and the switcher destination. Do not assume that adding /en/ to a path creates a valid linked translation in WordPress.
Prioritize mismatched prices or service scope, a broken EN form, outdated policy text and EN pages with Vietnamese body copy. Lower-impact wording differences can be scheduled, but should still have an owner and review date. Do not change approved commercial or legal wording on behalf of the client.
Six checks for each VI/EN pair
- Meaning and offer: compare the approved service scope, conditions, reference price, contact details and effective date. The business content owner confirms meaning; the website team publishes and verifies it.
- Navigation: open the page from the menu, cards, breadcrumbs and related articles on desktop and phone. The language switcher should lead to the corresponding translated page where one exists; any fallback for an untranslated page should be intentional.
- Enquiries: test field labels, validation, consent text, thank-you state, notification email, recipient and source-language data. Submit a clearly marked TEST enquiry in each language and confirm the receiving record.
- Search signals: check localized title, description, headings and slug, a sensible self-canonical, reciprocal hreflang, indexability and sitemap entries. EN copy should reflect how English-speaking customers search, not a word-for-word transfer of a VI keyword.
- Cache and devices: inspect both pages while logged out on desktop and mobile. Check that the cache does not return the other language’s menu, form or content. Repeat after plugin updates or a cache purge.
- Media and structured data: review the featured/OG image, alt text, breadcrumbs and schema language. A shared text-free visual can work across languages, but its surrounding metadata still needs review.
WPML can generate hreflang automatically for correctly connected translations, but automation does not prove the public copy, forms and canonicals are correct. Google Search Central recommends distinct URLs for language versions, clear visible page language and accessible language links; WPML’s documentation explains its URL, hreflang and sitemap behavior. These are audit criteria, not a ranking promise.
A release test after updating a service page
Suppose the Vietnamese service scope changes. The business owner supplies approved wording and flags what must change in English. The website team backs up the site, updates the correct content in each language and tests two independent journeys on the public, logged-out site:
- From VI: use the menu, read the revised offer, select the CTA, submit a TEST enquiry, verify its delivery, then use the language switcher.
- From EN: open the EN URL directly, read the page and FAQ in English, submit an EN TEST enquiry and verify the confirmation, language/source data and recipient.
- Inspect both pages’ canonicals and reciprocal hreflang URLs. The alternates should represent the actual corresponding pages, not a generic homepage.
- Recheck after cache refresh and record URLs, time, device, screenshots, TEST results and content approval.
If the EN form records an enquiry but sends a Vietnamese confirmation, the visitor journey is still incomplete. If an EN slug changed, check old internal links and the redirect before closing the change ticket.
When an English page disappears or shows the wrong language
| Symptom | First check |
|---|---|
| EN switch goes home | That page’s translation link, publication status and actual URL |
| EN URL contains VI copy | Translated fields, shared template, cache and published revision |
| EN form submits but no lead arrives | Entries, notification target, localized form settings and CRM handoff |
| Search shows the wrong page | Visible language, canonical, hreflang, indexability and Google’s selected canonical |
Do not edit every translation when one shared template or cache rule may be responsible. Reproduce the issue on one URL pair, establish the cause and blast radius, test on staging where possible, then apply a controlled fix. Avoid deleting and recreating translations before backing up and inspecting their language relationships.
Maintenance scope and project boundaries
Website management can cover pair monitoring, post-update checks, menu/form/cache repairs, translation-link corrections and issue reporting within the agreed contract. Translating hundreds of pages, reworking a market’s content strategy, changing the site’s language URL architecture or building international CRM routing are separate projects. The website management pricing page is a reference; the number of languages, paired URLs, forms, plugins and approval steps determines the actual workload.
A useful report shows paired URLs tested, missing translations, broken switches, form failures, content differences awaiting owner approval, changes made and retest evidence. Mark a release complete only after the business owner approves the EN meaning and the operations team confirms the public journey works.
Frequently asked questions
WPML adds hreflang automatically. Why check it?
Automation is only one step. Verify on the public URLs that the pages are correctly connected, the canonical and indexability are appropriate, and the visible content is genuinely in the intended language.
Should visitors be forced to their browser language?
A forced redirect can prevent a visitor or crawler from reaching the chosen language URL. Provide a clear switcher and test direct access to each version.
Must every page be translated?
No. Prioritize pages needed by the audience and its enquiry journey. Make the behavior of untranslated pages clear; do not publish an EN shell around a largely Vietnamese article.
Does editing VI automatically update EN?
Do not assume so. Track which changes require EN editing, who approves them, when they go live and how forms, links, cache and search signals are retested.
Start with one important URL pair
Send the VI and EN URLs and describe where the customer journey breaks. IT Systems can separate an operational repair from translation or integration work.
