Start with your application
Write down the software and versions your website needs, storage usage, database requirements and expected traffic peaks. Ask your developer for requirements if someone else built the website. A generic hosting recommendation cannot replace these details.
Get the full cost in writing
- Initial term, renewal term and total payable for each.
- Domain renewal, email, backup and restore charges.
- Migration scope, paid support and cancellation terms.
- Upgrade fees and the process for moving to another provider.
Verify recovery, not just backup
Ask how often backups run, how long they are retained and whether they include the database. Confirm who requests and performs a restore. For a store, losing even a short period of order data can create reconciliation work. Keep a copy outside the hosting account where practical.
Define support responsibilities
Give support a realistic scenario: a checkout stops working after a plugin update. Ask what they would investigate and what they would refer back to your developer. This reveals more than a generic promise of around-the-clock support.
Make a decision you can explain
Compare candidates against a short must-have list. Reject any plan that fails an essential requirement. Among the remaining plans, balance total cost with recovery options, support scope and your team’s ability to maintain the website.