Custom domain

On Pro, your changelog can live at your own address — say changelog.yourproduct.com — instead of only at changelogpilot.com/c/your-owner/your-repo. Setup lives in the repo's settings, under Custom domain. Each repo can have one custom domain.

What you'll need

A subdomain you control, like changelog.yourproduct.com or updates.yourproduct.com. Apex domains (yourproduct.com on its own) aren't supported — a custom domain needs a CNAME record, and DNS doesn't allow a CNAME at the apex. You'll also need access to your DNS provider to add two records.

Point the domain

Add the domain in the repo's settings, then create two DNS records. The settings page shows both, filled in for your domain:

1. A CNAME record pointing your subdomain at the host shown in settings. This is what routes traffic to us.
2. A TXT record at _changelogpilot-challenge.yourdomain with the value shown in settings (it looks like clp-domain-verify=…). This proves you control the domain — a CNAME alone doesn't, since anyone can point a CNAME anywhere.

Then press verify. DNS changes can take a little while to propagate, so if verification doesn't pass straight away, wait a few minutes and try again.

Leave both records in place. We re-check the TXT record periodically; if it disappears and stays gone across several checks, the domain stops serving until you re-verify. A single DNS blip won't do it.

HTTPS

We provision a TLS certificate for your domain automatically once the CNAME is in place — there's nothing to buy or upload. The certificate usually becomes ready within a few minutes of the DNS resolving.

What serves on your domain

Your domain serves the public changelog surface: the changelog page itself, its older pages, the RSS and Atom feeds (/rss.xml and /atom.xml on your domain), and robots.txt. The dashboard, sign-in, and settings stay on changelogpilot.com — your domain is for readers, not for administration.

The platform URL keeps working

changelogpilot.com/c/your-owner/your-repo keeps serving alongside your domain. While the custom domain is active, the platform page declares your domain as the canonical address, so search engines consolidate on the URL you actually want people to find. Links you shared before the switch keep working.

If you downgrade

Your domain keeps serving for 14 days after a downgrade, so a lapsed card doesn't take your changelog off the air the same hour. After that, requests to your domain redirect to the platform URL. The domain configuration and verification are kept — resubscribe and serving resumes without redoing the DNS.