Home / Ongoing Work / Hosting & Infrastructure / Subdomain creation & document root mapping

We create a subdomain and map it to the correct document root through your hosting control panel — a common need before installing a separate application, setting up a staging environment, or launching a distinct section of your site under its own address.

HCP-004

Subdomain creation & document root mapping

A subdomain created and correctly mapped to the right folder.

$41.53 delivered in 48 hours
Needs Hosting panel and Sub-account invite. Create a limited sub-account — we never ask for your own password.
  • Full backup taken before we start
  • If we can’t fix it, you get your money back
  • We never ask for your own password
Why this costs $49. An hour of a capable WordPress developer’s time runs about $82 in the UK, $100 in the US and $105 in the Gulf, and for anything urgent a two-hour minimum is normal. This is $49 for up to 45 minutes of hands-on work, with a full backup taken before we start. 2026 market rates.

What we need from you

  • Access to your hosting control panel
  • The exact subdomain name and which folder it should point to
  • Confirmation of what you intend to install or run at this subdomain, for context

This or something else?

You need a subdomain created and mapped to a specific folder This fix covers it
You want a completely separate, addon domain configured, not a subdomain of your existing site Addon & parked domain configuration
The subdomain exists but has a DNS-level issue, not a control panel mapping issue DNS zone record management at host
You want a staging environment specifically, with WordPress-aware setup beyond just the subdomain Staging environment creation & sync, in the Backups, Staging & Migration Ops category

What we do

  1. Confirm the subdomain name and intended document root folder
  2. Create the subdomain through your control panel
  3. Map it to the correct folder
  4. Verify it resolves correctly and serves content from the intended location
  5. Check SSL coverage for the new subdomain, flagging if it needs separate certificate attention
  6. Document the configuration for future reference

What is included

  • A subdomain created and correctly mapped to its intended folder
  • Verified correct resolution and content serving
  • A check on SSL coverage for the new subdomain
  • A written note on the configuration

Not included

  • Installing or configuring whatever application or site lives at the subdomain — a separate, related task
  • SSL certificate installation for the subdomain, if not already covered — a separate, related fix if needed
  • DNS-level configuration beyond what your control panel handles automatically
  • Ongoing management as your subdomain structure changes

Questions about this fix

Will this subdomain be automatically covered by my existing SSL certificate?

Depends on your certificate type — a wildcard certificate would typically cover it automatically, while a standard certificate might need the subdomain added explicitly, which we'd flag and address as part of this fix if needed.

How long does it take for a new subdomain to work correctly?

Once created and mapped through the control panel, it's often immediate, though DNS propagation can occasionally introduce a short delay depending on your specific setup.

Can I have the subdomain point to a completely separate WordPress installation?

Yes, mapping it to its own folder with its own separate installation is a common and straightforward use of this exact setup.

What if I want to remove this subdomain later?

That's a quick, separate task — removing a subdomain and its mapping is generally simpler than creating one.

Does every host's control panel handle this the same way?

The underlying concept is similar, though the specific steps and terminology vary between control panel software — we'd work within whatever your specific host provides.

Subdomain creation & document root mapping
$41.53 · delivered in 48 hours · needs Hosting panel, Sub-account invite

Related fixes

If this is the second time this year

A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.

See care plans

Your access, your rules

Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.

We back up first, always

Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.

If it is not what you bought

If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.

If we cannot fix it

You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.

If it comes back

Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.

What we are responsible for

If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.