The SEO project management tool where the backlog writes itself

Because the backlog is the hard part, not the board. Most SEO task lists are copied by hand from audits, keyword sheets and Search Console exports, then sorted by gut feel. By the time the list is tidy, the data behind it is old.

General project tools are good at tracking work once it exists. They don't know that one broken footer link is behind 3,000 audit findings, or that a page slipping to position 12 is worth more this week than a new blog post. An SEO project management tool should know both.

Every analysis in LogNorm produces moves, and each move records the source that found it. A move is one concrete piece of work: fix pages Google can't index, refresh an article losing clicks, write a comparison page.

When a second source finds the same move, LogNorm adds the evidence to the existing move and raises its confidence instead of creating a duplicate. See Moves and ranking.

By head-to-head comparison, not a formula. LogNorm asks which of two moves the team should do first this week, weighing upside, odds of working, effort and urgency, and fits the answers into one ranked list.

Each move's page shows its position, such as #4 of 62 open moves, and which moves it beat and lost to. You keep the last word: Rank higher, Rank lower or a drag in the weekly plan is stored as a preference and respected on every later pass.

You set a weekly target, how many moves the team can finish, and LogNorm recommends the top-ranked moves to fill it. You plan them into days, assign owners and track them to done.

• Fill to target adds the top recommendations until the week reaches your number; you can always plan more.
• A lane per day plus Anytime this week, with drag and drop on desktop.
• Unfinished moves from earlier weeks appear as carry-over, one click to bring forward.
• The week shows planned, in progress and done counts, the mix of work and total effort.
• A Monday digest emails every member the plan, carry-over, recommendations and last week's outcomes.

The Growth Plan page shows it in action.

Every move has the same shape, so anyone on the team, or an AI agent, can pick it up without a briefing call. The page holds the why, the evidence and the history in one place.

Content moves turn into a brief and are published from the editor. Fix moves come with a checklist and close with Mark done, or with Validate fix when they came from an audit.

Give each move an owner and, for content, a reviewer. People you assign get a notification, and the move shows on their list.

Assign from the move's page, or from a card's menu in the weekly plan. Content goes through Request review: the reviewer approves it or sends it back to drafting with a note, and only approved pieces can go live. Planning, assigning and publishing need the Owner, Admin or Editor role, so a Contributor can work their moves without reshuffling the week. The review workflow and custom roles are on the Growth and Scale plans.

Both, on the same plan. People claim and own moves, and AI coding agents such as Claude Code or Codex connect over MCP and claim moves the same way.

Claims are atomic, so two workers never pick the same move. Agents post their plan, changed files and pull request links as comments on the move, and their drafts go to a person for review. Roles decide the rest: Contributors see the moves assigned to them, Editors plan and review, Analysts run research. See roles and permissions.

Moves move through clear statuses, from Discovered and Planned through Drafting and In review to Published, Measuring and Won. A board view on the Moves page shows them by status.

Shipping is not the end. LogNorm records a Search Console baseline when a move goes live and measures it at 28 and 90 days, marking it Won when the numbers move enough. Campaigns group moves around one goal with a target such as moves shipped or clicks per 28 days and a due date.