Blogger Custom Domain Setup: Namecheap, Cloudflare, GoDaddy
Custom domain mapping on Blogger requires specific DNS records to route traffic through Google's infrastructure while maintaining SSL termination. The process involves configuring four CNAME records and two A records at your registrar or DNS provider. Failure to configure these records in the exact order specified by Google results in propagation delays or certificate validation errors.
Google manages SSL certificates automatically once DNS propagation completes. Users do not upload certificates manually. The domain verification process relies entirely on the presence of the correct CNAME targets pointing to ghs.google.com and the unique verification string provided in the Blogger dashboard.
DNS Record Requirements
Blogger requires two distinct types of DNS entries to function correctly. The A records direct the root domain (naked domain) to Google's IP addresses. The CNAME records handle the www subdomain and domain verification.
Root Domain A Records
Configure four A records for the host @ or leave the host field blank depending on your provider. These IPs belong to Google's global load balancers.
| Type | Host | Value | TTL |
|---|---|---|---|
| A | @ | 216.239.32.21 | 3600 |
| A | @ | 216.239.34.21 | 3600 |
| A | @ | 216.239.36.21 | 3600 |
| A | @ | 216.239.38.21 | 3600 |
WWW and Verification CNAME Records
Add two CNAME records. The first maps www to Google's hosting service. The second verifies domain ownership using a unique string generated in your Blogger settings.
| Type | Host | Value | TTL |
|---|---|---|---|
| CNAME | www | ghs.google.com | 3600 |
| CNAME | [Unique String] | [Unique String].verify.google.com | 3600 |
Retrieve the unique verification strings from the Blogger dashboard under Settings > Custom Domain. Enter your domain name and save. The interface displays two missing records if verification fails.
Namecheap Configuration Workflow
Namecheap uses a simplified Advanced DNS interface. Navigate to Domain List > Manage > Advanced DNS. Remove any existing URL Redirect records for the root domain or www subdomain before adding new records.
Step 1: Add A Records
Select "Add New Record" and choose "A Record". Enter @ in the Host field. Input the first Google IP address. Set TTL to Automatic or 3600. Repeat this process three more times for the remaining IP addresses.
Step 2: Add CNAME Records
Add a CNAME record with Host www and Value ghs.google.com. Add the second CNAME record using the verification string provided by Blogger. Ensure no trailing dots exist in the value field unless the interface requires them.
Step 3: Redirect Settings
Namecheap often defaults to URL Redirects for domains. Ensure no redirect rules conflict with the A records. The A records must resolve directly to Google IPs, not to a parking page.
Cloudflare Configuration Workflow
Cloudflare acts as a proxy by default. Blogger requires DNS-only mode for the initial setup to validate SSL certificates correctly. Proxying the domain through Cloudflare's orange cloud causes SSL handshake failures during the verification phase.
Step 1: Disable Proxy
Add the four A records and two CNAME records in the Cloudflare DNS dashboard. Click the orange cloud icon next to each record to turn it gray. This sets the proxy status to "DNS Only".
Step 2: SSL/TLS Settings
Navigate to SSL/TLS > Overview. Set the encryption mode to "Full" or "Full (Strict)" only after Blogger confirms the domain. During setup, keep it on "Flexible" or disable Cloudflare SSL temporarily to prevent redirect loops.
Step 3: Page Rules for Redirects
Cloudflare does not automatically redirect root domains to www like Blogger does internally when proxied. Create a Page Rule if you intend to keep the proxy active later. Use the pattern http://example.com/* and setting "Forwarding URL" to https://www.example.com/$1 with status code 301.
Re-enable the orange cloud proxy only after the Blogger dashboard shows "Verified" and the HTTPS toggle is active. Premature proxying interrupts the Google-managed certificate issuance.
GoDaddy Configuration Workflow
GoDaddy's DNS management interface separates "Forwarding" from "DNS Records". Users often confuse these sections. Custom domain setup requires editing DNS Records, not Domain Forwarding.
Step 1: Access DNS Management
Go to My Products > Domain > DNS. Scroll to the "Records" section. Delete any existing A records for @ or CNAME records for www that point to GoDaddy parking pages.
Step 2: Input Records
Click "Add" to create new records. Select Type "A". Enter @ for Host and the Google IP for Value. Repeat for all four IPs. Add the CNAME records similarly. GoDaddy may append .domaincontrol.com automatically if not careful; ensure the value is exactly ghs.google.com.
Step 3: Propagation Check
GoDaddy updates can take up to 48 hours but usually complete within 30 minutes. Use the Blogger "Save" button immediately after adding records. If it fails, wait and retry without changing the DNS records again.
Troubleshooting Common Errors
Error: "We have not been able to verify your authority..."
This indicates the verification CNAME record is missing or incorrect. Check the Host field in your DNS provider. It must match the random string exactly. Ensure the Value ends with .verify.google.com. Some providers add a trailing dot automatically; others do not. Test with dig or nslookup.
nslookup -type=CNAME [unique-string].yourdomain.com
Error: "The domain is already in use"
The domain is linked to another Blogger blog or a Google Workspace account. Remove the domain from the previous blog's Settings > Custom Domain section. If the previous blog is deleted, contact Google Support to release the binding.
Error: SSL Certificate Pending
Google issues certificates after DNS propagation. This process takes 15 minutes to 24 hours. Do not toggle the "HTTPS Availability" switch repeatedly. Wait for the status to change from "Pending" to "Available".
Verify DNS propagation using global lookup tools before contacting support. Inconsistent results across regions indicate TTL caching issues at the ISP level.
HTTPS Enforcement and Redirects
Blogger handles HTTPS redirection internally once the domain is verified. Enable the "HTTPS Availability" toggle in Settings. Wait for the certificate to issue. Then enable "HTTPS Redirect".
This setting forces all http:// traffic to https://. It also redirects the root domain to the www subdomain automatically. This behavior is hardcoded into Blogger's infrastructure and cannot be disabled.
Users utilizing Cloudflare must ensure their SSL settings do not conflict with Blogger's redirect. A "Flexible" SSL mode on Cloudflare combined with Blogger's "HTTPS Redirect" creates an infinite redirect loop. Set Cloudflare SSL to "Full" to resolve this.
Verification and Testing
Confirm setup completion by visiting the custom domain in an incognito window. The address bar must show the padlock icon. Inspect the certificate details to ensure it is issued by Google Trust Services.
Run a DNS lookup to confirm the four A records resolve correctly. Check that the CNAME for www resolves to ghs.google.com. Use command line tools for precise validation.
dig A yourdomain.com dig CNAME www.yourdomain.com
Monitor the Blogger dashboard for any "Invalid" status markers. If records appear correct but verification fails, clear the local DNS cache or wait for global propagation.
Related Implementation Tools
Validate your DNS and SEO configuration after setup to ensure no metadata leaks or structural errors exist. Use the Blogger Schema Validator to generate correct structured data for your new domain. Audit your template for mobile compatibility using the Blogger Template SEO Auditor.
For deeper technical analysis of your site's performance post-migration, refer to our guide on fixing LCP issues which often arise during domain transitions due to resource loading changes.