DEV Community

xiaoyumao
xiaoyumao

Posted on

How I built a wiki for a 6.7B-visit Roblox game (keyword-first, one page per entity)

Jujutsu Shenanigans is a Roblox battlegrounds game by Tze's Shenanigans — 6.7B+ visits, 2.84M+ favorites, 27 characters, 14 complete movesets, and a Black Flash mechanic that hits for 2.5x damage. It's chaotic on the surface and surprisingly deep underneath.

I built jujutsushenanigans.org — a text-first wiki for it. Here's the process, in case you're thinking about building around a game you actually play.

The problem with game wikis

Most game knowledge lives in three places: a generic Fandom page, a 20-minute YouTube video, or a Discord thread that scrolls away. None of them help when you just want to know "what's the input for Black Flash?" at 11pm.

Players don't want a video. They want a page that loads in under a second and answers one question.

Keyword-first, not content-first

Before writing a single page, I mapped what people actually search for:

  • Character names — every playable fighter is its own search term
  • Codes — always the highest-volume query for Roblox games
  • Tier list / best character — evergreen comparison intent
  • "Black Flash" — the mechanic's signature move, a low-competition specific query
  • Combos / movesets — the advanced-play long tail

Every one of those becomes its own page. Not one giant "guide" — one page per real question.

Structure: one page per entity

The site is organized around the game's actual systems, not around SEO keywords:

Section What it covers
Characters 27 fighters, movesets, playstyles
Combos Beginner opener (3 M1s into a downslam) to advanced strings
Black Flash The 2.5x strike, timings, and the seven characters that can use it
Codes Active codes, redeemed in-game
Skill Builder Custom movesets and Workshop sharing

Each page links to the others — a character page links to its combos, a combo links to the mechanic it abuses. That internal linking is what turns a pile of pages into a wiki.

The stack

Static HTML plus a little vanilla JS. No framework, no build step, no database. Pages are written from game data and deployed as flat files behind a CDN. It loads instantly, it's cheap to host, and there is nothing to break when the game patches.

What I learned

  1. Game data beats generic SEO advice. The best page on the site isn't "Jujutsu Shenanigans guide" — it's the Black Flash page, because that's a real question with a real answer.
  2. One page per player question. If a player would type it into Google, it deserves a page.
  3. Internal links are the wiki. The value is the graph, not any single page.
  4. Update on patches. A wiki that's stale on the current patch is worse than no wiki.

If you play Jujutsu Shenanigans (or are thinking about building a wiki for a game you love), the site is live at jujutsushenanigans.org — characters, combos, Black Flash timings, and codes.

What game would you build a wiki for?

Top comments (0)