How to Install WordPress on Plesk with WordPress Toolkit

Install WordPress on Plesk in two minutes with WordPress Toolkit, then set the day-one options: SSL, updates, hardening, backups and staging.

Published
Reading time
3 min

Plesk ships with WordPress Toolkit, which installs, updates and secures WordPress from the panel. It takes about two minutes and avoids every mistake of a manual install: wrong permissions, a database with too many privileges, a forgotten wp-config.php salt.

1. Install

  1. Open Websites & Domains and pick the domain.
  2. Click WordPress in the left menu (or Install WordPress on the domain card).
  3. Click Install. The defaults are right for most sites; check three of them:
    • Installation path: leave empty to install at the domain root, or type blog to install at /blog.
    • Website title, admin username (not admin), a strong password, and your email.
    • Automatic update settings: Minor (security) updates for core, Auto-update for plugins and themes if the site is simple, Manual if it runs anything custom.
  4. Click Install again. Plesk creates the database and user, downloads the current WordPress, writes wp-config.php, and sets file ownership.

You now have a working site with a login link on the Toolkit card.

2. Turn on HTTPS before anything else

If the domain does not have a certificate yet, follow install a free SSL certificate in Plesk. Then, on the WordPress Toolkit card, toggle SSL/TLS support — that rewrites the site URL to https:// and turns on the redirect so there is never a mixed-content phase.

3. Run the security check

The Toolkit card has a Security section with a checklist. Click Check Security, then Secure with all items selected. Among other things it:

  • restricts file permissions to 644/755,
  • blocks PHP execution in wp-content/uploads,
  • disables the file editor in the admin,
  • turns off pingbacks and XML-RPC (unless you need Jetpack),
  • changes the database table prefix if you still have wp_.

Each item can be reversed later, so there is no reason to skip any.

4. Set up updates the way you want them

Under the card's Updates section:

  • Core: minor updates automatically. These are security releases; installing them the same day is the single best thing you can do for a WordPress site.
  • Plugins and themes: automatic if the site is a standard theme with a few well-known plugins; manual with Smart Updates if anything is custom. Smart Updates clones the site, applies the update to the clone, compares screenshots, and only updates live if nothing broke.

5. Make a staging copy

Click Clone on the card, choose a subdomain such as staging.example.com, and Plesk copies the site and database. Test plugins and theme changes there, then use Sync to push the changes to the live site. The full workflow: WordPress staging on Plesk.

6. Confirm backups

Under Backup & Restore for the domain, schedule a daily backup with at least seven copies kept. On VPSPioneer plans this is already scheduled and stored off the server; on your own VPS, set it now. Restoring a single WordPress site from a Plesk backup takes one click, but only if the backup exists.

7. Basic performance settings

Three things worth doing on day one, all in Plesk rather than in plugins:

  • PHP version — the newest available; PHP Settings for the domain.
  • Serve static files directly by nginx — under Apache & nginx Settings.
  • Enable nginx caching — same page, 5 minutes is a safe default.

That combination usually makes a page-cache plugin unnecessary. The rest of the tuning is in speed up WordPress on Plesk.

Manual install, if you must

Occasionally you need to install by hand — a specific old version, or a site being restored from a zip. Upload the files, create a database under Databases, and copy wp-config-sample.php to wp-config.php with the credentials. Then open WordPress in Plesk and click Scan so the Toolkit picks the site up and manages it from then on.

Common problems

The install button is greyed out — the domain has no hosting enabled, or PHP is switched off. Check Hosting Settings.

"Unable to connect to the database" after install — rare, and usually a MySQL restart at the same moment. Click Repair on the card.

The site shows the Plesk default page — the document root is not where WordPress was installed. Check the path under Hosting Settings → Document root.

Every VPSPioneer shared and reseller plan includes WordPress Toolkit with Smart Updates, and on a managed VPS we install and harden the first site for you as part of setup.

#wordpress#plesk#wordpress-toolkit#install

Keep reading

More from WordPress

All guides

WordPress

How to Speed Up WordPress on Plesk in 20 Minutes

Six changes that make WordPress on Plesk noticeably faster — PHP-FPM, OPcache, Nginx caching, WebP images, database cleanup and a CDN — with exact settings.

3 min read →

Plesk

How to Install a Free SSL Certificate in Plesk (Let's Encrypt)

Secure any site in Plesk with a free Let's Encrypt certificate in under five minutes, including www, wildcard subdomains, mail and automatic renewal.

3 min read →

Domains

How to Choose a Domain Name That Still Works in Five Years

A practical method for picking a domain — length, spelling, TLD, trademarks, social handles — and the mistakes that force a rebrand later.

3 min read →