Skip to main content
Actions is your project’s queue of fixes, ranked by measured opportunity. Every action sits in one list, whatever its state, and each action has its own page with its evidence, brief, what shipped and its result.

Action states

A Blocked pill marks an accepted action that is waiting on something. Measuring and the result belong to a live action: DevTune shows them on the action and in Results. You don’t set them.

Actions queue

Select Actions in the project sidebar. The header holds Accept next and generate brief and Create Action. Three figures sit above the list:
  • Awaiting a decision - suggestions nobody has accepted or archived
  • Went live, 30 days - actions that went live in the last 30 days, with the change against the 30 days before
  • Improved results - improved actions out of conclusive measurements, with the number still measuring. This matches the scoreboard in Results. If your plan does not include Results, the figure says so.
Use the All, Suggested, Accepted, Live and Archived tabs to filter the list. Each tab shows its count. Suggestions keep their ranked order; accepted, live and archived actions are listed newest first. Each row shows the action’s title and one line of context:
  • Suggested - what the action recommends
  • Accepted - the date it was accepted and its owner, or Unassigned
  • Live - the date it went live, its owner or Unassigned, and, once measured, its result
  • Archived - the date it was archived and any reason recorded
On the Accepted tab, use the Owner filter to show Any owner, Unassigned work, or one team member’s actions. Project Home shows the top of the same list in its Suggested actions and Tracked actions cards. View all opens the queue.

How suggestions are ranked

The queue combines prompt gaps, owned-page Audit findings, 404 demand, and citation defence. Each type is ranked by its own measured opportunity, then the queue takes one suggestion from each type in turn. Projects with only search probes still use estimated prompt volumes and probe confidence; traffic sensors are not required. A suggestion’s page shows its position as Ranked N of M. Citation defence highlights an owned page whose primary-citation rate fell materially between two published 30-day windows. The rate uses successful executions for the prompt-platform pairs probed in both windows, so changes in collection volume or prompt mix do not show up as a page loss. Prompt-platform pairs seen in only one window are reported separately as a composition change, and deleted or disabled prompts are left out. The action’s evidence charts the page’s citations on each prompt that cited it, per platform, earlier window then now, next to the competitor that leads that prompt today. DevTune withholds a loss as insufficient overlap unless the compared prompt-platform pairs account for at least 60% of the earlier window’s citations. The Evidence section states the matched prompt count and how much of the earlier citations they cover. When a matched comparison isn’t available for the project yet, the Evidence section says the comparison uses all successful executions in each window instead. Page-audit recommendations require a recent assessment of the current crawled content and specific failing checks. They preserve the page’s existing purpose and format without assigning a genre from its URL or title. The Evidence section includes the assessment date, failing and passing checks, page link, demand window, and prompt-coverage limits. A citability score is a content assessment, not a citation rate.

Accept next and generate brief

Select Accept next and generate brief to accept the highest-ranked suggestion that has no brief yet and start writing its brief. DevTune then opens the action’s page. If every suggestion already has a brief, the button is unavailable; open a suggestion and select Accept instead. If the action is accepted but its brief cannot start, generate the brief from the action’s page.

Action page

Select any row to open its action page. The header shows the title, the state pill, and the key dates: Ranked N of M and Opened for a suggestion, Accepted for accepted work, Live with Measuring · closes or Measured for a live action, and Archived for an archived one. Accepted work, whether still accepted, live or archived after accepting, also shows its Owner in the header. If you can manage actions, you can rename and assign an accepted or live action. Restore an archived action first:
  • To rename the action, select its title, type the new one and press Enter. Press Escape to keep the current title. A blank title is not saved.
  • To assign the action, select the owner and choose a team member, or Unassigned to clear it.
DevTune’s suggestions, including dismissed and snoozed ones, keep their title and have no owner. Accept one to rename or assign it. Renaming an action does not mark its brief out of date, and the new owner is not notified. The Tracked actions card on project Home and the Accepted and Live rows in the queue show the owner. The sections follow the action’s state, most relevant first: Sections collapse as the action advances but never disappear. The right-hand rail shows the Lifecycle (Suggested, Accepted, Live, Measuring, Result, and Archived when it applies) with a date or the next step for each, and the Activity list.

Existing-page checks

For new-page suggestions based on a citation gap, DevTune checks a shortlist of up to twelve relevant existing pages, comparing the question with each page’s title, address and, when the crawl found one, the start of its description. A completed check can find a suitable page or find no suitable page within that shortlist; finding none doesn’t prove no other page on the site could answer the question. A suggestion can leave the queue for a while if its check hasn’t completed; a later refresh checks it again. If DevTune can’t read a page, it keeps the current suggestions and briefs until it can check again. Accepted and live actions stay where they are.

Recommendation

The Evidence section explains which page to change, the tracked questions behind it, the supporting source and why a nearby alternative was not selected. The explanation reflects the evidence when the action was created; check the page as it is today before you change it. A refresh can call for refactoring how an answer is organized or enriching missing or outdated detail. Retargeting needs an observed mismatch between the question and page intent. Consolidation needs evidence that pages serve the same intent and a retained destination. Multiple pages ranking for a query, or missing citations, do not establish them. Review the pages and differentiate useful distinct intent before considering consolidation. Preserve unique facts and leave locked or retiring pages unchanged. Page changes still need human approval. DevTune hasn’t edited pages, redirected URLs or changed links.

Move an action

The header control changes with the action’s state:
  • Accept moves a suggestion to Accepted.
  • Mark live asks for the Published URL. Enter the http:// or https:// address of the page you published and select Mark live. Measurement compares the 14 days before with the 14 days after. See Results for how the result is read.
  • Block flags accepted work that is waiting on something. Unblock clears the flag.
  • Reopen moves a live action back to Accepted. Its measurement so far stays in Results, and marking it live again continues the same window.
  • Move back to suggestions undoes accepting a suggestion that nobody has started: it has no owner, it isn’t blocked or in progress, it has never gone live, and it has no brief or draft, hasn’t been edited, and nobody has added a request to it from another prompt. Actions your team created, such as ones from a prompt, can’t go back to suggestions. Every suggestion merged into it goes back with it. Once work has started, archive it instead.
  • Archive takes the action off the queue from any other state.
  • Restore returns an archived action to where it was: a suggestion goes back to Suggested, accepted or live work returns to its earlier state, and blocked work stays blocked, except some older work archived while blocked, which returns to the status it had before it was blocked. When an older suggestion can’t be restored, the page tells you so and it stays archived.

Merged suggestions

If DevTune merged a reworded suggestion into an action your team already decided, the action page lists it under Merged suggestions. Select Split to bring one back as its own suggestion after the next refresh; it is never merged again, and a split can’t be undone. Split needs permission to manage actions. Agents can split one with devtune_split_merged_suggestion or POST /projects/{projectId}/actions/split.

Evidence

The Evidence section explains why the action exists: the signal that triggered it, the prompt set and window, the AI platforms involved, the competitive landscape, and the charts behind the recommendation. Links open the underlying prompts and citations in Insights › Visibility. An action you create yourself with Create Action shows its description here instead of generated evidence, and has no brief.

Briefs

A brief turns an action into a content plan: what to make or update, why it matters, the evidence behind it, and which owned and external pages matter. Some refresh briefs propose links to add from related pages. Check each proposed link against the current pages, approve each edit separately, and leave locked pages alone. Then recrawl to confirm the links are live. Review the brief for outstanding link edits before you mark the action live. Briefs are written for actions DevTune suggested, including ones created from a prompt’s page. On such an action, suggested or accepted, select Generate brief. To request a specific format, open the menu beside it and choose a style; Best fit lets DevTune pick. If project content preferences are enabled, the menu offers only allowed formats. DevTune does not intentionally recommend a blocked format, and a request for a blocked brief style is rejected rather than generated. To learn what gets cited, the brief studies up to five external pages that AI answers cite for the action’s prompts, one per site. Competitor pages and third-party pages, such as publications, docs and reviews, are treated the same. Each prompt’s leading page is included first, then the rest are ranked by how often they are cited and how high they appear in answers. The action’s evidence lists these ranked pages under Winning pages, each marked competitor or third-party, and the actions API returns them as winningPages when you request detailLevel=context. When fewer than five pages are winning, the brief also studies pages saved with the action to fill the remaining slots; those pages are not in either list. Generating a brief costs between 1 and 2 credits, depending on how much research it needs, from your account’s single credit balance. The monthly plan allowance and any purchased packs both fund it, and spending takes the expiring allowance first. See Account & Billing Overview for the full credit policy. Once a brief exists:
  • Copy markdown copies it for use in your own editor.
  • Regenerate brief writes a fresh version and costs the same as generating one.
  • If what the brief is written for changes, DevTune shows Action changed since this brief was written. That covers the action’s target, prompts or channels, the target page’s content, which fixes the page needs or which AI platforms cite it, page protection, or your content preferences. New probe runs, re-ranking and refreshed citation counts do not trigger it. The existing brief stays visible; compare it with the action and regenerate only if the plan no longer fits.
  • If the research ran long, DevTune notes that the brief was cut short and offers Regenerate brief.
  • Generate draft writes the page or section edits from the brief. See Content drafts.
On a live or archived action, the brief is kept as it was. Reopen the action to regenerate it.

Locked pages

A locked page is excluded from suggestions and change actions. Lock and unlock pages in Settings › Pages. When you create an action from a prompt, locked pages cannot be targeted. When you accept an action that changes a high-stakes page, one with significant Google Search traffic, DevTune asks Queue the change action for this page? Choose Queue action to accept it, Lock this page instead to protect the page, or Cancel. Accept next and generate brief asks the same question.

Agents and actions

Agents can draft actions and briefs for you. When you approve an agent’s action draft with Add to Actions, or its brief with Send to Actions, the action appears under Accepted. A brief written by an agent names the agent and links to View agent run. If the action changes after the agent wrote its brief, DevTune tells you and asks you to review the run before using the plan. Agents never publish or change your site. You mark an action live when the change is published.

Spot check

If you can manage actions, a live action’s page shows a Spot check section with Run spot check when the action has prompts from its evidence. A spot check asks up to 12 of those prompts, the ones that triggered the action first, once on each AI platform the project tracks, so you can see what the platforms answer soon after the change is published. Each action gets one spot check, and a project can run 10 in any 24 hours; after that, Run spot check tells you when you can run the next one. Once a spot check has run, everyone who can see the action sees its Spot check section. It lists each prompt and platform with whether the answer mentioned your brand and whether it cited your site, meaning any page on your brand’s domains, with a link to the page it cited. A platform that returns an answer without its sources shows Unmeasured for Cited your site. Each row keeps the prompt as it was asked, even if you edit or delete the prompt later. Answers appear as they come in. A platform that fails or takes over 4 minutes shows No answer. A spot check isn’t run again, so that answer stays missing from it; the API’s errorCode says why it failed. A spot check with no answer on any platform shows No answers. A spot check is one set of answers, not a measurement. It is not counted in Results, visibility, citations or share of voice. The action’s result still comes from its measurement window. Run it from the API with Start an action spot check or from MCP with devtune_start_action_spot_check, and read it with devtune_get_action_spot_check.

Create an action

To add work that did not start as a suggestion:
  1. Go to Actions
  2. Select Create Action
  3. Enter a title
  4. Optionally add Published URLs (for outcome tracking), one at a time with Add URL. The first URL is the primary target.
  5. Choose a Channel and write a Description
  6. Select Create Action
The action starts in Accepted and DevTune opens its page. An action created this way carries its description instead of evidence and a brief. You can also create an action from a prompt’s page in Insights › Visibility. Select Create action, or Create action & generate brief to start the brief at the same time, then enter a title, What should change?, and an optional Existing page URL.

Results

When a live action’s measurement window opens, its page shows Change so far; once the window closes, it shows Result with the outcome. Open Results in the project sidebar for every measured action in the project. See Results.

Next Steps

  • Results - Read what moved after an action went live
  • Agents - Let agents draft actions and briefs for review
  • Alerts - Get notified of important events