An Audit Trail Template for Autonomous SEO Work
An autonomous-SEO audit trail records, per change: what changed (URLs, fields, before/after), why (the evidence or rule that motivated it), who or what proposed it, who approved it and when, the rollback reference, and the outcome observation window. One row per change event, append-only, queryable by URL — so 'why does this page's title look like that' is a lookup, not an investigation.
Autonomous work has a memory problem: six months later, nobody remembers whether the odd canonical on /pricing-guide was a human decision, an agent's rule, or an accident. The audit trail is the institution that remembers — and it's also what makes automation reviewable, improvable, and defensible when someone senior asks pointed questions.
The template fields
- change_id, timestamp, and the URL(s) touched
- field and before → after values, verbatim
- motivation: the rule or evidence reference ('duplicate-title report 2026-09-12', 'rule T-3')
- proposer (agent + version, or human) and approver (named human, with the approval reference)
- rollback ref: the snapshot and rehearsed-path reference from the rollback plan
- outcome window: what was watched, for how long, and the verdict ('no regression at 14d' / 'rolled back on trigger')
A filled row
chg-0117 · 2026-09-16T10:04Z · /pricing-guide · title: 'Pricing' → 'Pricing Guide: Plans, Credits and Billing Explained' + canonical: '/' → self · motivation: dup-title report + canonical misconfig, rule M-1 · proposer: fix-agent v2.3 · approver: SK, PR #212 · rollback: snapshot s-0117, rehearsed path R-meta · outcome: watched 14 days, impressions stable, closed no-regression. Every claim in that row is checkable, which is the entire point.
A failure worth checking
The git-is-enough failure: assuming commit history is the audit trail. Git records what and when; it does not record why, who approved (merge ≠ informed approval), what the rollback plan was, or what happened after. Reconstructing those from PR archaeology takes hours exactly when you have minutes. The trail is a projection of git plus the four things git never knew — build it as data, at change time, or accept that your automation's history is write-only.
Put this to work on your own website.
Fenn finds what your customers ask, drafts the articles and site fixes, and measures what ChatGPT, Claude, Gemini, Perplexity and Grok say about you — with every change waiting for your approval.