ONE FOCUSED ACTION

Lower DNS TTL before migration cutover.

Domain migration SEO · HTTPS migration SEO

1 checklist items

Save for later 0

Use × to move an item here. You can restore it when you’re ready.

    Your checks and saved items stay in this browser. Nothing is submitted.

    Why this matters

    A lower TTL accelerates DNS propagation during cutover, reducing downtime.

    A STARTING-POINT EXAMPLE

    Hypothetical standard operating procedure

    Adapt this example to your site, access, tools, and change process. It is our suggested procedure, informed by the sources below.

    1. Access DNS management dashboard for old domain.
    2. Reduce TTL values for all relevant DNS records.
    3. Verify TTL change has propagated fully before cutover.
    4. Plan migration cutover after TTL change is effective.
    5. Restore TTL to normal post-migration if desired.

    Watch for

    High TTL delays DNS updates, causing inconsistent site access.

    Definition of done

    DNS TTL lowered to a short duration (e.g., 5 minutes) at least 24 hours before cutover.

    Sources & attribution

    1. Domain Migration Checklist | ChecklistLab ↗
    2. Site Migration SEO: The Complete Checklist for 2026 | DeepSEOAnalysis ↗
    3. Redirect Mapping Checklist for Site Migrations ↗

    Original checklist wording and example SOP by Best SEO Checklist, using source-grounded AI assistance. Editorial contact: Ted Kubaitis, @tedkubaitis on Teams. Check current source guidance before implementation.