Custom Domain Setup
Connect your own domain to Sellrn and configure SSL so your store loads at yourstore.com instead of sellrn.com/s/slug.
Updated 2026-06-21
domain
ssl
dns
cname
settings
By default, your Sellrn store is accessible at sellrn.com/s/your-slug. You can connect your own domain (like shop.yourbrand.com or yourbrand.com) so customers see your brand in the URL.
Step-by-step
- Go to Settings → Domains. Click Add domain in the top-right corner.
- Enter your domain. Type the full domain you want to connect, for example
shop.yourbrand.comoryourbrand.com. Click Add. - Get the DNS record. Sellrn shows you a CNAME record to add. It looks like this:
Type: CNAME Name: shop (or @ for the root domain) Value: stores.sellrn.com - Add the record in your domain registrar. Log in to where you registered your domain (GoDaddy, Namecheap, Cloudflare, Google Domains, etc.) and add the CNAME record shown by Sellrn.
- Wait for verification. DNS propagation can take a few minutes to 48 hours depending on your registrar. Sellrn checks automatically — you'll see the status change from "Pending" to "Verified".
- SSL issues automatically. Once the domain is verified, Sellrn provisions an SSL certificate automatically. This usually takes 5–15 minutes.
- Set as primary. If you have multiple domains, click Set as primary next to the domain you want customers to land on by default. All other connected domains redirect to the primary.
Root domain vs subdomain
You can connect either a subdomain or a root domain:
- Subdomain (e.g.,
shop.yourbrand.com) — add a CNAME record forshoppointing tostores.sellrn.com. Most straightforward option. - Root domain (e.g.,
yourbrand.com) — some registrars do not support CNAME on the root. In that case, use an ALIAS or ANAME record if your registrar supports it, or use Cloudflare (which handles root CNAMEs with its proxy).
Redirect mode
In the Domains settings, you can set the redirect mode for non-primary domains. Options are:
- Permanent (301) — best for SEO when you are migrating from an old domain.
- Temporary (302) — use when the redirect might change.
Common problems
| Problem | Solution |
|---|---|
| Verification stuck after 24 hours | Check the CNAME record is exactly right (name and value). Look for typos or extra spaces. Remove any conflicting A records on the same name. |
| SSL not issuing after domain verifies | Wait 10–15 minutes. If still stuck, remove the domain and re-add it to trigger a new certificate request. |
| Redirect loop in the browser | Make sure only one domain is marked as primary. Check that your registrar is not also redirecting the domain independently. |
| "DNS record not found" error | The record has not propagated yet. Wait a few hours and try again. You can check propagation at dnschecker.org. |