The ranked backlog your team and your agents work from

A move is one piece of growth work: a page to publish, a page to refresh, a technical fix, an internal-linking change, a comparison or integration page, or an AI visibility gap. Every move carries the evidence that produced it, a plain-language reason, impact, confidence and effort signals, and a place in the ranking. Site audits, Search Console, keyword research, competitor analysis and AI visibility checks all produce moves, so there is one backlog instead of five reports.

Priority is relative, so LogNorm never scores a move on its own. It compares open moves in pairs and asks which should come first if the team can only do one this week. Each pair is asked both ways round, because a model can lean towards whichever option it reads first. A Bradley-Terry fit then turns all the answers into one ranking. Each move shows the moves it came out ahead of and the moves it is behind.

Yes. Use Rank higher or Rank lower on a move, or drag moves into a different order in the week planner. LogNorm stores each of those calls and applies it as a constraint on every later ranking pass, so the order you chose holds and the ranking learns what your team cares about. If you edit a move's impact, confidence or effort, LogNorm uses your numbers when it compares.

You set a weekly target, for example five moves. LogNorm suggests the top-ranked moves that aren't planned yet, and Fill to target adds enough of them to reach it. The target is a guide rather than a limit: you can plan more, and the capacity bar turns amber when you go over. Unfinished moves from past weeks can be carried into the current week in one click.

When a move is published, LogNorm records a baseline from Google Search Console for the 28 days before publishing. It measures the page again at 28 and 90 days. A move counts as won when clicks rise by 20% or more, impressions rise by 20% or more, the page goes from zero to at least 10 clicks or 100 impressions, or its average position improves by three places or more. Outcome measurement needs Search Console connected.

Different sources can find the same opportunity, for example a competitor gap and a Search Console query that point at the same page. LogNorm checks moves for the same intent and shows possible duplicates side by side. You choose which one to keep, and the other one's evidence moves across, or you mark them as not duplicates and LogNorm won't suggest that pair again.

No. A solo founder can set a target of two or three moves a week and ignore assignments and campaigns entirely. Teams can assign owners and reviewers, group moves into campaigns and use the weekly digest to keep everyone on the same plan.

Yes. Connect Claude Code, Codex, Cursor or Claude and it joins your workspace as a named teammate. It reads the plan in LogNorm's rank order, claims moves so two agents never work on the same one, comments its plan and progress, and moves work forward. Your team reviews and publishes.