The Complete Small Business Website Launch Checklist: Domain, DNS, SSL, Email, and Performance

Overview

Whether you use a drag-and-drop website builder, managed website hosting, or a content management system, the launch sequence is broadly similar. First, make sure the site is complete and backed up. Next, connect the domain and verify DNS. Then confirm SSL, email, forms, analytics, mobile layouts, and performance. Finally, test the live site from the perspective of a visitor and a business owner.

Keep a simple record of your domain registrar, hosting account, DNS provider, email provider, renewal dates, and administrator logins. This information is especially useful when several people manage the website or when you later move to cloud hosting. For decisions about hosting capacity, support, backups, and migration, see How to Choose Web Hosting for a Small Business.

Before making DNS changes, decide whether the website and email will use the same provider. They do not have to. A site can be hosted in one place while business email remains with another provider, but the DNS records must be entered carefully. Treat DNS as a set of routing instructions: each record should have a clear purpose, and unnecessary records should not be changed during launch.

Checklist by scenario

New website with a new domain

• ☐ Choose a domain that is easy to say, spell, and associate with the business.
• ☐ Register the domain and confirm access to the registrar account.
• ☐ Select hosting or a website builder that supports the site’s pages, forms, media, and expected traffic.
• ☐ Build the essential pages: home, services or products, about, contact, privacy information, and any required terms.
• ☐ Add one clear primary action, such as calling, booking, requesting a quote, or purchasing.
• ☐ Connect the domain using the host’s recommended DNS method, such as nameservers or specific A, CNAME, or verification records.
• ☐ Decide whether both the root domain and the www version should work, then set one as the preferred address and redirect the other.
• ☐ Confirm that SSL is active and that the site loads over HTTPS without certificate warnings.
• ☐ Create business email addresses and test sending and receiving from an external mailbox.
• ☐ Submit a test contact, booking, or quote form and verify where the notification arrives.
• ☐ Install analytics or another measurement method only after deciding which actions matter.

Existing site moving to new hosting

• ☐ Record the current DNS records before changing anything.
• ☐ Confirm who controls the domain, hosting, email, forms, analytics, and backups.
• ☐ Create a complete backup of website files, databases, media, configuration, and email-related settings where applicable.
• ☐ Build and test the site on the new host using a temporary address or preview environment.
• ☐ Check links, images, redirects, forms, integrations, login areas, and search visibility settings.
• ☐ Lower DNS record time-to-live in advance only if the provider and migration plan call for it; do not change settings without recording the original values.
• ☐ Change the relevant DNS records during a low-risk period and monitor both the old and new environments.
• ☐ Keep the old hosting active until the new site, email, forms, and redirects have been verified.
• ☐ Review the migration again after DNS propagation has progressed. Guidance on checking propagation is available in How Long DNS Changes Take to Propagate and How to Check Status.

Launching a one-page or portfolio website

• ☐ Put the business name, location or service area, offer, and primary call to action near the top.
• ☐ Use descriptive headings so visitors can scan the page without reading every paragraph.
• ☐ Compress large images and check that project thumbnails remain clear on small screens.
• ☐ Add a contact method that works without requiring unnecessary fields.
• ☐ Check that navigation links scroll to the correct sections and that the browser back button behaves normally.
• ☐ Add a custom page title, meta description, social sharing image, and favicon if supported.
• ☐ Confirm that the site still communicates trust if JavaScript, animations, or external embeds fail to load.

Launching a site with business email

• ☐ Create the required mailboxes, aliases, or forwarding addresses before publishing the address widely.
• ☐ Add the email provider’s required DNS records exactly as supplied.
• ☐ Test messages to and from at least two unrelated email services when possible.
• ☐ Check the spam or junk folder during testing and confirm the sender name is recognizable.
• ☐ Avoid deleting existing mail records until you understand which service currently handles delivery.
• ☐ Document recovery options and ensure more than one responsible administrator can access the account.

What to double-check before going live

Domain and DNS: Confirm the domain is not expired, the correct DNS zone is being edited, and the records point to the intended website and email services. If you are unsure how to connect a domain to hosting, use the host’s exact record values rather than guessing. DNS changes can appear inconsistent while different networks update their cached information, so test from more than one connection and avoid repeated edits.

SSL and redirects: Open the site with both HTTP and HTTPS, with and without www, and check whether visitors are sent to the intended canonical address. Look for mixed-content warnings caused by images, scripts, fonts, or embeds still using HTTP. The guide SSL Certificates Explained provides additional setup context.

Content and usability: Read every page at normal zoom on a phone and desktop. Check names, addresses, opening hours, prices, service descriptions, spelling, calls to action, and legal links. Test keyboard navigation, visible focus states, text contrast, image alternatives, and whether buttons have clear labels.

Forms and notifications: Submit valid and invalid entries. Confirm required fields, confirmation messages, notification recipients, autoresponders, and spam controls. A form that appears to submit successfully but sends no notification is a launch blocker.

Speed: Test the home page and the most important landing page using a performance testing tool. Prioritize large images, unnecessary scripts, excessive fonts, slow third-party embeds, and unneeded plugins. For a practical sequence of fixes, see How to Speed Up a Slow Website.

Security and recovery: Use unique administrator passwords, enable multi-factor authentication where available, limit administrative access, update the builder or content management system, and confirm that backups can be restored. A backup that has never been tested is an assumption, not a recovery plan. Use the Website Security Checklist for Small Business Owners for a broader review.

Common mistakes

• Changing nameservers without checking email: A website connection can unintentionally interrupt mail if existing records are not copied or recreated.
• Launching with placeholder content: Sample text, broken links, unfinished pages, and missing contact details reduce confidence immediately.
• Testing only while logged in: Administrators may see cached pages or permissions that ordinary visitors cannot. Test in a private browser window and on a separate device.
• Ignoring the non-preferred domain version: Check the root domain, www version, HTTP version, and HTTPS version so visitors do not encounter duplicates or certificate errors.
• Forgetting mobile forms: A form can look correct on a desktop but be difficult to complete on a phone because of small fields, hidden buttons, or keyboard issues.
• Removing the old site too soon: During a migration, keep a rollback option until the new hosting environment and DNS behavior are confirmed.
• Measuring everything but learning nothing: Choose a small set of useful actions, such as form submissions, calls, bookings, or sales, and review those consistently.
• Assuming a builder removes all maintenance: A website builder simplifies publishing, but content, access, forms, integrations, security settings, and backups still need periodic attention.

When to revisit

Use this checklist before the initial launch, after a domain or hosting change, and whenever a major template, plugin, integration, or email provider changes. Revisit it before seasonal planning cycles, advertising campaigns, product launches, location changes, or periods when the business expects more enquiries.

Set a monthly review reminder for the following actions:

• ☐ Open the site on a phone and desktop and test the main call to action.
• ☐ Submit each important form and verify the notification path.
• ☐ Check backup status and, on a planned schedule, perform a restoration test.
• ☐ Review administrator accounts, access permissions, software updates, and multi-factor authentication.
• ☐ Look for broken links, expired services, incorrect business information, and outdated offers.
• ☐ Review meaningful analytics and investigate unusual changes in traffic or conversions.
• ☐ Run a basic speed check and address newly added images, scripts, or third-party tools.
• ☐ Confirm domain and hosting renewal details are recorded and accessible to the responsible owner.

Keep the completed checklist with the site’s technical notes. When a problem appears, record what changed, when it changed, and which provider or setting is involved. That small habit makes future launches, updates, and migrations easier to troubleshoot. For a deeper backup routine, see Website Backup and Restore Guide; for a planned move, use How to Migrate a Website to New Hosting Without Downtime.

Final action: Before publishing, assign one person to test the live site as a customer and another to verify the technical settings. Record the results, fix every launch blocker, and schedule the first monthly review before you announce the website.