Custom Domains Setup: go.yourbrand.com in Five Minutes

A branded short domain is the single highest-leverage branding move for your links: every URL you send becomes a trust signal instead of a liability (the data on CTR is unambiguous). The setup is small — a DNS record, a TLS certificate, a dashboard toggle — but the details matter. This guide walks the exact steps, the troubleshooting, and the migration path.

Step 1 — Choose the hostname

The standard pattern is a subdomain of your main domain:

go.yourbrand.com     ← recommended
link.yourbrand.com   ← also common
lnk.yourbrand.com    ← shorter for SMS

Why a subdomain rather than the apex: the link platform's DNS stays isolated from your site's records, cookies on your main domain don't interact with the link layer, and traffic classification (logs, analytics, security reviews) becomes trivial.

Step 2 — Add the domain in the dashboard

In the dashboard's domain settings, enter go.yourbrand.com. The platform validates that the domain is not already claimed, then presents the record to create.

Step 3 — Point DNS

At your DNS provider, create a CNAME:

Type:  CNAME
Name:  go
Value: <edge hostname provided in the dashboard>
TTL:   300 (or lowest available)

For apex domains (yourbrand.com directly), your provider may require A/ALIAS records to the platform's edge IPs — the dashboard shows the exact values after validation.

Verify propagation:

dig +short go.yourbrand.com CNAME
# → <edge hostname>  (when propagated)

Step 4 — TLS

The platform issues and renews certificates automatically (Let's Encrypt, 90-day rotation, auto-renewal). Expected timeline: seconds to minutes after DNS resolves. HTTPS is enforced — plain HTTP requests are upgraded with HSTS (max-age=63072000; includeSubDomains).

Step 5 — Create branded links

New links can now use go.yourbrand.com by default; the custom alias rules apply unchanged. Existing links keep their old domain — migration is a separate, deliberate step.

Migrating existing links

If you're moving links from another domain or provider:

1. Export all links (CSV export or the provider's export).
2. Re-shorten the same destinations under the new domain — the bulk creation guide covers volume workflows.
3. Forward the old URLs with 301s from the old domain so bookmarks and printed materials don't die. For Bitly and Short.io specifically, the migration guides give the exact mapping.
4. Compare analytics for two weeks before sunsetting the old domain.

Troubleshooting

Measurement: the branded domain dashboard

Every link on the custom domain reports into the same analytics pipeline: bot-filtered clicks, devices, referrers, daily series, per-link breakdowns. The domain itself becomes a filter — compare go.yourbrand.com traffic vs your old domain during migration to prove the switch didn't cost clicks.

Choosing the subdomain or domain

The first decision is where your link domain will live. The two realistic options:

• A subdomain of your existing domain, like go.yourbrand.com. This is the fastest and most common path: it inherits the trust and reputation of the root domain, needs no new purchase, and is the default for most teams.
• A dedicated short domain, like yourbrand.link. This gives the shortest possible URLs and a fully independent brand surface, at the cost of buying and managing a second domain and building its reputation separately.

There is a trade-off worth naming: a subdomain borrows the root domain's trust and is easier to set up, while a dedicated domain gives shorter, cleaner links but starts from zero reputation. Most teams start with a subdomain and move to a dedicated domain only when link brevity matters enough to justify it.

The DNS records you will need

Setting up a custom link domain comes down to a small set of DNS records. In most cases you create a CNAME for the chosen subdomain pointing at the value the platform provides; if your provider does not support a CNAME on a subdomain, an A record against the supplied address works as a fallback. If you plan to send or receive mail-related links, keep the mail records (MX, SPF, DMARC) in order too, so the domain's authentication stays healthy.

Two operational details matter:

• Plan the TTL. Lower the TTL well before the change so the new records propagate quickly, then raise it again after the change settles.
• Verify propagation with a DNS lookup before you rely on the new domain in a live campaign — a record that is not yet visible externally will make branded links fail at the worst moment.

Proving it works before launch

Once the records are set and propagated, test end to end before any campaign depends on it: open a branded link in a browser, scan it as a QR, and confirm the redirect resolves to the right destination from both mobile and desktop. This mirrors the verification discipline of the custom domains short links guide and prevents the embarrassing failure of a beautifully branded link that does not actually work.

A quick checklist

Before you go live with a branded link domain, confirm: the subdomain or domain is chosen deliberately, the CNAME or A record points at the platform value, the TTL was lowered before the change and raised after, propagation is verified with a DNS lookup, and a branded link resolves correctly on both mobile and desktop. That short checklist catches the failures that otherwise surface during a launch.

Getting this right once pays off across every future branded-link campaign.

Conclusion

Branded short domains are a five-minute DNS task with a permanent trust dividend: every link you ship carries your brand instead of a stranger's. Add go.yourbrand.com in the dashboard, point the CNAME, let TLS issue itself, and start creating branded links — the API picks up the domain automatically for all new links.