How To Connect Namecheap Domain To Blogger Blog Website, Solve 404 Error Easily 2026

In Blogger, open Settings and find Publishing, where your blog currently shows its default blogspot.com address. Click Custom domain and type the domain you want to use, including the www prefix — for example www.yourdomain.com rather than the bare root domain, since Blogger's setup is built around the www subdomain by default.

Hit Save, and Blogger will immediately try to verify the domain; at this point it will fail, because Namecheap doesn't yet have the DNS records Blogger needs. That's expected — this step just tells Blogger what to look for.

Sign in to your Namecheap account and go to Domain List, where every domain you've registered is shown alongside its expiration date and a Manage button. Find the domain you just entered into Blogger and click Manage to open its settings. This is also a good moment to note the domain's expiration date while you're there — a domain about to lapse is a separate problem from a 404 error, but it's an easy thing to miss if you're only focused on DNS.

Inside the domain's management page, open the Advanced DNS tab and use Add New Record. Blogger's verification step (or its help documentation) gives you two CNAME records to add: one for the www host pointing to ghs.google.com, and a second, longer verification CNAME with a unique host and value that Blogger generates specifically for your domain.

Set the record type to CNAME, fill in the host and value exactly as shown — no typos, no trailing dots added by hand — and leave TTL on Automatic. Click the checkmark to save each record, then Save All Changes at the bottom of the list.

A 404 error after adding the right records is very often caused by leftover records that conflict with them — most commonly an old A record, URL redirect record, or parking-page CNAME still pointed at Namecheap's default hosting on the same host (www or @). DNS only resolves one way for a given host, so if Namecheap is still serving its own placeholder page for www while a CNAME also points www at Google, the result is inconsistent or wrong. Scan the Advanced DNS list for anything else touching the www host or the root, and delete it.

DNS changes don't apply instantly — propagation across the internet's resolvers can take anywhere from a few minutes to a couple of days, though it's usually much faster. Once you've given it some time, go back to Blogger's Custom domain field and save it again (or just check your site) to trigger a fresh verification. If it still 404s after a reasonable wait, go back through the CNAME values character by character — a single wrong character in the verification record's host or value is the most common reason this drags on.

Once your domain loads correctly, test both www.yourdomain.com and the bare yourdomain.com in a browser. Blogger typically needs a redirect setting enabled so visitors who type the root domain get forwarded to the www version automatically — check the Redirect domain option in Blogger's Publishing settings if the non-www version isn't resolving. Getting both to work means links and bookmarks people already have won't break no matter which version they use.