Skip to main content
Results shows what happened after actions went live and after detected content changes. It uses page-level before-and-after measurements and reports what moved, not proof that an action caused the change.

​
Where results appear

  • Results in the project sidebar lists every measured action in the project, and content changes that no action claims.
  • Each live action’s page shows its own result, so you can read it where you did the work.

​
Open Results

  1. Open a project
  2. Select Results in the project sidebar
  3. Choose Measured actions or Unclaimed changes
Use the 7 days, 30 days, or 90 days control to choose which measured actions or changes appear. Row deltas always compare the 14 days from the date the action went live with the 14 days before it. Claimed crawl changes retain their recorded change date; the reporting-window control does not change that comparison.

​
Measured actions

The Measured actions tab is the default view. Its scoreboard summarizes:
  • Conclusive measurements: actions whose complete comparison has usable evidence
  • Improved: conclusive actions where a metric rose and none fell
  • Improvement rate: improved actions divided by conclusive measurements, unavailable when there are none
  • Still measuring: actions whose comparison window is still open
  • Unmeasured: actions without a usable comparison
DevTune compares the 14 days after the change with the 14 days before. A metric counts as moving when its count changes further than chance would explain:
  • Citations count the probe answers that cite the page. The comparison allows for how many probe answers each window had in total.
  • Answer fetches count the requests AI systems made for the page.
  • A move counts when a shift that large, up or down, would happen by chance less than 1 in 10 times, the higher window holds at least 3, spread over at least 3 days, and the rate moves by at least 20%. A one-day burst, or a small wobble on a busy page, doesn’t count.
The same rule applies in both directions. Hover over a result to see what moved for that action, and how often chance would move it that far. Citation comparisons require probe evidence in both windows. The citation-lift qualifier sums citation improvements only. For the same page, overlapping before/after windows contribute only the earliest supported comparison in each overlapping group. Each action keeps its individual result. A qualifying rise does not prove that the action caused it, and a qualifying fall does not prove the action harmed the page. Each row shows the action, result, citations per day, presence change, answer fetches when available, and measurement date. Select a row to inspect its evidence. Use the result filter and page-size control to explore the ledger. Previous and Next preserve the selected range and filter across reloads.

​
Result and confidence

  • Improved: at least one metric rose and none fell
  • Mixed: one metric rose and another fell
  • No clear change: the closed comparison has usable evidence, but no metric moved in either direction
  • Declined: at least one metric fell and none rose
  • Still measuring: the comparison is pending
  • Unmeasured: no usable comparison exists; missing evidence never counts as a decline
A citation improvement can be reported before the answer-fetch window closes. If answer fetches then fall, the result becomes Mixed. Confidence describes sensor coverage, not causality:
  • observed — the sensor covered the full measurement window
  • directional — the sensor covered part of the window
  • still measuring — the measurement window or its data is not ready
  • unavailable — no comparable sensor evidence exists
Cells use states such as measuring · day N of 14 and window open instead of treating incomplete measurement as zero.

​
Measured action detail

Select a ledger row to review:
  • The lifecycle from Action completed through Result available
  • Citation and presence changes
  • Answer-fetch changes and their sensor basis
  • AI referrals as unavailable when no comparable GA4 or PostHog measurement exists
  • A daily page-signals chart with the detected-change marker
  • The 14-day comparison for actions marked live; recorded content changes also offer 7-, 30-, and 90-day windows
  • Content hashes, crawl evidence, and a link to page history
Open windows remain labeled window open until enough time has passed. Measured actions receive citation and presence updates after new probe results arrive, through day 90 after the measurement starts. Results remain available afterward and can be corrected when late evidence arrives.

​
Result on an action

When you select Mark live on an action, its page gains a result section above What shipped:
  • While the window is open, the section is titled Change so far and compares the 14 days before with the days so far, showing when the window closes.
  • Once the window closes, the section is titled Result, shows the result, and compares the 14 days before with the 14 days after.
The section carries the same citation, answer-fetch, and AI referral evidence as the measured action detail in Results. If your plan does not include Results, the section says so. The action’s Lifecycle shows when it went live, when measuring closes, and when the result was read. Reopen moves a live action back to Accepted without discarding its measurement. Marking it live again continues the same window. See Move an action.

​
Published pages and tracking capacity

Marking an action live, or saving a published URL, starts measurement from the date the action went live, shown as Went live. New pages and updates to existing pages do not need to wait for a crawl. Citation, answer-fetch, and referral comparisons still depend on available source coverage. Missing evidence is shown as unavailable, not zero. While your plan’s page allowance is full, a banner at the top of each project screen shows how many pages AI answers cited in the last 30 days that DevTune does not track. Select See untracked pages to list them under Insights › Audit › Crawl coverage. Select the arrow to collapse the banner to one line. If your plan’s page allowance is full, a saved published URL that DevTune does not yet track shows Tracking limit reached. Select Upgrade to track more pages to raise the allowance; your plan defines it, and upgrading increases it automatically. Saved published pages are prioritized when space becomes available; you do not need to submit the URL again. Page tracking supports audits and content-change detection; its allowance does not block outcome measurement. Upgrading does not recreate missing historical evidence. An action shows only the status of its own published URLs. If the page has not been collected, it links to crawl settings without treating a project-level crawl failure as a failure of that URL. Agents can read the same status with devtune_get_page_tracking, and the REST equivalent is GET /api/v2/projects/{projectId}/outcomes/page-tracking. Include actionId to read an action’s published URLs, or omit it for project-wide capacity. Both return each saved URL’s status, the capacity in use (activePages, reservedPages, pageLimit) and allowanceStatus with the untracked AI-cited pages. Page tracking is read-only.

​
Unclaimed changes

Crawls detect content edits whether or not an action was recorded. Unclaimed changes lists those edits, newest first, beside any measured action that claims them. Filter by URL path and use the page-size, Previous and Next controls to review the full list. When the page has a measured action completed within 14 days of the detected change, select View existing measured action to open it. The change stays unclaimed until it is associated with an action. Claim prevents a duplicate measurement for that change. Later independent edits can still be claimed. Select Claim as measured action to create a completed action dated to the detected change. Select the claimed action to open its measurement detail. Unclaim archives an unchanged manually claimed action and removes its measurement from measured totals. The action, evidence and claim history remain. Claiming it again restores the same action and measurement, including its original title and description. DevTune rejects Unclaim when the action has been edited or gained other linked work. Automatic associations cannot be unclaimed here. Older claims without reversible history also cannot be safely reversed. No action is deleted. Unclaimed-change comparisons update daily through day 14 after the detected change. Their results remain available afterward; late evidence can still correct them. Claiming an older change succeeds immediately while its longer comparisons fill in. Those comparisons show Updating until ready; missing historical evidence remains a coverage gap. The list shows 14-day before/after citation and presence differences. These differences are correlation, not proof of what caused the change. Summary totals cover the selected date range. The path filter affects only the list and its count. The same list is available through GET /api/v2/projects/{projectId}/outcomes/changes and devtune_get_content_changes. Claim and Unclaim use the corresponding /claim and /unclaim POST routes and devtune_claim_content_change / devtune_unclaim_content_change MCP tools. The list returns existingMeasurementId for an unclaimed change on an already measured page; Claim returns 409 when the existing action was completed within 14 days of the detected change. Mutations require actions.write; listing requires outcomes.read. Unclaim requires the current claimToken returned by the list, so an old request cannot undo a later claim. Agents must obtain human approval before changing a claim.

​
Next steps