Connecting a domain you bought at Namecheap to your blog comes down to one thing: adding a DNS record in Namecheap's dashboard that points your domain at your blog. The whole process takes a few minutes of clicking. The part that takes longer is waiting for that change to spread across the internet, which is normal and not a sign anything broke.

Why DNS setup is the part people get stuck on

DNS setup trips people up because it asks you to work in two different dashboards that don't talk to each other directly. You add a record in Namecheap, then you go back to your blog's settings and click verify. Nothing updates automatically in between, and if you skip a step or copy a value wrong, the two sides just don't agree yet. That's the whole failure mode. There's no deeper technical trap once you know the sequence.

What you need before you start

You need two things: a domain you've already bought at Namecheap, and access to your blog's custom domain settings. On Floggy, connecting a custom domain is a Pro feature, so your account needs to be on the Pro tier before the domain settings will do anything. If you don't own the domain outright, or you don't have login access to the Namecheap account it's registered under, stop here and sort that out first. Everything downstream depends on being able to edit that domain's DNS records.

Step 1: find your domain's DNS settings in Namecheap

Namecheap's DNS records live under Domain List, then Manage on the domain you want to connect, then the Advanced DNS tab. That's where you'll add and edit Host Records, the entries that tell the internet where your domain points.

Log in to Namecheap and open Domain List.
Click Manage next to the domain you're connecting.
Open the Advanced DNS tab.
Find the Host Records section. This is where new records get added.

Step 2: add the records your blog needs

On Floggy's side, go to Settings > Domain and enter your domain name without the https:// in front of it, just yourdomain.com. Once you save it, Floggy's dashboard shows you the exact DNS record to add: a CNAME record, with your domain as the Host and a target value that's specific to your account. Always use the value shown on your own Settings > Domain screen. That screen is the source of truth, not a value from a guide or a screenshot somewhere else.

In Floggy, go to Settings > Domain and enter your domain, then save.
Copy the CNAME target value Floggy displays for your domain.
In Namecheap's Advanced DNS, add a new Host Record with Type set to CNAME.
Set the Host field to match what Floggy's dashboard tells you (often your domain or a subdomain like www, depending on what you entered).
Paste the target value from Floggy into the Value field.
Save the record in Namecheap.

Double-check the record type is CNAME, not A or something else. A wrong record type is the single most common reason this step doesn't work on the first try.

Step 3: verify propagation and confirm the domain is live

Once the CNAME record is saved in Namecheap, go back to Floggy's Settings > Domain and click Verify. Floggy checks whether the DNS record has propagated and also rechecks automatically in the background while you're sitting on the Domain tab, so you don't have to keep clicking it manually.

Propagation is just the DNS record spreading to servers around the internet that cache domain lookups. Floggy's own guidance is that this can take a little time, sometimes minutes, occasionally longer. That's consistent with how DNS works generally: changes typically show up within minutes but can occasionally take longer to reach every resolver, since some servers hold on to old records until their cache expires. If Verify doesn't succeed right away, wait and try again rather than changing the record.

Common errors and fixes

Wrong record type. If you added an A record or anything other than CNAME, Floggy won't be able to verify the domain. Go back into Advanced DNS in Namecheap, delete the incorrect record, and add a CNAME with the value from your Floggy Settings > Domain screen.

Propagation delay. This isn't an error, it's a wait. If Verify fails right after you save the record, give it time and check again later. Floggy keeps rechecking on its own while you're on the Domain tab.

Certificate not issuing. A domain's SSL certificate usually can't be issued until the DNS record verifies correctly, so a stuck certificate is often a symptom of the CNAME still propagating or being set up wrong, not a separate problem. Confirm the CNAME record is correct and verified first, then give it more time.

Typos in the Host or Value fields. Copy and paste the target value from Floggy directly rather than typing it. A single mismatched character in the Value field means the record technically exists but points nowhere useful.

What changes once the domain is connected

Once your domain verifies, it becomes the primary address for your entire Floggy presence: your homepage, your posts, your booking page, and any links you share all move to it. Newsletter sending, analytics and any email tied to your blog now run under your own domain instead of your Floggy subdomain.

If you ever need to disconnect the domain, you can remove it at any time from the same Settings > Domain screen. Your original Floggy subdomain stays active as a permanent backup, so your blog is never left without an address.