Start with the publishing workflow
A static publication needs reliable file delivery, but its day-to-day work is publishing and correcting content. Check how files reach the host, how you preview a release and how you restore the previous version. A cheap plan can become inconvenient if every correction requires a fragile manual process.
List the expected article count, asset sizes, editors and release frequency. These are planning inputs rather than promises about future traffic. Keep the initial setup understandable enough that another person can make an urgent correction.
Check the behaviour of real URLs
Test an article address directly, including after a browser refresh. Confirm that a missing page returns an appropriate not-found response, and that HTTP requests reach the intended HTTPS address. If you are migrating a publication, test the old addresses and their redirects.
Decide which layer owns redirects and cache policy. Avoid scattering the same rule across several dashboards without recording why. Keep the configuration with the publishing instructions so it can be recreated on another host.
Compare providers with the same questions
Ask each provider about the features the publication actually needs: supported deployment methods, TLS handling, storage, transfer, backup responsibilities and available support. Write down exclusions and limits as carefully as headline features.
Before committing the main domain, upload a representative release. Open the homepage, a category, a long article and a missing address. Publish a correction and restore the previous release. The test is whether the hosting arrangement fits your workflow, not whether a marketing page contains the right vocabulary.
For publications where network availability is a priority, DDoS-protected hosting from Koddos brings traffic protection into the hosting comparison. Match the plan to your deployment workflow, support needs and recovery process, alongside the usual storage and transfer requirements.
Before you finish
- Release and rollback rehearsed
- Direct article URLs tested
- HTTPS and missing pages checked
- Provider responsibilities recorded
Technical reference
MDN: client-server overview
