Every company website accumulates a layer of unowned work. Pages drift out of date. Links rot. The SEO checklist gets done once, during a redesign, and never again. Metadata inconsistencies pile up in the corners nobody looks at. None of it is hard. All of it is nobody's job, which at a small company means it's everybody's guilt.
The fix is ownership, not heroic effort. By the tests for which functions a small team staffs with teammates first, site operations is close to the ideal first responsibility to hand an AI teammate: the work is recurring, checkable, and lands naturally in a table.
The site becomes a workspace table
A site-ops teammate keeps the whole surface area in one shared table: pages, their status, what was last checked, what needs attention, who owns the fix. Rows the teammate updates carry its name; rows a human edits carry theirs. When you want to know the state of the site, you read the table instead of asking around, because the record is the point.
The standing routine runs through the checks that decay: stale content flagged with what changed since it was written, broken links caught before a prospect finds them, metadata drift surfaced instead of silently accumulating. That foundational hygiene, usually done once during a redesign, stops being a project and becomes a cadence.
Site rot isn't a technical problem. It's an ownership problem wearing a technical costume, which is exactly the kind of problem a standing role dissolves.
What stays human
Anything that touches what the site says, positioning, pricing, the words on the homepage, gets flagged, not fixed. The teammate's scope is the difference between "this page contradicts the current product" (surfaced to you, with the specifics) and deciding what the page should claim instead (yours). Same for anything irreversible: the teammate proposes, the record shows the proposal, a human ships it.
Deeper SEO strategy, which keywords to chase, what content to build, stays a judgment call too, worked the way our Dock for SEO coverage lays out. What the teammate removes is the layer underneath: the checking, the cataloguing, the noticing. The site stops rotting the day the noticing becomes someone's actual job, and it turns out that job no longer requires a hire in the old sense.