A custom domain turns a Blogspot address into a brand people can remember. Connecting a Namecheap domain to Google Blogger is straightforward once DNS records and Blogger Publishing settings match. You do not need to buy a separate SSL certificate for Blogger, and you do not need advanced networking skills.
This 2026 walkthrough covers why a paid domain helps, how to register at Namecheap, the exact Blogger custom-domain flow, the six DNS records Namecheap and Google still expect, HTTPS redirects, and common fixes when Save fails. If you are still building the blog itself, start with COMPROMATH’s Blogger setup guide.
Before you buy or connect a domain
A custom domain strengthens branding, removes the Blogspot look from your public URL, and usually looks more professional for AdSense, affiliates, and sponsorships. Free novelty TLDs that disappear or change ownership without warning are a poor foundation for a blog you care about.
Blogger provides free HTTPS for connected custom domains. Buying an extra SSL product from the registrar often conflicts with Google’s certificate process. If you use CAA DNS records, Google’s help says you must allow letsencrypt.org or Blogger cannot create or renew SSL. Skip extra SSL upsells during checkout unless you truly understand CAA.
Blogger does not publish the blog on a naked domain alone. You map something like www.example.com or blog.example.com, then optionally redirect the apex (example.com) to that www address with A records plus Redirect domain in Blogger.
Why Namecheap works well for Blogger
Any registrar that lets you edit A and CNAME records can work. Namecheap is a practical choice because Advanced DNS is clear, support docs specifically cover Blogger, and you keep full control of host records. GoDaddy and other mainstream registrars also work if you prefer them.
Google Domains is gone. Those domains moved to Squarespace Domains. If you still see old tutorials pointing at domains.google, ignore that path and use a current registrar with open DNS editing.
For free-domain experiments and tradeoffs, see custom domains for Blogger. For a paid setup you plan to keep, Namecheap is the path this guide uses.
Register a domain at Namecheap
Open Namecheap, search your preferred name, and only buy a domain that shows as available. If your first choice is taken, adjust the wording rather than settling for a confusing misspelling you will regret later.
Add the domain to cart, check out, and complete payment. Create a Namecheap account if you do not already have one. Keep WHOIS contact details accurate so renewal notices reach you. After purchase, Domain List should show the new domain as ready to manage.
Start the connection inside Blogger
Sign in to Blogger, open the blog, then go to Settings. Under Publishing, open Custom domain. Enter the www version of your domain, for example www.yourdomain.com, then click Save. Blogger expects a subdomain here. Naked-only values are not the publish target.
Blogger will usually show an error that it could not verify the domain yet, plus two CNAME instructions. That is normal. Do not force Save again until DNS is updated. Copy both records carefully.
You should see a blog CNAME and a security CNAME. The first is typically host www pointing to ghs.google.com. The second uses a unique host token and a unique gv-....dv.googlehosted.com target for your account. Your values will not match another publisher’s screenshot.
| Record job | Host (Name) | Points to (Destination) |
|---|---|---|
| Blog CNAME | www | ghs.google.com |
| Security CNAME | unique token from Blogger | gv-….dv.googlehosted.com from Blogger |
Add DNS records in Namecheap Advanced DNS
Open your Namecheap Domain List, click Manage on the domain, then open Advanced DNS. Under Host Records, remove conflicting parking, URL redirect, or old A records for @ that point somewhere else. Then add the Blogger set.
Namecheap’s Blogger guide still expects six host records in total. Use Automatic TTL unless you prefer a short TTL while testing. Replace the security CNAME placeholders with the exact pair Blogger showed you.
| Type | Host | Value |
|---|---|---|
| CNAME | www | ghs.google.com |
| CNAME | your Blogger security host | your gv-….dv.googlehosted.com target |
| A | @ | 216.239.32.21 |
| A | @ | 216.239.34.21 |
| A | @ | 216.239.36.21 |
| A | @ | 216.239.38.21 |
Click the green save control after each record or after the batch, depending on the current Namecheap UI. Namecheap says new host records often take about thirty minutes. In practice, some domains clear in a few minutes and others need a few hours. Full DNS propagation can stretch longer across networks.
Save again in Blogger and turn on redirects
Return to Blogger Settings, Publishing, Custom domain. Click Save again on the www domain. If verification still fails, wait and retry without changing the token values. Wrong security CNAME values are the usual culprit when waits do not help.
After the domain saves, enable Redirect domain so apex visits go to www. Then enable HTTPS availability. Wait until Blogger reports HTTPS as available before you force HTTPS redirect. Turning redirect on too early can produce temporary certificate errors in browsers.
During propagation you may see browser warnings or DNS errors. That is common. Do not buy panic SSL products or change nameservers mid-wait unless you intended to move DNS elsewhere.
Google notes that Blogspot to custom-domain redirect behavior can take up to about a day to settle everywhere. Keep both the Blogspot URL and the new domain bookmarked until visitors land cleanly on HTTPS www.
Troubleshooting when the domain will not save
Security CNAME mismatch. Copy host and destination exactly from Blogger. Do not reuse another blog’s token. Do not add your full domain into the host field if Namecheap already scopes records to that domain. Host is usually only the left label, such as www or the token string.
Conflicting A or URL records. Parking pages, old website builders, and URL redirects on @ fight the four Google A records. Remove them, keep the four Google IPs, save, and wait again.
Nameservers not pointing at Namecheap. If Advanced DNS will not edit, or edits never appear publicly, confirm Domain List shows Namecheap BasicDNS or PremiumDNS nameservers. Custom nameservers at Cloudflare or a host mean you must add the same six records there instead.
HTTPS stuck. Confirm CAA allows Let’s Encrypt if you use CAA at all. Toggle HTTPS availability off, wait a few minutes, turn it back on, then enable HTTPS redirect only after status looks healthy.
Wrong publish URL. Enter www.yourdomain.com in Blogger, not only the apex, unless you intentionally publish on another subdomain and set DNS for that label.
After the domain works
Update Search Console for the new domain property, refresh analytics and AdSense site settings if you already monetize, and check that menus and canonical habits still make sense. COMPROMATH’s Google Blogger SEO guide covers on-page habits after branding upgrades. If AdSense is next, read how to qualify for Google AdSense and the Blogger AdSense approval checklist.
A Namecheap domain plus clean Blogger Publishing settings is enough for a professional free-hosted blog. Keep DNS simple, wait through propagation, and enable HTTPS only after availability succeeds. That sequence still works in 2026.
