Mapping Pages for a Bilingual WordPress Website
Published:
Published by: Hedou Bibi
Map Chinese-English pages around visitor journeys, real translation relationships, missing versions and language-switch acceptance checks.

A bilingual website needs complete visitor journeys, not necessarily identical page counts. An English service page is not enough if its contact button leads to an untranslated form. Start with what each audience must do, then decide which pages need counterparts.
Map the visitor journey first
Follow a customer from service details through supporting information, contact instructions, form labels and the result message. Localised copy can use a different structure while preserving accurate service boundaries, specifications and contact details. Record deliberately untranslated editorial material separately from work still awaiting translation.
A working page map
This invented planning example is not a client record. Add real page IDs, final URLs, owners and version dates when applying it.
Scroll horizontally or use the arrow keys to view the full table.
| Purpose | Relationship | Acceptance check |
|---|---|---|
| Service detail | Independent versions of the same service | Switching preserves the service and its facts |
| Contact journey | Shared goal with localised instructions | Buttons and form messages use the intended language |
| Editorial article | Counterpart depends on audience need | Distinguish pending translation from intentional omission |
| Menus and categories | Routes to real language content | Check each destination, not only its label |
Store a real translation relationship
Similar titles and URL patterns do not prove that two pages are translations. The Polylang content translation guide explains assigning languages and linking existing versions or creating a translation. Save the actual relationship and verify it on the public site.
Use a slug convention supported by the installation. Do not force identical slugs or rewrite working public addresses just for consistency. Record redirects, numbered duplicates or mixed-language bodies as issues to resolve before acceptance.
Define missing-version behaviour
Agree what visitors should see when a counterpart is unavailable. Evaluate omitting an unavailable target, explaining the gap or offering relevant material in the chosen language. The actual behaviour depends on the theme and plugin configuration and requires testing. An unexplained jump to the homepage can look like a broken article switch; an unrelated page must not be presented as a translation.
Google’s localised-version guidance describes reciprocal references between real language versions. Checking one annotation on the Chinese page does not establish that the pair is correct.
Test both directions as a visitor
Open the final URLs while logged out. Review headings, body text, images, menus and contact links. Switch to the counterpart and back, recording both destinations. Check descriptions, canonical URLs and language annotations against the map. Use long headings and actual tables for mobile layout checks.
Use the multilingual launch checklist for the wider journey, and discuss page inventory, editorial ownership and acceptance scope through Hedou Bibi’s multilingual website service.
Keywords: wordpress, bilingual page mapping, translation relationships
