Skip to content

Blog

How to set up a branded short domain

16 July 2026

By Jaladhi Desai, Founder, SwiftURL

A branded short domain replaces a generic shortener’s name with your own, so a link reads go.yourbrand.com/spring instead of an anonymous string on a domain you do not control. It is one of the highest-return, lowest-effort things a marketing team can do: recognizable links get clicked more, they keep your brand, not a third party’s, front and center, and they insulate you from whatever reputation a shared public shortener has picked up. Setting one up takes about five minutes and a single DNS record.

This walkthrough covers why a branded domain matters, the four steps to set one up, and the mistakes worth avoiding.

Why bother with a branded domain

Three concrete reasons, beyond looking tidy:

  • Trust and click-through. People are wary of unfamiliar shortener domains, and rightly so, they are a common disguise for spam. A link on your own domain signals it is really you, and that shows up as higher click-through, especially in SMS and messaging where a suspicious link gets ignored.
  • Reputation you control. On a shared public shortener, your links sit on the same domain as everyone else’s, including bad actors. If that domain gets flagged by a filter, your links are caught in it. Your own subdomain carries only your reputation.
  • Consistency and recall. go.yourbrand.com reinforces your brand every time it is seen or shared. An anonymous string reinforces nothing.

For the fuller argument that a branded, safe link is part of the promise your brand makes, see why every short link is a compliance decision.

Step 1: Pick a subdomain

Use a subdomain of a domain you already own, rather than your bare root domain. Common choices are short and obvious:

  • go.yourbrand.com
  • links.yourbrand.com
  • s.yourbrand.com

A subdomain keeps your short links cleanly separated from your main site and avoids touching your root domain’s DNS in a way that could affect email or your website. Keep it short, the whole point is a tidy, memorable link, and every extra character works against that.

Step 2: Add one CNAME record

In SwiftURL, add your chosen domain under Custom Domains. You will be shown a single CNAME target to create at your DNS provider (for example, Cloudflare, Namecheap, or GoDaddy). Create a CNAME record where the name (or host) is your subdomain, go, and the value (or target) is the address SwiftURL gives you. That is the only DNS change required.

A couple of practical notes:

  • If your DNS is behind Cloudflare’s proxy, set the record to DNS only (grey cloud) while it verifies, unless instructed otherwise.
  • DNS changes can take anywhere from a few minutes to a few hours to propagate. This is normal; you do not need to do anything but wait.

Step 3: Let SwiftURL verify and secure it

Once the record propagates, SwiftURL confirms it and provisions an SSL certificate automatically, so your links are served over HTTPS with no manual certificate work. Certificates renew on their own, there is nothing to remember or re-do. In the dashboard, your domain moves to an “SSL active” state when it is ready to use.

If it stays “pending” longer than expected, the usual cause is a CNAME typo or the record being proxied when it should be DNS-only. Re-check the host and target against what SwiftURL displayed.

When you create a link, choose your custom domain instead of the shared sftl.in domain. Existing links can stay where they are; new ones carry your brand. There is no need to migrate everything at once, point new campaigns at the branded domain and let the old links live out their life.

A few tips

  • Keep the subdomain short. The whole point is a tidy, memorable link.
  • Use different subdomains for different purposes if it helps, for example one for marketing and one for transactional messages, so their delivery reputations stay separate.
  • Free plans use the shared sftl.in domain, which is a fine place to start; add your own domain when you are ready. Custom domains come in on Pro and above; see pricing.
  • Pair the branded domain with clean UTMs. A recognizable link with consistent tags is both trustworthy and measurable, see UTM best practices.

Common mistakes

  • Using your root domain instead of a subdomain. Editing root DNS risks your email and website; a subdomain isolates the change.
  • A CNAME typo. The most frequent reason a domain never verifies. Copy the target exactly.
  • Leaving the record proxied. If verification stalls behind a proxy, switch to DNS-only.
  • Picking a long subdomain. campaign-links.yourbrand.com defeats the purpose. Shorter is better.
  • Migrating every old link at once. Unnecessary. Start with new links and move on.

A worked example, start to finish

Say your brand is Acme and your domain is acme.in. Here is the whole thing, concretely:

  1. Pick the subdomain. You choose go.acme.in, short, obvious, memorable.
  2. Add it in SwiftURL. Under Custom Domains you enter go.acme.in. SwiftURL shows you a CNAME target, say cname.sftl.in.
  3. Create the DNS record. In your DNS provider you add: type CNAME, name go, value cname.sftl.in. If you use Cloudflare, set it to DNS-only (grey cloud) for now.
  4. Wait for propagation. Within minutes to a couple of hours, SwiftURL detects the record.
  5. SSL goes active. SwiftURL issues the certificate; the domain flips to “SSL active” in your dashboard.
  6. Ship a link. You create go.acme.in/diwali, put it in your campaign, and it serves over HTTPS under your own brand.

Total hands-on time: about five minutes, most of which is waiting for DNS. Nothing here requires touching your website or email.

One underrated benefit: a branded domain lets you keep your marketing and transactional link reputations separate. If you send both promotional campaigns and important transactional messages (receipts, confirmations), consider go.acme.in for marketing and something like m.acme.in for transactional. That way, if a promotional blast ever gets aggressive spam filtering, it does not drag down the deliverability of the links your customers actually need to click. This pairs naturally with the compliance thinking in why every short link is a compliance decision, a branded, safe, monitored link is the “branded” and “reliable” half of keeping a link’s promise.

Frequently asked questions

Do I need a separate domain to brand my links? No. A subdomain of a domain you already own, like go.yourbrand.com, is the recommended approach. You do not need to buy anything new if you already have a domain.

Is SSL automatic on a branded short domain? Yes. Once your CNAME verifies, SwiftURL provisions and renews the SSL certificate automatically, so your links are always served over HTTPS with no manual certificate work.

Will branding my domain break my existing short links? No. Existing links keep working on whichever domain they were created with. You simply choose your custom domain for new links going forward.

Which plan includes custom domains? Custom domains are available on Pro and above. The Free plan uses the shared sftl.in domain, which is a fine place to start. See pricing for details.

The takeaway

That is the entire process: pick a subdomain, add a CNAME, and SwiftURL handles verification and SSL. The payoff, more trust, more clicks, and a reputation you control, is out of proportion to the five minutes it takes.

See Custom Domains, or start free and brand your first link.