How to Set Up a Custom Branded Domain for Your Short Links

Rick Sarkar

author

11 min read

|

Updated November 8, 2026

A step-by-step guide to setting up a custom branded domain for your short links, covering domain choice, DNS records, SSL, and the mistakes that break setup.

Every time you share a generic short link, you are advertising someone else's brand.

shortener.com/3xK9pQ tells a recipient nothing about who sent it, whether it is safe, or where it leads. In an era where most people have been trained to distrust unfamiliar links, that ambiguity costs you clicks.

go.yourbrand.com/offer answers all three questions before anyone clicks.

The gap between those two links is one DNS record and about fifteen minutes of work. This guide walks through the entire process - choosing the right domain, adding the record, getting SSL working, and fixing the handful of things that commonly go wrong.

What Is a Custom Branded Domain?

A custom branded domain replaces a generic shortener's domain with one you own.

Generic:   shortener.com/xK3p
Branded:   go.yourbrand.com/summer-offer

Everything else is identical. The redirect works the same way, the analytics are the same, and management is unchanged. Only the domain differs - and that is the part your audience actually reads.

Mechanically, the setup is simple. You point a domain you control at the infrastructure that serves your short links using a DNS record. Requests to your domain get routed there, the alias is looked up, the click is logged, and the redirect is issued. The visitor sees only your domain.

The walkthrough below uses SkyShare, our own link platform, which supports custom branded domains on every plan. The DNS work is identical wherever your links are hosted - only the screen you copy the record from changes.

We covered why this matters for trust and click-through in what is a branded link. This guide is about how.

Subdomain or Dedicated Short Domain?

This is the first decision that has real consequences, because changing it later means every link you have already published stops working. Both options are legitimate and they suit fairly different situations, so it is worth spending five minutes on rather than picking the one you happened to read about first.

Option A - a subdomain of your existing domain

go.yourbrand.com/offer
links.yourbrand.com/offer

This is the recommended default. It inherits recognition from your main domain, costs nothing extra, and carries no risk to your website when configured on a subdomain.

Common subdomain choices are go, links, link, hub, and try. Pick one and stay consistent - the value of a branded domain compounds with repetition.

Option B - a dedicated short domain

yrbrnd.link/offer
skyh.in/offer

A dedicated domain is shorter, which matters more than people expect. In SMS you are counting characters against a hard limit. On packaging or a billboard, every character is one more thing someone has to read and type correctly.

The .link TLD is popular for this because short combinations are still available and the meaning is self-evident. Country TLDs like .in work well too, and often give you a shorter result.

Practical advice: start with a subdomain. It costs nothing and takes fifteen minutes. Register a dedicated short domain later, once you know link sharing is a real part of your workflow and character count is a genuine constraint.

Choosing the Right Domain

A few things worth getting right, because changing this later means every printed link breaks.

• Short beats clever. The entire point is brevity. go.yourbrand.com is fine; short-links.yourbrand.com defeats the purpose.
• Typeable out loud. Someone should be able to read it from a flyer, a slide, or over the phone and type it correctly. Avoid hyphens and ambiguous spellings.
• Never reuse an active hostname. If links.yourbrand.com already serves something, pointing it at your link platform will break whatever is there.
• Avoid free or throwaway TLDs. Some TLDs carry a poor reputation from spam abuse, and links on them get filtered by email providers and messaging apps. That defeats the trust benefit entirely.
• Keep it on a domain you plan to keep. Short links live in printed material and old emails for years. Losing the domain means every link ever shared dies at once.

Step 1: Add the Domain in SkyShare

Start on the platform side, not in DNS. You need the target value before you can create the record.

In SkyShare, open your domain settings and add the domain you intend to use - go.yourbrand.com, for example.

SkyShare will then show you a DNS record to create. Typically that means:

• A record type (usually CNAME, sometimes A)
• A name or host (the subdomain part - go)
• A value or target (SkyShare's hostname or IP address)

Copy the value directly rather than typing it. A single mistyped character produces a failure that is genuinely hard to spot later.

The domain will show as pending or unverified until DNS is in place. That is expected.

Step 2: Add the DNS Record

Now go to wherever your domain's DNS is managed. That is usually your registrar, or Cloudflare if you have delegated nameservers there.

For a subdomain, you are creating a single CNAME:

Type:   CNAME
Name:   go
Value:   the hostname SkyShare gave you
TTL:   3600 (or Auto)

The Name field is the subdomain only - go, not go.yourbrand.com. Most DNS interfaces append the domain automatically, and entering the full hostname produces go.yourbrand.com.yourbrand.com, which fails silently.

Provider-specific notes

Cloudflare. After creating the record, set Proxy status to "DNS only" - the grey cloud, not the orange one. This is the single most common setup failure. The orange-cloud proxy intercepts traffic before it reaches SkyShare, which prevents certificate issuance and breaks the redirect.

Also check SSL/TLS → Overview and make sure the encryption mode is Full (strict). If it is set to Flexible, Cloudflare talks to SkyShare over plain HTTP, and modern browsers will flag or block the result. Some apps refuse to preview such links entirely.

Route 53. Create the record under your hosted zone. For a subdomain, a regular CNAME is correct. For an apex domain, enable Alias instead.

GoDaddy, Namecheap, and similar registrars. Look for the DNS or Records section. CNAME records on subdomains work normally. Apex domains are a different matter - see below.

Delete conflicting records first. If an A or AAAA record already exists on the same hostname, it will take precedence over your new CNAME and the setup will fail with no obvious error. Remove old records before adding the new one.

Step 3: Wait for Propagation and SSL

DNS changes take time to spread. In practice:

• Cloudflare: usually under five minutes
• Most modern providers: five to thirty minutes
• Older registrars: occasionally a few hours

Once SkyShare detects the record, it requests an SSL certificate for your domain - typically from Let's Encrypt, and typically automatically. This is what makes your links work over https://.

You can check propagation yourself:

dig go.yourbrand.com CNAME +short

Or on Windows:

nslookup -type=CNAME go.yourbrand.com

If the value returned matches what SkyShare gave you, DNS is done and the rest is just waiting for verification and certificate issuance.

Step 4: Test Before You Ship

Do not put a new branded domain on a printed flyer until you have confirmed all four of these.

• Create a test link on the new domain pointing anywhere.
• Open it in a private window. Regular windows may serve cached DNS or a cached redirect, hiding real problems.
• Confirm HTTPS works with no warning. The padlock should appear cleanly. A certificate warning will destroy trust faster than a generic short link ever would.
• Paste the link into WhatsApp, Slack, or an email client. Preview generation is a good end-to-end check, and it is where a Flexible SSL misconfiguration usually reveals itself.

Only after all four pass should the domain go anywhere permanent.

The Apex Domain Problem

An apex domain (also called root or naked domain) is the domain without a subdomain - yourbrand.com rather than go.yourbrand.com.

Two quite different problems get bundled together under "apex domains do not work", and separating them is what makes the answer clear - one is a technical limitation with workarounds, the other is a decision you should not make regardless of whether it is technically possible.

First: DNS does not formally allow a CNAME at the apex. The apex must carry other records - MX for email, NS for nameservers - and a CNAME cannot coexist with them. Providers work around this with ALIAS, ANAME, or CNAME flattening. Cloudflare flattens automatically, Route 53 calls it ALIAS, and several registrars support it under one of those names. Some, including GoDaddy's default DNS, do not - in which case the cleanest fix is moving nameservers to a provider that does.

Second, and more important: do not point your main website's apex at your link platform. If yourbrand.com serves your website, redirecting the apex will take your site down. This mistake is easy to make and immediately visible to everyone.

Apex configuration is appropriate in exactly one situation: a dedicated short domain registered specifically for links, with no website on it. In that case yrbrnd.link/offer is the shortest possible branded link, and using the apex is the right call.

For any domain that hosts your actual website, use a subdomain.

Troubleshooting Common Failures

Domain stuck on "pending" or "unverified"

DNS has not propagated, or the record is wrong. Run dig to see what is actually resolving. Check for a doubled hostname (go.yourbrand.com.yourbrand.com) caused by entering the full name in the Name field.

Certificate error, or "Not Secure" in the address bar

Usually SSL has not finished provisioning - give it a few more minutes. If it persists on Cloudflare, check that the proxy is off (grey cloud) and encryption mode is Full (strict).

Links work but previews are broken in Slack or WhatsApp

Almost always Cloudflare SSL set to Flexible. Switch to Full (strict).

The old site loads instead of the redirect

A stale A or AAAA record on the same hostname is taking precedence. Delete it.

Works for you, broken for colleagues

DNS caching on your machine. Test in a private window or from mobile data rather than office Wi-Fi.

Everything looks right but nothing resolves

Confirm you edited DNS at the provider that actually controls the domain. If nameservers are delegated to Cloudflare, changes at your registrar have no effect - a genuinely common source of wasted time.

After Setup: Getting Value From It

Getting the domain resolving is the infrastructure half, and it is the half that has a definite finish line. What you do with it afterwards is where the actual benefit comes from, and there is no finish line there - just a handful of habits that either take hold or do not.

• Use it everywhere. Recognition compounds through repetition. Mixed generic and branded links waste the effect.
• Write readable aliases. go.yourbrand.com/diwali beats go.yourbrand.com/a8Kd2. Readable aliases are the entire reason for doing this.
• Keep tracking parameters on the destination, not the short link. Your UTM parameters belong on the destination URL. The short link stays clean and the analytics still receive everything.
• Serve links as temporary redirects. So destinations stay editable and every click gets logged - the reasoning is covered in 301 vs 302 redirects.
• Document the setup. Note which domain, which DNS provider, and where the record lives. The person who needs this in two years may not be you.

Setting up a branded domain on SkyShare

SkyShare supports custom branded domains, and the DNS side is the same work described above - you add the record at your registrar and point it at the platform. What you get on top is the part that makes the domain worth having: aliases you choose rather than accept, per-link click data down to city, device and referrer with crawler hits filtered out, destinations that stay editable after the link is printed, and QR codes generated on your own domain rather than someone else's.

What the First Week Actually Looks Like

The DNS record takes two minutes to add. The confusing part is the hours afterwards, when the domain works from one machine and not another and it is not obvious whether something is broken or simply not finished yet. Here is roughly how it goes.

The first few minutes. Nothing works, and that is expected. Your resolver has not seen the new record and may be holding a cached negative answer. Checking every thirty seconds from the same laptop tells you nothing useful, because that machine is the least likely place to see the change first.

The first hour or two. The record starts resolving somewhere, usually not everywhere. Mobile data often picks it up before office wifi does, because they use different resolvers with different caches. This is the point where people assume the setup failed and start changing records, which resets the clock. Do not. If the record is correct at the registrar, waiting is the fix.

Once DNS resolves, HTTPS follows. Certificate issuance cannot start until the domain points at the platform, so the certificate lags the DNS by minutes to a few hours. A browser warning during this window is normal and clears itself. A browser warning three days later is not - that means the certificate never issued and the domain needs looking at.

The end of the first day. Create one real link on the new domain and open it in a private window on a phone, on mobile data rather than wifi. That single test covers resolution, HTTPS and the redirect in one go. Then paste it into whatever chat app your team uses and check the preview card renders, because link previews are fetched by the platform's own crawler and are the last thing to come right.

After that, nothing. A branded domain has no ongoing maintenance beyond keeping the registration renewed - which is worth an automatic renewal and a calendar reminder, because an expired short domain breaks every link you have ever published on it at once.

If you only remember three things from this article, make them these: start with a subdomain rather than an apex, never point your live website's root record at a link platform, and test in a private window before you put the domain on anything printed.

If your domain is ready and you want to point it somewhere:

Connect your domain to SkyShare

Frequently Asked Questions

What is a custom domain for a URL shortener?

A custom domain replaces a generic shortener's domain with one you own, turning a link like shortener.com/xK3p into go.yourbrand.com/summer-offer. The redirect behaviour and analytics are identical - only the domain changes, which is the part recipients actually read before deciding whether to click. SkyShare supports custom branded domains on every plan.

Do I need to buy a new domain for branded short links?

No. The simplest approach uses a subdomain of a domain you already own, such as go.yourbrand.com, which costs nothing and takes about fifteen minutes to configure. A dedicated short domain is worth buying later if you run SMS or print campaigns where every character counts.

Can I use my main domain for short links?

Only through a subdomain, such as go.yourbrand.com or links.yourbrand.com. Pointing your main domain's apex at your link platform will break your website, since the apex is what serves your homepage. Apex configuration is appropriate only for a dedicated short domain with no website on it.

How long does DNS propagation take for a custom short domain?

Usually between five and thirty minutes on modern DNS providers, and often under five minutes on Cloudflare. Older registrars can take a few hours. You can check progress yourself by running dig yourdomain.com CNAME +short and comparing the result against the value SkyShare provided.

Why is my branded short domain showing a certificate error?

Most often the SSL certificate has not finished provisioning yet, which resolves on its own within a few minutes. If it persists and your DNS is on Cloudflare, check two settings: the record's proxy status should be "DNS only" (grey cloud), and the SSL/TLS encryption mode should be Full (strict) rather than Flexible.

Do branded short links help SEO?

Not directly, since redirects pass ranking signals to the destination regardless of which domain issues them. The benefit is behavioural: recipients recognise your domain and click more often, which improves campaign performance even though the search rankings themselves are unchanged.

How long does a branded short domain take to start working?

The DNS record itself takes about two minutes to add. Resolution typically spreads within an hour or two but can take up to 48 hours depending on the TTL on the record and the caches between you and your visitors. HTTPS follows after that, because a certificate cannot be issued until the domain already points at the platform. A browser warning during the first few hours is normal; one that is still there three days later means the certificate never issued.

Can I move my short links to a different domain later?

The links themselves do not move. A short link is the domain plus the alias, so changing the domain produces new links and every copy of the old one - printed, scheduled, embedded in old emails - keeps pointing at the domain you left. This is the reason to spend time on the domain choice up front rather than treating it as reversible.