website updates: software heartbeat, freshness heartbeat

web · 2026-10-13 · 6 min

two update clocks tick: software (security, breakage) and content (accuracy, trust). wordpress itself says update to latest AND back up first — the conjunction is the whole discipline. here's both routines and the breakage playbook.

software: the maintenance heartbeat

wordpress core, themes, plugins: updates fix security holes attackers scan for within hours. enable auto-updates for minor releases; do majors deliberately (backup → stage if critical → update → test). backups before every change (wordpress docs insist; rollback backups are the undo button). test after: homepage, contact/booking, checkout, mobile view. cadence: check weekly, update promptly, verify always. unmaintained sites don't age — they get recruited (botnets love stale plugins).

why updates break things (and the fix)

plugin conflicts (two plugins claiming the same hook — deactivate-half, isolate, replace the weaker). theme overrides lost (customizations in parent theme get overwritten — child themes exist for this). PHP/hosting drift (old code on new runtimes). auto-update roulette on business-critical sites (scheduled tasks misfire). the playbook when broken: restore backup (minutes, not heroics), then diagnose calmly; update ONE thing at a time afterward so the culprit names itself. prevention: few plugins, reputable vendors, staging for the critical.

content: the freshness heartbeat

prices, hours, services, team, policies: review quarterly (stale facts lie to customers). one answer-page monthly (compounding SEO). seasonal passes (holidays, closures, offers — announced BEFORE, removed AFTER). blog? only with rhythm you can keep — a dead 2021 blog hurts more than none. every page carries an implicit review date; honor it. cost context: what recurring costs does a website have.

FAQ

pay for a maintenance plan?

when downtime costs more than the plan (shops, bookings, lead machines) or updates scare you into never updating (the commonest vulnerability). plans buy backups, updates, monitoring, and someone to call — price against one bad week.

update everything blindly?

minors yes (security), majors watched (compatibility), all with backups and tests. never-update is the only universally wrong policy.