Actions (Beta)

What an action represents

Actions are recommended pieces of work derived from project evidence. They stay connected to the prompt, executions, source gap, or site policy that produced them so a team can verify the reason before starting.

Actions can cover owned work such as pages and technical fixes, or earned work such as editorial outreach and external source presence. Priority helps order review; it is not an automatic business case.

Open actions is the count of all project actions whose status is open. High priority is the open subset marked high. Prompts with actions counts distinct linked prompt groups plus distinct unlinked prompt text groups, so it is not the number of actions. By priority sorts open actions by generated opportunity score descending, then priority band high to low, then newest. Opportunity score ranks candidates relative to one another; it is not a probability, percentage, revenue forecast, or guaranteed impact.

Review before assigning work

1. Open the originating prompt Confirm the question represents a valuable audience and intent.
2. Read the evidence Check the cited answers, competitors, sources, and affected pages behind the recommendation.
3. Remove duplicates Combine recommendations that point to the same page, claim, source relationship, or technical root cause.
4. Set ownership and outcome Translate the recommendation into a deliverable with an owner, deadline, and measurable expected change.
5. Mark completion deliberately Complete an action only when the real-world work is finished, not when it has merely been read.

Beta expectations

The Actions module is marked Beta. Generated recommendations should be reviewed by a person with brand, market, technical, and editorial context. Evidence may support several valid responses, and the product cannot know every cost or dependency.

Turn a recommendation into a useful brief

A useful action is specific enough for an owner to complete and for a reviewer to verify later. Replace broad instructions such as “improve visibility” with a defined audience, evidence, deliverable, intended outcome, and measurement plan.

• State the prompt, topic, market, and provider pattern that triggered the action.
• Link the representative answers, source domains or URLs, and affected owned pages.
• Describe the observed gap without assuming that one publication or page will guarantee an AI result.
• {"Choose one deliverable" => "update a page, publish a missing format, fix a technical blocker, gather original proof, or develop an external relationship."}
• Assign an owner and review date that fit the real publishing or outreach process.
• Define what later evidence would support success, such as improved retrieval, stronger mention context, or broader provider coverage.