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

# Actions

> Prioritized recommendations (content to create, off-page targets to pursue, and technical fixes to apply), each backed by evidence from your tracked answers.

Actions are Mavel's answer to "what should I do next?" Every action is generated from real data: the prompts you track, the answers the AI surfaces return, and the sources cited in those answers. They tell you which pages to improve, which third-party domains to pursue, and which technical issues are hurting how AI engines read your site.

## Action types

Actions are organized into four groups:

| Group             | What it covers                                                                                                                    |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| **Owned content** | Pages on your own domain that AI engines crawl but rarely cite: improvements to relevance, structure, or coverage.                |
| **Editorial**     | Editorial publications and news sites that engines cite in your category. If they mention competitors but not you, that is a gap. |
| **UGC**           | User-generated content communities (forums, Reddit threads, review sites) where real discussions drive AI citations.              |
| **Reference**     | Authoritative reference sources (directories, industry databases, Wikipedia-style pages) cited as supporting evidence.            |

Each action carries a priority tier (**High**, **Medium**, or **Low**) based on how often the relevant sources appear in your tracked answers and your current visibility in them.

The **Technical** tab surfaces a separate set of findings: issues with your `robots.txt`, sitemap, and structured data (JSON-LD) that affect how AI engines discover and interpret your content.

## Evidence on every action

Opening an action shows the specific evidence behind it: which prompts triggered it, what the AI answers said, and which URLs were cited or missed. This is the data you need to brief a writer, pursue a publisher, or prioritize a fix.

## Working the board

<Steps>
  <Step title="Review open actions">
    The **All** tab shows your full open backlog. Use the tab filters (Owned content, Off-page, Technical) to focus on one category at a time. Within Off-page, the sidebar filters further by Overview (everything), Editorial, UGC, or Reference.
  </Step>

  <Step title="Add actions to your task board">
    Open any action and add it to your tasks. It moves to the kanban board at `/actions/tasks`, where you can manage work across four columns: **To do**, **In progress**, **Done**, and **Validated**.
  </Step>

  <Step title="Drag cards through the board">
    Drag cards between columns as work progresses. Cards in the **Validated** column are read-only: they arrive there automatically after a card is moved to Done.
  </Step>

  <Step title="Dismiss what does not apply">
    Actions you want to skip can be dismissed from the detail drawer. Dismissed actions can be restored if circumstances change.
  </Step>
</Steps>

## Validation

When you move a **Technical** card to **Done**, Mavel queues a real re-check of the original finding: if the issue is resolved the card advances to **Validated**, and if it is still present the card moves back to **To do** so it stays on your radar. Owned content, Editorial, UGC, and Reference actions advance to **Validated** when moved to Done; no external re-verification runs for those categories yet.

For Technical findings, you can also trigger a manual **Re-check** from the Technical tab without moving a card, useful when you have just deployed a fix and want to confirm it landed.

<Note>
  On the board, the Validated column is system-managed: you cannot drag cards into it directly; move a card to Done instead. The `transition_action` [MCP tool](/mcp/tools) follows the full state machine, which does permit moving an in-progress action straight to Validated.
</Note>

## Owned content inventory

The **Owned content** tab includes a grouped view of all URLs on your tracked domain, classified by page type. For each URL you can see how many open actions are attached to it, and link through to the full URL detail in [Sources](/results/sources).

## API and MCP access

Actions are available outside the dashboard on Growth and Enterprise plans.

* **MCP tools**: `get_actions` returns a group-level overview or a drill-down list for a specific group. `get_action_rollups` returns daily counts and opportunity scores over a date range. `transition_action` moves an action through the same workflow as the board. See [MCP tools](/mcp/tools) for full parameter reference.
* **REST API**: the `/api/v1/` endpoints expose action data for custom integrations. See [API reference](/api-reference/introduction).

API and MCP access require a Growth or Enterprise plan. You can generate an API key from [Account / API keys](/account/api-keys).