Column 1
Skip to content
Column 1

How to Install WordPress Manually with SFTP and phpMyAdmin

How to Install WordPress Manually with SFTP and phpMyAdmin installation tutorial showing setup, verification, SSL, backups, and first-hour checks

SFTP plus phpMyAdmin or a database panel is a good WordPress installation path when it matches the host and future maintenance plan. This method is best for portable WordPress installs on hosting accounts where direct file and database access are available.

Audience: developers, support teams, and site owners working on hosts without a WordPress installer. Before installing, decide who owns the site, where backups live, how updates happen, and what will happen if the first plugin or theme choice breaks the site.

Before install

  • Use SFTP, not plain FTP, when possible.
  • Download WordPress from the official source.
  • Create a database and database user.
  • Know the document root for the domain.

Install steps

  1. Upload the WordPress files to the document root over SFTP.
  2. Create the database and user in the hosting panel.
  3. Visit the domain and follow the WordPress installation screen.
  4. Enter database details and administrator details.
  5. Set permalinks, timezone, and site visibility.
  6. Remove leftover install archives and confirm backups.

Post-install verification

Check SSL, wp-admin, media uploads, file permissions, email sending, plugin installation, and the first backup.

Also confirm public pages return 200, the dashboard loads over HTTPS, the administrator email can receive password resets, updates are visible, and a backup exists before you start building heavily.

Install risks

  • Plain FTP exposes credentials on unsafe networks.
  • Wrong document root can put the site in the wrong place.
  • Manual installs need their own update and backup routine.

Backup and rollback planning

A new WordPress site still needs a rollback plan. Create the first backup before installing large themes, builders, ecommerce extensions, membership tools, LMS plugins, or custom code. If this install is for a customer, document the host, login ownership, backup location, update policy, and launch checklist.

Fix I.T. Phill recommendation

Use SFTP plus phpMyAdmin or a database panel when it gives you the cleanest path to updates, backups, SSL, and support. Keep the install lean, verify it publicly, and connect it to the backup, restore, and migration guides before the site becomes important.

Related Fix I.T. Phill Guides

Sources Checked

2026 SEO Refresh: Manual WordPress Install with SFTP and phpMyAdmin Checklist

Admin action path: SFTP and phpMyAdmin installs need careful evidence around file ownership, database credentials, wp-config, SSL, and install cleanup.

What to verify before changing production

  • Create database and file backups before replacing an existing site.
  • Check file ownership, wp-config credentials, salts, SSL, and install cleanup.
  • Verify wp-admin, public pages, REST, sitemap, forms, and email after install.

Source-backed references and next reads

Ticket evidence should include the method used, backup timestamp, destination URL, DNS or SSL state, mail-delivery result where relevant, and the public verification steps completed after the change.