Website and WordPress maintenance plans in Dundee

If nobody can say who is responsible for your website after launch, small faults tend to sit until they become urgent. I provide website maintenance for Dundee businesses that need an accountable developer for agreed updates, checks and technical support. WordPress sites can be covered, as can other business websites where the code, hosting and access are suitable.

The first step is not an automatic update button. I review the website address, hosting, administrator access, software versions, licences, backups, forms and known faults. You then get a clear answer on what can move into routine care, what needs fixing first and what sits outside the plan.

Web Spinner UK is based in Preston and does not claim a Dundee office. The maintenance work is delivered remotely, which is how server access, WordPress administration, backups and most website repairs are handled in practice. You deal directly with Sam rather than passing requests through an account manager.

A site bought through the managed Web Spinner UK checkout moves to the published £250 per year care plan after its included first year unless it is cancelled before renewal. A Dundee site inherited from another developer is different: its condition and third-party costs are unknown, so it is assessed and quoted before I accept responsibility for it.

A takeover review looks for the quiet problems that make later maintenance unreliable: abandoned plugins, a custom theme with no update path, an old PHP version, backups stored only on the same server, expired licences, shared administrator accounts and forms that send mail through an unverified setup.

I also need to know what matters most when the site changes. A brochure website needs its contact route checked. A booking or membership site has more moving parts. A WooCommerce store needs cautious updates and a defined checkout test. Those differences affect the scope; they are not hidden behind one generic plan name.

Routine work follows a simple order: check the current state, create or confirm a usable backup, apply the agreed change, test the important public journey and record anything that still needs a decision. WordPress itself advises backing up before an update, and I treat that as a baseline rather than an optional extra.

If an update exposes a compatibility fault, the sensible response may be to roll back and investigate instead of applying more changes. Major repairs, a redesign, new functionality, paid plugin licences and recovery from a pre-existing compromise are quoted separately. That boundary keeps the Dundee care plan useful and prevents “maintenance” becoming an unlimited development promise.