Managed WordPress hosting: what is actually managed?

Start with the website you operate

A brochure site, a membership service and an online shop have different recovery needs. Write down the forms, payments, integrations and customer records that matter. Include the theme and plugins the business depends on, especially licensed components maintained by another supplier.

For a fictional training company, a broken course-booking form is more serious than a cosmetic spacing problem. Its hosting brief should therefore include the booking journey, confirmation message and administrator handover. That gives the provider a concrete application to discuss instead of a vague request for a fast managed server.

Separate platform updates from application maintenance

WordPress’s update documentation recommends backing up before an upgrade. Hosting automation may help apply updates, but ask which components are included, whether timing can be controlled and who investigates a conflict. A current WordPress core does not prove every plugin remains compatible.

SiteGround’s automatic-update recovery guidance describes a backup made before its update and a restoration route. Use this as a precise question for any proposal: which event creates a restore point, and what application state will be replaced if that restore point is used?

Check the testing environment

A staging copy provides somewhere to rehearse a change. SiteGround’s staging overview identifies eligibility conditions for its tool; do not assume the same feature exists in every hosting package. Ask for the exact plan and supported website type.

The training company should test booking, payment configuration and confirmation routing in an isolated setup. Prevent test messages and transactions from reaching real customers. A staging URL alone does not establish that the copy is isolated from production integrations or that publishing it will preserve new bookings.

Ask about recovery in business terms

Define how much recent work the business could reconstruct and how quickly it needs service restored. Then ask the provider to explain the proposed recovery path. Backup frequency and successful restoration are different pieces of evidence; a list of dated backups does not demonstrate that the booking system works after a restore.

Read the support boundary before an incident

Ask whether support handles server availability, WordPress configuration, plugin conflicts, custom code or only some of those areas. Record response channels and escalation options in the selected plan. A round-the-clock contact route does not necessarily mean every application repair is included.

Name the developer or administrator who can make application changes when support identifies a plugin problem. Keep account ownership and recovery access with the business. If an agency manages the site, establish who can contact the host and authorise a restoration when the usual contact is absent.

Check migration and account ownership

Ask what the business receives if it leaves: files, database export, mail where applicable and a clear explanation of provider-specific components. Confirm who owns the domain registration and which account controls DNS. Moving the website and moving email can be separate projects, so list them separately in the handover.

For the training company, the acceptance test should include a usable copy of the course site and an inventory of paid components needed to run it elsewhere. A migration assistance promise should identify its scope and exclusions. Keep enough information to change providers without depending on one unavailable individual.

Compare total ownership cost

Include hosting, renewal, premium plugins, email where separate, maintenance work and any required monitoring or backup service. A lower hosting fee may be sensible if the team already maintains the application; a more comprehensive service may suit a business without that capacity. Compare the actual scope before comparing the monthly equivalent.

The hosting renewal-cost guide covers the later bill. The staging workflow guide covers release risk. Research providers through the SiteGround and Kinsta profiles, then ask each shortlisted host to respond to the same responsibility map.

Frequently asked questions