Assign a client's own domain to their UniLink sub-account so their page lives at their URL, not yours.
- Custom domains are assigned at Agency Dashboard → Sub-accounts → select client → Domain → Add Domain.
- After adding the domain, UniLink provides DNS records the client (or their web host) must add — SSL is provisioned automatically once DNS resolves.
- DNS propagation typically takes 15 minutes to 24 hours depending on the client's registrar and TTL settings.
A client page at myrestaurant.com/menu is a different product from a page at unil.ink/myrestaurant. The custom domain signals professionalism, reinforces brand trust, and keeps your client from having a third-party URL in all their printed materials. Connecting a custom domain to a UniLink sub-account is straightforward once you know the steps, but it requires coordination with the client or their web host to update DNS records.
What Custom Domain Assignment Does
When you assign a custom domain to a sub-account, UniLink maps incoming traffic for that domain directly to the client's UniLink page. Visitors who go to the client's domain see their UniLink page instantly — there is no redirect visible in the browser bar, no "powered by UniLink" in the URL, and no indication they are on a third-party platform. From the visitor's perspective, it is just the client's website.
SSL (HTTPS) is provisioned automatically after DNS verification is confirmed. UniLink uses Let's Encrypt to generate and renew the certificate without any action from you or the client. The certificate renews on its own every 90 days. You do not need to manage SSL manually or purchase a certificate — this is handled at the platform level. The only prerequisite is that DNS must be correctly pointing to UniLink before the certificate can be issued.
Custom domain assignment at the sub-account level is independent of any domain the agency might use for their own pages. Each client sub-account can have exactly one primary domain assigned. If the client wants multiple domains pointing to the same page (e.g., both mybusiness.com and mybusiness.co), you can set up CNAME or redirect records at the registrar level pointing all additional domains to the primary one — only one domain needs to be registered in UniLink.
How to Get Started
- Confirm the client has a domain they want to use. Before opening UniLink, confirm with the client which domain (or subdomain) they want to assign. Common choices: their root domain (mybusiness.com), a subdomain (links.mybusiness.com), or a new domain purchased specifically for their link page. If they don't have a domain yet, direct them to a registrar (Namecheap, Google Domains, Cloudflare Registrar) to purchase one first.
- Determine who manages the client's DNS. Ask the client whether they manage their own DNS or if their web host or a developer does. You'll need DNS access to add records. If neither you nor the client has access, identify the right contact before starting — waiting to find out mid-process adds delays.
- Open the target sub-account. Log in at app.unilink.us, go to Agency → Sub-accounts, and click on the client's sub-account to open it.
- Navigate to Domain settings. Inside the sub-account, click Settings → Domain. This section shows the current domain assignment (unil.ink/username by default) and a button to add a custom domain.
- Have the DNS records panel and registrar login open simultaneously. The fastest domain setup happens when you add the domain in UniLink, see the required DNS records, and enter them in the registrar or DNS manager in the same session. If you can't do both at once, copy the DNS records to a note before closing UniLink.
How to Set a Custom Domain
- Add the domain in UniLink. In Settings → Domain, click Add Domain. Enter the client's domain exactly as it will be used (e.g., mybusiness.com or links.mybusiness.com). Click Confirm. UniLink will display a set of DNS records — typically one or two CNAME or A records depending on whether you're using a root domain or subdomain.
- Copy the DNS records. Note down or copy the exact record type, name (host), and value (target) for each record shown. Accuracy matters here — a single typo in the record value means verification fails and the domain won't connect.
- Add the DNS records at the registrar. Log in to the client's domain registrar or DNS manager (Cloudflare, Namecheap, GoDaddy, Google Domains, etc.). Navigate to the DNS settings for the domain. Add each record exactly as shown in UniLink. Save changes.
- Wait for DNS propagation and verify. Return to the sub-account's Domain settings in UniLink. Click Verify DNS. If records have propagated, the domain status changes to "Verified" and SSL provisioning begins automatically. If verification fails, double-check each record value — pay attention to trailing dots, extra spaces, and CNAME vs A record types.
- Confirm SSL and test the domain. Once verified, the domain status shows "SSL Active" within 5–15 minutes. Open the domain in an incognito browser window and confirm the client's page loads with HTTPS and no certificate warnings. Share the live URL with the client to confirm from their end as well.
Key Settings
| Setting | What It Does | Recommended |
|---|---|---|
| Custom Domain | The domain or subdomain that maps to the client's UniLink page | Use the client's primary brand domain or a branded subdomain (links.brand.com) |
| DNS Record Type | CNAME for subdomains; A record for root domains — UniLink specifies which to use | Follow UniLink's specification exactly — do not substitute one type for another |
| SSL Certificate | Automatically provisioned via Let's Encrypt after DNS verification | No manual action needed; auto-renews every 90 days |
| Fallback URL | The unil.ink/username URL remains active even after a custom domain is connected | Keep as a fallback; do not delete until the custom domain is fully verified and stable |
| DNS TTL | Time-to-live on the domain's DNS records — lower TTL means faster propagation | Set TTL to 300–600 seconds at the registrar before adding records to speed up propagation |
Get the Most Out Of Custom Domain Setup
Build domain setup into your standard onboarding checklist as step three — right after white-label branding and before page customization. Starting it early is important because DNS propagation is the one step you can't control or speed up significantly. If you wait until the page is fully built to start the domain process, you may find yourself waiting hours at the end when the client is eager to see their live page.
Use subdomains when the client already has an active website at their root domain. Pointing the root domain (mybusiness.com) to UniLink typically requires replacing the existing DNS A record, which would take down their main website. A subdomain like links.mybusiness.com or go.mybusiness.com avoids this entirely — it adds a new DNS record without touching the existing site. This is the safest option when the client has a live website you don't manage.
If the client's domain is behind Cloudflare with proxy mode (orange cloud) enabled, the CNAME record needs to be set to DNS-only mode (grey cloud) for UniLink's SSL provisioning to work correctly. Cloudflare's proxy mode rewrites DNS responses in a way that conflicts with Let's Encrypt's domain verification. This is a common source of domain verification failures for clients using Cloudflare — check proxy status if verification is taking longer than expected.
After the domain is live, do a quick redirect check. If the client's old unil.ink URL has been shared publicly, visitors who used that link will still land on the page correctly — both URLs point to the same content. However, for long-term SEO and brand consistency, advise the client to update any printed or published links to use the custom domain. The unil.ink URL will continue to work indefinitely, but the custom domain is the canonical version.
Troubleshooting
| Problem | Cause | Fix |
|---|---|---|
| Domain verification still pending after 24 hours | DNS records were entered incorrectly, or propagation is slow due to high TTL | Use a DNS checker (dnschecker.org) to confirm records have propagated; re-verify each record value against what UniLink specified |
| SSL certificate shows as "Failed" after domain verification | Domain was verified but proxy mode (Cloudflare orange cloud) is blocking certificate issuance | Set CNAME record to DNS-only mode in Cloudflare, then click Re-issue SSL in UniLink Domain settings |
| Client's main website went down after adding domain records | Root domain A record was replaced, removing the existing website's DNS entry | Restore the original A record for the root domain; use a subdomain (links.domain.com) for UniLink instead |
| Custom domain shows a certificate warning in browser | SSL not yet provisioned or certificate issued for wrong domain name | Wait 15–30 minutes after verification for SSL to activate; hard refresh the browser (Ctrl+Shift+R) |
- Client's page appears at their own domain with no visible platform branding in the URL
- SSL is automatic and auto-renewing — zero certificate management overhead
- Both the custom domain and the original unil.ink URL continue to work simultaneously
- Works with any registrar or DNS provider (Cloudflare, Namecheap, GoDaddy, Route53, etc.)
- DNS propagation can take up to 24 hours — timing is outside your control
- Requires DNS access from the client or their web host — a dependency that can delay onboarding
- Using a root domain may conflict with the client's existing website DNS setup
Frequently Asked Questions
Can I assign the same custom domain to multiple sub-accounts?
No. Each domain can be assigned to only one sub-account at a time. If you try to add a domain that is already assigned to another account, UniLink will show an error. You would need to remove the domain from the current sub-account before assigning it to a different one.
Does the custom domain affect the client's page SEO?
Yes, positively. A custom domain is the canonical URL for the page, which is stronger for SEO than a unil.ink subdirectory URL. Any links the client shares or earns that point to their custom domain contribute to the domain's authority. This is especially relevant for clients who use their link page as a primary landing destination from social media profiles.
Can I connect a domain that uses a different registrar than Namecheap or GoDaddy?
Yes. UniLink domain setup works with any DNS provider — it requires only that you can add DNS records (CNAME or A records) for the domain. The registrar or DNS provider doesn't matter as long as you have access to add records.
What happens to the custom domain if I deactivate the client's sub-account?
The domain stops resolving — visitors to the domain will see an error or a platform-level notice. The domain is still registered in UniLink, but traffic stops being served. To restore, reactivate the sub-account. If you permanently delete the sub-account, remove the DNS records at the registrar to prevent a "dangling CNAME" security issue.
Can the client manage their own domain settings after onboarding?
This depends on the role you assign them. If the client has an Admin role in their sub-account, they can access Domain settings and make changes. If you assign them an Editor role, domain settings are read-only for them. Most agencies keep clients as Editors to prevent accidental domain changes.
- Add a custom domain in Agency → Sub-accounts → select client → Settings → Domain → Add Domain.
- DNS records must be added at the client's registrar; SSL is then issued automatically — no manual certificate management.
- Start the domain step early in onboarding since DNS propagation is the one factor you can't control.
- Use subdomains (links.domain.com) when the client has an existing website at the root domain to avoid conflicts.
- If the client uses Cloudflare, set the CNAME to DNS-only mode (grey cloud) for SSL to provision correctly.
Give your clients a professional URL on their own domain. Log in to your UniLink Agency account at app.unilink.us, open the client's sub-account, and start the domain setup process today — the sooner you start, the sooner DNS resolves.