Introduction #

In this doc you’ll learn more about WP Toolkit and how it works with your WordPress site at ProRedLine. WP Toolkit is a key feature when creating, editing and maintaining your WordPress site.

---

Understanding WP Toolkit #

WP Toolkit is the central management interface for WordPress inside cPanel. It is designed to give you a clear overview of the WordPress installations on your hosting account and provides tools to manage them from one place. Rather than handling every task manually, WP Toolkit allows you to work with your WordPress sites through a structured interface inside cPanel.

WP Toolkit does not install WordPress automatically. A website will only appear in WP Toolkit after a WordPress installation has been created or detected on your hosting account. If no installations are shown, this usually means that WordPress has not yet been installed.

Where to Find WP Toolkit #

To access WP Toolkit, log in to cPanel and look for WP Toolkit in the sidebar or WordPress Management in the Domains section. Once opened, you will see an overview of the WordPress installations that exist on your account.

The Main Overview Screen #

The main WP Toolkit screen is built around an overview of your WordPress sites. Each installation is shown separately, allowing you to quickly see which websites are present and what their current status is.

The overview includes:

• the domain and installation path
• the WordPress version
• update and security indicators
• quick action buttons for common management tasks

This overview is intended to give you a fast operational view of your WordPress environment without having to open each site manually first.

Installation Cards #

Each WordPress installation is shown as its own card within WP Toolkit. These cards help separate one site from another and make it easier to manage multiple WordPress installations from the same hosting account.

A typical installation card may include:

• the website domain and install location
• a login button for the WordPress admin area
• the update status for WordPress core, plugins, and themes
• maintenance or security-related indicators
• action buttons for site-specific tasks

Any action you use on an installation card applies only to that specific WordPress site, so it is important to confirm that you are working on the correct installation before making changes.

Common Actions in WP Toolkit #

WP Toolkit provides direct access to common WordPress management actions. The exact options may vary slightly depending on the installation and server configuration, but common actions often include logging in to WordPress, updating the core installation, updating plugins or themes, enabling maintenance mode, cloning a site, creating a staging copy, or removing an installation.

Some of these actions are routine, while others can significantly affect the website. For example, updates and maintenance mode are usually straightforward, but cloning, staging, or removing a site should always be used carefully because they can impact the structure or content of an installation.

Status Indicators and Scope #

WP Toolkit also uses status indicators to highlight available updates, security recommendations, or configuration warnings. These indicators are meant to help identify potential issues or maintenance tasks, but they do not always mean that the website is broken or offline. In many cases, they simply point to areas that may need attention.

It is also important to understand the difference between site-specific tools and global tools. Some actions only affect one selected WordPress installation, while others may apply more broadly across multiple installations on the same hosting account. Before confirming a change, always verify the scope of the action so you know exactly which site or sites will be affected.

---

Removing & Detaching a WordPress Installation #

WP Toolkit offers different ways to stop managing a WordPress site, and it is important to understand the difference before taking action. Removing and detaching may sound similar, but they do not do the same thing. One permanently deletes the installation, while the other only disconnects it from WP Toolkit management.

Removing a WordPress Installation #

Removing a WordPress installation is the destructive option. This action is intended for situations where the site is no longer needed and should be permanently deleted from the hosting account.

When an installation is removed, WP Toolkit typically deletes:

• the WordPress files
• the related database
• the installation itself from the hosting environment

In practice, this means the website is permanently removed. Unless you have a valid backup available, this action cannot be reversed. For that reason, removal should only be used when you are fully certain the site is no longer required.

Detaching a WordPress Installation #

Detaching a WordPress installation works differently. Instead of deleting the site, WP Toolkit simply stops managing it. The WordPress files and database remain in place, and the website itself stays intact.

A detached installation:

• is no longer managed through WP Toolkit
• keeps its files and database
• continues to exist on the hosting account

This is usually useful when WordPress was installed manually, when you prefer to manage it outside of WP Toolkit, or when you do not want WP Toolkit to handle updates and management tasks for that installation.

When Removal Makes Sense #

Removing a site is usually appropriate when the installation is no longer needed, when WordPress was installed by mistake, or when you want to completely start over with a fresh setup. Because this action is destructive, a backup should always be made first if there is any chance the site or its data may be needed again later.

When Detaching Makes Sense #

Detaching is usually the better choice when the site should remain online and intact, but no longer needs to be managed through WP Toolkit. This can be useful for independently managed installations or custom setups where WP Toolkit is no longer part of the workflow.

Important Warning #

Before using either option, always confirm which action you are selecting. Remove permanently deletes the installation, while Detach only disconnects it from WP Toolkit. If there is any doubt, create a backup first and review the action carefully before confirming.

---

Security Features in WP Toolkit #

WP Toolkit includes a set of basic security tools that can help improve the baseline security of a WordPress installation. These features are intended to support safer default settings and reduce common risks, but they should be seen as part of general WordPress hardening rather than as a complete security solution.

What These Security Features Do #

The security tools in WP Toolkit are mainly focused on hardening the WordPress environment. In practice, this means they can help apply recommended settings that make certain common attack paths less accessible and improve the default security posture of the installation.

Depending on the installation and server setup, WP Toolkit may offer measures such as:

• disabling file editing from inside WordPress
• protecting sensitive files
• enforcing safer permissions
• hiding WordPress version information
• enabling basic login-related protections

These settings help reduce exposure to common weaknesses and are useful for improving the initial security baseline of a WordPress site.

What These Security Features Do Not Do #

It is equally important to understand the limits of these tools. WP Toolkit security features do not replace proper maintenance, careful plugin and theme management, or broader website security practices. They also do not function as a full security monitoring or malware cleanup solution.

For example, these features do not actively monitor your site for compromise, and they do not automatically repair a hacked WordPress installation. Ongoing updates, secure passwords, limited admin access, and responsible plugin usage remain essential parts of WordPress security.

How Security Measures Are Applied #

Security measures in WP Toolkit are generally reviewed and applied per WordPress installation. This means you can inspect the available recommendations for a specific site and decide which measures to enable. These changes are not automatically forced on every installation by default, so customers remain in control of what is applied.

Before enabling security changes, it is still good practice to review what each recommendation does, especially on websites with custom configurations. While most hardening measures are beneficial, some settings may affect how certain plugins, themes, or workflows behave.