Hosting for a content management system: what to check before ordering

Start with the application's current requirements

A content management system needs a supported runtime, a database and a secure connection. Recommended versions change, so check the current documentation for your system and for any important theme or extension before ordering. The official requirements page of a common content management system is one example of such documentation. Also ask how easily you can change and test the PHP version without affecting the live site.

Running a site takes more than one click

An installer saves the first step, but routine operation includes updates to the core, theme and extensions, compatibility checks, backups and recovery. For a 'managed' service, ask for an exact list of tasks the provider handles and those that remain yours. Automatic changes without a way to test them can be as troublesome for a complex site as outdated software.

A separate staging environment is useful for a larger site. Check whether it is included, whether it can copy both files and the database, and how it prevents new orders or comments from being overwritten when changes return to production. Also verify access to files, the database and logs, since some problems are difficult to diagnose without them.

Try a specific scenario

Instead of asking whether a plan is suitable for your site, send support the requirements of your project: the required runtime version, database size, expected peak traffic, email needs and planned extensions. The answer tells you more than a broad product label. Once the site is running, monitor real page speed and resource use so you can adjust the configuration or plan in time.