WordPress is not a mysterious appliance. It is a folder of PHP files, a MySQL database, and a browser-based installer. Hosting it well means giving those three things a working home — not selling you a “one-click WordPress experience” that hides what actually happened.

On WPHost there is no Softaculous-style one-click installer today. You download WordPress (or export an existing site), upload a zip, provision MySQL if you need it, finish the famous five-minute install yourself, and attach a custom domain when DNS is ready. That order matters. Domain last. Preview HTTPS first.

This walkthrough is the first-install path for a fresh site. If you are moving an existing blog, use how to migrate WordPress to new hosting instead.

What you need before you start

  • A WPHost account and a plan with a free site slot (Starter is one site; Pro is three; Scale is ten; Business is thirty).
  • A zip of WordPress core from wordpress.org, or a zip you already built locally.
  • About twenty minutes and a password manager — you will create an admin user and store database credentials.

You do not need cPanel, SSH fluency, or an email mailbox on the same host. WPHost does not include email hosting. Keep mail at your registrar or a mail provider; point MX there and leave web DNS for the site.

Step 1: Create a PHP site

WordPress needs PHP. Create a PHP site in the dashboard — not a static HTML site. WPHost runs PHP 8.4, which is what current WordPress expects. A static slot will not execute index.php.

You get a preview URL with HTTPS immediately. Use that URL for install and smoke tests. Do not point your public domain at the site until the installer has finished and you have verified wp-admin loads.

Step 2: Upload the WordPress zip

Upload the zip of WordPress files. The deploy should land so that the document root sees wp-admin, wp-includes, wp-content, and index.php — not a nested wordpress/ folder that 404s. If you zip the outer directory by mistake, re-zip the contents or adjust and redeploy.

There is no marketplace of “approved” themes at this stage. You are putting files on a PHP host. Themes and plugins come later through wp-admin or additional deploys.

Deploy history keeps previous file releases. That is useful if you upload the wrong zip. It is not a scheduled full-site WordPress backup of posts and options. Plan on UpdraftPlus or similar once content exists.

Step 3: Provision MySQL

WordPress stores posts, users, and options in MySQL. Create a database from the site dashboard. Copy the database name, user, password, and host exactly. You will paste them into wp-config.php (or map them through environment variables if you prefer that pattern — covered in how to set up WordPress hosting).

Do not skip this and hope SQLite plugins will “just work” for a normal install. The standard installer path is MySQL.

Step 4: Configure wp-config before the browser installer

If the zip is a fresh WordPress download, you may only have wp-config-sample.php. Copy it to wp-config.php and set:

define( 'DB_NAME', 'your_database_name' );
define( 'DB_USER', 'your_database_user' );
define( 'DB_PASSWORD', 'your_database_password' );
define( 'DB_HOST', 'your_database_host' );
define( 'DB_CHARSET', 'utf8mb4' );
define( 'DB_COLLATE', '' );

Generate unique salts from the WordPress secret-key service and paste them over the placeholder AUTH_KEY / SECURE_AUTH_KEY block. Choose a non-default $table_prefix if you like (wp_ works; something less guessable is fine too).

Redeploy the updated wp-config.php if you edited it outside the live tree. Wrong credentials here produce the classic “Error establishing a database connection” — fix the four defines before blaming the host.

Step 5: Run the installer on the preview HTTPS URL

Open the preview URL. You should see the language picker and then the site title / admin user form. Create a strong admin password. Do not use admin as the username if you can avoid it.

Complete the install. Log into wp-admin. Confirm the front page renders over HTTPS on the preview hostname. Mixed content and redirect loops usually appear later when people attach a custom domain without updating WordPress Address and Site Address — we will do domain work last on purpose.

Step 6: Basics inside WordPress (still on preview)

Before DNS:

  • Settings → Permalinks: pick a pretty structure and save once so rewrite rules settle.
  • Delete sample comments you do not want public.
  • Install only the theme and plugins you actually need. Fewer plugins means fewer update chores — and WPHost does not auto-update core or plugins. You update in wp-admin.
  • Install a backup plugin and run a first full backup (files + database) to storage you control.

Optional on Pro and above: enable a real cron schedule instead of relying only on traffic-driven wp-cron, and use staging before you experiment with cache plugins.

Step 7: Custom domain last

When the site looks right on preview:

  1. Add the domain in site settings and create the DNS records the dashboard shows.
  2. Wait until the custom-domain certificate issues. Preview HTTPS was already there; the custom cert follows DNS.
  3. In wp-admin → Settings → General, set WordPress Address (URL) and Site Address (URL) to https://your-domain (both, consistently).
  4. Save. Visit the custom domain and confirm no HTTP→HTTPS redirect loop.

If you change those URLs incorrectly, wp-admin can bounce forever. Fix via database siteurl / home options or a careful search-replace — details in WordPress hosting with a custom domain.

Keep MX records for email at your mail host. Changing the web A/AAAA or CNAME does not require moving mail.

What this host is not doing for you

  • No one-click WordPress installer.
  • No automatic plugin or core updates.
  • No cPanel, no bundled inbox, no built-in CDN product.
  • No nonprofit coupon; trial is short (~1 day) then paid.
  • Deploy rollback restores files, not a magical database time machine.

If you want a concierge that patches WooCommerce for you every Tuesday, pick a specialist managed WordPress shop. If you want PHP 8.4, MySQL, TLS, deploys, logs, and optional staging — and you are willing to own the CMS — this path is the honest one.

Aftercare in the first week

Update WordPress core and plugins when updates appear. Turn on two-factor authentication with a plugin you trust. Confirm backups restore somewhere that is not only the production origin. Skim secure WordPress hosting once before you install “security suite” kitchen-sink plugins.

For a launch-oriented checklist (permalinks, HTTPS on the real name, first backup, going public), see how to launch a WordPress website. For pricing sized to one site versus many, see WordPress hosting pricing.

FAQ

Do I need to know PHP to host WordPress here?

No. You need to upload files, paste database credentials, and use wp-admin. PHP 8.4 runs under the hood. You are not writing application code unless you want to.

Can I install WordPress with one click?

Not on WPHost today. Upload a zip of WordPress (or an existing export), provision MySQL, finish the browser installer. The upside is fewer opaque steps and a host that matches how WordPress actually works.

Should I connect my domain before the installer?

Usually no. Finish install on the preview HTTPS URL, then attach DNS and update WordPress Address / Site Address. Domain-first installs are a common source of redirect loops.

Does deploy history back up my posts?

No. Deploy history restores previous files. Posts and options live in MySQL. Use a WordPress backup plugin (or your own dumps) for the database.

Which plan do I need for one new site?

Starter at $9/month covers one site and 2 GB. Add Pro ($30) when you want staging, more sites, or more disk. See WordPress hosting pricing for Scale and Business.