Website maintenance services in Birmingham

Start with the site itself. A static or custom-coded site has no plugin layer to patch, so it generally needs fewer security updates than a plugin-based content management system. It still needs dependency updates, renewals and monitoring. A site with plugins calls for more attention to those updates, which affects how much maintenance work you need to arrange.

Hosting is a separate decision. If you want one party responsible for hosting speed and uptime, hosting managed by your maintainer is a suitable choice. If your company has an IT team and established server policies, keeping hosting under its management gives that team control of the environment.

A monthly care plan suits you when you want updates, monitoring and an agreed amount of change work handled. Pay-as-you-go support fits a stable site with rare changes, though the response can be slower when something breaks. An in-house developer can handle maintenance; an outside provider fits when nobody on your team has the website as their main job. We help you choose by discussing your staff capacity and how often the site needs changes.

For cookies used solely for statistics or to adapt the site’s appearance to user preferences, UK rules allow use without consent when visitors receive clear information and an easy way to object. Where your site uses those cookies, we set up that information and an objection route as part of the work.

Website services also need reasonable adjustments for disabled people. We make the relevant adjustments to your pages as part of the maintenance work, so accessibility is considered when those pages are changed.

Gather what you can about the site and the accounts that keep it running.

• Access to website admin, hosting, the domain registrar, DNS, email and premium plugin or theme accounts.
• A list of connections, including forms, CRM, payments, booking, analytics and ad tracking.
• Known problems or past incidents, such as a hack, outage, broken form or slow page, with rough dates if remembered.
• Renewal dates for the domain, SSL certificate, hosting and licences, or the accounts where those dates can be checked.
• Any written record of accounts, renewals and changes already made, so that access and history stay with your business.

• !

  Leaving the site without an owner

  Name someone responsible for renewals, broken forms and outdated plugins, even when an outside provider does the work.

• !

  Keeping backups only on the website server

  Keep a separate copy so a server failure or hack does not take the site and its backups with it.

• !

  Never testing a restore

  Check that a backup can actually be restored before it is needed in an emergency.

• !

  Leaving domain or hosting accounts with a former employee or agency

  Move control to your business so renewals and changes remain possible.