Language plan overview
This page prepares Azur Promilia Guide for future multilingual SEO without creating thin or risky translated pages too early. English remains the canonical source while the game is still in a pre-launch state.
Future translated pages should keep the same verification labels as the English source and avoid publishing unconfirmed gameplay claims.
Language roadmap
| Language | Path | Status | First pages | Rule |
|---|---|---|---|---|
| English | / | Canonical active | All current guide, database, media, tool, support, and policy pages. | English remains the source version for facts, titles, slugs, and verification notes. |
| German | /de/ | Planned | Codes, Download, Kibo, Map, FAQ, Help. | Translate stable page structure first; keep unverified gameplay fields marked as pending. |
| French | /fr/ | Planned | Codes, Download, Kibo, Map, FAQ, Help. | Use the same source labels as English and avoid converting assumptions into confirmed claims. |
| Spanish | /es/ | Planned | Codes, Download, Kibo, Map, FAQ, Help. | Prioritize high-intent launch pages before full database translation. |
| Japanese | /ja/ | Planned | Codes, Download, Kibo, Map, FAQ, Help. | Keep official names and terms aligned with the English source page until official localized terms are verified. |
| Korean | /ko/ | Planned | Codes, Download, Kibo, Map, FAQ, Help. | Translate stable routing and support pages first, then expand database pages after source checks. |
Live pilot pages
These first language pages cover low-risk search intent: codes and download. They keep unverified code, client, and gameplay details marked as pending until official confirmation exists.
| Language | Home | Codes | Download |
|---|---|---|---|
| German | /de | /de/codes | /de/download |
| French | /fr | /fr/codes | /fr/download |
| Spanish | /es | /es/codes | /es/download |
| Japanese | /ja | /ja/codes | /ja/download |
| Korean | /ko | /ko/codes | /ko/download |
Next translation targets
After the first utility pages, the next best translation targets are the new matrix pages and trust pages: character team synergy, material usage matrix, weapon usage matrix, quest reward routes, region progression paths, boss strategy matrix, trust dashboard, and page trust matrix.
Translation phases
Stable utility pages
These pages serve high-intent searches and can be translated without inventing gameplay details.
Kibo and map hubs
Kibo and map topics are distinctive to Azur Promilia and can support strong long-tail growth.
Character and database hubs
Database depth should expand once official or in-game fields are stable enough to localize.
Tools and community pages
Tools and feedback pages help returning readers, but translation should follow verified workflow wording.
Quality rules
| Rule | What it means |
|---|---|
| Canonical source | Use English pages as the source of truth for facts, internal links, and verification labels. |
| Slug strategy | Use short language folders such as /de/, /fr/, /es/, /ja/, and /ko/ when full localized pages are ready. |
| Claim safety | Do not translate pending, beta-only, or unverified gameplay details as confirmed facts. |
| Page parity | Keep page titles, headings, FAQ blocks, and related links aligned across language versions. |
| Media reuse | Reuse official images and videos only with the same source labels and cautious captions. |
| Search intent | Translate player questions naturally instead of word-for-word when search behavior differs by language. |