Create a maintenance routine that fits the site
A static informational site and a WordPress ecommerce store do not need the same schedule. Review software dependencies according to their risk and update frequency. Confirm that backups exist and that someone knows how they would be restored.
Test important forms and transactions periodically. A page can remain online while an email service, payment integration or API has stopped working.
Keep business information and accounts current
Review phone numbers, addresses, staff details, prices, policies and service information when the business changes. Old information can damage trust even if the website is technically healthy.
Track domain, hosting and paid-service renewals. The business should know who owns each account and which email receives notices. A specialist example is ongoing webmaster support in Canada.
Know when maintenance becomes redevelopment
Repeatedly patching an obsolete theme, unsupported framework or confusing content structure can eventually cost more than addressing the underlying problem. Maintenance should include judgment about when a larger change is warranted.
When rebuilding, preserve valuable URLs and content rather than assuming everything old should disappear.
Keep a small change history for significant technical work. Knowing when a plugin, redirect, DNS setting or integration changed can shorten troubleshooting later. Maintenance is also a good time to remove unused accounts, obsolete scripts and old files rather than allowing the website to accumulate dependencies indefinitely. For important sites, distinguish urgent incident support from ordinary content updates so expectations are clear.