A WordPress blog is still one of the best ways to own your writing on a domain you control. Medium can close a door. Social platforms bury links. Your origin, your wp-content, your export — that is the point.

WPHost is blog hosting in the literal sense: PHP 8.4, MySQL, HTTPS, deploys. You upload WordPress (no one-click installer today), finish the installer, write in wp-admin. We do not run a writing social network. We run the host.

What a blog needs from hosting

  • Permalinks that do not break when you change themes
  • Media library storage for images in posts
  • HTTPS so readers and logins stay encrypted
  • Backups that include the database where posts live
  • Enough PHP performance for theme + a couple of plugins

You do not need cPanel, Softaculous, or a built-in CDN to publish essays. You might want staging later if you test heavy plugins — that starts on Pro.

Starter is sized for one blog

Starter — $9/mo — 1 site — 2 GB. Plenty for text-forward blogs with compressed images. If you paste 5 MB photos straight from a phone, you will meet the storage ceiling — resize or upgrade; see image-heavy and photographers if galleries dominate.

Pro ($30, 3 sites, 10 GB, staging), Scale ($65), Business ($130) exist when you grow properties or teams. Pricing table: pricing.

First-week blog setup (host + CMS)

  1. Create PHP site; upload WordPress zip; provision MySQL — how to host.
  2. Installer on preview HTTPS; strong admin user (not admin).
  3. Settings → Permalinks → “Post name” (or similar); save once.
  4. Backup plugin to off-site storage — deploy history ≠ post backup — SSL and backups.
  5. Lean theme; avoid page-builder bloat unless you truly need it.
  6. Optional SEO plugin — one, not three.
  7. Custom domain last; set siteurl/home to https — custom domain.

Writing stays in WordPress. Hosting does not become a CMS.

Media library habits for bloggers

  • Resize featured images before upload.
  • Prefer JPEG/WebP over huge PNG screenshots when possible.
  • Do not install five image-optimization plugins that fight.
  • Offload media if the library becomes the product.

Performance basics: fast hosting. When traffic grows, read high-traffic blogs — cache helps; mythology does not.

Comments, newsletters, and email

Comments: native comments need spam discipline (or a moderated approach). Third-party comment systems are plugins or embeds — your choice.

Newsletters: do not expect WPHost to send bulk mail. Use a newsletter provider; embed forms. Transactional mail for “new comment” notices needs SMTP configuration; we do not include inboxes.

Updates without drama

We do not auto-update core or plugins. For a personal blog, a monthly hour is enough: backup, update, skim the site. For blogs with many plugins, use staging on Pro+. Security habits: secure hosting.

Blog vs brochure vs portfolio

If you rarely write and only need five pages, WordPress still works — or static HTML might be simpler. If the site is a portfolio with light blogging, see portfolio hosting. If it is a company site with occasional posts, see small business.

WordPress.org vs .com for beginners: beginners.

What we will not pretend a blog host must include

  • Email hosting
  • Built-in CDN
  • One-click installer
  • Automatic plugin updates
  • Nonprofit coupons
  • Long free trials (ours is ~1 day)
  • Concierge editorial support

Managed infrastructure yes; managed writing career no — what is managed.

Monetization footnotes

Ads, affiliates, and membership paywalls can run as plugins. Membership caches are tricky — membership. Small digital product shops via Woo are possible with the usual honesty limits — Woo. Hosting plans do not include tax advice.

A sustainable publishing rhythm

Hosting is ready long before your editorial calendar is. Publish imperfect posts. Fix themes later. Keep backups. When you outgrow one blog into a network of sites, count them against Pro/Scale/Business instead of stacking weird subdirectory schemes on Starter.

Migrating an existing blog off shared hosting: migrate. Keeping the domain at the registrar: transfer.

Editorial workflow on a small team

Authors should not all be administrators. Use the Editor/Author roles. Enable 2FA for anyone who can publish. If freelancers draft posts, give them Author and a deadline — not your hosting dashboard login. Business teams matter when multiple people need WPHost access; WordPress roles still govern editorial — agencies.

Revisions bloat databases over years. That is normal. Occasional database care plus backups matter more than buying a larger plan for “performance” when the real issue is autoloaded options from abandoned plugins — fast.

Feeds, newsletters, and canonical URLs

WordPress still exposes feeds. Fine for subscribers; watch for scrapers. Newsletters should pull from canonical https URLs after domain attach — custom domain. Duplicate http/https content is a self-own at launch — how to launch.

From blog to micro-business

Many blogs add tips jars, digital downloads, or memberships later. That is OK. Re-read membership and Woo before flipping switches so cache settings evolve with the business model. Hosting plans stay capacity plans; your monetization plugins are application choices.

Scheduling posts the grown-up way

WordPress scheduled posts depend on cron. On a quiet personal blog, a post may publish late until someone visits. Pro+ real cron removes that quirk — managed. If you stay on Starter, visit the site after the scheduled time or accept occasional delays.

Draft sharing with clients via preview links is fine; do not open staging to the world without noindex. When a post goes viral, re-read high-traffic before installing five new “share count” plugins that hammer APIs on every page view.

Editorial workflow on an honest host

Writers need wp-admin, not SSH. WPHost gives them PHP 8.4, MySQL, and HTTPS. You still install WordPress from a zip — no Softaculous — and you still click Update for core and plugins. That is not “unmanaged neglect”; it is refusing to surprise you with breaking auto-updates mid-newsletter.

Use drafts and scheduled posts in WordPress itself. For theme experiments, Pro staging with a DB copy beats editing the live blog during a traffic spike. Deploy history helps if a bad functions.php deploy blank-screens the site; restore the database from your backup plugin if editorial content vanished.

Comments, spam, and mail

Comment spam is application noise. Use moderation, Akismet-class tools, or turn comments off. Contact forms and author notifications need SMTP — we do not host inboxes. DNS for the blog domain should leave MX alone when you point A/CNAME records at WPHost — custom domain.

Starter ($9) fits a single modest blog; Pro ($30) when you want staging and cron. No built-in CDN; optimize images before chasing edge lore — image-heavy.

Imports from other writers’ tools

Leaving Substack, Ghost, or Medium usually means export → import → fix media → fix URLs. Budget time for broken images. Hosting is the easy part; content sanitation is the work — migrate. Keep the custom domain moving carefully so subscribers’ bookmarks survive — transfer.

FAQ

Is WordPress overkill for a blog?

Sometimes. If you love writing in wp-admin and want plugins, no. If you want a single markdown page, static may be less ceremony.

Can I host multiple blogs?

Yes — one site slot per blog on your plan (1 / 3 / 10 / 30). Multisite networks are advanced and not a special WPHost product mode.

Do you provide a CDN for images in posts?

No built-in CDN. Optimize images; add Cloudflare yourself if needed.

Will you migrate my Medium export?

You move files/DB (or use import tools). We provide the PHP/MySQL home. Path: migrate guide.

Does Starter include staging for theme experiments?

Staging starts on Pro. On Starter, experiment carefully or locally, and keep backups.