A website launch is more than publishing a homepage. This 45-step website launch checklist helps you confirm that your domain, hosting, content, forms, analytics, security, accessibility, SEO, and performance are ready before visitors arrive—and gives you a practical schedule for checking the site after launch.
Overview
Use this guide as a website setup guide for a new business site, blog, portfolio, landing page, or online store. The exact tasks will vary by platform, but the order is broadly useful: establish the technical foundation, review the visitor experience, test important actions, then monitor the site after it goes live.
Keep a copy of the checklist in a project document and record the date, person responsible, and result for each item. A simple status such as “not started,” “in progress,” “passed,” or “needs attention” makes unfinished work visible. Do not treat launch as a single finish line. A new site needs a short period of close observation because real visitors, devices, traffic patterns, and search crawlers can reveal issues that a staging review misses.
If you are still choosing infrastructure, first clarify the domain and hosting difference: the domain is the address people use, while hosting provides the server space and services that deliver the website. Your provider, CMS, theme, plugins, and DNS arrangement should be documented before you begin the final checks.
What to track
1. Domain, DNS, and hosting
- Confirm that the correct domain is registered and that renewal contact details are current.
- Record where the domain is registered, where DNS is managed, and who can access each account.
- Choose the preferred version of the site, such as the www or non-www address.
- Point the domain to the correct hosting account using the provider’s required DNS records.
- Check that the main domain and any required subdomains resolve correctly.
- Confirm that the hosting plan supports the site’s CMS, storage, traffic expectations, and email needs.
- Verify that the site uses HTTPS and that the certificate covers the live domain.
- Remove temporary, duplicate, or abandoned DNS records when they are no longer needed.
- Write down the hosting support route and the process for restoring access if an account is locked.
DNS changes may not appear everywhere immediately, so check from more than one network or device when possible. Avoid changing several DNS records at once unless you have documented the original configuration.
2. Content, navigation, and design
- Replace placeholder text, sample images, default posts, and unfinished sections.
- Check the homepage title and make its purpose clear within the opening screen.
- Review the navigation on desktop and mobile, including menus, dropdowns, and the logo link.
- Test every internal link and correct links that lead to drafts, staging URLs, or missing pages.
- Create useful 404 and search-result experiences where the platform supports them.
- Confirm that the logo, colors, fonts, buttons, and spacing are consistent across key templates.
- Check that images have suitable dimensions, descriptive alternative text where appropriate, and meaningful filenames.
- Review contact, privacy, terms, cookie, shipping, refund, or other required pages for your site type and location.
- Read important pages aloud or use a second reviewer to catch unclear wording and obvious errors.
Templates should help visitors understand what to do next, not merely make the site look complete. If a page has no clear purpose or action, revise it before launch.
3. Forms, accounts, and important actions
- Submit every contact, newsletter, booking, quote, login, or checkout form with a test record.
- Confirm that submissions reach the correct inbox, CRM, spreadsheet, or database.
- Check confirmation messages, thank-you pages, autoresponders, and error messages.
- Test required fields, invalid email addresses, long entries, and accidental empty submissions.
- Verify that buttons work on touchscreens and that keyboard users can reach each field.
- Check that payment, account creation, downloads, or booking steps work in a safe test mode when available.
- Remove test submissions and confirm that customer-facing notifications do not expose private data.
4. SEO, analytics, and discoverability
- Give each important page a unique, descriptive title and a useful meta description.
- Check the page heading structure and use one clear primary heading for each main page.
- Set readable, stable URLs and redirect old URLs when content has moved.
- Review canonical settings, noindex directives, and robots.txt so important pages are not accidentally blocked.
- Generate or confirm the XML sitemap and make sure it contains the URLs you want indexed.
- Install analytics or another measurement system and test that visits and key events are recorded.
- Connect the site to the relevant search monitoring tool and submit the sitemap if appropriate.
- Preview shared links to check titles, descriptions, and social images.
These checks form a practical on-page SEO checklist. They do not guarantee rankings, but they reduce avoidable technical and editorial problems. For content workflows, tools such as a keyword extractor or text summarizer can assist research and editing, but every published page still needs human review. See our guide to AI writing and web productivity tools for content creators for related workflows.
5. Speed, security, and accessibility
- Test the homepage and important landing pages on a phone, tablet, and desktop-sized screen.
- Check layout at narrow and wide widths, including landscape orientation where relevant.
- Compress oversized images and remove unnecessary scripts, fonts, plugins, and embeds.
- Test loading and interaction on a normal mobile connection rather than only a fast office network.
- Confirm that administrator accounts use strong, unique passwords and appropriate permissions.
- Enable available backups, updates, malware protection, login protection, and activity monitoring.
- Navigate key pages with a keyboard and check focus states, labels, contrast, captions, and readable text size.
- Verify that important content is not hidden behind inaccessible pop-ups or dependent on hover alone.
- Record the current speed and error baseline so future changes can be compared.
Use the website speed optimization checklist for a deeper performance review. Performance work is not only about a score; focus on whether visitors can see content, use controls, and complete the main task without unnecessary delay.
Cadence and checkpoints
A staged schedule prevents the final review from becoming an exhausting single session.
- One to two weeks before launch: Confirm the domain, hosting, DNS plan, content inventory, backup method, analytics setup, and launch owner.
- Three to five days before launch: Freeze major design changes, complete the 45 checks, test forms, review mobile layouts, and create a rollback plan.
- Launch day: Take a final backup, publish during a period when someone can monitor the site, confirm HTTPS and DNS, submit a test form, and inspect the homepage from an independent device.
- First 24 to 48 hours: Review uptime, error logs, analytics, form delivery, search-console messages, broken links, and support questions.
- First week: Compare real device behavior with the pre-launch review. Check the most visited pages, exit points, conversions, and unexpected traffic.
- Monthly: Apply available CMS, theme, plugin, and security updates after checking backups. Review forms, links, storage, uptime, speed, and account access.
- Quarterly: Revisit navigation, top landing pages, search visibility, accessibility, conversion paths, hosting capacity, and the relevance of key content.
Sites with frequent publishing, ecommerce activity, memberships, or multiple administrators may need more frequent checks. Keep a change log so a sudden issue can be connected to a recent update rather than guessed at.
How to interpret changes
Not every change requires an urgent response. Start by separating technical failures from normal variation. A broken form, expired certificate, widespread error, or missing page is an immediate operational issue. A gradual change in traffic, engagement, or conversions needs investigation before you alter the site.
When a metric changes, ask four questions:
- What changed? Identify the page, device type, traffic source, date range, and user action involved.
- When did it change? Compare the timing with a deployment, plugin update, DNS edit, campaign, content change, or hosting incident.
- Can it be reproduced? Test the page yourself and, where possible, use another browser, device, network, or account.
- What is the smallest safe fix? Correct the specific issue, document the change, and monitor before making unrelated edits.
For example, a drop in form submissions might result from a broken notification address, a confusing field, slower mobile loading, lower-quality traffic, or a seasonal shift. Check delivery logs and complete the form yourself before rewriting the whole page. If speed worsens after adding a feature, compare the page with the previous baseline and test whether removing or replacing that feature resolves the issue.
Use backups as a recovery tool, not as a substitute for testing. A backup is useful only if it exists, is recent enough for your needs, and can be restored. Periodically confirm where backups are stored and who can perform a restoration.
When to revisit
Return to this checklist before every major redesign, domain move, hosting change, CMS migration, theme replacement, analytics change, or new form integration. Revisit it after a security incident, unexplained traffic change, repeated downtime, or a noticeable drop in completed actions.
For routine maintenance, schedule a short monthly review and a deeper quarterly review. At minimum, the monthly pass should cover updates, backups, forms, links, certificates, uptime, and recent errors. The quarterly pass should cover mobile usability, accessibility, SEO settings, performance, account permissions, content accuracy, and whether the current hosting setup still matches the site’s needs.
To finish your launch plan, copy the 45 items into a tracker, assign an owner to every unfinished task, and set a launch decision date. Do not publish while a critical item—such as domain routing, HTTPS, form delivery, backup access, or administrator security—remains unresolved. Once the site is live, keep the tracker as a maintenance record rather than abandoning it. Related planning resources include the complete website launch checklist, guidance on domain registrars and DNS tools, and comparisons of shared, VPS, and cloud hosting.