A comprehensive website maintenance plan includes: CMS and plugin updates (keeping all software current and patched against security vulnerabilities); security monitoring (scanning for malware, checking for known vulnerability exposure); uptime monitoring (24/7 availability checking with prompt alert on downtime); performance monitoring (page speed and Core Web Vitals tracking); content updates (text, images, and page changes on request); regular backups (ensuring recovery capability in case of incident); and monthly reporting (maintenance activity summary and website health metrics). Specific inclusions depend on the plan tier selected.

Security-critical updates should be applied promptly — within days of release for known vulnerabilities being actively exploited. Routine CMS and plugin updates are typically applied monthly, in a maintenance window, after testing in a staging environment. Major version upgrades (e.g., WordPress 6.x to 7.x) are planned projects requiring more careful testing and are typically undertaken when the current version approaches end-of-support. The risk of not keeping up with updates is significant: the majority of website hacks exploit known vulnerabilities in outdated software.

Standard content update requests (text changes, image swaps, new blog posts) are typically completed within 1–2 business days. More complex changes (new page creation, structural changes, new feature additions) take longer depending on scope. Emergency content changes (incorrect pricing, critical misinformation) are prioritised and addressed as quickly as possible, typically within hours during business hours. We establish a clear content update request process — typically email or a project management tool — so requests are tracked and completed reliably.

If a website under our maintenance experiences a security incident, we respond immediately — assessing the scope, taking the site offline if necessary to prevent further damage, cleaning the infection, identifying and patching the vulnerability exploited, restoring from clean backup if required, and implementing additional security measures to prevent recurrence. We provide a full incident report explaining what happened, how it was resolved, and what changes were made to prevent similar incidents. Our maintenance programme is specifically designed to reduce the likelihood of successful attacks.

Yes. We configure automated daily backups of website files and database — stored securely off-server so a server failure does not also lose backups. We test backup restoration periodically to confirm backups are actually usable in a recovery scenario. Backup retention periods (typically 30 days) are agreed as part of the maintenance plan. Backups are the essential safety net for both security incidents and mistakes — ensuring recovery is always possible.

Yes. We take on maintenance for websites built by other developers. We begin with a thorough website audit — assessing the current state of the platform, plugins, code quality, security, and performance — to establish a clear picture of what we are taking on. We then develop a remediation plan for any issues identified before starting the ongoing maintenance programme. For very poorly maintained websites, we may recommend an initial remediation project before commencing ongoing maintenance to bring the site to a maintainable standard.

Website maintenance keeps an existing website running well — updating software, fixing issues, making content changes, and optimising performance within the current design and structure. Website redesign is a project to create a new website (or significantly overhaul the existing one) — new visual design, new information architecture, potentially a new platform or significant new features. Maintenance is an ongoing operational service; redesign is a one-time (or periodic) project. We provide both: maintenance plans for the ongoing care of existing websites and redesign projects when a more significant refresh is needed.