Actions

Actions at /actions is where you decide what to do about your AI visibility and then do it. Pages tells you which URL has a problem, Actions is where the work on it gets chosen, run and shipped, and Results says what the change earned.

It keeps two facts apart. Did the work ship? is one question. Did it earn anything? is a different one, answered weeks later by measurement. Work that shipped and moved nothing is a real, visible outcome.

One queue, one brief, one decision

Actions is a rail on the left and a brief on the right, with a single decision bar under the brief. There is no tab bar over the queue. Every row is one piece of work, and the group it sits in tells you what it is waiting on.

A row shows its title and one figure with its unit. Opening it fills the brief: the verdict, the first step, a facts band, Evidence (every check behind the row, each one a link to the surface it came from), the change or draft if there is one, What to do as numbered steps, and Activity.

The decision bar carries at most two verbs. The secondary is usually Decline or Later; the primary is chosen for that row, so it says what the click actually does rather than a generic "Start". Measuring and dismissed rows show a sentence instead, because there is nothing to decide.

The queue has a keyboard: j and k walk rows, e runs the primary verb, x dismisses, s snoozes, / focuses the filter, [ folds every group, ] opens them all, and ? shows the full map.

The six groups

Every group heading folds and states its own count. This week also carries the week's clock (Friday is the close) and, once something finishes, how many are done this week.

Results is not a group. It is a door at the foot of the rail showing how many judged results worked, because a measured outcome is not waiting on you. Opening it replaces the brief with the full Results table.

Old links still resolve: ?view=proof and ?view=measuring both open Results, and /proof redirects to /actions?view=results.

What lands in Needs your call

Four things, and none of them applies itself.

• A staged change the Agent prepared, shown as a before and after diff with its passing gates. Approve or Decline.
• A draft it wrote. Nothing sends itself; you send it or it stays a draft.
• A question that changes the plan, with the options it can see. Answer hands it to the Agent, or take Use the default.
• A measured drop, where a change coincided with a fall large enough to be worth a decision. Revert or Keep.

The nine kinds of work

The kind of work says what sort of change this is. It is not a status, and it decides what measurement will watch.

Those windows are the defaults. The frozen plan shown before you start has the final word, and each kind has a permitted range around its default rather than one fixed number.

Starting freezes the plan

Starting is a commitment to a plan, not a claim that the change is done. Everything except Setup opens What we'll measure first: the primary measure, the subject it applies to, anything else being watched, the window in days, and one line stating the bar. You also choose whether it joins this week's plan or just queues.

Confirm, and Trakkr stamps the plan and freezes it. Nobody swaps the measure later because a different number looks better. Declining asks why in one click (Not relevant, Wrong target, Bad evidence and five more), and that answer tunes what gets suggested next.

Once the work ships it leaves the active plan and appears under Measuring, then moves to Results when the window closes. The Agent never marks its own work Earned.

Doing the work

The brief shows exactly one way to do the work, picked for that row, so there is never a tab bar hiding three you do not need.

When a better path is one connection away, the surface offers the connection rather than hiding it. A handoff follows a plain division of labor: Trakkr diagnoses, your AI acts, Trakkr verifies. Mark as handed off starts the action and writes a note into Activity.

How much the Agent can do

Permission belongs to a standing automation, not to you as a person or to a kind of work in general. Each automation sits on one rung, and each area of work inside it can sit lower.

Outreach drafts and reply drafts are capped at Prepare drafts permanently. There is no rung that sends a pitch or posts a reply on your behalf.

The rung is a ceiling, not a promise. Before any autonomous change Trakkr checks that the target is a host you own, the platform can reverse that exact change, the original value is saved, the weekly limit has room, auto-rollback is armed, and the quality record is clean. Any failure stages the work in Needs your call instead. Agent permissions has the full rules.

Where suggested work comes from

Suggestions are built from evidence already attached to the brand, not from a content calendar: Search Console gaps, crawler access and fetch patterns, site audit findings, outreach sources worth being cited by, discussion threads, content gaps, competitor movement, perception and diagnosis findings, and answer accuracy checks.

The same suggestion appears wherever you meet the problem. Optimize, Accuracy and the crawler dashboard each embed the matching lane, and those rows are the same rows as the queue's, not a second list. Duplicate signals update one suggestion instead of filling the queue with copies, and a suggestion can retire when the fact behind it stops being true.

If the same work should happen every time a known condition appears, that belongs in Automations.

Common questions

How is this different from a to-do list?

Every row is tied to measured evidence, a subject, a kind of work and a frozen result plan. A to-do list holds what someone remembered to type, and it cannot retire itself when the underlying fact changes.

Will Trakkr push changes to my live site?

Only when the rung, the platform, the saved original, the target scope, the weekly limit and the safety checks all allow it. Suggest only and Prepare drafts never publish anything. If a platform cannot reverse a change, it is not applied automatically.

What is the difference between shipped and earned?

Shipped means the work is done. Earned means its frozen before-and-after measure cleared the published bar when the full window closed. Shipped with No movement is a real answer and stays visible.

Why did my action disappear from This week?

It shipped, so it moved to Measuring and then to Results. The work left the plan because it is finished; its outcome is not known yet.

Can I change the measurement after starting?

No. The plan is frozen at the moment you start. If the wrong page or measure was chosen, dismiss that item and start a new one with the right plan.

Why does the queue look empty on a new brand?

Suggestions are generated from your first completed visibility scan. Until that lands, Actions shows the loop in words and a Check again control rather than inventing work.