How-to · Beginner · 5 minutes

How to Create a Subdomain

Everything you need to stand up blog.yourdomain or app.yourdomain before the kettle boils — the steps in order, the snag to watch, and the tip our support desk gives everybody.

See the plans Ask us a question

Straight answer first

In a line: stand up blog.yourdomain or app.yourdomain before the kettle boils — a beginner-level task that takes 5 minutes.

Below you get the exact steps, the classic snag, and a tip from the support desk. Where our platform handles a step for you, the guide says so rather than making you do the robot's work.

Written by the Hosting Seller staff · Checked 1 August 2026

Beginner

Difficulty level

5 minutes

Time to allow

Stages

24/7

Help at any hour

This guide assumes no expertise at all — just a hosting account, a browser and 5 minutes of attention. Every instruction works on our platform exactly as written, and carries over to any standard cPanel host.

One promise before you start: nothing in this guide is irreversible. Where a step could bite, we say so and give you the undo.

The route, start to finish

The job breaks into a few clear stages: make it inside cpanel, choose its folder on the disk deliberately, give it a minute, then check ssl and put some actual content on it.

No stage needs code or a terminal unless the guide says so outright, and where it does, the exact commands are printed. The full step-by-step sits below; the sections around it give the context that makes it stick.

The mistake nearly everyone makes

Expecting the main site's certificate to cover the new name the instant it exists. Every hostname needs its own coverage. It is automatic here, but not instant — give issuance a few minutes before you decide it is broken.

Forewarned really is forearmed here. This one mistake accounts for most of the frustration the subject produces, and it is entirely avoidable once somebody names it.

The trick worth borrowing

Subdomains cost nothing and stay walled off from each other, so use dev.yourdomain as a sandbox for the experiments you would never risk on the live site. Delete it when the experiment is over.

It costs a minute now and pays that back every time the job comes round again — which, like most hosting jobs, it certainly will.

The parts we have already done for you

We have automated the steps that do not deserve your time: certificates issue and reissue themselves, the installer handles application setup, the daily backup covers the what-if, and per-site settings live in a panel instead of a config file. The guide above covers what remains — the part that is actually about your site.

And when a step misbehaves anyway, support answers at any hour with the actual fix, not a knowledge-base link and a shrug. Half our best guides began life as a pattern in the ticket queue.

A long aisle of servers inside a global data centre network

A good platform makes every guide shorter

Tutorials age badly when they are written against imaginary hosting. These are written against ours: the same panel, the same installer and the same defaults you will meet.

SSL comes free with every plan and reissues itself before it lapses, so nobody has to diary the padlock.

Step by step, tested exactly as printed
The snag flagged before you reach it
The dull steps are already automated
People on hand at any hour if you stall

Why Hosting Seller

On every plan, as standard

Written from real tickets

Our guides come off the support desk, so the snags flagged here are the ones people genuinely hit.

Help on the counter

Stuck on step three at midnight? Support answers at any hour, mid-guide included.

No jargon toll

Terms are explained where they appear or linked to the glossary — nothing assumes you already know.

Works exactly as written

Every step tested on the platform we run — no 'your host may differ' hand-waving anywhere.

Automation where it belongs

SSL, backups and installs run themselves here, so the guide covers only what is genuinely yours to do.

The snag, named early

The classic mistake for this exact job is flagged before step one, so 5 minutes stays 5 minutes.

First Steps

From choosing to live

1
Make it inside cPanel
Go to Domains, then Create a New Domain (older panels call it Subdomains). Type the prefix you want and cPanel writes the DNS record and creates the folder it will serve from in one move.
2
Choose its folder on the disk deliberately
Each subdomain gets a document root of its own. Keep them side by side in something like /subdomains/blog rather than buried inside the main site's files, and future-you will thank present-you.
3
Give it a minute, then check SSL
On a zone hosted here the new record answers almost immediately, and the free certificate for the subdomain issues by itself once it does. Reload with https before deciding anything is wrong.
4
Put some actual content on it
Treat the subdomain as a brand new site: one-click WordPress into it, or upload the application it exists to run. Nothing else about the main site changes.

In the Box

Packed with every plan

cPanel, the panel the rest of the trade already knows
Nothing added at setup — no joining fee, ever
A domain free for year one when you order annually
DDoS filtering handled out at the network edge
Webmail in the browser plus IMAP, POP and SMTP for your own client
Mailboxes that carry your own domain name
One-click installs for WordPress and 400+ other applications
The Softaculous installer for one-click application setup
LiteSpeed caching running at the server, not bolted on by plugin
Site migration done for you by our staff, at no charge

Across the Counter

The questions we get asked most

Is a subdomain or a subdirectory the better choice here?

A subdirectory like /blog shares the main domain's standing with search engines and suits content sections. A subdomain suits a genuinely separate application — app., portal., dev. — where keeping things apart matters more than pooling authority.

Do subdomains carry an extra charge or hit any cap?

They are free and effectively uncapped on our plans. The files inside them use the same storage as anything else, but there is no per-subdomain charge and no number you are likely to bump into.

Can I bring a domain I already own?

Yes, and transfers in are routine. Unlock the name at your present registrar, collect the auth code, then start the transfer from your client area. Whatever registration time is left comes across with it, and DNS keeps answering the whole way through.

Is there a refund if it does not suit?

Yes — thirty days. Put the hosting through real work, and if it is not right, ask for the money back and you get it; there is no retention script to survive first. Domain registrations are the one carve-out, because registries take that fee the moment the name is placed.

Are backups included, and can I put one back myself?

A backup is taken daily on every plan, and the restore is yours to run from the panel in minutes — files, databases or both, at three in the morning without waiting on a ticket. Keeping your own copy offsite as well is never a bad habit, and nothing here stops you.

What uptime do you commit to, and who is watching?

We commit to 99.9% uptime and watch it continuously. That figure is an operational target rather than a poster line, and the alerting behind it usually has an engineer on a problem before the first customer notices anything is wrong.

Does hosting come with mailboxes?

It does — mailboxes on your own domain ship with every hosting plan, with webmail, IMAP, POP and SMTP access and spam filtering fitted as standard. There is also standalone email hosting for domains whose website lives somewhere else entirely.

Packing up and moving host? Take our checklist.

A plain running order for a move nobody notices: what to copy first, how to carry email across without dropping a single message, when to point DNS, and the two slips behind nearly every hour of downtime we get called about.

Start on a plan with a plain price tag.

From a first website to a rack of servers, moving up is a change to your account rather than a migration.

See the plans