Docs

What is Claude SEO Dungeon?

Claude SEO Dungeon is an open-source AI SEO tool built as a Claude Code skill. It turns full-site SEO audits into 16-bit boss battles — every SEO issue becomes a demon you can fight, and every fix is a real code edit made by Claude. The tool ships with 23 SEO skills and orchestrates up to 17 parallel subagents during a full audit. MIT licensed. Free to use; you provide your own Claude Code subscription or Anthropic API credits.

The game is an optional gamified interface. Everything the dungeon does is also reachable from the Claude Code CLI via commands like /seo audit, /seo technical, or /seo schema.

Architecture

The dungeon has three processes that talk to each other: the browser game (Phaser.js + Vite), a small bridge server running on port 3001, and Claude Code CLI running on your machine.

Browser (Phaser.js)
    ↓ WebSocket
Bridge Server (:3001)
    ↓ spawn
Claude Code CLI
    ↓
SEO Skills (23) + Subagents (17)
    ↓
Your project files (read + edit)

The bridge server is the only thing that spawns Claude Code processes. It receives commands from the Phaser front-end over WebSocket, shells out to Claude Code with the model mapped to your character class, streams results back to the browser in real time, and surfaces every tool call and file edit in the Guild Ledger so you can see exactly what Claude is doing to your code.

Install

Requires Node.js 18+, Python 3.10+, Git, and Claude Code installed and authenticated. The installer copies all 23 skills and 17 agents into your Claude Code config.

# 1. Clone the repo
git clone https://github.com/avalonreset/claude-seo-dungeon.git
cd claude-seo-dungeon

# 2. Install the Claude SEO skill suite
#    (copies 23 skills + 17 agents into your Claude Code config)
.\install.ps1          # Windows
bash install.sh         # macOS / Linux

# 3. Start the dungeon front-end
cd dungeon
npm install
npm run dev             # opens http://localhost:3000
                        # bridge server auto-starts on :3001

After the installer finishes, run claude in any project directory and type /seo audit to kick off a full audit without the game. To play the game, start the dev server and open the URL it prints.

Character classes

Your class selects which Claude model the dungeon calls during gameplay. The choice trades off analysis depth, response speed, and token cost.

Combat loop

Each dungeon floor is one page of your site. Each demon is one discovered SEO issue. In battle you have four actions:

• Attack — You type a prompt describing what you want Claude to do about this issue. The selected demon's severity, category, URL, file, and selector travel with your prompt as a structured focus header, so Claude knows exactly which issue you're on. Polite directives become real code edits; questions get answered without triggering edits. You can Attack as many times as you want — real fixes often need multiple prompts. The Guild Ledger streams every tool call, file read, and edit live on the right.
• Vanquish — Your judgment call that the demon is handled. Marks the issue defeated in your quest log. You decide when the fight is done, not the machine.
• Defend — Flavor action. Adds animation theater without changing code.
• Flee — Skip this demon and return to the Dungeon Hall. You can come back and fight it later.

Outside of battle the Guild Ledger becomes a plain pass-through to claude -p, so you can chat with Claude about anything with no SEO scope applied. Git commits are not automatic — every code edit stays in your working tree so you review and commit on your own cadence.

All 23 SEO skills

Every skill runs as a specialized subagent during a full audit. You can also invoke any of them individually from the Claude Code CLI.

Using the skills without the game

The game is optional. Every skill above is callable directly from Claude Code:

claude
> /seo audit https://yoursite.com
> /seo technical yoursite.com
> /seo schema yoursite.com --generate

The CLI mode is what you want for CI pipelines, headless runs, or repeated audits on a schedule. The game exists for a more tactile, exploratory experience when you want to walk through findings visually.

FAQ