How to Use Your Kennext Kanban Board
Created Date
26 Nov, 2025
.png)
INTRODUCTION
From audit to action
Most SEO tools give you a list of problems and leave you to figure out the rest. Kennext's Kanban board turns your scan results into a managed workflow — with priorities, assignments, effort estimates, and AI-generated code fixes — so your team can actually get issues resolved instead of just knowing about them.
Understanding the columns
Your Kanban board has four columns that mirror a standard development workflow:
New — Issues identified by your most recent scan that haven't been assigned yet. This is your inbox. Every new scan adds issues here.
In Progress — Issues your team is actively working on. Drag cards here when someone picks them up, or assign them to a team member to signal ownership.
Verified — Issues your team has marked as fixed. When you run your next scan, Kennext will automatically confirm whether the fix worked. If it did, the card stays in Verified. If the issue is still present, it moves back.
Closed — Issues that have been resolved and confirmed by a rescan, or issues you've intentionally dismissed.
Understanding priority levels
Every issue card has a colored priority stripe on its left edge:
P0 — Critical (Red): Issues that may be actively blocking search engine indexing or causing significant ranking loss. Fix these first.
P1 — High (Orange): Important issues with meaningful SEO impact. Should be addressed in the near term.
P2 — Medium (Yellow): Moderate impact. Good to address once P0 and P1 issues are cleared.
P3 — Low (Gray): Minor improvements. Address when bandwidth allows.
Effort estimates
Each issue card shows an effort size: S (Small), M (Medium), or L (Large). This reflects how much developer or content time the fix is likely to require. Use this alongside priority to plan your sprint — a P1/S issue is the ideal quick win to tackle first.
Using the AI fix button
Click any issue card to open the detail panel. At the bottom you'll find the Generate Fix button. Click it and Kennext's AI writes the exact code or copy change needed to resolve that specific issue on your specific site. You can copy the output directly and hand it to your developer, or paste it into your CMS yourself.
The fix is generated based on the actual page and issue context — not a generic template. Each fix is unique to your site.
Assigning issues to team members
Click any card and use the assignment field to assign it to a team member. Assigned team members receive a Slack notification if your Slack integration is connected. The assignee's name appears on the card face so everyone can see at a glance who owns what.
Filtering and searching
Use the filter toolbar above the board to filter by priority, category, effort size, or assignee. The search bar lets you find issues by keyword. This is especially useful on large sites with many issues — you can quickly pull up all P0 Technical Health issues, for example, and work through them as a batch.
Tracking progress over time
The summary bar above the board shows live counts of issues by priority. Run a rescan after making fixes and use the Compare Scans view to see exactly which issues were resolved, which are new, and how your score changed. This is your proof-of-progress report for leadership.

.png)
