Everything in this series is a loop: alerts watch daily, the report ships monthly, the deep checks run quarterly. The annual audit is the loop that checks the loops, and it fits in half a day because the smaller ones ran all year.
This capstone assembles the whole system, ending in the one-page scorecard your next year gets planned from.
The loops, nested
The half-day agenda
| Block | Audit | The guides |
|---|---|---|
| 0:00-0:45 | Foundations: GSC views intact, exports archived, monitors covering the right pages, alert thresholds still trusted | GSC setup, monitoring, the boring alerts, thresholds |
| 0:45-1:30 | Data health: device gaps, country views, metric sanity in reporting | device gaps, countries, average position |
| 1:30-2:30 | Content health: the year-scale decay sweep, full cannibalization pass, CTR audit of money pages | decay, cannibalization, CTR, the reports |
| 2:30-3:15 | Threats: the features map of money SERPs, the competitor year in review, the update incident log | features, competitors, updates |
| 3:15-4:00 | The scorecard and the three bets | Below |
Each block asks the same two questions: is this area healthy, and is the system that watches it still working? A decayed page is a finding; a decay check that stopped running is a bigger one.
The scorecard
Each area gets a color and one sentence of evidence. Green: healthy and watched. Yellow: working, with named risks. Red: broken or unwatched, with the fix on the bets list.
| Area | Green means |
|---|---|
| Foundations | Views saved, exports current, monitors on the right pages, alerts acted on more than ignored |
| Data health | No sustained device or market gaps unexplained; reporting metrics carry their caveats |
| Content health | Decay caught on the slope, zero unresolved collisions, money-page CTR at band |
| Threats | Feature map current, rivals tracked with context, update log maintained |
The change log and the drop log get audited here too: both are the memory the whole system leans on, and both quietly die in busy years unless something checks.
The three bets
The audit's last half hour writes next year: three bets, each specific, owned and dated. "Close the mobile template gap by March", "refresh the 2024 cluster before its season", "win the snippet set on the comparison keywords".
Three is the number because bets compete with the loops for the same hours, and the loops win ties: a year that only ran the loops well beats a year of abandoned moonshots.
Scheduling it
Book the audit four to six weeks before annual planning, so the scorecard and bets land inside real budgets, and put next year's on the calendar before closing this year's. Recurring calendar entries outlive motivation, which is the entire theory of this system.
Then the loops resume: the report hour keeps shipping, the digests keep arriving pre-triaged, the quarterly checks keep the gaps visible, and rankings stop being a mood and stay what this series kept insisting they are: a system you read, watch and steer.
The one-line takeaway: run the loops all year, then spend half a day auditing four areas: foundations, data, content, threats, into a one-page scorecard and three owned bets. The audit is cheap because the loops ran, and the loops run because something audits them.