Website Launch Checklist: Everything to Do Before and After Publishing a New Site

Overview

A new site can appear ready while important systems remain untested. A domain may point to the wrong server, a contact form may fail silently, or search engines may be blocked by a temporary setting used during development. Treating launch as a series of checkpoints reduces these avoidable problems and gives you a record to revisit later.

The process applies to a small business website, WordPress installation, online portfolio, landing page, or ecommerce project. The exact controls depend on your platform and web hosting plan, but the underlying checks are similar. First confirm that visitors can reach the correct site securely. Then test the experience, confirm measurement and recovery systems, and monitor the site after publication.

Keep a simple launch record containing the domain registrar, hosting account, DNS provider, renewal dates, administrator contacts, analytics property, backup location, and the date of each check. This information is especially useful when several people manage the business website setup or when a future website migration is required.

What to track

Domain, DNS, and hosting

• Confirm that the intended domain is registered to the correct owner and that renewal notifications go to an active address.
• Check the DNS records used to connect the domain to hosting. Review the A, AAAA, CNAME, MX, and TXT records that your website and email services require.
• Verify both the preferred domain version and its alternate, such as the www and non-www versions. Redirect the version you do not use rather than leaving two separate site addresses.
• Confirm that the hosting account has sufficient storage, processing capacity, and database access for the current site. A low-cost or entry-level plan may be appropriate for a small launch, but it should still provide a clear path to a scalable hosting plan if traffic or functionality grows.
• Record the hosting control panel address, support contact method, and account recovery details.

If you are unsure how to connect a domain to hosting, use the provider’s documented nameservers or DNS instructions and make one deliberate change at a time. Keep a copy of the previous records before editing them. Email records deserve particular care: a website launch should not accidentally interrupt business email. The domain connection guide and business email setup guide provide useful reference points.

Security and reliability

• Open the site using HTTPS and confirm that the SSL certificate is valid for every domain version you intend to use.
• Redirect HTTP requests to HTTPS where appropriate, then check for mixed content such as images, scripts, or stylesheets still loading over HTTP.
• Remove unused administrator accounts, change temporary passwords, and enable available multifactor authentication.
• Confirm that automated backups include the files and database. Store at least one copy separately from the live hosting account and test that a restore is possible.
• Set up website uptime monitoring and decide who receives an alert when the site becomes unavailable.

SSL protects connections, but it does not replace updates, strong account security, or backups. For more detail, review the SSL certificate guide, the guide to fixing mixed content errors, and the website backup checklist.

Content, usability, and conversion paths

• Check the homepage, navigation, logo link, footer links, privacy information, and every important call to action.
• Submit each form using a real test address. Confirm validation, confirmation messages, notification delivery, and the storage or handoff of submissions.
• Test phone numbers, email links, maps, downloads, account creation, checkout, and any booking or search functions.
• Review the site on a phone, tablet, and desktop-sized screen. Look for clipped text, difficult-to-tap controls, horizontal scrolling, and menus that do not open.
• Proofread titles, headings, prices or service descriptions, contact details, image captions, and legal or policy pages.

SEO and measurement

Before launch, give each important page a clear title, descriptive heading structure, useful meta description, readable URL, and one primary purpose. Check that internal links work and that images have meaningful alternative text when the image conveys information.

Confirm that the production site is not carrying a development-only noindex directive or restrictive robots.txt rule. A robots.txt file and a meta robots tag serve different purposes, so check both rather than relying on one setting. The guide to robots.txt versus meta robots explains where each belongs.

Install or verify analytics and search performance measurement before publishing. Test that a page view, form submission, purchase, or other important event is recorded once—not repeatedly or under the wrong property. Save the test date and expected result so a later review can identify changes.

Cadence and checkpoints

Use three checkpoints rather than treating launch as a single moment.

Before publishing

Run the full checklist on a staging or preview version. Confirm that placeholder text, sample accounts, test orders, debug messages, and temporary access restrictions will not reach visitors. Check the final domain, canonical URLs, redirects, forms, analytics, and backup configuration.

On launch day

Open the live site in a private browser window and test the main visitor path from the homepage to the primary conversion. Check the site from a mobile connection as well as the network used during development. Submit a form, inspect the confirmation, verify the notification, and check the analytics event. Review the homepage source or SEO controls if search visibility is important.

Monitor server responses during the first hours. A spike in 4xx or 5xx responses can reveal a broken redirect, missing asset, permission problem, or application error. Use the HTTP status code guide to prioritize problems.

After launch

Check the site daily during the first few days, then move to a weekly or monthly review depending on how often the site changes and how important availability is. Review uptime alerts, backup results, software updates, form delivery, analytics trends, search indexing, and page speed. A quarterly review should also include domain renewal information, DNS records, user access, hosting resource usage, and the recovery process.

How to interpret changes

Not every change indicates a serious fault. Interpret measurements alongside recent edits, campaigns, seasonality, and traffic sources.

• Traffic falls but uptime is normal: Check analytics tracking, search indexing controls, redirects, rankings, campaign tags, and recent content changes before assuming a hosting problem.
• Forms stop producing leads: Submit a controlled test. If the form appears to work but no message arrives, inspect notification settings, spam handling, third-party integrations, and mailbox capacity.
• Pages become slower: Compare the affected templates and recent changes. Large images, new scripts, unoptimized plugins, database growth, or hosting resource limits can all contribute.
• Uptime alerts increase: Note the time, duration, affected URLs, and response code. Repeated short failures may require hosting support; an isolated alert may be a monitoring or network issue.
• Search pages are missing: Check indexability, canonical tags, sitemap availability, redirects, and whether the page contains enough useful information to deserve inclusion. Avoid making several SEO changes at once, since that makes the result harder to understand.

Keep a change log with the date, adjustment, reason, and observed result. This simple record prevents repeated troubleshooting and helps separate a technical incident from a normal performance fluctuation.

When to revisit

Return to this checklist on a monthly or quarterly cadence, and immediately after any change that affects the site’s infrastructure or visitor journey. Revisit it after a domain transfer, DNS change, hosting upgrade, website migration, redesign, WordPress update, new plugin installation, analytics change, or SSL renewal.

At minimum, schedule a monthly operational review for backups, uptime, forms, software updates, user access, and renewal dates. Use a quarterly review for mobile testing, broken links, page speed, search visibility, content accuracy, DNS records, and hosting capacity. After a major launch or migration, shorten the interval until the site has completed several stable checks.

To make the next review practical, assign each check to a person, record the expected result, and mark unresolved items with a priority. Start with issues that block visitors, expose accounts, interrupt email, lose leads, or prevent recovery. Then address performance and content improvements. A repeatable review turns an instant website launch into a maintained, dependable site rather than a one-time publishing event.