> ## Documentation Index
> Fetch the complete documentation index at: https://docs.devtune.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Actions and Results

> How DevTune turns Visibility, Audit, and AI Traffic signals into a ranked queue of fixes, and measures what moved after each one went live.

DevTune does not stop at showing metrics. **Actions** turns Visibility, Audit, and AI Traffic signals into a ranked queue of evidence-backed fixes, and **Results** shows what moved after each fix went live.

## Actions

Every action sits in one queue and moves through four states:

* **Suggested** - DevTune proposed it; nobody has decided yet
* **Accepted** - your team has taken it on
* **Live** - the change is published, and its measurement is running or complete
* **Archived** - off the queue

Suggestions are ranked by measured opportunity. Each one can draw on:

* Prompt and citation performance from Visibility
* Competitor movement
* Audit findings and page readiness gaps
* 404 demand and other AI Traffic context

Open any action to see its evidence and move it on with **Accept**, **Mark live**, **Archive** or **Restore**. On an action DevTune suggested, you can also generate a brief; an action made with **Create Action** has no brief. Locked pages are excluded from suggestions and change actions. See [Actions queue](/insights-actions/actions-hub).

## Briefs

A brief turns an action into a content plan. It answers:

* What should we make or update?
* Why does it matter?
* What evidence supports it?
* Which owned and external pages matter?

Briefs are generated when you request them and spend from your account's single credit balance. When project content preferences are enabled, suggestions and briefs respect the project's allowed and blocked content formats, so you can rule out formats that do not fit your strategy, such as comparison pages, while DevTune still chooses the best allowed format for each action. See [Briefs](/insights-actions/actions-hub#briefs).

## Results

When you mark an action live with its published URL, DevTune compares the page's citations and answer fetches in the 14 days before and after, with AI referrals alongside where analytics is connected. The result is **Improved**, **Mixed**, **No clear change**, **Declined**, **Still measuring**, or **Unmeasured**. A result shows what moved, not what caused it.

Each live action shows its result on its own page. **Results** in the project sidebar lists every measured action in the project, along with content changes that no action claims. See [Results](/insights-actions/outcomes).

## How recommendations become work

1. Review **Suggested** actions in **Actions**
2. Open an action and generate a brief where more context is needed
3. Select **Accept** on the work you want to do, or **Accept next and generate brief** to take the top suggestion
4. Publish the change
5. Select **Mark live** and enter the published URL
6. Read the result on the action or in **Results**

## Where to find them

In the project sidebar:

* **Actions** opens the queue
* **Results** opens every measured action
* **Home** shows the top suggestions and tracked actions; alerts arrive under **Notifications** in the top bar

Notification settings control which events interrupt you immediately and which ones wait for scheduled digests. See [Alerts](/insights-actions/alerts).

## Next Steps

* **[Actions queue](/insights-actions/actions-hub)** - Work the queue, from suggestion to live
* **[Results](/insights-actions/outcomes)** - Read what moved after an action went live
* **[Alerts](/insights-actions/alerts)** - Decide what should interrupt you
* **[Visibility](/search-tracking/search-overview-dashboard)** - Investigate the evidence behind a recommendation


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.