How to Invite Your Team to Kennext

Why bring your team in

Kennext is built for teams, not just auditors. Most SEO issues require collaboration: a developer to implement code changes, a content writer to update copy, and a marketing manager to prioritize and track progress. Inviting your team means everyone works from the same source of truth — no more exporting CSVs, pasting into spreadsheets, or losing track of what's been fixed.

Who to invite

Think about everyone who touches your website:

Your developer — They'll implement the AI-generated code fixes. Giving them direct access to the Kanban board means they can grab the fix code themselves without you acting as a middleman.

Your content writer or SEO manager — They can own metadata, content quality, and AEO issues. Many of these fixes don't require code — just CMS access and the AI-generated copy suggestions from Kennext.

Your marketing director or CMO — They can see the score trend over time, monitor progress without needing a weekly status update, and use the Compare Scans view to report on results to leadership.

How to invite a team member

Go to Settings in the top navigation bar and select the Team tab. Enter your team member's email address and click Invite. They'll receive an email invitation to create their Kennext account and join your workspace.

Once they accept, they'll have access to your scan results, Kanban board, and issue detail panels. You can assign issues directly to them from any card.

Team seat pricing

Additional team seats are $29 per month per user. There's no limit on how many team members you can add. Every seat gets full access to your workspace, including scan results, the Kanban board, AI fix generation, and integrations.

Assigning issues to team members

Once your team is in, open any issue card and use the Assignee field to assign it to a specific person. The assigned team member appears on the card face so the whole team can see who owns what at a glance. If your Slack integration is connected, the assignee also gets a Slack notification when an issue is assigned to them.

Tips for running an effective team workflow

Start with a short kickoff: share your scan results with the team, walk through the priority breakdown, and agree on who owns which categories. A good default split is developer owns Technical Health and Internal Linking, content writer owns Metadata Quality and Content Quality, and marketing owns AEO Readiness and Conversion Readiness.

Use the In Progress column to signal active work. Use Verified when a fix is deployed but not yet confirmed by a rescan. Run a rescan every two to four weeks to confirm fixes and catch new issues. The Compare Scans view gives you a clean before-and-after that's easy to share in a leadership meeting or client report.