Last year I audited a client site whose homepage still announced that the site was coming in 2008. On another project I found a pitch page for a co-founder who had left roughly fifteen years earlier, still pulling traffic because Google had never stopped sending people there. Both pages were live, working, and lying.
Episode 8 of The Web Managers Podcast is about giving that aging an owner. It is also, quietly, a Security Month episode. Nearly every emergency this blog has rehearsed since October, the hacked site, the expired domain, the stale plugin a bot found, is a maintenance task nobody scheduled. This post is the companion: the content audit and its four verdicts, governance sized for a two-person shop, the weekly half hour called update Tuesday, the maintenance calendar that gathers every cadence into one system, and the honest bill for all of it.
The audit: every page gets a verdict
A content audit is a complete, honest list of every page the site serves, with a verdict attached to each. The episode's method is sized for the reader: a site under about a hundred pages is listed from the content management system (CMS) into a spreadsheet; larger sites get a crawler, and Screaming Frog's free tier handles up to 500 addresses. Before judging anything, add two columns of evidence: when the page was last updated, and whether anyone visits it, which Google Search Console reports at no cost. Reviewing pages without traffic data is guessing.
Then every page gets one of four verdicts. Keep means accurate, useful, and visited. Update means it earns its place but has drifted, and most pages land here. Merge means two or three thin pages are circling the same topic. Delete means the page serves no one. The delete verdict carries one safety rule: never remove a page with traffic or inbound links without a 301 redirect to its closest living relative. Done that way, deletion is pruning. Done carelessly, it is vandalism against your own visibility.
Governance without bureaucracy
Content governance answers three questions in advance: who may create, who may approve, and who may publish. The episode's version fits a two-person organization. The four-eyes rule means nothing reaches the public with fewer than two sets of eyes on it, and the approval can be a reply to an email. Enforcement belongs to the CMS, where roles exist for exactly this: the volunteer who writes gets contributor, the second reader gets editor, and almost nobody gets administrator. Publishing should never require the account that can delete the site, which is the same least-privilege rule Chapter 8 enforces for security reasons.
The episode also names the burst-and-silence cycle, where one motivated month produces six posts and the next two quarters produce none. Visitors and search engines both read the silence. Size the rhythm to real capacity and keep it.
Update Tuesday
For self-managed sites, update policy is security policy wearing maintenance clothes. A meaningful share of platform and plugin updates close holes that are publicly documented the day they ship, so an unapplied update is an advertised vulnerability. The decision rule is by criticality: auto-update everything on a brochure site, backed by regular backups; on a commerce or membership site, update manually on a fixed schedule with a snapshot first, and leave security-only updates automatic.
The schedule has a name because the name is the point. The same half hour every week: confirm the latest backup ran, take a snapshot, apply updates, click through the five most important pages, submit the contact form, log the date. Most weeks nothing happens. That uneventfulness is the goal; the gap between an update's release and its application stays under a week, permanently, without anyone being heroic.
The calendar and the honest bill
The episode's centerpiece is the maintenance calendar: every recurring task from the whole season in four tiers. Weekly, fifteen to thirty minutes. Monthly, about an hour, including the broken-link scan. Quarterly, two to three hours, including the restore test, the accessibility pass, and the access review from Monday's post. Annually, a half day for the full content audit, the domain health audit, and the plugin audit. Summed and amortized, the whole system costs roughly three to five hours a month, and that is the entire price of professional-grade web management at this scale. There is no secret expenditure the organizations with reliable websites are making.
When the week allows only twenty minutes, the security lines hold and the rest slides with a new date. A skipped task with a new date is management; a skipped task with no date is the first brick out of the wall.
Myth busted: "More pages means better search results"
The old search engine optimization (SEO) advice was to publish for volume. A hundred stale pages are a hundred small arguments against trusting you, and search engines and AI answer systems have reached the same conclusion. Publish less, tend more.
Also in this episode
The Question Line takes a client who wants fifty AI-written blog posts to fill out the site, and the episode makes the smaller, better counter-offer. The Tool Minute covers Screaming Frog, the crawler that finds the pages your platform forgot.
Quick win: update your oldest high-traffic page
Open Google Search Console and sort your pages by traffic.
Find the three oldest pages among the most visited.
Pick one and update it this week: current facts, names, links, and year.
Done looks like one page updated where freshness pays most, and the date logged.
Get the worksheet. The M7.1 Annual Web Maintenance Calendar and Content Audit Sheet arrives pre-loaded with every recurring task from the book, weekly through annual, with an owner column and a done column, plus the page-by-page audit sheet with the four verdicts. It is free with a Web Managers account at https://webmanagers.com/register, and it arrives with the weekly Web Managers letter.

