What to Decide When Operating a Japanese–English Website CMS
A Japanese–English site can launch with both languages complete and still drift apart with each later update. A CMS alone does not prevent this. The team needs a workable answer to who owns each kind of information, what gets reviewed, and whether one language can be published before the other.
Start with responsibility, not screens
When the person who updates, checks specialist facts and publishes is unclear, adding more CMS access rarely helps. Divide the roles simply and give people only the access they need to do their real work.
A responsibility table for bilingual CMS operation
| Role | Main responsibility | Language-specific check |
|---|---|---|
| Content owner | Provide the change trigger and source material | Does this require an update in both languages? |
| Fact owner | Approve conditions, figures, names and specialist information | Do the shared facts still agree? |
| Language editor | Make the information natural and useful for its audience | Does a direct translation omit necessary context? |
| Publisher | Check status, links, rendering and release time | Are the counterpart and language switch appropriate? |
| Operations owner | Set priority, exceptions, review and handover rules | How should incomplete or stale information be handled? |
In a small team, one person can hold several roles. It is still useful to record the capacity in which something was checked: the person writing a sentence is not necessarily the person authorised to approve the underlying business fact.
1. Give each content type an owner
Services, news, recruitment, cases and company information have different update frequencies and reviewers. Record which items must correspond in Japanese and English, which can begin in one language, and which facts require both versions to be revisited after a change. Make publication status visible instead of forcing every page through the same translation deadline.
2. Share translation, review and publication status
When the team can see whether a page is being drafted, translated, fact-checked, edited or published, it is easier to find incomplete and outdated information. Where important conditions or figures change, the source fact should remain clear even if different people manage each language.
3. Distinguish simultaneous, staged and language-specific publication
Conditions, prices and important notices may need both languages to change together. A local event or audience-specific article may reasonably exist in one language. For a staged release, record the other language’s state, owner, target and any explanation visitors need. A visible status is more responsible than leaving old copy looking current.
| Release model | Suitable condition | Record to keep |
|---|---|---|
| Simultaneous | Conditions, company facts or important guidance must agree | Reviewers for both languages and the release decision |
| Staged | There is an operational reason for one language to publish first | Other-language state, owner, target and interim guidance |
| Language-specific | The audience and subject genuinely belong to one language | Why no counterpart is planned and what would trigger review |
4. Match CMS permissions to the work
WordPress roles and capabilities can separate who creates, edits, publishes and changes settings. Giving every contributor administrator access is less useful than assigning the minimum practical permission and reviewing access as people change roles. It also makes handover clearer.
5. Keep a path for urgent and routine updates
For a change to hours, contact details, events or important guidance, decide who updates each language. Keep a route for urgent corrections as well as normal publishing. A realistic monthly or quarterly review of corresponding pages is often more sustainable than waiting for perfect completeness.
6. Match the change record and recovery path to the content
For an important change, retain the source, affected pages, contributor, reviewer and release time. CMS revisions may not restore an external form, image, translation workflow or cache. Decide who checks the affected scope, and how an earlier approved version can be consulted, according to the actual setup.
Keep planning, information architecture and operation distinct
Use the Japanese–English website planning guide for the initial brief and the information-architecture guide for page relationships and message order. This article owns the continuing questions of roles, states, exceptions and change records.
OPERATE BOTH LANGUAGES
Could bilingual updates rely on a clearer system than individual memory?
Starting with your current CMS, content and review process, we can organise practical roles and publishing rules.
Review and sources
Reviewed 20 August 2026. See WordPress’s Roles and Capabilities documentation and Google Search Central’s guidance for localised page versions.
