IAI Foundation
EN VI

Operational Standard

Language and Multilingual SEO Standard

This standard locks how IAIFoundation.com handles page language, route parity, locale-specific metadata, and multilingual release quality.

Treat each locale as a first-class product surface with its own meaning, metadata, and QA gate.

Locked Baseline

Use one route key across locales.

English stays on the root route. Every non-default locale uses a locale prefix while keeping the same route key.

Canonical URLs always point to the apex host and each locale page self-canonicalizes to its own URL.

  • Primary host: https://iaifoundation.com
  • Default locale: English on /
  • Active localized locale: Vietnamese on /vi/
  • Route parity required for home, docs, partners, and future public routes

Language Governance

One page, one dominant language.

Navigation, headings, body copy, CTA labels, metadata, and structured data must all match the page locale.

The only exceptions are locked brand or product names and approved technical nouns that would lose meaning if translated.

  • Do not mix English metadata into Vietnamese pages
  • Do not publish placeholder translations
  • Do not ship mixed-language navigation or footer labels
  • Do not change locked terminology without an approved decision record

Vietnamese SEO

Vietnamese is its own search surface.

Vietnamese content targets Vietnam-based readers and search behavior. It is not a side effect of English localization.

Every Vietnamese page must carry its own title, meta description, Open Graph copy, Twitter copy, structured data language, and internal anchor language.

  • Use full Vietnamese diacritics everywhere in visible UI and metadata
  • Use vi_VN as the Open Graph locale
  • Do not reuse the English keyword cluster on Vietnamese pages
  • Do not index a Vietnamese page before its metadata and schema are localized

Release Gates

No multilingual work is complete without proof.

A locale or SEO task is only done when the localized copy, metadata, hreflang cluster, sitemap, schema, and live smoke checks all agree.

The release team must use the locale brief and the multilingual QA checklist before a new locale or updated localized page goes live.

  • Update localized HTML, sitemap, locale manifest, and switchers together
  • Keep users inside the same locale whenever an equivalent route exists
  • Attach QA evidence before claiming completion
  • Escalate any change to route model, default locale, or locked terminology

Next step

Read source markdown

Use the HTML page for browsing and the source markdown for locked reference and audit trails.

Read source markdown

Related