Custom domains
Point your own domain at your publication instead of its paragraph.com address.
A custom domain puts your site on an address you own, like example.com or blog.example.com, instead of your paragraph.com address. It strengthens your brand, and the search value you build over time accrues to a domain that's yours.
Custom domains are included with Starter and above. See Plans and credits.
Before you start
You'll need:
- A domain you own, registered anywhere (Namecheap, Cloudflare, GoDaddy, and so on).
- Access to that domain's DNS settings at your registrar.
A subdomain like blog.example.com is the easiest to set up and works with every DNS provider. A root domain like example.com works too, with one caveat covered below.
Connect your domain
In Settings → Website, find the custom domain section and enter your domain.
Paragraph shows the DNS records to add: a CNAME record that points your domain at Paragraph, and TXT records that verify you own it. Copy each one exactly as shown.
Add those records in your registrar's DNS dashboard, then save.
Wait a little while (30 minutes is a good first check), then refresh the verification status in Paragraph. Once every record verifies, your site loads at your new domain.
DNS changes can take up to 24 to 48 hours to propagate everywhere, though most domains resolve within a few hours.
You can remove the domain later from the same page, and your site goes back to its paragraph.com address.
Common DNS mistakes
Entering the full domain in the Name field. Most DNS providers append your domain to whatever you type:
| You enter | What gets created |
|---|---|
blog | blog.example.com (correct) |
@ | example.com (correct) |
blog.example.com | blog.example.com.example.com |
Leaving an old A record in place. If the same name already has an A record (from a previous website), delete it before adding the CNAME. A records take precedence and will keep traffic from reaching Paragraph.
Wildcard records. A * record pointing elsewhere can interfere with your subdomain. Remove it, or make sure your specific record wins.
Root domains without CNAME support. Some DNS providers don't allow CNAME records at the root (@). If yours doesn't, use an ALIAS record instead, use a subdomain like www.example.com, or move your DNS to a provider that supports CNAME at the root (Cloudflare does, for free, and your domain can stay registered where it is).
Troubleshooting
Still stuck after 48 hours? Email support@paragraph.com with your domain, a screenshot of your DNS records, and what you're seeing. We'll get you sorted.