Actions and measurement

An Action groups work around a target: an owned page, planned page, earned-source page, product, category, search query or visibility prompt. Multiple findings can support the same Action.

This gives your team one place to understand the diagnosis, start Agent work and track implementation.

Choose what to work on

Open Agent → Actions. Use status and target filters to narrow the list, then inspect an Action’s detail.

Read the diagnosis, contributing evidence, recommended approach and what to avoid. The priority comes from CiteLadder’s deterministic rules. An Agent explanation does not replace that ranking or create new measured facts.

Choose Work on this when the Action is suitable for your team. Linked chats remain visible on the Action.

Understand status

Status	Meaning
Open	Available work that has not been dismissed or declared implemented
In progress	An open Action has a linked chat with an output
Dismissed	A user has set the Action aside
Implemented	A user has explicitly declared the work implemented
Measuring	Later observations have not verified every expected check
Done	The latest observation verified every expected check

A generated draft does not mean the work has shipped. Dismissal is not implementation. A later conflicting observation can move previously verified work back into measuring.

You can dismiss or reopen eligible Actions. Declared work follows its measurement lifecycle rather than being freely overwritten with another status.

Declare implementation

First make the change in your website, publishing workflow or external process. Then use Mark implemented for the relevant Action.

When work came from the Agent, confirm the output revision that matches what you shipped. An outline is not an implemented draft. Work done outside CiteLadder can be declared without an Agent output.

CiteLadder uses the Action’s current findings to determine the expected checks. An Action without a current finding cannot be declared merely to create a measurement plan.

Read the measurement result

The declaration keeps the target, baseline and expected checks tied to that implementation event. Later eligible crawls, audits, traffic imports or source inspections provide the observations used to check it.

Review what each measurement leg is waiting for. A missing later crawl or incompatible window is a reason for limited measurement, not an observed failure.

An earned-source Action checks the relevant placement or discrepancy on the publisher page. That is distinct from proving a later visibility improvement.

Report progress honestly

Use “implemented” for the work your team shipped and “verified” for the checks supported by later evidence. Neither status proves that the change caused every movement in traffic or AI visibility.

For the actual draft history, see Outputs and revisions.