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

# Content update ledger: measure the impact of every change

> VeluraHQ's content update ledger tracks every publish and refresh with matched before-and-after metrics so you can prove what moved the needle.

The content update ledger is VeluraHQ's attribution layer. Every time you publish, refresh, or update a page through VeluraHQ — whether manually, via workflow, or through a Sheet run — the ledger creates a timestamped event and begins tracking before-and-after performance against matched windows. The result is a complete record of what your team shipped and exactly what it produced. You get evidence, not anecdotes, and a defensible basis for every future content investment decision.

## What gets tracked

The ledger captures update events from every execution path in VeluraHQ:

* **Workflow runs** that produce CMS output — any workflow with a publishing step creates a ledger entry for each URL it writes to.
* **Manual page refreshes** marked in the system — when you flag a page as updated without a workflow, the ledger records it and starts the performance window.
* **Sheet batch executions** with publishing enabled — each row that triggers a CMS write generates its own timestamped entry.
* **Direct CMS pushes** through VeluraHQ integrations — updates pushed to WordPress, Webflow, or other connected CMS platforms are captured automatically.

Each event is linked to the source workflow, Sheet, or action that triggered it, so you always know not just that something changed, but what process made it happen.

## Reading ledger entries

Each entry in the ledger gives you a complete before-and-after picture of a single update event:

* **Page URL** and the exact **date of the update**
* **Source** — the workflow name, Sheet name, or "Manual" if it was a direct update
* **Before-and-after metrics** in matched windows:
  * Organic clicks
  * Impressions
  * AI citations
  * Engagement time

Metrics are shown as raw numbers alongside the percentage change, so you can assess both magnitude and direction at a glance.

**Example entry:**

> **Content refresh playbook** · `/blog/content-refresh-playbook` · Refreshed 28 days ago
>
> | Metric          | Before | After | Change    |
> | --------------- | ------ | ----- | --------- |
> | Clicks          | 4,012  | 5,281 | **+31%**  |
> | Impressions     | 91K    | 118K  | **+29%**  |
> | AI citations    | 8      | 23    | **+188%** |
> | Engagement time | 1:48   | 2:37  | **+45%**  |

## Matched windows

Raw before-and-after comparisons can be misleading if the periods being compared aren't equivalent in length. VeluraHQ avoids this by comparing equal-length periods on either side of the update event to minimize seasonal distortion.

For a page updated 28 days ago, VeluraHQ compares the 28 days immediately before the update with the 28 days immediately after. As more time accumulates post-update, the windows extend in lockstep — keeping the comparison fair regardless of when in the year the update happened.

<Note>
  The ledger attributes impact to the last update event on a page. For pages that receive multiple updates, each event gets its own matched window so you can see each change in isolation. If you refresh a page three times over six months, you'll have three separate entries — each with its own before-and-after metrics — rather than a single blended view that obscures which update actually moved the needle.
</Note>

## Filtering the ledger

Use the ledger's filter controls to focus on exactly the entries you need:

* **Date range** — scope the ledger to a specific quarter, campaign period, or sprint
* **Workflow or Sheet** — isolate the performance of a specific workflow or batch operation
* **Team member** — filter by the person who triggered the update
* **Page path** — narrow to a section of the site (e.g., `/blog/` or `/guides/`)
* **Metric change threshold** — show only entries where clicks increased by more than 20%, or where AI citations improved, filtering out low-signal events

When you've dialed in the view you need, click **Export CSV** to pull the filtered ledger data for reporting, stakeholder decks, or offline analysis.

## Using ledger data

The ledger is most valuable when you treat it as a learning system, not just an audit log. Here are three ways to put it to work:

**Find your repeatable playbooks**

Sort the ledger by percentage click improvement and look for patterns in the top-performing entries: Which content types improved most? Which workflows drove the biggest lifts? Which topic areas respond best to refreshes? Use those patterns to templatize your highest-performing approaches and run them more systematically.

**Diagnose refreshes that didn't move the needle**

Filter for entries where metrics were flat or declined after an update. These pages need a deeper audit — the change you made wasn't sufficient. Routing them back through a more thorough workflow (deeper restructuring, new evidence, updated claims) is more productive than leaving them in a stalled state.

**Report content impact to stakeholders**

Pull a filtered ledger export for a specific period or workflow and use the before-and-after data to build stakeholder reports. Concrete metrics from matched windows — "our Q3 refresh program drove a 31% average click increase across 24 pages" — are far more persuasive than activity-based reporting and give leadership a clear basis for continued content investment.

***

**Continue reading**

* [Page Intelligence](/docs/platform/pages) — find the pages worth updating using unified search, engagement, and AI citation data.
* [Actions](/docs/platform/actions) — see how VeluraHQ surfaces, ranks, and routes content opportunities before you have to ask.