ANANTA Codex uses this keyword map as a public content directory. The goal is simple: connect common search intent to the most useful maintained page, avoid duplicate thin articles, and make it clear which topics are ready now versus waiting for official launch data.
This is not a private SEO dump. It is a reader-facing navigation page for people who arrive before ANANTA has a full launch database. As the game moves from pre-launch marketing into public testing and release, this map will evolve into a stronger wiki index with characters, equipment, bosses, quests, map pages, and system explainers.
Release and platform intent
| Search intent | Best current page | Notes |
|---|---|---|
| ANANTA release date | Release date and platforms | Top-level source-first launch tracker. |
| ANANTA beta date | Beta date tracker | Use for test timing, eligibility, and carryover questions. |
| ANANTA pre-registration | Pre-registration guide | Explains official reservation flow and safe source checks. |
| ANANTA PC | PC release info | Storefronts, launcher, controller, and account questions. |
| ANANTA PS5 | PS5 release info | PlayStation-specific status and future PS Store checks. |
| ANANTA mobile | Mobile release info | Combined mobile overview. |
| ANANTA Android | Android release info | Google Play, APK safety, device requirements. |
| ANANTA iOS | iOS release info | App Store, iPhone/iPad, controller support. |
Systems and beginner intent
| Search intent | Best current page | Notes |
|---|---|---|
| ANANTA beginner guide | Beginner guide | Pre-launch orientation without fake launch routes. |
| ANANTA gacha | Gacha system explained | Tracks acquisition and monetization claims carefully. |
| ANANTA reroll | Reroll guide | Pre-launch checklist; no invented reroll route. |
| ANANTA crossplay | Crossplay and cross-save tracker | Account-linking and platform transfer watchlist. |
| ANANTA PC requirements | PC requirements and settings | Hardware, settings, and performance test plan. |
| ANANTA vs Genshin Impact | ANANTA vs Genshin Impact | Comparison page focused on structure, not fandom bait. |
Character intent
Character searches are currently routed to source-first profiles rather than build pages. Build pages need confirmed skills, stats, equipment, and team rules; profile pages can be useful earlier if they clearly separate confirmed details from interpretation.
| Search intent | Best current page |
|---|---|
| ANANTA characters | All confirmed characters |
| ANANTA tier list | Character tier list tracker |
| Captain ANANTA | Captain |
| Richie ANANTA | Richie |
| Seymour ANANTA | Seymour |
| Taffy ANANTA | Taffy |
Database intent after launch
Some search intent should not be forced before official data exists. Bosses, equipment, materials, quests, and map pages need names, locations, rewards, and repeatable testing before they become strong standalone pages.
| Future intent | Current hub | Publish criteria |
|---|---|---|
| ANANTA bosses | Boss codex | Confirmed boss names, encounters, weaknesses, rewards, or beta footage. |
| ANANTA weapons | Equipment codex | Confirmed weapon types, stats, acquisition, and upgrade paths. |
| ANANTA map | Future map hub | Official district names, collectibles, or route data. |
| ANANTA quests | Future quest hub | Quest names, objectives, rewards, and branching notes. |
| ANANTA materials | Equipment/material pages | Drop sources, upgrade recipes, and farming routes. |
Internal linking rules
ANANTA Codex avoids making many small pages that answer the same question poorly. When several searches share one intent, they should point to one stronger page until the topic has enough confirmed information to split.
- Release date, platforms, beta, and pre-registration pages should cross-link because users often ask all four questions together.
- PC, PS5, Android, and iOS pages should link back to the main release tracker so platform details do not drift away from source status.
- Character profiles should link to the confirmed roster and tier-list tracker, but not pretend build rankings exist before kits are public.
- Boss and equipment pages should stay hub-first until individual entries have real data.
- Any page that is mainly an editorial planning note should either become a useful public directory or remain noindex.
Quality bar
Every indexed page should do at least one useful job for a reader today: answer a known question, summarize the official state, explain what is still unknown, provide safe-source guidance, or point to a better maintained page. If a page cannot do that yet, it should be drafted, noindexed, or merged into a stronger hub.
This map is reviewed whenever a major content cluster changes, especially around platform announcements, beta tests, new character reveals, and public build access.