Technical Checklist for Clean Domain & DNS Migrations

Migrating a blog to a new custom domain or reconfiguring DNS infrastructure represents a high-risk operation for digital publishers. Incorrect CNAME mapping, lingering TTL cache limits, misconfigured A-records, or dropped canonical tags can cause prolonged site downtime, broken SSL handshakes, and severe search ranking loss. Executing a seamless migration requires a disciplined technical workflow that accounts for every step of the domain name system lifecycle.

This authoritative migration checklist establishes a production-tested framework for moving your Blogger site to a custom domain or transferring DNS management between registrars without sacrificing search authority. Following these systematically ordered phases ensures zero downtime, rapid DNS propagation, and complete indexing continuity across Google Search Console and analytics platforms.

1. Pre-Migration DNS Audit and TTL Minimization

Before modifying any DNS records at your domain registrar, you must conduct a thorough audit of all existing zone entries. This includes documenting TXT records for site ownership verification, SPF and DKIM entries for email routing, and existing CNAME mappings. Unexpectedly deleting these records during a migration will disrupt search console access and third-party integrations.

The crucial pre-migration step involves lowering the Time to Live (TTL) settings across all active zone records. TTL determines how long recursive DNS resolvers and internet service providers cache your domain's routing instructions. If your TTL is set to 86,400 seconds (24 hours), global resolvers will continue serving outdated IP addresses for an entire day after you save new settings.

Migration Stage Recommended TTL Setting Operational Objective Timing Threshold
Pre-Migration Audit 300 Seconds (5 Minutes) Forces global DNS resolvers to clear cached records rapidly. Execute 24 to 48 hours prior to switchover.
Active Cutover Phase 300 Seconds (5 Minutes) Allows immediate rollback if record mapping fails. Maintain during DNS record propagation.
Post-Migration Stability 86,400 Seconds (24 Hours) Reduces DNS lookup latency and server request overhead. Apply 72 hours after successful validation.

Lowering your TTL to 300 seconds 24 to 48 hours prior to cutover ensures that when you point your domain to Blogger's servers, the new DNS routing propagates globally in minutes rather than days.

2. Configuring Google A-Records and Subdomain CNAMEs

Connecting a custom root domain to Google's hosting infrastructure requires precise mapping of four apex A-records and two specific CNAME aliases. Omitting the apex A-records prevents naked domain traffic (example.com) from redirecting to your primary subdomain (www.example.com).

+-----------------------------------------------------------------+
|                GOOGLE APEX A-RECORD IP MAPPING                  |
+-----------------------------------------------------------------+
| Host Name: @ (or Blank)  ->  Type: A  ->  IP: 216.239.32.21    |
| Host Name: @ (or Blank)  ->  Type: A  ->  IP: 216.239.34.21    |
| Host Name: @ (or Blank)  ->  Type: A  ->  IP: 216.239.36.21    |
| Host Name: @ (or Blank)  ->  Type: A  ->  IP: 216.239.38.21    |
+-----------------------------------------------------------------+
Standard Google Anycast IPv4 address range required for apex domain routing on Blogger.

Next, you must add two distinct CNAME records inside your registrar control panel. The first CNAME points the www host to ghs.google.com. The second CNAME provides a unique security token pair generated directly by the Blogger Publishing panel to verify domain ownership.

<!-- Required CNAME Record Configuration Example -->
Record 1: Host: www                Target: ghs.google.com
Record 2: Host: [Unique Key Code] Target: [Unique Security Token].dv.googlehosted.com

If you encounter domain verification issues or DNS lookup failures during setup, consult our comprehensive troubleshooting guide on Help! My Custom Domain Isn't Working on Blogger (Top 5 Quick Fixes).

3. Establishing Canonical 301 Redirects and SSL Provisioning

Once your DNS records propagate, you must configure canonical redirection inside the Blogger dashboard. Navigate to Settings > Publishing and enable Redirect domain. This setting forces all traffic arriving at example.com to seamlessly forward to www.example.com via an automatic 301 permanent redirect, preserving consolidated link equity.

+-----------------------------------------------------------------+
|                 BLOGGER SETTINGS WORKFLOW PANEL                 |
+-----------------------------------------------------------------+
| 1. Dashboard -> Settings -> Publishing -> Custom Domain         |
| 2. Enter Domain Name (e.g. www.yourdomain.com) -> Save           |
| 3. Toggle "Redirect domain" Switch -> Enabled                   |
| 4. Settings -> HTTPS -> Toggle "HTTPS Availability" -> Enabled  |
| 5. Settings -> HTTPS -> Toggle "HTTPS Redirect" -> Enabled      |
+-----------------------------------------------------------------+
Blogger admin settings path for enabling domain redirection and provisioning SSL encryption.

Immediately after enabling domain redirection, activate both HTTPS Availability and HTTPS Redirect. Google will request and deploy a free Let's Encrypt SSL certificate for your custom address. Certificate provisioning typically completes within 15 to 60 minutes.

Critical Security Note: Do not disable HTTPS during a migration. Disabling SSL triggers security warning screens in web browsers and temporarily invalidates indexed HTTPS URLs in search engines.

For a detailed breakdown of secure protocol activation, review our dedicated tutorial on How to Enable HTTPS and SSL Certificates on Blogger (Free & Easy).

4. Google Search Console Verification and Property Migration

When migrating from a default .blogspot.com address to a custom domain, search engines treat the new domain as an entirely distinct website property. To maintain crawl budget and request indexing transfer, you must create a new Search Console property for the custom domain.

+-----------------------------------------------------------------+
|              SEARCH CONSOLE MIGRATION CHECKLIST                 |
+-----------------------------------------------------------------+
| 1. Add Domain Property (dns.example.com) via DNS TXT Record     |
| 2. Verify URL Prefix Property (https://www.example.com)          |
| 3. Submit XML Sitemap Index URL (https://www.example.com/sitemap.xml)|
| 4. Execute "Change of Address" Tool from Old Blogspot Property   |
+-----------------------------------------------------------------+
Step-by-step verification and property migration sequence inside Google Search Console.

Use the Change of Address tool inside the original Search Console property to notify Google of the domain move. This signals search crawlers to accelerate URL re-indexing and transfer historical ranking signals to your new destination.

Publishers should also follow our essential post-connection checklist in What to Do IMMEDIATELY After Connecting a Custom Domain to Blogger to avoid indexing delays.

5. Post-Migration Validation and Traffic Monitoring

The final phase of a domain migration involves auditing internal link structures, canonical headers, and analytics tracking scripts. When moving to a new domain, existing post permalinks remain intact on Blogger, but internal contextual links inside older articles may still point to the old URL structure.

Conduct a thorough crawl using auditing tools to identify any hardcoded internal links that require updating. Additionally, verify that Google Analytics 4 (GA4) property data streams correctly recognize your new domain name under Data Stream settings.

If your migration involves modifying individual post slugs alongside the domain update, refer to our guide on How to Change a Blogger Permalink Safely Without Losing Traffic.

Master Your Custom Domain Infrastructure

Learn how to connect custom domains to Blogger step-by-step, set up DNS records properly, and resolve common connection errors.

{getbutton} $text={Follow the Custom Domain Guide} $icon={link}$size={1}

Helpful Resources for Blogger Publishers

Explore our foundational guides and utilities as you build your publication:

  • Curated Publisher Tools: Access vetted software on our Recommended Tools & Resources page.
  • Search Domain Name Availability: Planning your next digital project? Check available .com addresses with our free Domain Checker.
  • Technical Support: Need assistance with theme or platform settings? Reach out directly via our Contact Page.

{getbutton} $text={Explore the Blogger Roadmap} $icon={link}$size={1}

K. Wise - Lead Technical Editor and Founder at BlogManual
Written by Lead Technical Editor

Lead Technical Editor & Founder, BlogManual

K. Wise is a lead technical editor and web publisher focused on advanced Blogger XML development, custom widget structuring, and Core Web Vitals performance. He shares practical blueprints and technical guides to master custom blogging platforms.

Previous Post Next Post