How to Set Up a Custom Domain on Blogger with Free HTTPS & DNS in 2026

Setting up a branded custom domain on Google Blogger (Blogspot) is a crucial step toward establishing online credibility, maximizing organic search rankings, and getting approved for Google AdSense and premium programmatic ad networks. While Blogger provides free subdomains (yourname.blogspot.com), professional publishing demands your own domain (e.g., drillseo.com). In 2026, Google provides automated SSL certificate provisioning and HTTPS redirection natively for all custom Blogger domains.

In this comprehensive, step-by-step master guide, you will learn how to configure your DNS CNAME and A records, link your custom domain inside Blogger settings, enable free Google SSL certificates, force automatic HTTPS redirection, and optionally integrate Cloudflare for enterprise-grade CDN caching.

Prerequisites: What You Need Before You Start

• An active Blogger blog on blogspot.com.
• A registered custom domain from any standard domain registrar (Namecheap, GoDaddy, Google Domains / Squarespace, Porkbun, or Hostinger).
• Administrative access to your registrar's DNS Management dashboard.

Step 1: Initiate Custom Domain Setup in Blogger Dashboard

1. Log in to your Blogger Dashboard at blogger.com.
2. In the left sidebar menu, click Settings.
3. Scroll down to the Publishing section and click Custom domain.
4. Enter your full domain name including the www subdomain (e.g., www.yourdomain.com). Blogger requires a third-level domain (like www) to anchor CNAME records.
5. Click Save. Blogger will intentionally display an error message containing two unique CNAME verification records:
   • CNAME 1 (Host: www → Destination: ghs.google.com): Points web traffic to Google's load balancers.
   • CNAME 2 (Unique Verification Pair): Unique string of letters/numbers generated exclusively for your Google account (e.g., Host: abcdef123456 → Destination: gv-xyz987.dv.googlehosted.com).

Step 2: Add Blogger CNAME Records in Your Domain Registrar

Leave the Blogger settings tab open. Open a new browser tab and navigate to your domain registrar's DNS management console (Advanced DNS / DNS Records):

Step 3: Add Google's 4 Official IPv4 Anycast A Records

To ensure visitors who type your root naked domain (yourdomain.com without www) successfully reach your website, you must point your root domain (@) to Google's four official Anycast IP addresses:

Step 4: Save Custom Domain & Enable Naked Domain Redirection

1. Wait 5 to 15 minutes for your DNS records to propagate across global nameservers.
2. Return to your Blogger Settings > Publishing > Custom domain window and click Save. Blogger will now successfully verify domain ownership.
3. Directly below the Custom domain field, enable the toggle: Redirect domain (Redirect yourdomain.com to www.yourdomain.com). This guarantees that all non-www traffic automatically redirects to your primary canonical www address with a clean 301 header.

Step 5: Enable Free Google HTTPS Availability & HTTPS Redirect

Google automatically provisions a free, managed TLS/SSL certificate through Let's Encrypt for all custom Blogger domains. Follow these steps to activate it:

1. In Blogger Settings, scroll down to the HTTPS section.
2. Toggle HTTPS availability to Yes / On.
3. Blogger will initiate SSL certificate issuance. The status will initially read "HTTPS Status: Processing" or "Pending". This typically takes between 15 minutes and 2 hours.
4. Once the certificate is issued (status switches to "Available"), toggle the second switch: HTTPS redirect to Yes / On.
5. All incoming HTTP requests will now automatically forward to secure HTTPS, satisfying Google's search algorithms and modern browser security criteria.

Optional Power-Up: Adding Cloudflare CDN to Blogger

While Blogger handles hosting directly on Google infrastructure, adding Cloudflare provides significant extra advantages: Edge caching for static images, DDoS mitigation, and faster global TTFB:

• Point your registrar nameservers to Cloudflare.
• In Cloudflare DNS, set the ghs.google.com CNAME and the 4 A records to DNS Only (Grey Cloud) during initial SSL verification.
• Once Google's SSL status confirms "Available", switch Cloudflare proxying to Proxied (Orange Cloud).
• Ensure your Cloudflare SSL/TLS encryption mode is set to Full (Strict).

Troubleshooting Common Blogger DNS & SSL Errors

• "We have not been able to verify your authority to this domain": This occurs if DNS propagation is still in progress or if the unique verification CNAME was typed with an extra domain suffix. Check DNS propagation at whatsmydns.net before re-saving.
• "HTTPS Status: Failed": If SSL issuance fails, verify that your 4 A records are exactly matching Google's IPs and that CAA records in your registrar are not blocking Let's Encrypt or Google Trust Services.
• Mixed Content Warnings: If your browser shows an insecure icon after enabling HTTPS, inspect your Blogger theme HTML and replace any old hardcoded http:// image or script links with https://.