How to Connect a Custom Domain to Blogger or WordPress (2026 Beginner Guide How to)
If you’re here because your site address still ends in “blogspot.com” or “wordpress.com” and it’s starting to feel like showing up to a wedding in gym shorts… yeah, same. Connecting a custom domain to Blogger or WordPress sounds like a “tech person” task, but honestly it’s mostly copy/paste, one small panic spiral, and then waiting for DNS to do its slow, mysterious thing.
This 2026 beginner guide how to connect a custom domain walks you through the exact steps (with the messy real-life parts included): what to buy, what to click, which DNS records matter, how to avoid the classic “why is my site broken??” moment, and how to get HTTPS working without sacrificing your sanity.
30-second summary (save your future self)
- Buy a domain (Namecheap/GoDaddy/Google Domains alternatives) and decide: Blogger or WordPress.
- Add the domain inside Blogger/WordPress first (so it generates the right DNS values).
- Update DNS: either nameservers (common for WordPress hosting) or CNAME/A records (common for Blogger and WordPress.com manual).
- Wait for propagation (it’s normal; don’t rage-refresh for 45 minutes straight like I did).
- Turn on HTTPS + redirects so Google doesn’t see duplicates.
First: domain + DNS (in normal-people language)
A custom domain is your “real” website name (like yourname.com) that you rent yearly from a domain registrar.
DNS is the set of directions that tells the internet where your site lives. When you “connect” a domain, you’re basically updating DNS so yourname.com points to Blogger or WordPress.
Here are the DNS terms you’ll see most:
- CNAME record: Points one name to another name (common for
www). - A record: Points a domain to an IP address (often used for the “naked domain” like
yourname.comwithoutwww). - Nameservers: The “big switch.” Changing nameservers means you let another company manage all DNS for your domain.
If your eyes glazed over: totally fine. The steps below are still simple.
Before you start (the “don’t make it harder” checklist)
Do these quick things first:
- Pick your preferred version:
www.yourdomain.comoryourdomain.com(either works, but pick one and stick to it). - Log into your domain registrar in a separate tab (you’ll bounce between screens).
- If you’re moving from an old site, lower your TTL (optional) and plan your redirect strategy.
- Expect a wait: DNS updates can take a while (minutes to hours, occasionally longer).
Also: write down where your domain is registered (GoDaddy, Namecheap, etc.). Half of domain problems are really “I changed DNS in the wrong account.”
How to connect a custom domain to Blogger (2026)
Blogger domain setup is weirdly straightforward… right after it scares you with an error message (that you actually need).
Step 1: Add the domain in Blogger
- Open Blogger dashboard
- Go to Settings
- Under Publishing, click Custom domain
- Enter your domain with www (example:
www.yourdomain.com) and click Save
Blogger will usually throw an error and show you two CNAME records you must add at your domain provider:
- One CNAME that points
wwwtoghs.google.com - One Security CNAME that is unique to your blog/account
That “error” is basically Blogger handing you the keys.
Step 2: Add the two CNAME records in your domain DNS
Go to your domain registrar → DNS settings (sometimes called “Manage DNS”, “Zone Editor”, or “Advanced DNS”).
Add:
- CNAME
- Host/Name:
www(or whatever subdomain Blogger shows) - Target/Points to:
ghs.google.com
- CNAME (Security)
- Host/Name: a weird random-looking value Blogger gives you
- Target/Points to: another weird random-looking value Blogger gives you
Save.
Now wait at least an hour if you can. (If you’re like me, you’ll wait 6 minutes, try again, then act offended that the internet didn’t rearrange itself instantly.)
Google notes it can take time for redirects/changes to fully kick in after setting a custom domain.
Step 3: Make the “naked domain” work (yourdomain.com without www)
This is the part people miss, then they text their friend like:
“Why does www work but the normal domain doesn’t???”
To redirect yourdomain.com → www.yourdomain.com, add four A records for the root (@). Blogger’s help docs list these IPs:
- 216.239.32.21
- 216.239.34.21
- 216.239.36.21
- 216.239.38.21
Then go back to Blogger:
- Settings → Publishing → turn on Redirect domain (so naked → www)
Step 4: Turn on HTTPS (and HTTPS redirect)
In Blogger settings, you’ll see options for HTTPS. Enable:
- HTTPS availability (may take a bit)
- HTTPS redirect (once available)
If HTTPS won’t enable, one sneaky cause is DNS settings that block certificate issuance (CAA records). Blogger specifically warns that if you use CAA records, you must allow Let’s Encrypt so Blogger can create/renew SSL.
Common Blogger “uh-oh” fixes
-
“We were unable to verify your authorization to this domain”
Usually: CNAME typo, missing security CNAME, or DNS added in the wrong place.
-
Site works only with www
Usually: missing A records + Redirect domain toggle.
-
HTTPS stuck/off
Usually: propagation not done yet, or CAA record blocking Let’s Encrypt.
How to connect a custom domain to WordPress (2026)
This section depends on which WordPress you’re using, because WordPress is basically two different worlds wearing the same hat:
- WordPress.com (hosted platform; easier, more limited)
- WordPress.org (self-hosted WordPress on Bluehost/SiteGround/WP Engine/etc.)
WordPress.com: connect your existing domain (typical beginner route)
WordPress.com’s official flow is:
- Go to your site’s dashboard
- Upgrades → Domains (or Hosting → Domains)
- Click Add new domain → Use a domain I own
- Choose Connect your domain
- Either connect automatically (if your registrar supports it) or update nameservers manually
If you do the manual method, WordPress.com provides nameservers. Their support page lists:
Then you verify the connection inside WordPress.com. They also mention DNS can take up to 72 hours to fully work in some cases, which is annoying but normal.
After it turns “Active,” set it as the primary domain in Domains settings.
Self-hosted WordPress (WordPress.org): the most common approach
If you bought hosting (Bluehost, SiteGround, etc.), you’ll typically connect your domain in one of two ways:
Option A: Change nameservers (simplest)
- Your host gives you nameservers (like
ns1.yourhost.comandns2.yourhost.com) - You paste those into your domain registrar
- Your host now controls DNS
This is usually the least error-prone.
Option B: Keep nameservers, edit DNS records (more control)
You keep your registrar’s nameservers, then set:
- An A record for
@pointing to your hosting server IP - A CNAME for
wwwpointing to@(or whatever your host instructs)
This is great if you’re using Cloudflare, email hosting, or you just like controlling your DNS like a tiny internet goblin (respect).
Blogger vs WordPress: quick decision guide
If you’re torn, here’s the real-world version:
- Choose Blogger if you want free hosting, simple blogging, and you don’t want to manage updates/plugins.
- Choose WordPress if you want flexibility, better long-term scalability, and more control over SEO/monetization features.
Tiny personal note: Blogger is the “I just need it live” platform. WordPress is the “I might turn this into something big” platform.
What most people miss (aka the stuff that causes 90% of domain drama)
1) DNS propagation is not instant
Even when you did everything right, you might see:
- old site
- error pages
- partial loading
- working on mobile but not laptop
That’s propagation + caching. Try:
- Incognito window
- Clear cache
- Check again later
- Use a DNS checker tool (optional)
2) You need one “canonical” version
Pick one:
Then force redirects so Google doesn’t index both. (Duplicates = messy SEO.)
3) SSL isn’t optional anymore
Visitors expect HTTPS. Browsers punish HTTP. Ad networks don’t love insecure sites either.
4) Email can break when you change nameservers
If you use Google Workspace or another email provider and you switch nameservers, you must re-add MX records. Otherwise: email goes poof.
Tools & helpful gear (affiliate-ready, actually useful)
These are the things that make domain setup less painful (and yes, they’re the kind of boring purchases that quietly save your weekend).
- A decent password manager so you’re not guessing which registrar login you used in 2022: <a href="https://www.amazon.com/s?k=password+manager&tag=azadaffus-20">password manager</a>
- A cheap USB-C hub if you’re juggling laptop + phone + screenshots + your last nerve: <a href="https://www.amazon.com/s?k=usb-c+hub&tag=azadaffus-20">USB-C hub</a>
- A notebook (seriously) for writing down DNS values so you stop alt-tabbing like a maniac: <a href="https://www.amazon.com/s?k=small+notebook&tag=azadaffus-20">small notebook</a>
- Blue-light blocking glasses for the “it’s 1:12 AM and I’m still doing DNS” lifestyle: <a href="https://www.amazon.com/s?k=blue+light+blocking+glasses&tag=azadaffus-20">blue light blocking glasses</a>
Mini case story: the night I “broke” my site (and didn’t)
True story: I once changed a CNAME record, hit save, and immediately opened my site. It didn’t load. I refreshed 18 times like that would help.
Then I did what every calm, rational adult does: I opened a new tab and started googling “DNS not working I’m going to throw up.”
Thirty minutes later? Site was fine. Nothing was broken. DNS was just… being DNS.
So if your site is in that weird in-between state right now: step away, drink water, and stop touching the records unless you’re 100% sure something is wrong.
Troubleshooting decision tree (fast)
If your custom domain isn’t working:
- Does www work but root doesn’t?
- Add A records for root + enable redirect (Blogger), or fix A/CNAME (WordPress).
- Does nothing resolve?
- Nameservers wrong, DNS not saved, or you edited the wrong domain account.
- Does HTTPS not work?
- Wait longer, then check CAA records (Blogger warns about Let’s Encrypt permission).
- Does WordPress show the wrong site?
- Domain connected to a different WordPress.com site, or cached old DNS.
Ethical CTA (because you’re busy)
If you do the steps above carefully, you’ll get your custom domain connected without paying a developer tax. If you’re stuck, drop a comment with:
- platform (Blogger, WordPress.com, or self-hosted WordPress)
- your registrar (GoDaddy, Namecheap, etc.)
- what’s working vs not working (www, root, https)
And yes, include the exact error message. Screenshots save lives.
Frequently Asked Questions about How to Connect a Custom Domain to Blogger or WordPress
1) How long does it take to connect a custom domain to Blogger?
Usually 1–24 hours, but sometimes it feels instant and sometimes it tests your patience.
2) Why does my Blogger custom domain only work with www?
Because the naked/root domain needs extra setup (A records) plus the redirect toggle.
3) Do I need A records for Blogger custom domain setup?
If you want yourdomain.com to work (not just www), yes—A records are the common fix.
4) What are the two CNAME records Blogger asks for?
One is the standard www → ghs.google.com, and the other is a unique security CNAME for verification.
5) How do I connect a domain to WordPress.com without transferring it?
Use the “Connect your domain” option and either automatic setup or manual nameservers.
6) What nameservers does WordPress.com use?
WordPress.com provides its own nameservers during setup; you paste them into your registrar.
7) Should I use nameservers or DNS records for WordPress?
Nameservers are easiest for most beginners. DNS records are better if you want more control (Cloudflare, custom email, etc.).
8) Will connecting a custom domain hurt SEO?
Not if you set redirects correctly and keep one canonical version (www or non-www).
9) Why is my SSL/HTTPS not working on Blogger?
It can take time, or your DNS/CAA settings can block certificate issuance.
10) Can I use Cloudflare with Blogger or WordPress?
Yes, but it adds extra moving parts. Set it up only after the domain works normally.
11) What is “DNS propagation” and why is it so slow?
It’s the time it takes for DNS changes to spread across the internet. Slow is normal.
12) What if I changed DNS and my email stopped working?
Your MX records probably didn’t come along for the ride. Re-add them in your active DNS provider.
13) Do I need to buy hosting for Blogger?
No. Blogger hosts your site; you only pay for the domain.
14) What’s the easiest way to connect a custom domain to self-hosted WordPress?
Point nameservers to your host, then set the domain as primary in your hosting dashboard/WordPress.
15) How do I make sure both www and non-www go to the same site?
Pick one as primary, then set redirects (platform setting + DNS/host rules).