multilingual-readiness

What this datapoint measures

Actual multilingual content availability with depth parity across language variants. Whether the brand’s content depth, coverage, and freshness are comparable across the languages the brand operates in, or whether one language (typically English) dominates and the others are thin.

This datapoint is structurally different from hreflang-implementation. Hreflang measures whether the cross-reference structure is correct; multilingual-readiness measures whether there is actual substantive content in each language to cross-reference.

What high looks like

• Each language variant has content covering the brand’s primary topics in depth
• Per-language content is original or substantively localized, not auto-translated
• Update cadence is similar across languages (a new feature announcement appears in all language variants within a similar timeframe)
• Per-language content has the same structural quality (headings, formatting, citations) as the primary language
• Localized content reflects local market context where appropriate (regional pricing, compliance, market conventions)

What low looks like

• Some languages have substantial content, others are thin or missing
• Translated content with no localization (literal translations that miss local conventions)
• Update lag — one language sees new content months after the primary language
• Language variants with shorter content than primary (truncated translations)

What at floor looks like

A brand at floor on multilingual-readiness has implemented hreflang and language navigation but the actual multilingual content is minimal. The brand’s “Japanese site” may consist of a translated homepage and a few pages, with most of the brand’s depth available only in English.

This is common in brands that have begun multilingual expansion but not completed it. The brand’s stakeholder may describe operations as multilingual (“we have a Japanese site”) while the operational reality is single-language with translated marketing surfaces. The remedy is Manifest-pillar work in the lagging languages, typically scoped as multi-cycle commitment given the editorial capacity required.

What affects this datapoint

• Per-language content depth measured against primary language
• Per-language content freshness measured against primary language
• Per-language content coverage of primary topics
• Whether content is translated, localized, or originally written per language
• Per-language editorial cadence

OMG actions that influence this datapoint

Action	Influence
O-4 Technical Infrastructure, Performance & International Foundation	Indirect. O-4 enables multilingual sites to work technically; the content depth itself is M-pillar work.
M-1 through M-10 (Manifest-pillar actions)	Direct. Multilingual-readiness lifts when the M-pillar actions are executed in each target language.
G-2 Advanced Topic Clustering	Substantial. Per-language topic clustering establishes the structural plan for content depth; without it, multilingual expansion is unfocused.

Multilingual considerations

This datapoint is the multilingual datapoint. Per-language considerations from Document 1, Part 6 apply directly.

A common operational pattern: brands score this datapoint very differently across languages. A brand may show high multilingual-readiness in English (the primary language is fully developed), low in Indonesian (some translation, some localization), and floor in Japanese (effectively absent). The diagnostic conversation is per-language, not aggregated.

Common failure modes

• Auto-translation pipelines producing literal translations that miss local conventions
• Outsourced translation without editorial review producing inconsistent terminology
• Translated content missing the cultural and market context that makes the primary content effective
• “Multilingual” implementation that translates only the marketing surface (homepage, landing pages) while leaving the depth content (blog, knowledge base) English-only
• Update lag where new primary-language content takes months to appear in other languages
• Translation that loses citations and attribution because the original sources are English-only

Diagnostic interpretation

Multilingual-readiness at floor for a brand the stakeholder describes as multilingual is a critical engagement-scoping moment. The practitioner must surface the gap between stakeholder claim and operational reality, recommend either reducing scope to actual operational capacity or scoping a Manifest-pillar build in the lagging languages.

Multilingual-readiness at low with hreflang-implementation at high indicates a brand whose technical multilingual infrastructure is correct but whose content underneath is incomplete. The technical work is done; the editorial work is not.

Multilingual-readiness at high in only one language indicates a single-language brand. This is fine if the brand’s operational scope is genuinely single-language; the datapoint should be evaluated per-language rather than aggregated.

---