Walkthrough · Beginner · 5 minutes
How to Create a Subdomain
Put blog.yourdomain or app.yourdomain live in less time than it takes to make coffee — a hands-on walkthrough in plain words that names the classic mistake before you reach it.
The short answer
One line covers it: put blog.yourdomain or app.yourdomain live in less time than it takes to make coffee — a beginner-level job of roughly 5 minutes.
Below are the precise steps, the classic stumble, and one tip from the support desk. Wherever the platform already does a step for you, the guide says so rather than handing you a machine's chores.
By the Hosting & Domains team · Reviewed 18 August 2026
Beginner
Experience required
4
Stages, start to finish
Free
Support included
Proven
On the platform itself
No prior knowledge assumed — a hosting account, a browser and 5 minutes of attention is the whole entry requirement. Every instruction runs on our platform exactly as printed, and carries over to any standard cPanel host.
A promise before step one: nothing here is a one-way door. Any step with teeth is flagged, and the way back is printed beside it.
The route, mapped end to end
The work falls into a few clean stages: create it in cpanel, choose the document root carefully, wait a moment, then check ssl and put something on it.
No part of this needs code or a terminal unless the guide says so plainly — and where it does, the exact commands are printed. The step-by-step is below, with the surrounding sections supplying the context that makes it hold.
The error nearly everyone hits
Expecting the main site's certificate to cover the new hostname immediately. Every name needs its own, which is automatic on this platform but not instant. Give issuance a few minutes before calling it broken.
Forewarned is genuinely forearmed here. This one mistake accounts for most of the frustration the topic ever causes — and it disappears entirely once somebody points it out.
A habit worth borrowing
Subdomains cost nothing and are isolated from one another, so run dev.yourdomain as the place to break things that must not break in production. Remove it when the experiment is over.
A minute spent now repays itself every time this job comes round again — and like almost every hosting job, come round it will.
The steps already done before you arrive
Steps that never deserved your time are taken out: certificates issue and reissue themselves, the installer handles application setup, the daily copy absorbs the what-ifs, and per-site settings live in a panel rather than a configuration file. The guide covers the remainder — the part that is actually about your site.
Should a step still misfire, support answers at any hour with an actual fix rather than a knowledge-base link and a shrug. Half the guides on this site began as repeat patterns in our ticket queue.
The hosting these steps were tested on
Tutorials written against imaginary hosting go stale fast. Ours are written against the real thing: the same panel, installer and defaults waiting in your account.
Support means a person at any hour, and the remit covers the awkward practical questions other hosts hand straight back.
- Every step checked exactly as published
- The snag named before it arrives
- The dull steps taken out of your way
- People reachable at any hour you stall
Why Hosting & Domains
Standard on every plan
Taken from real tickets
These guides came out of the support queue, so every snag flagged is one people genuinely hit.
Help that keeps your hours, not ours
Stuck on step three at midnight? Support answers at any hour, mid-walkthrough included.
Jargon never charges you
Every term is defined on the spot or linked to the jargon buster — nothing assumes prior knowledge.
Works exactly as printed
Every step is proven on the platform we run — none of the 'your host may vary' hedging.
The dull parts automated
SSL, backups and installs look after themselves here, leaving the guide to cover only what is genuinely yours.
The snag, flagged up front
The classic error for this particular task is named before step one, which is how 5 minutes stays 5 minutes.
Quick Start
Order placed to site online
- 1
Create it in cPanel
Go to Domains, then Create a New Domain, which older panels label Subdomains. Enter the prefix and cPanel writes the DNS record and builds the serving folder in one action.
- 2
Choose the document root carefully
A document root of its own comes with each subdomain. Keep them together under something like /subdomains/journal rather than nesting them inside the main site's tree, and later maintenance becomes far less painful.
- 3
Wait a moment, then check SSL
With the zone hosted here the new record answers almost at once, and the subdomain's free certificate follows by itself. Load it over https before deciding anything has gone wrong.
- 4
Put something on it
Treat the subdomain as a new site: install WordPress into it in one click, or upload whatever application it exists to serve. The main site carries on untouched.
Built In
Fitted to every plan
- Free SSL on every plan, reissued before the old one lapses
- WordPress Toolkit, with the updates seen to for you
- LiteSpeed caching in the server itself rather than bolted on by plugin
- cPanel, which is what most of the industry already runs
- DDoS filtering absorbed at the network edge
- A renewal figure identical to the one you registered at
- No set-up charge at any point, and no joining fee
- Spam and virus screening on every mailbox by default
- WordPress and 400+ further applications installed in one click
- The name's first year included when you order annually
Frequently Asked
The questions that come up most
Subdomain or subdirectory?
A subdirectory such as /journal inherits the main name's search authority and suits sections of content. A subdomain suits a genuinely separate application — app., portal., dev. — where the separation is worth more than the pooled authority.
Is there a charge or a limit on subdomains?
Neither, on our plans. Whatever files they hold come out of the same storage as the rest of the account, but nothing is billed per subdomain and no cap will realistically get in your way.
Can I transfer in a name I already own?
Yes, and it is routine. Unlock the name at your current registrar, take the auth code, and start the transfer from your client area. Whatever registration time remains carries over, and DNS keeps resolving the whole way through.
What is the refund position if I change my mind?
Shared, business, WordPress and WooCommerce hosting get thirty days, and reseller gets seven. VPS and dedicated servers are built to order the moment payment lands, so they sit outside the guarantee — as do domain registrations, where the registry charges the instant the name is secured. Inside the window one request returns the hosting fee, with no retention script to sit through.
Keep reading
How to Migrate a WordPress Site
Shift a WordPress site onto a new host without a single visitor noticing a gap — intermediate level, about 1–2 hours, or one free ticket to us.
How to Check DNS Propagation
Find out whether the internet has taken up your DNS change, and why some corners have not — beginner level, about 5 minutes.
Subdomain (Glossary)
The plain-English definition this page rests on, with a worked example.
Website Builder
Drag, drop, publish — a no-code builder on genuinely quick hosting.
Domain Names
Find, register and transfer names — year one free with annual hosting.
Changing hosts? Run through our checklist first.
A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.
Put the site on ground you own.
Every plan carries the essentials other hosts bill as extras — and support that answers.
View Website Builder plans