Hosting a WordPress site is not magic. WordPress is a PHP application that reads and writes a MySQL database. You need a PHP runtime, a database, HTTPS, and a place to put the files. On WPHost you install that yourself — there is no Softaculous-style one-click installer, and plugins are not auto-updated for you.

This guide is a numbered procedure for a fresh personal blog. If you are migrating an existing site, see how to launch a WordPress website and the migration articles linked at the end.

The checklist before you create anything

Gather these first:

  • A plan with a free site slot (Starter $9/mo = 1 site; Pro $30 = 3; Scale $65 = 10; Business $130 = 30).
  • The WordPress zip from wordpress.org, or a zip you built locally.
  • A password manager for the admin user and database credentials.
  • A domain you actually control — or a willingness to stay on the preview hostname until you buy one.

You do not need cPanel, email mailboxes on the same host, or a CDN. WPHost does not include email hosting or a built-in CDN. Keep mail at Google Workspace, Microsoft 365, or your registrar.

1. Create a PHP site, not a static one

WordPress’s front door is index.php. Create a PHP site in the dashboard so PHP 8.4 can run it. A static HTML slot will serve files as dead text and the installer will never boot.

You immediately get a preview URL with HTTPS. Treat that URL as the place where install and smoke tests happen. Do not point public DNS at an empty or half-configured tree.

2. Upload WordPress so the document root is correct

Upload the zip. The document root must see wp-admin, wp-includes, wp-content, and index.php — not a nested wordpress/ folder that 404s everything useful.

Deploy history stores previous file releases. That is handy if you upload the wrong zip. It is not a full WordPress backup of posts, users, and options. Once content exists, use UpdraftPlus (or similar) for database-inclusive backups.

3. Create MySQL and wire wp-config

Create a database from the site dashboard. Copy name, user, password, and host exactly into wp-config.php (from wp-config-sample.php if this is a fresh download). Paste unique salts from the WordPress secret-key service. Redeploy if you edited the file offline.

Wrong credentials produce “Error establishing a database connection.” Fix the four DB_* defines before blaming the host. WordPress is PHP + MySQL; skipping the database is not a shortcut.

4. Run the installer on preview HTTPS

Open the preview URL. Choose language, site title, and a strong admin password (avoid the username admin if you can). Finish the installer. Confirm the front page and wp-admin load over HTTPS on the preview hostname.

Do not change WordPress Address and Site Address to a custom domain yet. The custom certificate issues after DNS verifies. Changing URLs early is a common way to create redirect loops.

5. Shape the personal blog home page (worked example)

Still on preview, build a minimal home:

  • One sticky post introducing who you are and what you write about.
  • Permalinks set to a pretty structure (save once so rewrites settle).
  • A lean theme — avoid installing ten page builders “just in case.”
  • A contact form that emails an address you already read (SMTP plugin to your real mailbox).
  • UpdraftPlus installed with a first full backup to storage you control.

WPHost does not auto-update core or plugins. Your “done” checklist includes a calendar reminder or a maintainer who clicks Update in wp-admin.

Optional on Pro+: real cron instead of traffic-only wp-cron, and staging for theme experiments. Staging copies files; you still need a database copy if you want real posts on the staging site — see how to set up WordPress hosting.

6. Attach the domain only when preview looks right

When the blog home looks correct:

  1. Add the domain in site settings and create the DNS records shown.
  2. Wait for the custom-domain certificate.
  3. Set WordPress Address and Site Address both to https://your-domain.
  4. Confirm no HTTP→HTTPS loop and that images still load over HTTPS.

Keep MX records pointing at your mail provider. Changing web A/AAAA or CNAME does not require moving email.

What to skip on purpose

Skip Softaculous fantasies — there is no one-click installer here. Skip “unlimited everything” marketing. Skip bundling email, CDN, and SEO retainers into the hosting decision. Skip pointing DNS before the preview install works. Skip treating deploy history as a substitute for UpdraftPlus.

Skip forever-free expectations. Preview and short trials exist; long open-ended free hosting does not.

What “done” looks like

Done means: PHP site live, MySQL connected, installer finished, home page readable on HTTPS, backup plugin has at least one full backup, plugins you installed are ones you will update, and — if you use a custom domain — home/siteurl match the cert’d hostname. WooCommerce can run later if you need a shop; there is no PCI product and no checkout SLA on WPHost.

Failure: skipping a database dump on a WordPress move

People often upload wp-content and call it a migration. The database holds posts, pages, users, options, and most plugin settings. Files without a dump give you an empty shell that looks like WordPress but has none of your writing. Before any host change, export MySQL (phpMyAdmin, mysqldump, or a backup plugin restore package). After files land, import the dump, fix wp-config, then search-replace old URLs carefully. Deploy history will not resurrect missing rows. If the dump never left the old host, the new host cannot invent your posts.

For related paths, see how to launch a WordPress website, how to set up WordPress hosting, and how to host a WordPress website.

FAQ

Does WPHost install WordPress for me with one click?

No. You upload the WordPress zip (or your export), create MySQL, configure wp-config, and run the browser installer on the preview HTTPS URL.

Are plugin and core updates automatic?

No. You update in wp-admin. That is intentional: automatic updates can break themes and plugins without a human watching.

Is deploy history enough backup for a blog?

No. Deploy history restores files from previous deploys. Use UpdraftPlus or similar for database-inclusive backups you can restore after a bad edit or plugin failure.

Can I run a small store on the same hosting?

WooCommerce can run. There is no PCI compliance product and no checkout uptime SLA. For modest catalogs and standard gateways that is often enough; for peak-season commerce SLAs, evaluate specialist hosts before you import thousands of SKUs.