Validation report
Sampled search data shows strong launch-window demand, many long-tail guide clusters, and multiple young/weak niche domains already receiving clicks. The correct move is a small validation site, not a broad wiki.
| Source | Type | Main intent | Strong modules | Weaknesses | Reusable insight |
|---|---|---|---|---|---|
| Steam store | official | Game facts and requirements | Release date, developer/publisher, features, system requirements, languages, achievements | No strategy guidance | Use as the primary source for factual claims. |
| Steam Community | community | Discussions and troubleshooting | Real launch-week issues and user questions | Claims are noisy and unverified | Use for question discovery, not final fixes. |
| taskbarhero.wiki | fan database wiki | Runes, heroes, gear, stages, farming tools, drop tools, and broad wiki capture | Deep database modules, rune-node pages, hero pages, farming optimizer, drop finder, and visible stage/item scale | Broad wiki surface can be hard to maintain and often answers data lookup better than player decision context | Use it as a cross-check and intent validator; keep this site focused on decision guides instead of copying database structure. |
| tbhtaskbarhero.wiki | multilingual wiki | Wiki query capture across languages | Fast multilingual traffic capture | Little backlink support and likely template risk | Keep English first; localization can wait. |
| Game Rant | publisher guide | Best party setup | Covers comp, build, and class-related keywords | Publisher format is less useful for compact comparison | Combine tier and party pages around role decisions. |
| Sportskeeda | publisher guide | Class tier list | Page-level traffic from tier-list and best-class terms | Needs continuous updates to stay accurate | Tier page must expose criteria and update policy. |
| Pro Game Guides | publisher guide | Classes, pets, team comps | Matches expected page bundle for users | Can become too broad for a validation page | Use role-first modules and keep claims cautious. |
| GAMES.GG | publisher guide | Beginner guide and team combinations | Clear beginner funnel and team setup demand | Less source transparency | Beginner page should be a first-10-hours decision route. |
Ship a small English validation site with a home page plus beginner guide, role-first tier list, rune priorities, black-screen checklist, and farming route framework. Each page must show source notes, avoid copied competitor prose, and mark unverified gameplay values.