A branded short domain builds more trust than a generic one. Here's how to set one up, the DNS mistake that trips people, and when it's not worth doing.
Paste a raw bit.ly or tinyurl link into a text message and watch what happens. Someone asks if it's a scam, or they just don't tap it. That's not paranoia, it's trained behaviour: generic shortener domains get used for phishing often enough that people have learned to hesitate. A link on `go.yourbrand.com` doesn't trigger that same pause, because it plainly comes from a business the reader already recognizes.
That's the entire case for a custom domain. Everything else, the setup steps, the DNS record, the plan tier, is just getting there.
What changes when the domain is yours
Three things, and only one of them is about looks.
Trust is the obvious one. A short link that shows your brand name reads as an extension of your site instead of a third-party redirect. For anything going into an email campaign, an SMS blast, or a printed ad, that difference shows up directly in click-through rate.
Control is the one people don't think about until they need it. If you ever move off a particular shortening tool, links built on a domain you own can be redirected to wherever you land next. Links built on someone else's shared domain die the day you stop paying that provider, full stop, because you never had the domain in the first place.
The third is smaller but real: a branded domain doesn't sit in the same shared reputation pool as a public shortener. When one bad actor abuses a generic domain, spam filters sometimes flag the whole domain, and every legitimate link on it takes the hit. Your own subdomain only has your own sending history attached to it.
Setting it up today
You need a domain you already own (your main site's domain is fine) and about fifteen minutes.
- Pick a subdomain, not your root domain. Something like `go.yourbrand.com` or `lnk.yourbrand.com`. Never point your bare root domain (`yourbrand.com`) at a shortener; it's overkill and it complicates your main site's DNS for no reason.
- Add a CNAME record at your domain registrar or DNS host pointing that subdomain to the target the shortener gives you. This is a DNS change, not a code change, so it works no matter what your main website runs on.
- Add the domain inside your account under your links dashboard and wait for verification. Most tools check for the CNAME automatically once it's live.
- Test with a throwaway link before you use a real one. Shorten something disposable, open it in an incognito window, confirm it redirects correctly, then start building the links you actually intend to send out.
The mistake that eats an afternoon
DNS propagation is the part that trips people up, not the setup itself. You add the CNAME, it looks correct, and the domain still won't verify twenty minutes later. That's normal. DNS changes can take anywhere from a few minutes to 24 to 48 hours to propagate fully, and your own computer or phone may have the old (non-existent) record cached longer than that. If verification fails right after you add the record, wait before you start troubleshooting. If it's still failing the next day, then check the record itself, not your patience.
The second-most common error: pointing the CNAME at the wrong target string, usually because it got copied with a trailing period or an extra `www.` that shouldn't be there. Copy it exactly as given, and don't add anything the instructions didn't include.
Where this isn't worth doing
If you're sending a handful of links a year, personally, a shared domain is genuinely fine. Nobody's phishing-training instincts fire on one link from a friend. Set up a custom domain when you're sending links at volume where trust and click-through actually move a number: email campaigns, paid social, SMS, anything printed and public-facing. Below that, you're spending fifteen minutes and a bit of ongoing plan cost on a problem you don't have yet.
Generic vs. custom domain, side by side
| Shared domain | Custom domain | |
|---|---|---|
| Setup time | None | ~15 minutes (DNS) |
| Recognized brand | No | Yes |
| Reputation risk | Shared with every other user of that domain | Isolated to your own sending history |
| Survives switching tools | No, links die with the account | Yes, if you keep the domain and redirect it |
| Cost | Usually free tier | Paid tier on most tools, check what each plan includes |
Frequently asked questions
Does a custom domain actually improve click-through rate?
Generally yes, especially in email and SMS where recipients are actively watching for anything that looks like phishing. The size of the lift depends on your audience, but the direction is consistent: a recognizable domain gets clicked more than an unfamiliar one.
Do I need to buy a new domain, or can I use a subdomain of my existing site?
A subdomain of your existing domain works fine and is what most people should do. You don't need a second domain purchase just for this.
Will a custom short domain hurt my SEO?
No. Short links redirect traffic; they don't compete with your main site for rankings, and a subdomain used only for redirects has no content of its own to rank or cannibalize.
What happens to my links if I stop paying for the tool?
That depends entirely on whether you kept the custom domain. If your links live on a shared domain owned by the provider, they stop working the day your account does. If they live on your own domain, you can point that domain somewhere else and keep the redirects alive, even after switching tools.
Can I add a custom domain to links I already created?
Usually not retroactively without recreating them. Decide on the domain before you start handing out links in a campaign, print run, or signature, since going back and swapping every existing short link is far more work than setting the domain up correctly the first time.
If you're also setting up a bio-link page to sit behind one of these links, our 10-minute link-in-bio walkthrough covers the setup in the same order: domain and page first, individual links second.