Release Checklist
Multilingual Release QA Checklist
This checklist creates one shared release gate for dev, content, QA, SEO, and AI agents whenever language, metadata, or locale routing changes.
Preflight
Lock scope before touching production.
The affected locales, routes, and release note must be explicit before the team starts validating the release candidate.
No multilingual release should proceed with hidden scope or unreviewed copy.
- Scope matches the release note
- Affected locales and routes are explicit
- Copy review is complete
- No placeholder or unreviewed machine translation remains
Language QA
Check visible UI text first.
Navigation, CTA labels, footer text, form copy, and error states must all match the active locale.
Vietnamese pages must use full diacritics and locked terminology. English pages must read naturally in international US English.
- One dominant language per page
- No mixed-language UI strings
- Locked product names remain consistent
- Vietnamese diacritics and English grammar are correct
SEO QA
Validate the metadata pack on every route.
Each indexable page needs a locale-specific title, description, canonical, hreflang cluster, Open Graph copy, Twitter copy, and schema language.
The checklist should catch duplicate metadata, missing alternates, and weak internal link language before release.
- One H1 per page
- Locale-specific title and description
- Correct canonical and hreflang cluster
- Localized Open Graph, Twitter, and schema fields
Browser & Menu QA
Do not separate language QA from browser QA.
Header navigation and language switching are part of the multilingual experience, especially on smaller viewports.
The team should confirm the menu opens, closes, resizes back to desktop cleanly, and does not trap the user in the wrong locale.
- Header menu works on desktop, tablet, and mobile
- Menu closes on link click, outside click, resize, and Escape
- Language switcher points to a true equivalent page
- Live HTML and assets match the intended release
Next step
Read source markdown
Use the HTML page for browsing and the source markdown for locked reference and audit trails.
Related