Hosting Suite's managed WordPress workflow uses cPanel's native WP Toolkit integration. Prepare the server, package and sample account before creating products, so that new orders receive a working WordPress environment and the customer manager can discover their websites.
IN THIS ARTICLE
01 Prepare the hosting environment
- Check that the cPanel server meets its own requirements and has WP Toolkit installed. Installing Hosting Suite does not install a missing WP Toolkit server package.
- Confirm that the WHMCS server connection can manage the intended hosting accounts and read the required package information.
- Open the relevant WHM package and feature list. Make WP Toolkit available to the accounts that should receive WordPress management.
- Create or identify an active sample hosting account on that server. Confirm WordPress is accessible through WP Toolkit for this account.
- Open Hosting Suite's App Hosting area, select the server or server group, and check the Managed WordPress option and server checks.
02 Understand feature-list changes
The module can help enable an available WP Toolkit feature when it has sufficient permission. A package's feature list can be shared by several accounts. Review that scope before changing it, because the change can affect other customers on the same package. Use a separate feature list when different plans should expose different tools.
WP Toolkit availability also depends on the server installation and its applicable licensing. A successful WHMCS API connection alone does not prove that every WordPress action is available.
03 Run an end-to-end test
Provision a test application plan with an unused domain or safe test location. Confirm the account is created, WordPress installs in the selected path, and the service opens the correct website manager. Test WordPress administration login, plugin listing, an available backup action and a harmless setting change. Check HTTPS after DNS and the certificate are ready.
Review the customer sections such as Dashboard, Plugins, Updates, Backups and Staging & clone. AI, CDN, security and performance integrations need their own configuration and should be checked separately.
Why is an existing website missing?
Confirm the service is linked to its real cPanel username and main domain, then check whether WP Toolkit has registered the installation. A WordPress directory on disk is not sufficient evidence that the manager has discovered it. Refresh the supported website list and investigate the provider response before creating another installation.
Use the current native WordPress workflow in your customer documentation. Do not describe these plans as WP Squared or promise features from a different website builder.