Disclosure: I run Wangdada Labs, a hosting comparison site, and some pages there contain affiliate links (marked as sponsored). This post has no affiliate links. I used AI assistance to draft it, then checked it against the guides linked below. I left out prices on purpose, because they change; check each provider's own page.
Most small-site hosting decisions go wrong in the same way: people compare the monthly price on the checkout page, and that number is only one part of what the site costs. Here is the worksheet I use instead.
1. Split year one from year two
Introductory prices often apply only to the first term. Write down the price for the first term and the price at renewal as two separate lines. If the plan page does not show the renewal price, find it in the provider's pricing notes or terms before you buy.
I wrote this up with a worked example in How to estimate the real cost of hosting a small website. If you would rather plug in numbers, the hosting cost calculator runs in the browser and does not need an account.
2. Add the costs the plan page leaves out
- Domain registration and its renewal price
- Backups, if they are not included, and where the copies are stored
- Domain email
- Migration, if you are moving an existing site
- Your own time for updates, restores and support tickets
3. Test recovery before you need it
A backup you have never restored is a guess. Pick a restore path, run it on a copy, and note how long it took and who has to be involved. The framework for evaluating hosting backups, migration and support lists the questions to ask a provider in writing, such as what the migration covers and what it excludes.
If you are moving hosts, do not change DNS first. Restore to a separate destination, validate it, then switch traffic and keep the old host until you are sure. The website migration checklist walks through that order.
4. Upgrade only when you have evidence
A bigger plan does not fix a slow theme, oversized images, or a broken DNS record. Before paying for managed cloud or a VPS, find out what is actually slow or failing. Two guides cover this from opposite sides: when not to pay for managed cloud hosting and whether low-traffic WordPress should stay on shared hosting.
5. Run a pre-launch pass
Before a site goes live, check backups, HTTPS, redirects, email, access, monitoring and a rollback plan. There is a printable WordPress pre-launch checklist for that.
The short version
- Price the first term and the renewal separately.
- Add domain, backups, email, migration and your time.
- Restore a backup once before you rely on it.
- Upgrade for evidence, not for a feeling.
If I got something wrong or you handle one of these steps differently, tell me in the comments.
Top comments (0)