Website Launch Checklist: Domain, DNS, SSL, Hosting, and Analytics Setup

Overview

Launching a website is more than publishing pages in a website builder or uploading files to cloud web hosting. A reliable launch depends on several systems working together: the domain registration, DNS records, hosting environment, security certificate, application configuration, and measurement tools. Treating these as separate checkpoints makes it easier to identify what is ready and what still needs attention.

This workflow applies to a new small business website, a site built with a website builder with hosting, a managed hosting migration, or a relaunch on a different platform. Keep a written record of the domain registrar, DNS provider, hosting account, administrator contacts, deployment steps, and recovery details. That record is useful during launch and whenever someone else needs to maintain the site later.

Before changing anything, confirm which system controls DNS. The registrar may provide DNS, or the domain may use nameservers from a separate provider. This distinction matters: adding a record in the wrong control panel will not connect the domain to the site.

Checklist by scenario

For a new website

• Define the canonical domain: Decide whether visitors should use the root domain, such as example.com, or a preferred www version. Configure the other version to redirect consistently.
• Confirm hosting readiness: Verify that the site is published to the intended cloud or managed hosting environment and that the hosting provider has supplied the required target, such as an IP address, hostname, or nameserver pair.
• Record DNS values: Copy the required A, AAAA, CNAME, MX, TXT, or other records exactly as provided. Do not remove email-related records simply because the website is moving.
• Connect the domain: Add records at the authoritative DNS provider, then check both the root domain and the preferred hostname. A DNS checker can help compare results from different locations; see Best DNS Check Tools for Website Owners and Developers.
• Enable SSL: Turn on the hosting platform's certificate process, if available, and wait for the certificate to become active. Test the HTTPS version rather than assuming that an active certificate means every page is configured correctly.
• Install analytics: Add the chosen analytics or measurement tag only after confirming the production domain. Test a visit or event in the tool's verification view, while respecting the site's applicable consent and privacy requirements.

For a site migration

• Inventory the old site: List important URLs, forms, downloads, images, integrations, subdomains, email services, and search-related settings before changing DNS.
• Build and test the new site privately: Use a staging URL, temporary hostname, or access restriction. Check navigation, forms, checkout or booking flows, embedded tools, and responsive layouts.
• Prepare redirects: Map changed URLs to their closest relevant destinations. Avoid sending every old page to the homepage, since that can make it difficult for users and systems to find the intended content.
• Lower DNS TTL ahead of time when appropriate: A shorter TTL can make a planned DNS change easier to adjust, but it does not guarantee immediate worldwide visibility. For propagation expectations and testing methods, read How Long DNS Changes Take to Propagate and How to Check Them.
• Preserve required records: Compare the old and new DNS zones, especially MX, SPF, DKIM, DMARC, verification, and third-party service records. Website migration should not unintentionally interrupt email.
• Switch during a monitored window: Make the DNS change when someone can test the site, forms, email, and key integrations. Keep the old hosting available until the new site is confirmed.

For a launch on a business or creator site

• Confirm the contact details, calls to action, opening hours, service descriptions, and legal or privacy pages are current.
• Test the site on a phone and a desktop-sized screen using more than one browser.
• Check that forms reach the intended inbox, confirmation messages work, and failure states are understandable.
• Review image sizes, page titles, descriptions, headings, internal links, and social sharing previews.
• Verify that the hosting plan can support the expected traffic and storage needs without relying on an untested scaling assumption.

What to double-check

DNS and domain ownership: Confirm the domain has not expired, the correct nameservers are active, and the records are entered in the authoritative zone. Check for conflicting records, such as an old A record alongside a new CNAME where the DNS provider does not allow both. If you need to inspect structured configuration or exported records, a JSON formatter and validator can make syntax errors easier to spot, but it does not replace DNS-specific validation.

HTTPS behavior: Test the root domain, the preferred hostname, a representative internal page, an image, and a form. Look for certificate warnings, mixed content, redirect loops, and links that still use HTTP. Confirm that HTTP redirects to the chosen HTTPS URL and that there is one clear canonical version.

Application and hosting settings: Check the production environment variables, database connection, file permissions, caching behavior, scheduled jobs, webhooks, and backup settings. Remove staging credentials and test data before launch. If scheduled tasks are part of the site, document them and review their timing with a cron expression builder such as the one covered in Cron Expression Builder Guide.

Performance and availability: Test key pages without relying only on a logged-in or cached session. Compress unnecessarily large media, confirm that important resources load, and check the site from an external network. The Page Speed Optimization Checklist provides a useful follow-up review, while uptime monitoring can help detect problems after launch.

Measurement: Confirm that analytics records the correct hostname and that internal test traffic is understood or excluded where appropriate. Test important events such as form submissions, purchases, downloads, or bookings. Do not place secrets, private tokens, or sensitive customer data in URLs or analytics fields.

Common mistakes

• Editing the wrong DNS panel: The registrar's dashboard is not always the authoritative DNS provider. Check the active nameservers first.
• Changing nameservers without copying essential records: A new DNS zone may omit email, verification, or service records. Export or document the existing zone before switching.
• Testing only one hostname: The root domain and www can behave differently. Test both, along with HTTP and HTTPS versions.
• Launching with placeholder content: Temporary text, broken links, sample form submissions, and default administrator accounts are easy to overlook in a rushed release.
• Assuming DNS is broken because one network is stale: Compare several resolvers and allow for caching. Avoid repeatedly changing records before the previous change can be observed.
• Forgetting the old site: During a migration, keep a rollback plan and document the previous DNS values, redirects, and hosting access until the new environment is stable.
• Adding analytics without verification: A tag in the source code is not proof that the intended property is receiving useful data. Test a real page view and the important conversions.

When to revisit

Run the full checklist before every new domain connection, major redesign, hosting migration, nameserver change, or platform replacement. A shorter version is appropriate before seasonal campaigns, product launches, planned traffic increases, and changes to payment, booking, or email systems.

Review the operational notes whenever a team member changes, a hosting workflow is updated, a domain or DNS provider is replaced, or a third-party integration is added. At a regular maintenance interval, confirm domain renewal details, administrator access, backups, SSL status, redirects, analytics events, forms, and uptime alerts. Also revisit the checklist when browsers, hosting tools, privacy requirements, or deployment processes change.

For the next launch, copy this final action list into a project ticket:

1. Record the authoritative DNS provider and current records.
2. Confirm hosting, staging, backup, and rollback access.
3. Test the site privately and prepare redirects.
4. Connect the domain and verify DNS from multiple networks.
5. Enable SSL and test HTTPS, redirects, forms, and key pages.
6. Install and verify analytics and important conversion events.
7. Monitor uptime, errors, traffic, and customer-facing workflows after release.
8. Save the final configuration and schedule the next review.

A documented launch process turns domain and hosting setup into a repeatable operation rather than a one-time guess. Keep the checklist with the site's technical records, update it when the workflow changes, and use it again before the next launch or migration.