The cadences are not ours. They come from the standards and the people who set the rules, and the job is to keep to them.
Patching. The UK’s Cyber Essentials scheme requires any critical or high security fix to be applied within 14 days, and says that is the maximum, not the target. The UK National Cyber Security Centre’s own guidance for internet-facing software, which a public website is, says five days. Where a public exploit exists the right window is shorter still. Unsupported software must be removed, not left.
Backups. The UK National Cyber Security Centre’s principles say a backup must survive an attacker who has the main system, and must be tested as routine. For a site built from a repository, the repository is the backup of content and code, and the test is to rebuild and redeploy from it alone and time it. We ran that test on each of the sites in our case studies on 28 October 2026. The first time we ran it for one shop it failed for want of 32 settings, which is why the test exists.
Certificates. The maximum lifetime of a security certificate is 200 days now, 100 from March 2027 and 47 from March 2029. Renewal must be automatic and watched, because the failure is a full-page browser warning and no visitors.
Code, links, speed and search. Broken links, redirect chains and failing forms are crawled for monthly. Google’s thresholds for loading, responsiveness and stability are measured on real visitors at the 75th percentile and reported in Search Console, which is read monthly. Google’s own advice is to check previously published content and update or remove it, so a dated review of each page is part of the job.
The log. Every task above produces a line in a log the client can read: what was done, when, and what it found. A care arrangement without a log is a direct debit.