Use this guide for a new WordPress site on your own server. If your service already includes an installed site, start with the verification section. Do not install over an existing site or use a fresh installation as a migration.
1. Confirm the starting point
Check your service details for a control-panel address and application login. A server password is not a WordPress password. A control panel or installer is available only when included in your order; this article does not add a licence to your service.
For a new manual installation, prepare a supported PHP runtime, a web server, a private database and HTTPS. WordPress currently recommends PHP 8.3 or later and MariaDB 10.11 or later, or MySQL 8.0 or later. Check plugin compatibility before choosing versions.
2. Install a fresh site
- If your existing panel provides a WordPress installer, select the correct domain and an empty document root. Choose HTTPS, a unique administrator name and a strong password. Leave the directory field empty only when installing at the domain root. Review the destination before starting.
- Without an installer, use the official WordPress download and installation guide linked below. Create a separate database and a user restricted to that database. Upload the extracted WordPress files to the domain's empty document root using SFTP.
- Open the domain in a browser and complete the database and site setup. Record the administrator account in your password manager. Do not reuse your server password.
- If PHP source downloads or appears as text, stop: the web server is not executing PHP. Fix the runtime before entering any database credentials.
3. Verify before publishing
- Open the home page and /wp-admin/ over HTTPS without a certificate warning.
- Log in, save a draft page, upload a small test image and open its URL. Delete only the test content you created.
- Open Tools → Site Health and resolve critical issues. Confirm the correct site URL in Settings → General.
- Check a permalink and a password-reset email using an address you own. A working website does not prove outbound email works.
4. Keep the site recoverable
Back up the database and files before changing themes, plugins or major versions. Test upgrades on a copy first. Keep only maintained extensions and use separate accounts for editors. Do not set world-writable permissions to fix upload errors.
Database connection errors usually require checking the database service, host and credentials. Redirect loops require checking the site URL and reverse-proxy HTTPS configuration. For an existing site, follow a migration plan instead of rerunning setup.
Next: Domain and HTTPS · Backups and restore checks.
Official references
Technical guidance reviewed: 28 October 2026. Match instructions to your actual service and application version.
