Skip to main content
Office: 01772 485 348 24/7 emergency: 07903 505 874 WhatsApp
This Week's Special Offer ANY Custom Coded Website 10% off fully coded systems this week. Call now on 01772 485 348 or contact us and we will point you in the right direction. Call Now: 01772 485 348 Contact Us Google Reviews Trustpilot
Website care and support · Cheltenham

Website care plans and WordPress support in Cheltenham

Controlled updates, backups, practical checks and direct developer support for Cheltenham businesses. Existing websites are inspected before responsibility or pricing is agreed.

Sami Swain, founder of Web Spinner UK, with his son Teddy
Backup before risky changes Direct developer support Scope agreed before takeover
Takeovers are scoped after a website review Managed builds £250/year after year one; inherited sites assessed first
Project Intake

Request a website takeover check

Send the website address and the main concern. Do not send passwords or access keys here; I will explain a secure access route if an inspection is appropriate.

Do you already have a website?
£199
£ Drag or type to set it. Snaps to £50 (max £10,000+).

By sending this enquiry, you agree to Web Spinner UK contacting you about your request. See our Privacy Policy.

Submitting this form does not transfer responsibility for the website or start paid work.

The takeover method

Inspect first. Then maintain what is actually there.

An inherited website is not placed on a cheap plan before its access, software, licences, backups and existing faults are understood.

What to send first The public website address and the main concern

Do not send passwords or access keys in the form. A secure access route is agreed only if an inspection is appropriate.

01 / Website takeover

Six checks before routine care begins

  1. Send the website address

    Tell me who hosts it, what platform it uses if known, and which fault or maintenance gap is causing concern.

  2. Review access and condition

    I check ownership, versions, licences, backups, forms and the parts of the website the business relies on.

  3. Separate old faults

    Repairs needed before takeover are identified instead of being hidden inside a routine monthly or annual fee.

  4. Write down the plan

    The update cycle, backup route, checks, support channel, change allowance, reporting and exclusions are agreed for this website.

  5. Back up, change and test

    Risky work starts from a recovery point and finishes with the agreed enquiry, checkout, booking or login check.

  6. Escalate what needs a decision

    Unsupported software, larger repairs and new development are explained and quoted instead of silently ignored.

Choose the right care route

The price depends on who built the site and what it needs.

The managed renewal belongs to websites bought through the managed checkout. An inherited site is reviewed before its maintenance scope or price is agreed.

Managed website renewal £250/year

After the included first year, unless cancelled before renewal.

02 / Care routes

Compare the three starting points

Choose by the current ownership and level of work, not by trying to force every website into the same plan.

Managed-site renewal

Annual continuity after year one

Websites bought through the managed checkout move to the £250/year care plan after 12 months unless cancelled before renewal.

See the managed plan
Existing website

Takeover review, then a clear plan

An inherited WordPress or business website is inspected before the maintenance scope and price are agreed.

Request a takeover check
Regular changes

Active maintenance and management

From £350 per month where the brief includes continuing technical changes, content work or active improvement.

Discuss active management

Maintenance plan boundaries

What is fixed on the managed annual plan?

The £250/year managed plan covers the domain, hosting, security, backups, essential updates and support for the website bought through the managed checkout. It follows the included first year and can be cancelled before renewal.

What is written down for an inherited website?

The proposal identifies the update cycle, backup storage and restoration route, post-change checks, support channel, response arrangement, any change allowance, reporting and third-party subscriptions. It also lists faults that must be fixed before routine care begins.

What is not included automatically?

Major repairs, redesigns, new features, malware clean-up, emergency out-of-hours work, paid plugin licences and unlimited edits are separate unless the written scope explicitly includes them.

Why back up before updating?

WordPress advises creating a backup before updates and keeping both site files and the database recoverable. Read the official WordPress update guidance and backup handbook.

Not sure whether maintenance or a rebuild makes sense for a Cheltenham business? Send the public website address and the main concern. I will explain the next access step if an inspection is appropriate.
Ask Sam to check it
Local service detail

Website & WordPress Maintenance for Cheltenham businesses

The website, its ownership and its important customer journeys are assessed before routine care begins.

What this maintenance page covers

A hosting invoice does not mean somebody is maintaining your website. Hosting provides the server; a care plan defines who checks software, deals with agreed faults, protects a recovery route and keeps routine technical work from being forgotten. This page is for Cheltenham businesses comparing those two very different things.

I maintain WordPress and other business websites after reviewing the site that actually exists. The review covers access, hosting, core software, plugins or packages, theme or code ownership, backups, forms, SSL and known problems. I then separate routine care from repairs or development that need their own scope.

Eligibility, delivery and pricing

Web Spinner UK supports Cheltenham websites remotely from Preston; there is no Cheltenham office. The useful part of that arrangement is direct access to the person checking the site. You can send the website address and explain what is worrying you, without first translating the problem for a sales desk.

The £250 per year figure on this site is the renewal care plan for websites bought through the managed checkout after their included first year. It is not a blanket price for taking over an unknown WordPress installation. Existing websites are quoted after inspection, while active maintenance and management starts from £350 per month when the brief includes regular changes or growth work.

What I check before taking responsibility

WordPress maintenance is more than updating the core. A safe plan has to account for the theme, plugins, PHP version, database, forms, email delivery and any booking, membership or ecommerce features. One update can be technically successful while still breaking a visible journey that customers use.

The takeover also needs clean ownership. Domain, DNS, hosting, premium licences and administrator accounts may sit with different suppliers. If nobody knows which account controls what, recovery takes longer. I identify those dependencies first and make clear which third-party subscriptions remain the client's responsibility.

How updates and fixes are handled

For routine updates, I confirm the backup position, review the change, update the agreed components and check the parts of the site that matter. That might mean the enquiry form on a service website or the basket and checkout on a WooCommerce store. The exact smoke test is agreed for the site rather than copied from a generic checklist.

A plan does not guarantee that software will never fail or that a website cannot be attacked. It reduces avoidable neglect and gives the business a defined response when something changes. Malware cleanup, emergency recovery, new features and major design work are assessed separately unless the written scope says otherwise.

After takeover

What ongoing website care looks like in Cheltenham

Once access, ownership, the recovery route and the written scope are agreed, routine care follows a controlled change-and-check cycle. Work outside that scope is explained before it is added.

Accountable maintenance What the maintenance record should make clear

What changed and when. Which important journey was checked. What needs a decision from the website owner. What sits outside the agreed maintenance scope.

03 / Ongoing care

The controlled change-and-check cycle

  1. Plan the change

    Routine updates and agreed requests are handled against the website’s written scope and important customer journeys.

  2. Confirm the recovery point

    Risky work starts only when the agreed backup or restoration route is available.

  3. Change and check

    The maintained component is changed, then the relevant form, checkout, booking or login route is checked where applicable.

  4. Record and escalate

    Material work is recorded. Unsupported software, larger faults and decisions for the owner are raised rather than hidden inside routine care.

Maintenance timing

There is no universal update timetable or emergency SLA. The maintenance cycle and response arrangement are written around the platform, risk and business-critical journeys.

  • Routine work follows the agreed cycle.
  • A risky update may be deferred while compatibility is checked.
  • Urgent or out-of-hours work is covered only when the written scope says so.
Responsibility and terms

Responsibility starts only after the site is reviewed, any required stabilisation is agreed and the maintenance proposal is accepted.

  • Included work and any change allowance are written down.
  • Third-party subscriptions and pre-existing repairs are identified separately.
  • New features and major development are quoted before work starts.
A sensible fit
  • Ownership and the required access can be verified.
  • The site is supportable or can first be stabilised.
  • The business wants one accountable developer for agreed technical care.
Needs a different first step
  • The website is actively compromised or needs emergency recovery.
  • Ownership, access or a workable recovery route cannot be established.
  • Unsupported code makes safe routine maintenance unviable.
  • Unlimited edits, development or out-of-hours cover are expected under a routine fee.
Useful questions

Website & WordPress Maintenance in Cheltenham FAQs

What is the difference between hosting and a Cheltenham website care plan?
Hosting supplies the server environment. A care plan covers the agreed human and technical work around updates, backups, checks and support. They can be supplied together, but paying for hosting alone does not mean the website is being maintained.
Do you install every WordPress update as soon as it appears?
No. The update is considered against the site’s theme, plugins, PHP version and important customer journey. A risky or incompatible release may be held back while the correct route is investigated.
What backup arrangement is checked during takeover?
I look for both website files and the database, where copies are stored, how recent they are and whether there is a credible restoration route. A backup name in a control panel is not treated as proof on its own.
Who pays for premium WordPress licences?
Licence ownership and renewal costs are recorded before takeover. They remain separate unless the written maintenance proposal explicitly includes them, because an old agency or developer may currently own the licence.
Can a compromised Cheltenham website join a routine plan?
Not immediately. Diagnosis and recovery are separate from routine maintenance. I will explain the likely recovery work first, including where specialist security support may be needed.
WhatsApp us