Hosting for a business WordPress website
How to choose hosting for your website.
Start with three questions: what must the website do, how much recent data could you afford to lose, and who will restore it after a failure? This guide helps you compare what each offer includes and agree responsibilities before buying.
Business needs
First, describe what the website does.
List its essential functions: presenting services, receiving enquiries, taking bookings or selling products. Include how often content changes, when you expect traffic peaks and who is available for maintenance. A site with occasional edits and a store receiving new orders need different backup schedules.
Define an acceptable interruption and how much recent work you could recreate. Agree these requirements with the provider rather than assuming a plan name guarantees them.
In this guide: plan types, resources, backups and recovery, support and costs, and questions for a quote.
Planning a new website rather than moving an existing one? See how we scope WordPress website development.
Type of service
Compare who takes responsibility for each task.
01
Shared hosting
Check your account limits, isolation from other customers and upgrade options. Ask what happens when the plan reaches a limit.
02
Managed WordPress hosting
Ask for a written scope: does it cover WordPress and plugin updates, backups, recovery and troubleshooting within the website? Check restrictions on plugins and access.
03
VPS or dedicated server
Agree who maintains the operating system, security settings and WordPress. The term VPS alone does not tell you whether administration is included or who responds when something stops working.
Compatibility and capacity
Check resources against the actual website.
The plan should meet the current recommended WordPress requirements, including supported PHP and database versions and HTTPS. Ask how new versions are tested with your theme and plugins before a change.
Alongside storage, ask about CPU, memory, concurrent processes and disk input/output limits. Usage reports and notifications when you approach a limit can help you plan upgrades.
Assess a demanding website using representative pages and actions, such as search or the shopping basket. Record the test conditions and load. Themes, plugins, images and caching also affect speed, as the WordPress optimisation guide explains. Without comparable tests, you cannot reliably conclude which plan is faster.
Want help applying this to your website? See Website security or tell us about your project ↗
Backups and recovery
Ask how the website will be restored.
A complete WordPress recovery needs both the database and files. Check what each backup contains, how often it runs, how many versions are kept and whether a copy is stored separately. The official backup guidance explains these components.
Agree who can request a restore, how incidents are reported and whether recovery carries an extra charge. Ask whether you can download your own copy and what happens to backups after the account expires.
How to check that a restore works
Request a trial restore in a separate test environment. The person running it should prevent real messages and payments, restrict access to test data and check important pages, images, login and key functions.
Record the backup date, test date, restore duration, functions checked and any problems. The gap between the backup and the incident indicates which recent changes would need to be recreated. Use this to agree a suitable backup frequency.
Support and costs
Read what is included after purchase.
Check support hours, the route for urgent failures and the escalation process. Ask whether a stated time refers to the first response or to resolution. Clarify who fixes a plugin fault and who handles a hosting service failure.
Compare renewal pricing and charges for backups, recovery, migration, email and required licences. Record who owns the account, who has administrative access and how you can export your data when leaving.
Hosting and ongoing maintenance may cover different work. Our WordPress maintenance page explains how we agree an initial review, responsibilities and further work.
For your next quote
A checklist you can send to a provider.
01
Compatibility and resources
Which software versions and limits does the plan have? How can I monitor usage and increase capacity?
02
Backups
Do they include both the database and files? How often are they created, where are they stored and how long are they available?
03
Website recovery
Who performs a restore, what does it cost, and can we arrange a test with a written result?
04
Support and maintenance
When is support available? What is included and who follows an issue through to resolution?
05
Pricing and leaving
What is the renewal price with all required extras? How do I download my website and backups if I change provider?
Send the same questions to the providers you are considering. Mark incomplete answers for clarification before deciding.
A backup only counts once a restore has worked. WordPress backup restore test shows what such a test checks.
Need a clearer maintenance plan?
Send your website address and describe what matters most: reliable recovery, clear responsibilities or regular checks. The first step is to review the current setup and agree the scope.
More guides
Keep reading.
Last updated:
Related services: Website security · WordPress care · Website development