Hosting choices
Managed WordPress hosting: what should the service actually include?
Compare platform work, support boundaries, updates, backups, and remaining responsibilities before choosing a managed plan.
Managed WordPress hosting is worth paying for when the provider takes on specific platform work you would otherwise have to perform or arrange. The word “managed” alone does not tell you whether plugin updates, malware cleanup, checkout problems, or custom-code fixes are included.
Choose the service by its responsibility and recovery promises, then check its capacity and price. A long feature list is less useful than knowing who responds when the site stops taking enquiries.
Ask who performs each task
| Task | Question for the provider |
|---|---|
| Platform maintenance | Who updates the server software and manages PHP changes? |
| WordPress updates | Which core, theme, and plugin updates are performed, and how are failures handled? |
| Backups | What is included, how often is it copied, and who restores it? |
| Security incidents | Does the service include investigation and cleanup, or only detection? |
| Application faults | Where does hosting support stop and developer responsibility begin? |
For each answer, record whether the task is automatic, available on request, an add-on, or your responsibility. Include response channels and the conditions under which paid assistance is required.
Read the support boundary
Kinsta’s support scope is a useful example of a documented boundary: it covers platform assistance and investigation of server issues, while code changes and development work remain outside the support scope. Other providers define their own boundaries.
Ask a concrete scenario: “After a plugin update, checkout returns an error. What will your team do, what will it restore, and what must our developer fix?” This reveals more than asking whether support is available around the clock.
A support team identifying a broken plugin can be valuable even when it does not rewrite that plugin. Budget for the developer who owns the next step.
Check workflow restrictions before moving
Inventory the plugins, scheduled tasks, external integrations, and server configuration your site uses. Confirm compatibility with the host’s caching, security controls, and any restricted-plugin list. Managed platforms can intentionally limit changes that would compromise their operating model.
Review staging access and how changes return to production. Copying a staging database over a live store can erase orders placed since the staging copy was created. The presence of a push button does not remove the need for a data plan.
Confirm whether email hosting, domain registration, and transactional email are included or separate. A successful website move does not prove that business mail will continue working.
Compare real workload capacity
Record sites, storage, transfer or visit allowances, PHP concurrency where disclosed, and overage behavior. Ask what happens during a traffic burst. A plan suitable for cached articles may not support the same number of logged-in users or checkout requests.
If the site is already slow, collect the evidence described in our WordPress CPU guide. A new management arrangement is not proof that an expensive application operation has been fixed.
Include recovery and exit in the price
Check backup retention, downloadable copies, and restoration granularity. Our backup guide explains why a restore button inside one provider’s dashboard should not be your only recovery path.
Compare the recurring plan, required add-ons, extra sites, overages, and remaining maintenance work. As a hypothetical example, a $35 plan plus $15 of necessary services and an hour of developer work is not a $35 operating arrangement.
Choose it when the responsibility match is clear
Managed WordPress hosting fits owners who want an operated platform and documented help while retaining someone to own the application. A self-managed VPS fits a different division of work. Use the managed-versus-unmanaged comparison if you are weighing that tradeoff.
Before committing, confirm the migration scope, recovery process, and first renewal quote. The strongest reason to buy is a specific reduction in work and uncertainty that matters to your site.