Every time I run an audit and generate a fix list, the list becomes a problem. 40 findings land on my screen. I fix three, close the tab, come back next week, can't remember what I did.
The fix is a board. Not a Linear project board — that costs $8 per seat and requires an account. Not a Trello board — you pay once you want more than 10. A simple 4-column kanban that lives in localStorage on this site.
The SEO Action-Tracking Kanban is exactly that.
What it does
Four columns: To do, Doing, Blocked, Done.
Each card has:
- Title (required)
- Priority (high / medium / low, color-coded)
- Category (free text — "Performance", "Schema", "AEO", anything)
- Notes (optional body)
- Created timestamp
You can:
- Add cards manually
- Bulk-import from a findings list (paste
[fail] Performance: LCP 4.8s\n[warn] AEO: No llms.txt— each line becomes a card in "To do") - Drag cards between columns with your mouse
- Click arrow buttons to move cards step-by-step
- Block a card with the Block button (goes to Blocked column)
- Delete cards
- Export the whole board as JSON
- Clear the Done column in one click
Everything persists in localStorage. Close the tab, come back next week, board is exactly where you left it.
The bulk import is the point
Running an audit produces a findings list. Bulk import turns that list into cards:
[fail] Hygiene: No meta description
[fail] Performance: LCP 4.8s (POOR)
[warn] Security: No CSP header
[warn] AEO: No llms.txt file
[fail] Schema: Missing Article schema
Paste into the Bulk Import textarea, click Import. You get five cards in To do, priority auto-assigned (fail → high, warn → medium, info → low), category extracted from the prefix ("Hygiene", "Performance", etc.).
Now you drag them. As you fix each, move to Doing, then Done. Progress is visible.
Why drag-and-drop + buttons
Mouse drag is fast for people at a desk. The arrow buttons handle touchscreens, keyboard-only users, and power users who dislike drag targets. Both interact with the same model; the board updates live.
Integration with the rest of the stack
- Mega SEO Analyzer v2 — run audit, get findings list, paste into kanban
- SEO Roadmap Generator — produces a 30/60/90 structure; kanban makes it executable
- Scheduled Auto-Monitor — when a regression fires, add a card via the bulk import
- Code-Diff Patch Generator — each patch suggestion becomes a kanban card
The tools don't formally talk to each other, but they compose: each outputs a findings-shaped list, each list is paste-ready for kanban import.
Why this is the end of the transformative series
When I mapped out the "10 transformative additions" to Mega SEO Analyzer two sessions ago, this kanban was item #13. It's not sexy — localStorage + drag + 4 columns. But it's the final piece that turns an audit workflow into an execution workflow.
Audit → findings → kanban → done.
Without the kanban, audits produce anxiety. With it, they produce progress.
Related reading
- HTML Sandbox Playground — paired release
- SEO Roadmap Generator
- Mega SEO Analyzer v2 — paid-tool parity
Fact-check notes and sources
- localStorage capacity: MDN Web Storage API. 5-10 MB per-origin quota.
- Drag-and-drop API: MDN HTML Drag-and-Drop API.
- Linear / Trello reference pricing: Linear pricing, Trello pricing as of 2026-04.
This post is informational. Mentions of Linear, Trello, Asana, Jira, GitHub Projects, Notion, and similar products are nominative fair use. No affiliation is implied.
